Had the same issue just now, uninstalled aiogithubapi and reran the upgrade. I suspect aiogithub was a leftover from a (now removed) HACS installation, but I admit that is only speculation.
I love Home Assistant. Iām an IT guy, and am somewhat comfortable editing scripts and code, but never really authoring it.
On the topic of color changes, I donāt understand most of the work arounds being discussed. I have read through the comments and find myself agreeing with some that it would be great to just be able to control variables for on/off colors on the cards. Iām just curious as to the technicals on why that would be difficult.
My experience isnāt that I canāt see the contrastā¦ it just makes my very logical, very easy cards look weird and inconsistent. Thatās allā¦ and I donāt know how to change it. And itās ONLY for my covers (front shades).
I have many menus. All items are either blue when off or amber when on. All the sudden my covers are purple when on (up). It just doesnāt seem to make sense, and Iād hope the color changes can either be reverted, or that someone could point me in a direction that would allow me to change the off/on colors for anything I use. Thatās all.
I only updated to 2022.12.1 (from 2022.11.x) yesterdy and already my previously rock solid system has crashed twice, once on 2022.12.1 and again after updating to 2022.12.2 today.
Iām not seeing the memory issue that others have mentioned (24.5% max).
My log doesnāt seem to reveal anything other than a bunch of issues connecting to CCTV cameras.
Log
2022-12-12 11:33:47.606 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration plex_assistant 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-12-12 11:33:47.607 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bom_radar 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-12-12 11:33:47.608 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartir 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-12-12 11:33:47.609 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration google_home 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-12-12 11:33:47.610 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration braviatv_psk 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-12-12 11:33:47.610 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration anniversaries 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-12-12 11:33:47.610 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-12-12 11:33:47.610 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration adaptive_lighting 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-12-12 11:33:47.611 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration webrtc 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-12-12 11:33:47.611 WARNING (SyncWorker_0) [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-12-12 11:33:47.611 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ytube_music_player 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-12-12 11:33:47.612 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration presence_simulation 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-12-12 11:33:47.613 WARNING (SyncWorker_0) [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-12-12 11:33:47.613 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration mass 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-12-12 11:33:47.614 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya 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-12-12 11:33:47.614 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tuya_local 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-12-12 11:33:47.615 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration xiaomi_cloud_map_extractor 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-12-12 11:33:47.615 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration netradio 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-12-12 11:33:47.616 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fronius_inverter 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-12-12 11:33:47.616 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration browser_mod 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-12-12 11:33:47.617 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate 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-12-12 11:33:47.617 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman 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-12-12 11:33:47.617 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fullykiosk 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-12-12 11:33:47.617 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alarmo 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-12-12 11:33:47.617 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sleep_as_android 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-12-12 11:33:47.618 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bureau_of_meteorology 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-12-12 11:33:54.292 WARNING (SyncWorker_1) [pyhik.hikvision] Sensor type "faceSnap" is unsupported.
2022-12-12 11:34:05.086 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform feedparser is taking over 10 seconds.
2022-12-12 11:34:11.094 WARNING (MainThread) [homeassistant.components.tasmota.discovery] Multiple Tasmota devices are sharing the same topic 'cmnd/tasmota/lights/'. Offending devices: 'Stage_Light_1' (192.168.0.241), 'Stage_Light_2' (192.168.0.213)
2022-12-12 11:34:15.380 WARNING (MainThread) [homeassistant.setup] Setup of automation is taking over 10 seconds.
2022-12-12 11:34:16.482 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Living Room IR' for broadlink integration not ready yet: [Errno -4000] Network timeout: No response received within 5s; Retrying in background
2022-12-12 11:34:19.409 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for garden_lights_front_2 @ 192.168.0.124: Error connecting to ('192.168.0.124', 6053): [Errno 113] Connect call failed ('192.168.0.124', 6053)
2022-12-12 11:34:19.411 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for gas_heater_plug @ 192.168.0.57: Error connecting to ('192.168.0.57', 6053): [Errno 113] Connect call failed ('192.168.0.57', 6053)
2022-12-12 11:34:19.412 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for garden_lights_front_1 @ 192.168.30.121: Error connecting to ('192.168.30.121', 6053): [Errno 113] Connect call failed ('192.168.30.121', 6053)
2022-12-12 11:34:19.462 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for garden_lights_back_1 @ 192.168.30.123: Error connecting to ('192.168.30.123', 6053): [Errno 113] Connect call failed ('192.168.30.123', 6053)
2022-12-12 11:34:24.365 WARNING (MainThread) [homeassistant.config_entries] Config entry 'WLED-Wardrobe' for wled integration not ready yet: Invalid response from API: Error occurred while communicating with WLED device at 192.168.30.155; Retrying in background
2022-12-12 11:34:27.816 WARNING (MainThread) [homeassistant.config_entries] Config entry '192.168.0.126' for wled integration not ready yet: Invalid response from API: Error occurred while communicating with WLED device at 192.168.0.126; Retrying in background
2022-12-12 11:34:27.821 WARNING (MainThread) [homeassistant.config_entries] Config entry '192.168.0.127' for wled integration not ready yet: Invalid response from API: Error occurred while communicating with WLED device at 192.168.0.127; Retrying in background
2022-12-12 11:34:27.938 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform frigate is taking over 10 seconds.
2022-12-12 11:34:27.939 WARNING (MainThread) [homeassistant.components.camera] Setup of camera platform frigate is taking over 10 seconds.
2022-12-12 11:34:27.940 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform frigate is taking over 10 seconds.
2022-12-12 11:34:27.940 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform frigate is taking over 10 seconds.
2022-12-12 11:34:39.991 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'UPS Fault Notifications' trigger: In 'numeric_state' condition: unknown entity sensor.ups_ups_temperature
2022-12-12 11:34:41.821 WARNING (MainThread) [custom_components.hacs] You have 'maykar/lovelace-swipe-navigation' installed with HACS this repository has been removed from HACS, please consider removing it. Removal reason (Repository is archived)
2022-12-12 11:34:41.824 WARNING (MainThread) [custom_components.hacs] You have 'maykar/plex_assistant' installed with HACS this repository has been removed from HACS, please consider removing it. Removal reason (Repository is archived)
2022-12-12 11:34:41.826 WARNING (MainThread) [custom_components.hacs] You have 'custom-cards/text-element' installed with HACS this repository has been removed from HACS, please consider removing it. Removal reason (Repository is archived)
2022-12-12 11:34:41.829 WARNING (MainThread) [custom_components.hacs] You have 'mattieha/slider-button-card' installed with HACS this repository has been removed from HACS, please consider removing it. Removal reason (Abandoned, community fork maintained at custom-cards/slider-button-card)
2022-12-12 11:34:45.300 WARNING (MainThread) [homeassistant.components.input_select] Current option: loading no longer valid (possible options: e26d30e4_efc01c6f, Games Room Speaker, de0e6afb_e21c35e9, 3acbfe55_4fdc7a79, f17e5907_41f77178, mass_googlehome0011, Broadcast Group, Lounge Mini, c8b21fea_bb10eb6b, a768a500_914816da, Kitchen Speaker, Plex Bedroom TV, mass_gym_speaker, 050ba25a_9b451109, Lounge Speakers, mass_back_yard, M5Stack Atom Speaker Kit 1, Onkyo Amp, mass_everywhere, Alfresco Speaker, 900ab4fe_8b4cfffa, b57b93ef_5069dd90, 5c394ef6_c83cb626, mass_googlehome3019, mass_house, Bedroom TV, mass_games_room_speaker, Lounge TV, Lounge and Office, Plex (Plex Web - Chrome), 21a0da67_6ff87a98, House except office, Shed Speakers, Everywhere, Bedroom, Office speakers, Plex Living Room TV, kogan_smartertv, 9b999678_ba24392d, Living Room TV, 6b410767_0b0fd108, 90132a5a_4882e41d, Plex Lounge TV, mass_lounge_speakers, mass_chromecastaudio8002, mass_bedroom_tv, mass_bedroom, Gym Speaker, House group, mass_lounge_tv, Plex (Plex for Android (Mobile) - Galaxy S22), mass_living_room_tv, Alfresco nest mini, Alfresco Sony, 7dd6dcb0_f014643e, 8a0d6c8a_27d6b1c8, mass_shed_speakers, 9e6c1ff0_8e582713, All except office, Back Yard)
2022-12-12 11:34:45.431 ERROR (MainThread) [custom_components.ytube_music_player.media_player]
== == == == == == = ytube_music_player Integration Error == == == == == == == ==
2022-12-12 11:34:45.450 ERROR (MainThread) [custom_components.ytube_music_player.media_player] unfortunately we hit an error, please open a ticket at
2022-12-12 11:34:45.451 ERROR (MainThread) [custom_components.ytube_music_player.media_player] https://github.com/KoljaWindeler/ytube_music_player/issues
2022-12-12 11:34:45.453 ERROR (MainThread) [custom_components.ytube_music_player.media_player] and paste the following output:
2022-12-12 11:34:45.458 ERROR (MainThread) [custom_components.ytube_music_player.media_player] Traceback (most recent call last):
File "/config/custom_components/ytube_music_player/media_player.py", line 1085, in async_update_playlists
self._playlists = await self.hass.async_add_executor_job(lambda: self._api.get_library_playlists(limit=self._trackLimit))
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/ytube_music_player/media_player.py", line 1085, in <lambda>
self._playlists = await self.hass.async_add_executor_job(lambda: self._api.get_library_playlists(limit=self._trackLimit))
File "/usr/local/lib/python3.10/site-packages/ytmusicapi/mixins/library.py", line 27, in get_library_playlists
response = self._send_request(endpoint, body)
File "/usr/local/lib/python3.10/site-packages/ytmusicapi/ytmusic.py", line 142, in _send_request
raise Exception(message + error)
Exception: Server returned HTTP 401: Unauthorized.
You must be signed in to perform this operation.
2022-12-12 11:34:45.460 ERROR (MainThread) [custom_components.ytube_music_player.media_player]
thanks, Kolja
2022-12-12 11:34:45.466 ERROR (MainThread) [custom_components.ytube_music_player.media_player] == == == == == == = ytube_music_player Integration Error == == == == == == == ==
2022-12-12 11:39:12.909 WARNING (stream_worker) [libav.flv] DTS 72151 < 4295039386 out of order
2022-12-12 11:39:12.931 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Timestamp overflow detected: last dts = 4295039386, dts = 72151
2022-12-12 11:45:02.991 WARNING (stream_worker) [libav.flv] DTS 22340 < 4294989587 out of order
2022-12-12 11:45:02.993 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Timestamp overflow detected: last dts = 4294989587, dts = 22340
2022-12-12 11:48:34.616 ERROR (MainThread) [frontend.js.latest.202212080] http://192.168.0.14:8123/hacsfiles/lovelace-flower-card/flower-card.js:1:9 Uncaught SyntaxError: The requested module '/local/lovelace-flower-card/data/data.js' does not provide an export named 'FlowerData'
2022-12-12 11:50:32.168 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 11:51:00.639 ERROR (Thread-21) [pychromecast.socket_client] [All except office(192.168.0.82):32234] Error reading from socket.
2022-12-12 11:51:00.640 WARNING (Thread-21) [pychromecast.socket_client] [All except office(192.168.0.82):32234] Error communicating with socket, resetting connection
2022-12-12 11:51:00.654 ERROR (Thread-31) [pychromecast.socket_client] [Everywhere(192.168.0.82):32071] Error reading from socket.
2022-12-12 11:51:00.655 WARNING (Thread-31) [pychromecast.socket_client] [Everywhere(192.168.0.82):32071] Error communicating with socket, resetting connection
2022-12-12 11:51:00.657 ERROR (Thread-21) [pychromecast.socket_client] [All except office(192.168.0.82):32234] Failed to connect to service ServiceInfo(type='host', data=('192.168.0.82', 32234)), retrying in 5.0s
2022-12-12 11:51:00.667 ERROR (Thread-31) [pychromecast.socket_client] [Everywhere(192.168.0.82):32071] Failed to connect to service ServiceInfo(type='host', data=('192.168.0.82', 32071)), retrying in 5.0s
2022-12-12 11:52:26.922 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 11:52:55.126 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 11:54:13.080 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 11:55:06.982 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 12:02:14.283 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 12:03:25.074 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 12:04:08.508 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 12:04:17.243 ERROR (Thread-32) [homeassistant.components.cast.media_player] Failed to cast media http://ic2ti.scahw.com.au/2easy_128. Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
2022-12-12 12:05:15.055 ERROR (MainThread) [homeassistant.components.xiaomi_miio] Timeout fetching Robot vacuum data
2022-12-12 12:07:01.892 WARNING (stream_worker) [libav.flv] DTS 0 < 1330464 out of order
2022-12-12 12:08:48.282 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 12:09:08.435 WARNING (Thread-44) [pychromecast.socket_client] [Shed Speakers(192.168.0.89):8009] Heartbeat timeout, resetting connection
2022-12-12 12:11:52.303 WARNING (Thread-38) [pychromecast.socket_client] [Living Room TV(192.168.0.88):8009] Heartbeat timeout, resetting connection
2022-12-12 12:13:51.903 WARNING (stream_worker) [libav.flv] DTS 0 < 403060 out of order
2022-12-12 12:15:23.424 WARNING (Thread-38) [pychromecast.socket_client] [Living Room TV(192.168.0.88):8009] Heartbeat timeout, resetting connection
2022-12-12 12:16:04.507 WARNING (Thread-38) [pychromecast.socket_client] [Living Room TV(192.168.0.88):8009] Heartbeat timeout, resetting connection
2022-12-12 12:17:11.961 WARNING (stream_worker) [libav.flv] DTS 0 < 192305 out of order
2022-12-12 12:17:15.592 WARNING (Thread-38) [pychromecast.socket_client] [Living Room TV(192.168.0.88):8009] Heartbeat timeout, resetting connection
2022-12-12 12:17:36.672 WARNING (Thread-38) [pychromecast.socket_client] [Living Room TV(192.168.0.88):8009] Heartbeat timeout, resetting connection
2022-12-12 12:20:01.941 WARNING (stream_worker) [libav.flv] DTS 0 < 165120 out of order
2022-12-12 12:28:32.038 WARNING (stream_worker) [libav.flv] DTS 0 < 502858 out of order
2022-12-12 12:28:42.033 WARNING (stream_worker) [libav.flv] DTS 0 < 4927 out of order
2022-12-12 12:28:52.036 WARNING (stream_worker) [libav.flv] DTS 0 < 4923 out of order
2022-12-12 12:30:44.021 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error demuxing stream: [Errno 1414092869] Immediate exit requested: 'rtmp://ccab4aaf-frigate-fa/live/front_door'
2022-12-12 12:33:32.059 WARNING (stream_worker) [libav.flv] DTS 0 < 155521 out of order
2022-12-12 12:33:52.086 WARNING (stream_worker) [libav.flv] DTS 0 < 14888 out of order
2022-12-12 12:34:12.076 WARNING (stream_worker) [libav.flv] DTS 0 < 17287 out of order
2022-12-12 12:40:22.119 WARNING (stream_worker) [libav.flv] DTS 0 < 360665 out of order
2022-12-12 12:40:48.185 WARNING (Thread-38) [pychromecast.socket_client] [Living Room TV(192.168.0.88):8009] Heartbeat timeout, resetting connection
2022-12-12 12:45:39.332 WARNING (Thread-38) [pychromecast.socket_client] [Living Room TV(192.168.0.88):8009] Heartbeat timeout, resetting connection
2022-12-12 12:48:47.798 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error demuxing stream: [Errno 1414092869] Immediate exit requested: 'rtmp://ccab4aaf-frigate-fa/live/front_door'
2022-12-12 12:49:27.856 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 12:50:17.911 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 12:51:18.001 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 12:52:28.059 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 12:53:48.102 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 12:55:18.145 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 12:56:58.190 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 12:58:48.234 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 12:58:50.876 WARNING (Thread-38) [pychromecast.socket_client] [Living Room TV(192.168.0.88):8009] Heartbeat timeout, resetting connection
2022-12-12 12:59:11.964 WARNING (Thread-38) [pychromecast.socket_client] [Living Room TV(192.168.0.88):8009] Heartbeat timeout, resetting connection
2022-12-12 13:00:48.275 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 13:02:58.321 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 13:05:18.362 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 13:07:48.407 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 13:08:38.465 ERROR (MainThread) [homeassistant.components.nmap_tracker] Nmap scanning failed: 'Timeout from nmap process'
2022-12-12 13:10:28.469 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 13:13:18.520 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
2022-12-12 13:16:18.571 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_door] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://ccab4aaf-frigate-fa/live/front_door
You mention CCTV cameras. That pretty much guarantees that you problem is related to the same memory leak others are reporting.
Good news is that itās supposed to be fixed in 2022.12.3 which should be available about now. Try it out.
Thanks for the tip, I just noticed the update being available. Hopefully it fixes the issueā¦ you know, WAF etc.
I just did update from 2022.12.1 to 12.3 and now it not shows my dashboard anymore if I cast it to my nest hub or hub maxā¦ it stays on the connection screen. Anyone else with this problem?
Yes, Iāve the same issue after updating from 12.1 to 12.3
anyone using here_travel_time noticed this (new to me) error?
Logger: homeassistant.components.here_travel_time.coordinator
Source: components/here_travel_time/coordinator.py:79
Integration: HERE Travel Time (documentation, issues)
First occurred: 11:42:23 (1 occurrences)
Last logged: 11:42:23
Unexpected error fetching here_travel_time data: (429, {'error': 'Too Many Requests', 'error_description': 'Rate limit for this service has been reached'})
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 225, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/components/here_travel_time/coordinator.py", line 79, in _async_update_data
response = await self._api.route(
File "/usr/local/lib/python3.10/site-packages/here_routing/here_routing.py", line 186, in route
response = await self.request(uri=ROUTES_PATH, params=params)
File "/usr/local/lib/python3.10/site-packages/here_routing/here_routing.py", line 125, in request
raise HERERoutingError(response.status, json.loads(decoded_contents))
here_routing.exceptions.HERERoutingError: (429, {'error': 'Too Many Requests', 'error_description': 'Rate limit for this service has been reached'})
Youāve reached the rate limit. Might be a change on HEREās side.
If you have 4 HERE travel time sensors, youāll reach the 1000 per day rate limit at 20:50 (8:50pm)
Iāve just raised an issue, explicitly mentioning all configs have polling disabled and only update on person state change.
This has been working for years, so maybe HERE indeed changed something. HA dev should be aware, hence the issue
Are you sure you donāt have aggressive person updates (out of nowhere)? Is your automation based on person state changes or location changes? GPS can get into update fits when it canāt find your location and you bounce around.
yes, I think I have guarded over anxious updating, also, based them on proximity, so not on battery_state ;-):
- alias: Update Travel sensors
id: update_travel_sensors
trigger:
platform: state
entity_id:
- proximity.marijn_home
- proximity.xxx
condition:
- >
{{trigger.to_state is not none and trigger.from_state is not none}}
- >
{% set x = ['unavailable','unknown'] %}
{{trigger.to_state.state not in x and trigger.from_state.state not in x and
trigger.to_state.state != trigger.from_state.state}}
- >
{{trigger.to_state.attributes.dir_of_travel != 'stationary'}}
action:
service: homeassistant.update_entity
target:
entity_id: >
{% set id = trigger.to_state.object_id.split('_home')[0]|title %}
{% set dev_id = device_id(id ~ ' naar huis') %}
{{device_entities(dev_id)}}
Iād just make sure you turned off polling and provide that automation (and a description) to the code owner in the PR
Thanks, @tom_l, I did read through that, and actually followed the steps to a tee. The issue in that āClassicā themes solution, at least for me, is that it worked to turn the covers blue again, but then covers, and binary off/on switches lost their āonā colorā¦ stayed blue.
Thanks for the attempt to point me in the right direction. I do appreciate that.
Yep. I have the same issue. Tested on all devices. ( TVās and Hubās ). All good before in 12.2 and no longer after update to 12.3
You can pick any colours you want.
Actually, was just going to reply againā¦ I have it now, and thanks again for pointing me back there. I can only guess that something didnāt update on my phone client quick enough, and I didnāt think about it. I tried the solution one more time.
Again, the first time, my covers would turn Amber (because thatās what I chose in the theme code), but many other items wouldnāt turn amber if I turned them on. (I think this is where something didnāt refresh on my phone fast enough or something.)
After reading/replying to your response this morning, I decided to give it another shot, and it all works perfectly again. Donāt exactly know what it was, but Iām good to go now.
Thanks again!
maybe, you want to have a look into this theme?
It does still have some of the ācustomā colors - but they can be adjusted with this option, since Iāve tried to group the variables in some ālogicā wayā¦
And I am open for suggestions (as long as it is possible / implemented in the core )