Hi, I’m using Raspian and docker installation of Home Assistant Version 0.107.7. Ever since installing it, my Lovelace panel displays UTC time.

In my configuration file I’ve been using command line to get the date as a sensor:

sensor:
  - platform: command_line
    name: get_time_date
    command: date "+ %I:%M %p";echo;date "+%b-%d-%Y"

It was working great. If I login to the raspberry and type the same command, it returns the correct time and date.

I’ve been looking for what the issue is and if others have had it but come up empty. So sorry if this is documented somewhere and I missed it, but it’s driving me crazy trying to fix it.

All suggestions welcome.

1 post - 1 participant

Read full topic

RF worked flawlessly till I upgraded to 0.115.2 (RM3Pro)
Now I can only randomly can send a couple of codes, usually when i delete the integration and re-connect it…
IR still works as expected.
I was not able to find any reference in the log.

Anyone with a similar situation?

Below the service call and my configuration

remote.send_command

entity_id: remote.rm_cucina
command: b64:sgXXXXXXXXXXXXXXXXXXXAAA

arch	x86_64
dev	false
docker	true
hassio	false
installation_type	Home Assistant Container
os_name	Linux
os_version	5.4.0-47-generic
python_version	3.8.5
version	0.115.2
virtualenv	false

1 post - 1 participant

Read full topic

1. It looks like my Fibaro Roller Shitter thinks that the blinds are closed when they are opened and vice versa. I reversed the Q1 and S1 connections in the config but I don’t know how to reverse the state.

2. I’ve read some posts on this forum and I know that the device doesn’t refresh the most recent state properly. Is there recommended work around to fix this issue temporarily?

1 post - 1 participant

Read full topic

Since updating to the latest release I’m not seeing any entries in Logbook or History.

I also have a message saying:
The following integrations could not be set up:

• automation.

All automations are running fine.

I am using MariaDB.

I have recorder: in my configuration.yaml file.

MariaDB shows a warning:
2020-09-21 18:01:21 31 [Warning] Access denied for user ‘homeassistant’@'172.30.32.1

My HA resides at 10.0.1.210:8123 running in a VM.

Prior to the update all was well.

I’m a bit stumped!

1 post - 1 participant

Read full topic

Since migrating to 0.115 I am having problems with Kodi controls. Integrations has successfully detected my Kodi device but HASS is doing some very weird things.

If I restart HASS I get the following error in the log…

Log Details (ERROR)
Logger: homeassistant.components.kodi.config_flow
Source: components/kodi/config_flow.py:51
Integration: Kodi (documentation, issues)
First occurred: 18:16:31 (1 occurrences)
Last logged: 18:16:31

