RichieFrame
commented
2 years ago 2022-04-10 15:02:49 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nws_alerts which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-10 15:02:49 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration feedparser which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-10 15:02:49 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration simpleicons which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-10 15:02:49 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration weatherbit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-10 15:02:49 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration wiz_light which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-10 15:02:49 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-10 15:02:49 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration lutron_caseta_pro which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-10 15:02:49 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration snoo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-10 15:02:49 ERROR (SyncWorker_1) [homeassistant.loader] The custom integration 'snoo' does not have a version key in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details
2022-04-10 15:02:49 WARNING (MainThread) [homeassistant.components.recorder] The 'purge_interval' option near /config/configuration.yaml:16 is deprecated, please remove it from your configuration
2022-04-10 15:02:49 WARNING (MainThread) [homeassistant.components.lovelace] Lovelace is running in storage mode. Define resources via user interface
2022-04-10 15:02:50 INFO (MainThread) [pyenvisalink.envisalink_base_client] Latching onto an existing event loop.
2022-04-10 15:02:50 INFO (MainThread) [pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at 192.168.0.6:4025
2022-04-10 15:02:50 ERROR (MainThread) [pyenvisalink.envisalink_base_client] Unable to connect to envisalink. Reconnecting...
2022-04-10 15:02:50 ERROR (MainThread) [homeassistant.components.envisalink] Could not establish a connection with the Envisalink- retrying
2022-04-10 15:02:50 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Closing connection with server...
2022-04-10 15:02:51 WARNING (MainThread) [homeassistant.components.statistics.sensor] The configuration parameter 'state_characteristic' will become mandatory in a future release of the statistics integration. Please add 'state_characteristic: mean' to the configuration of sensor 'Temperature Smooth' to keep the current behavior. Read the documentation for further details: https://www.home-assistant.io/integrations/statistics/
2022-04-10 15:02:51 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform lutron_caseta_pro.fan: Platform not found (cannot import name 'SPEED_HIGH' from 'homeassistant.components.fan' (/usr/src/homeassistant/homeassistant/components/fan/__init__.py)).
2022-04-10 15:02:51 WARNING (MainThread) [homeassistant.components.statistics.sensor] The configuration parameter 'state_characteristic' will become mandatory in a future release of the statistics integration. Please add 'state_characteristic: mean' to the configuration of sensor 'Temperature Trend' to keep the current behavior. Read the documentation for further details: https://www.home-assistant.io/integrations/statistics/
2022-04-10 15:02:52 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'int' got invalid input 'unknown' when rendering template '{% if states('sensor.nws_alerts') | int > 0 %}
mdi:weather-lightning
{% else %}
mdi:weather-sunny
{% endif %}' but no default was specified. Currently 'int' will return '0', however this template will fail to render in Home Assistant core 2022.1
2022-04-10 15:02:53 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2022-04-10 21:02:53+00:00', which is different from the system '2022-04-10 20:02:53.237748+00:00', this could lead to authentication issues
2022-04-10 15:02:53 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2022-04-10 21:02:53+00:00', which is different from the system '2022-04-10 20:02:53.247843+00:00', this could lead to authentication issues
2022-04-10 15:02:53 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2022-04-10 21:02:53+00:00', which is different from the system '2022-04-10 20:02:53.162286+00:00', this could lead to authentication issues
2022-04-10 15:02:53 WARNING (MainThread) [homeassistant.components.onvif] The date/time on the device (UTC) is '2022-04-10 21:02:52+00:00', which is different from the system '2022-04-10 20:02:53.170787+00:00', this could lead to authentication issues
2022-04-10 15:02:54 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Brother MFC-J4535DW' for ipp integration not ready yet: Invalid response from API: Error occurred while communicating with IPP server.; Retrying in background
2022-04-10 15:02:54 WARNING (MainThread) [homeassistant.config_entries] Config entry '192.168.2.123' for shelly integration not ready yet: Cannot connect to host 192.168.2.123:80 ssl:default [Connect call failed ('192.168.2.123', 80)]; Retrying in background
2022-04-10 15:02:54 WARNING (MainThread) [homeassistant.config_entries] Config entry '192.168.2.131' for shelly integration not ready yet: Cannot connect to host 192.168.2.131:80 ssl:default [Connect call failed ('192.168.2.131', 80)]; Retrying in background
...... and so onThat is the start of the log as of the last restart, as you can see it is immediate. The rest of the log at restart is the common complaints about statistics changes, devices with times that differ from the system time, and devices that are not available (because they are not powered on)
ufodone
audymatic
TheFuzz4
crackers8199
abarbaccia
Damien2s
issue-triage-workflows[bot]
The problem
In version 2022.3.5 the envisalink integration is no longer working. It will talk to the module but it will not arm/disarm the alarm system. Rolled back to 2022.3.4 and there is no issue at this level.
The logs show that it connected to it and then the connection is closed immediately stating that no response was received and attempts to retry. It does semi work in that it is able to pull the current state of the alarm system but any attempts to run a command on the system fail.
What version of Home Assistant Core has the issue?
2022.3.5
What was the last working version of Home Assistant Core?
2022.3.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Envisalink
Link to integration documentation on our website
https://www.home-assistant.io/integrations/envisalink/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response