Cannot connect to Kodi
Traceback (most recent call last):
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 936, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs) # type: ignore # noqa
File “/usr/local/lib/python3.8/asyncio/base_events.py”, line 1025, in create_connection
raise exceptions[0]
File “/usr/local/lib/python3.8/asyncio/base_events.py”, line 1010, in create_connection
sock = await self._connect_sock(
File “/usr/local/lib/python3.8/asyncio/base_events.py”, line 924, in _connect_sock
await self.sock_connect(sock, address)
File “/usr/local/lib/python3.8/asyncio/selector_events.py”, line 494, in sock_connect
return await fut
File “/usr/local/lib/python3.8/asyncio/selector_events.py”, line 526, in _sock_connect_cb
raise OSError(err, f’Connect call failed {address}’)
ConnectionRefusedError: [Errno 111] Connect call failed (‘192.168.1.115’, 8080)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/local/lib/python3.8/site-packages/jsonrpc_async/jsonrpc.py”, line 32, in send_message
response = await self._request(data=message.serialize())
File “/usr/local/lib/python3.8/site-packages/aiohttp/client.py”, line 480, in _request
conn = await self._connector.connect(
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 523, in connect
proto = await self._create_connection(req, traces, timeout)
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 858, in _create_connection
_, proto = await self._create_direct_connection(
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 1004, in _create_direct_connection
raise last_exc
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 980, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 943, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.115:8080 ssl:default [Connect call failed (‘192.168.1.115’, 8080)]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/local/lib/python3.8/site-packages/pykodi/kodi.py”, line 161, in ping
response = await self._server.JSONRPC.Ping()
File “/usr/local/lib/python3.8/site-packages/jsonrpc_async/jsonrpc.py”, line 34, in send_message
raise TransportError(‘Transport Error’, message, exc)
jsonrpc_base.jsonrpc.TransportError: (“Error calling method ‘JSONRPC.Ping’: Transport Error”, ClientConnectorError(ConnectionKey(host=‘192.168.1.115’, port=8080, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=269936207), ConnectionRefusedError(111, “Connect call failed (‘192.168.1.115’, 8080)”)))

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/kodi/config_flow.py”, line 49, in validate_http
await kodi.ping()
File “/usr/local/lib/python3.8/site-packages/pykodi/kodi.py”, line 167, in ping
raise CannotConnectError from error
pykodi.kodi.CannotConnectError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/kodi/config_flow.py”, line 220, in async_step_import
await validate_http(self.hass, data)
File “/usr/src/homeassistant/homeassistant/components/kodi/config_flow.py”, line 51, in validate_http
raise CannotConnect from error
homeassistant.components.kodi.config_flow.CannotConnect
Home Assistant has started!

OK so the port on Kodi @ 192.168.1.115 is actually 9090 I can prove this because I can connect to Kodi OK using browser to http://192.168.1.115:9090;

Lets change it (on kodi) to 8080 (I can now connect to kodi OK using browser to http://192.168.1.115:8080)

Do nothing to HASS except restart.

I now get the following error in the log (having never touched HASS Settings at all):

Logger: homeassistant.components.kodi.config_flow
Source: components/kodi/config_flow.py:82
Integration: Kodi (documentation, issues)
First occurred: 18:24:01 (1 occurrences)
Last logged: 18:24:01

Unexpected exception
Traceback (most recent call last):
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 936, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs) # type: ignore # noqa
File “/usr/local/lib/python3.8/asyncio/base_events.py”, line 1025, in create_connection
raise exceptions[0]
File “/usr/local/lib/python3.8/asyncio/base_events.py”, line 1010, in create_connection
sock = await self._connect_sock(
File “/usr/local/lib/python3.8/asyncio/base_events.py”, line 924, in _connect_sock
await self.sock_connect(sock, address)
File “/usr/local/lib/python3.8/asyncio/selector_events.py”, line 494, in sock_connect
return await fut
File “/usr/local/lib/python3.8/asyncio/selector_events.py”, line 526, in _sock_connect_cb
raise OSError(err, f’Connect call failed {address}’)
ConnectionRefusedError: [Errno 111] Connect call failed (‘192.168.1.115’, 9090)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/local/lib/python3.8/site-packages/jsonrpc_websocket/jsonrpc.py”, line 56, in ws_connect
self._client = await self.session.ws_connect(
File “/usr/local/lib/python3.8/site-packages/aiohttp/client.py”, line 721, in _ws_connect
resp = await self.request(method, url,
File “/usr/local/lib/python3.8/site-packages/aiohttp/client.py”, line 480, in _request
conn = await self._connector.connect(
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 523, in connect
proto = await self._create_connection(req, traces, timeout)
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 858, in _create_connection
_, proto = await self._create_direct_connection(
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 1004, in _create_direct_connection
raise last_exc
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 980, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
File “/usr/local/lib/python3.8/site-packages/aiohttp/connector.py”, line 943, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.115:9090 ssl:default [Connect call failed (‘192.168.1.115’, 9090)]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/local/lib/python3.8/site-packages/pykodi/kodi.py”, line 135, in connect
await self._ws_server.ws_connect()
File “/usr/local/lib/python3.8/site-packages/jsonrpc_websocket/jsonrpc.py”, line 59, in ws_connect
raise TransportError(‘Error connecting to server’, None, exc)
jsonrpc_base.jsonrpc.TransportError: (‘Error connecting to server’, ClientConnectorError(ConnectionKey(host=‘192.168.1.115’, port=9090, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=1902911753), ConnectionRefusedError(111, “Connect call failed (‘192.168.1.115’, 9090)”)))

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/kodi/config_flow.py”, line 75, in validate_ws
await kwc.connect()
File “/usr/local/lib/python3.8/site-packages/pykodi/kodi.py”, line 137, in connect
raise CannotConnectError from error
pykodi.kodi.CannotConnectError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/kodi/config_flow.py”, line 221, in async_step_import
await validate_ws(self.hass, data)
File “/usr/src/homeassistant/homeassistant/components/kodi/config_flow.py”, line 82, in validate_ws
raise WSCannotConnect from error
homeassistant.components.kodi.config_flow.WSCannotConnect

Any help on this gratefully received!

1 post - 1 participant

Read full topic

Since IFTTT is going to a subscription model, I am looking at moving to Home Assistant and I was just wondering what is currently possible with Wyze cams. I currently have IFTTT applets set up to enable/disable motion detection on several cameras throughout the house based on location triggers from Life360. Is this at all possible with Home Assistant? Thanks!

1 post - 1 participant

Read full topic

Hi, I started using InfluxDB 1.8.2 and was very pleased and impressed with the performance, but also the usability of Chronograf and Kapacitor, but especially Telegraf that allows to easily integrate all kinds of metrics (this really pulled me over towards InfluxDB).

Then I learned about the upcoming 2.0 version, where SQL is replaced with Flux and queries cannot be ported over - need to be rewritten. I believe it is a huge strategic mistake (they should have added Flux as a new option), and I intend to stay on InfluxDB 1.x.

Any suggestions for an alternate time series database? As far as I can see Telegraf supports other outputs, so could go with Telegraf + PostgreSQL (or a different time series db).

Now for the questions:

1. Anyone used InfluxDB 2.0? How is the experience?
2. Any suggestions regarding an alternative to InfluxDB, but also Telegraf.

1 post - 1 participant

Read full topic

Sometimes after 0.114, I’m getting this message.

The following integrations and platforms could not be set up:
    automation
Please check your config.

The only reference i can see in the log is this

Logger: homeassistant.config
Source: config.py:413
First occurred: 8:03:17 AM (88 occurrences)
Last logged: 7:37:54 PM
Invalid config for [automation]: (See /config/configuration.yaml, line 15). 

This is a snippet of my configuration.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
config:
api:
wake_on_lan:
logbook:
breaking_changes:
owntracks:
mobile_app:

scene: !include scenes.yaml
sensor: !include sensors.yaml
binary_sensor: !include binary-sensors.yaml
light: !include lights.yaml
automation: !include automations.yaml
switch: !include switches.yaml

I’ve tried including the automations directly into the configuration.yaml file and then hoping to see more detailed where the error is, but i still get the same error.

3 posts - 3 participants

Read full topic

Anyone knows how to remove this padding on left and right on mobile?
Its there since 0.115

Screenshot_20200921-2058341080×2376 622 KB

1 post - 1 participant

Read full topic

With the very poor built-in light card, I’ve relied on custom light card for a while for all my wled devices.
But the project has stopped, so what should we use now?
Or is somebody picking up the code, or could it be integrated instead of the standard light card?

1 post - 1 participant

Read full topic

Hi All,

Is there something to do about the start of week from Sunday to Monday?
Lots of countries have Monday as start day of the week…

To bad ljmerza/calendar-card as been archived so it won’t be maintain anymore…

1 post - 1 participant

Read full topic

I have an input_boolean on my dashboard which limits sounds being played through my 3.5mm jack.
In every automation I have written which uses TTS (for example) I perform a check to see if this input is on or off.
Is it possible to create a service based on the original TTS which perform this check for all calls, without having to perform checks in every single automation?

Thanks!

1 post - 1 participant

Read full topic

Did some quick Googling and couldn’t find anything. Please let me know if addressed somewhere that I missed.

Is there a specific folder images / etc. should be stored in order to not be publicly available? HTTP Documentation specifically calls out that:

Files served from the www folder ( /local/ url), aren’t protected by the Home Assistant authentication. Files stored in this folder, if the URL is known, can be accessed by anybody without authentication.

but doesn’t mention other ways to serve files that does require authentication.

Am I completely misunderstanding the basics?

1 post - 1 participant

Read full topic

I have a webcam pointed at my gate. I also have a sensor that triggers when a car passes the gate. I have HA detecting the sensor, and it sends me an SMS message (via SMTP to my phone number) whenever the sensor is triggered.

What I want is to capture an image from the webcam and include it in the message when this happens. I have a URL which will fetch and return a single image from the camera, but if I use that in the “images” section of the automation, it doesn’t work. (I tested it with a static image file and it does work with that, so I know my syntax is ok.)

Is there a way to include a real-time snapshot from the webcam with an SMTP automation?

1 post - 1 participant

Read full topic

I have the google assistant relay up and running. I can use the sandbox function and successfully send a broadcast. I have the test broadcast in the HASSIO UI I can send a test broadcast from successfully. For the life of me I cannot get the automation to send a broadcast and was wondering how I need to set it up in the automation. This is how I currently have it configured. Any guidance would be appreciated I have been looking for an answer for weeks now without any success.

1 post - 1 participant

Read full topic

Using 0.115.1, Calling media_player.play_media to any Plex target is resulting in a URL connection error.

It looks like it’s trying to connect to a link-local address instead of the IP of the machine that Plex is running on (or app.plex.tv)

Failed to call service media_player/play_media. HTTPConnectionPool(host='169.254.97.70', port=32400): 
Max retries exceeded with url: /player/playback/playMedia?address=10-0-1-220.REDACTED.plex.direct&commandID=3&containerKey=%2FplayQueues%2F9852%3Fwindow%3D100%26own%3D1&key=%2Fplaylists%2F61807&machineIdentifier=REDACTED&offset=0&port=32400&token=REDACTED&type=music 
(Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0xa2ac8d90>: Failed to establish a new connection: [Errno 113] Host is unreachable'))

Has anyone encountered this? Everything is working fine with the plex entity sensors etc, so I am certain that the API connection otherwise is working correctly.

1 post - 1 participant

Read full topic

I’m having problems with Universal Media Player. I think I have it all setup, but I keep getting errors with mute. I get this error:

Failed to call service media_player/volume_mute. required key not provided @ data['is_volume_muted'].

As far as I can tell, my is_volume_muted is working correctly though.

Here’s my config:

media_player:
  platform: universal
  name: Test Universal
  device_class: tv
  children:
    - media_player.sony_xbr_75x90ch
    - media_player.sony_bravia_tv

  commands:
    turn_on:
      service: media_player.turn_on
      data:
        entity_id: media_player.sony_bravia_tv
    turn_off:
      service: media_player.turn_off
      data:
        entity_id: media_player.sony_bravia_tv
    volume_up:
      service: media_player.volume_up
      data:
        entity_id: media_player.sony_bravia_tv
    volume_down:
      service: media_player.volume_down
      data:
        entity_id: media_player.sony_bravia_tv
    volume_mute:
      service: media_player.volume_mute
      data:
        entity_id: media_player.sony_bravia_tv
    select_source:
      service: media_player.select_source
      data:
        entity_id: media_player.sony_bravia_tv
        source: "{{ source }}"
    volume_set:
      service: media_player.volume_set
      data:
        entity_id: media_player.sony_bravia_tv
        volume_level: "{{ volume_level }}"

  attributes:
    state: media_player.sony_bravia_tv
    is_volume_muted: media_player.sony_bravia_tv|is_volume_muted
    volume_level: media_player.sony_bravia_tv|volume_level
    source: media_player.sony_xbr_75x90ch|source
    source_list: media_player.sony_bravia_tv|source_list

When I put this in the Template Editor, I get False for both.

{{ state_attr('media_player.sony_xbr_75x90ch', 'is_volume_muted') }}

{{ state_attr('media_player.test_universal', 'is_volume_muted') }}

1 post - 1 participant

Read full topic

Is there any way retrieve and display some kind of artwork for YouTubeTV/Netflix/Hulu, etc. in the Media Control Card or Mini Media Player? I have a Sony TV that runs Android TV. My Media Control Card displays the App, Network, and Show (for YouTubeTV).

IMG_6287433×937 66.1 KB

Is there any way to use any of that info to create some kind of dynamic picture? It automatically does it for the HBO Max App:

4436F2BA-EFA9-4AA7-8E8F-E2D9FE4B6A13.PNG1242×2688 282 KB

1 post - 1 participant

Read full topic

The map card does a fair job of displaying location data, but I want to extract more info.
I have “Hours to show” set to 1440 to view a weeks worth of data.
I am planning a long drive and want to capture and store more information:

• location
• timestamp
• speed

so that I can measure progress, travel status, alerts when arriving at a way-point, calculate ETA etc. (to provide tracking bread-crumbs (not just current position)) to the folks at home.

Since the Map Card relies on retention of location data, is this info stored in a data file somewhere that is user accessible.??

1 post - 1 participant

Read full topic

I’m banging my head with a zone transition trigger that does not do what i expect.
So i made this simple trigger to test the trigger

- id: _test_zona
  initial_state: True
  alias: _TEST Zona
  trigger:
    - platform: state
      entity_id: person.lorenzo
  action:
    - service: notify.telegram
      data_template:
        title: 'TEST'
        message: >

          From: '{{trigger.from_state.state}}' - To: 
          '{{trigger.to_state.state}}'

This sends a message to my telegram every time the state changes (even if the zone is the same).
I expected to see only messages with different “from” and “to” , because the state chages means the person changed zone
but i got the opposite. 99% of my messages are with the same from and to. For example, when i exit home (leaving home zone and entering ‘home_street’ zone) , i get a message with "from: home_stree to:home_street. Same when i get home, leaving not_home and enterning home_street. I got "from home_street to home street. I know that i can filter out those with a simple != condition, but the point is that, in one full day of me traveling around the city and getting home several times, only ONE time i got a from: different to the to:. I’m missing hundred of triggers entering and exiting known zones.

Anyone knows why?

1 post - 1 participant

Read full topic