2023.2: How can I Assist?

[osre (Reinhard)]

Had a look at the log file now just before it gets unresponsive:
Here is the MQTT error I get every 80ms

2023-02-07 04:31:14.330 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback MQTT._mqtt_handle_message(<paho.mqtt.cl...xffff800d3b50>)
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/mqtt/client.py", line 693, in _mqtt_handle_message
    self._mqtt_data.state_write_requests.process_write_state_requests()
  File "/usr/src/homeassistant/homeassistant/components/mqtt/models.py", line 267, in process_write_state_requests
    entity.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 566, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 683, in _async_write_ha_state
    self.hass.states.async_set(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1512, in async_set
    state = State(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1144, in __init__
    raise InvalidStateError(
homeassistant.exceptions.InvalidStateError: Invalid state encountered for entity ID: sensor.thermostat_musikzimmer_program. State max length is 255 characters.

This one I have posted in the integrations thread already.

But after a couple of hours this happens and then the log ends

2023-02-07 04:54:20.385 WARNING (Thread-2 (_thread_main)) [homeassistant.components.mqtt.client] Disconnected from MQTT server homeassistant.local:1883 (16)
2023-02-07 04:58:32.615 WARNING (KNX Interface) [xknx.log] Received DisconnectRequest from tunnelling server.
2023-02-07 05:50:14.620 WARNING (KNX Interface) [xknx.log] Received DisconnectRequest from tunnelling server.
2023-02-07 06:03:31.525 WARNING (MainThread) [xknx.cemi] Could not send CEMI frame: Sending telegram failed. No active communication channel. for <CEMIFrame code="L_DATA_REQ" src_addr="IndividualAddress("15.15.12")" dst_addr="GroupAddress("0/0/4")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueRead />" />
2023-02-07 06:03:31.632 WARNING (MainThread) [xknx.log] Sending telegram failed. No active communication channel.
2023-02-07 06:03:31.724 WARNING (MainThread) [xknx.cemi] Could not send CEMI frame: Sending telegram failed. No active communication channel. for <CEMIFrame code="L_DATA_REQ" src_addr="IndividualAddress("15.15.12")" dst_addr="GroupAddress("0/0/10")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueRead />" />
2023-02-07 06:03:31.732 WARNING (MainThread) [xknx.log] Sending telegram failed. No active communication channel.
2023-02-07 06:03:32.361 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 0/0/4
2023-02-07 06:03:32.450 WARNING (MainThread) [xknx.log] Could not sync group address '0/0/4' (Esszimmer nord-ost - Position)
2023-02-07 06:03:32.452 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 0/0/10
2023-02-07 06:03:32.453 WARNING (MainThread) [xknx.log] Could not sync group address '0/0/10' (Esszimmer ost - Position)
2023-02-07 06:03:42.299 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_mosquitto/stats request
2023-02-07 06:03:42.617 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch stats for core_mosquitto: 
2023-02-07 06:03:42.635 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/45df7312_zigbee2mqtt/stats request
2023-02-07 06:03:42.638 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch stats for 45df7312_zigbee2mqtt: 
2023-02-07 06:03:42.640 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_vscode/stats request
2023-02-07 06:03:42.642 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch stats for a0d7b954_vscode: 
2023-02-07 06:04:56.192 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 06:05:47.391 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_2_4ghz is taking over 10 seconds
2023-02-07 06:05:47.456 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_5ghz is taking over 10 seconds
2023-02-07 06:05:47.457 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_gast is taking over 10 seconds
2023-02-07 06:05:47.458 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 06:05:47.459 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating fritz binary_sensor took longer than the scheduled update interval 0:00:30
2023-02-07 06:05:47.460 WARNING (MainThread) [homeassistant.components.switch] Updating fritz switch took longer than the scheduled update interval 0:00:30
2023-02-07 06:05:47.462 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 06:06:31.893 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 06:23:48.846 WARNING (KNX Interface) [xknx.log] Received DisconnectRequest from tunnelling server.
2023-02-07 06:57:01.180 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.fritz_box_7590_link_upload_noise_margin is taking over 10 seconds
2023-02-07 06:57:20.091 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_2_4ghz is taking over 10 seconds
2023-02-07 06:57:32.041 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_5ghz is taking over 10 seconds
2023-02-07 06:57:45.024 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_gast is taking over 10 seconds
2023-02-07 06:58:27.649 WARNING (MainThread) [homeassistant.components.switch] Updating fritz switch took longer than the scheduled update interval 0:00:30
2023-02-07 06:58:38.628 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 06:59:26.534 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.fritz_box_7590_link_upload_noise_margin (<class 'homeassistant.components.fritz.sensor.FritzBoxSensor'>) took 2.008 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+fritz%22
2023-02-07 07:00:14.317 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:00:14.895 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating fritz binary_sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:00:15.256 WARNING (MainThread) [homeassistant.components.switch] Updating fritz switch took longer than the scheduled update interval 0:00:30
2023-02-07 07:00:15.438 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:00:18.986 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from supervisor (172.30.32.2). Requested URL: '/api/config'. (HomeAssistantSupervisor/2023.01.1 aiohttp/3.8.3 Python/3.10)
2023-02-07 07:00:19.455 ERROR (MainThread) [homeassistant.components.homeassistant_alerts] Timeout fetching homeassistant_alerts data
2023-02-07 07:00:19.699 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 0/0/4
2023-02-07 07:00:19.719 WARNING (MainThread) [xknx.log] Could not sync group address '0/0/4' (Esszimmer nord-ost - Position)
2023-02-07 07:00:19.722 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 0/0/10
2023-02-07 07:00:19.725 WARNING (MainThread) [xknx.log] Could not sync group address '0/0/10' (Esszimmer ost - Position)
2023-02-07 07:00:33.768 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/a0d7b954_vscode/stats request
2023-02-07 07:00:36.002 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch stats for a0d7b954_vscode: 
2023-02-07 07:00:36.822 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_mosquitto/stats request
2023-02-07 07:00:37.301 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch stats for core_mosquitto: 
2023-02-07 07:00:37.774 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/45df7312_zigbee2mqtt/stats request
2023-02-07 07:00:38.107 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch stats for 45df7312_zigbee2mqtt: 
2023-02-07 07:00:39.233 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 0/0/16
2023-02-07 07:00:39.870 WARNING (MainThread) [xknx.log] Could not sync group address '0/0/16' (Esszimmer süd-ost - Position)
2023-02-07 07:00:40.601 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 0/0/22
2023-02-07 07:00:41.287 WARNING (MainThread) [xknx.log] Could not sync group address '0/0/22' (Esszimmer süd - Position)
2023-02-07 07:00:43.955 ERROR (MainThread) [homeassistant.components.hassio.handler] /addons/45df7312_zigbee2mqtt/changelog return code 500
2023-02-07 07:00:44.257 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch changelog for 45df7312_zigbee2mqtt: 
2023-02-07 07:00:55.287 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_mosquitto/changelog request
2023-02-07 07:00:55.859 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch changelog for core_mosquitto: 
2023-02-07 07:01:07.991 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/0/9
2023-02-07 07:01:08.585 WARNING (MainThread) [xknx.log] Could not sync group address '3/0/9' (Bad süd-ost - Position)
2023-02-07 07:01:13.938 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:01:17.625 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/0/15
2023-02-07 07:01:18.183 WARNING (MainThread) [xknx.log] Could not sync group address '3/0/15' (Bad süd - Position)
2023-02-07 07:01:18.544 WARNING (MainThread) [xknx.log] Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 3/0/21
2023-02-07 07:01:18.936 WARNING (MainThread) [xknx.log] Could not sync group address '3/0/21' (Bad süd-west - Position)
2023-02-07 07:03:20.580 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:03:52.861 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:04:38.198 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_5ghz is taking over 10 seconds
2023-02-07 07:04:39.208 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_gast is taking over 10 seconds
2023-02-07 07:05:36.909 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating fritz binary_sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:05:37.035 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:05:37.058 ERROR (MainThread) [homeassistant.components.fritz.common] Unexpected error fetching fritz-192.168.178.1-coordinator data: Unable to perform operation. 401 Unauthorized (ERR_NONE)401 UnauthorizedERR_NONEWebserver Tue, 07 Feb 2023 06:05:30 GMT
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/fritzconnection/core/soaper.py", line 140, in raise_fritzconnection_error
    root = etree.fromstring(response.content)
  File "/usr/local/lib/python3.10/xml/etree/ElementTree.py", line 1342, in XML
    parser.feed(text)
xml.etree.ElementTree.ParseError: mismatched tag: line 1, column 156

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 239, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/components/fritz/common.py", line 243, in _async_update_data
    await self.async_scan_devices()
  File "/usr/src/homeassistant/homeassistant/components/fritz/common.py", line 470, in async_scan_devices
    dev_info.wan_access = await self._async_get_wan_access(
  File "/usr/src/homeassistant/homeassistant/components/fritz/common.py", line 330, in _async_get_wan_access
    wan_access = await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.10/site-packages/fritzconnection/core/fritzconnection.py", line 378, in call_action
    return self.soaper.execute(service, action_name, arguments)
  File "/usr/local/lib/python3.10/site-packages/fritzconnection/core/soaper.py", line 259, in execute
    return handle_response(response)
  File "/usr/local/lib/python3.10/site-packages/fritzconnection/core/soaper.py", line 241, in handle_response
    raise_fritzconnection_error(response)
  File "/usr/local/lib/python3.10/site-packages/fritzconnection/core/soaper.py", line 150, in raise_fritzconnection_error
    raise FritzConnectionException(msg)
fritzconnection.core.exceptions.FritzConnectionException: Unable to perform operation. 401 Unauthorized (ERR_NONE)401 UnauthorizedERR_NONEWebserver Tue, 07 Feb 2023 06:05:30 GMT

2023-02-07 07:07:22.281 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:07:58.289 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:08:00.217 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating fritz binary_sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:08:04.719 WARNING (MainThread) [homeassistant.components.switch] Updating fritz switch took longer than the scheduled update interval 0:00:30
2023-02-07 07:08:05.386 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:08:21.411 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /info request
2023-02-07 07:08:22.991 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /core/info request
2023-02-07 07:08:24.027 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/info request
2023-02-07 07:08:26.227 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /os/info request
2023-02-07 07:08:29.885 ERROR (MainThread) [homeassistant.components.hassio] Error fetching hassio data: Error on Supervisor API: 
2023-02-07 07:08:35.041 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating fritz binary_sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:09:04.039 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:09:59.225 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:10:05.300 WARNING (MainThread) [homeassistant.components.switch] Updating fritz switch took longer than the scheduled update interval 0:00:30
2023-02-07 07:10:09.475 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 07:12:38.517 WARNING (KNX Interface) [xknx.log] Received DisconnectRequest from tunnelling server.
2023-02-07 07:13:18.405 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_2_4ghz is taking over 10 seconds
2023-02-07 07:13:23.404 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_5ghz is taking over 10 seconds
2023-02-07 07:13:29.042 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_gast is taking over 10 seconds

Looks to me like everything is failing and running into timeouts until it stops eventually.
The total runtime from restart to end of logfile is about 10 hours.

[osre (Reinhard)]

And it happend again, after 11 hours runtime
here are its last minutes:

2023-02-07 18:03:51.368 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback MQTT._mqtt_handle_message(<paho.mqtt.cl...xffff78fa2420>)
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/mqtt/client.py", line 693, in _mqtt_handle_message
    self._mqtt_data.state_write_requests.process_write_state_requests()
  File "/usr/src/homeassistant/homeassistant/components/mqtt/models.py", line 267, in process_write_state_requests
    entity.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 566, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 683, in _async_write_ha_state
    self.hass.states.async_set(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1512, in async_set
    state = State(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1144, in __init__
    raise InvalidStateError(
homeassistant.exceptions.InvalidStateError: Invalid state encountered for entity ID: sensor.thermostat_buro_program. State max length is 255 characters.
2023-02-07 18:03:55.402 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback MQTT._mqtt_handle_message(<paho.mqtt.cl...xffff79f7da10>)
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/mqtt/client.py", line 693, in _mqtt_handle_message
    self._mqtt_data.state_write_requests.process_write_state_requests()
  File "/usr/src/homeassistant/homeassistant/components/mqtt/models.py", line 267, in process_write_state_requests
    entity.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 566, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 683, in _async_write_ha_state
    self.hass.states.async_set(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1512, in async_set
    state = State(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1144, in __init__
    raise InvalidStateError(
homeassistant.exceptions.InvalidStateError: Invalid state encountered for entity ID: sensor.thermostat_buro_program. State max length is 255 characters.
2023-02-07 18:22:59.241 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating fritz binary_sensor took longer than the scheduled update interval 0:00:30
2023-02-07 18:23:00.870 WARNING (MainThread) [homeassistant.components.switch] Updating fritz switch took longer than the scheduled update interval 0:00:30
2023-02-07 18:23:02.617 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 18:23:04.731 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_2_4ghz is taking over 10 seconds
2023-02-07 18:23:06.210 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_5ghz is taking over 10 seconds
2023-02-07 18:23:06.934 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.fritz_box_7590_wi_fi_osre_gast is taking over 10 seconds
2023-02-07 18:23:16.263 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 18:23:28.865 WARNING (Thread-2 (_thread_main)) [homeassistant.components.mqtt.client] Disconnected from MQTT server homeassistant.local:1883 (16)
2023-02-07 18:23:36.268 WARNING (Thread-2 (_thread_main)) [homeassistant.components.mqtt.client] Disconnected from MQTT server homeassistant.local:1883 (16)
2023-02-07 18:24:33.409 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_eg_bathroom (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 1.298 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:24:51.023 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_eg_kitchen (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 0.424 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:25:04.842 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_eg_dining (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 1.191 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:25:35.749 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_eg_child (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 6.078 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:26:07.213 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_eg_livingroom (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 4.412 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:26:53.752 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_ug_roomwest (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 4.271 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:27:28.994 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_ug_bedroom (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 3.887 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:27:52.477 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_ug_bathroom (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 1.963 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:28:16.680 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_ug_child (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 1.250 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:28:40.127 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for climate.temp_ug_washroom (<class 'homeassistant.components.mqtt.climate.MqttClimate'>) took 1.021 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
2023-02-07 18:30:15.711 WARNING (MainThread) [homeassistant.components.sensor] Updating fritz sensor took longer than the scheduled update interval 0:00:30
2023-02-07 18:40:05.077 WARNING (KNX Interface) [xknx.log] Received DisconnectRequest from tunnelling server.

I see if i can find the log level and set it to critical. Then we see if it’s the large number of logs written that causes the issue

[blackie333]

Thank you for help, it’s working again.

[JeffreyHA (Jeffrey)]

Is anyone else still having issues with this release of HA and the Conbee2 stick. It sees it in the device page but will not load. I tried passing through the entire usb controller instead of the stick and that still did not work. Everything works perfect in 2023.1 but as soon as I update my whole ZigBee network is dead, changing ports, trying to reconfigure the radio, nothing works. I have again restored a backup to get back up and working but I find it hard to believe this issue is limited to me.

Some specifics to my current setup. I am running unraid and passing the entire usb controller through to the VM. The conbee2 stick is being detected and working great in 2023.1 but in 2023.2 ZHA wont start up.

I ordered a skyconnect with the hope that might be a better long term solution then the conbee2 but it bothers me this update broke it.

[Nerdix]

Seems you are not the only one having issues:

Zigbee is not longer working After updating

[CChris (Christoph)]

@osre

State max length is 255 characters

it seems that your sensor.thermostat_buro_program is receiving a state exceeding the limit of 255 characters.
This is probably causing the integration to crash.

I found this on the forum:

Mqtt sensor error "State max length is 255 characters"

Hi There, I’m trying to add a sensor where the output is an invalid json, so I have to manipulate it before use. I was able to manipulate the data using the Template on Developer Tools, but doesn’t matter how many characters I’m filtering using regex_replace, however when I try to configure the sensor, I’m receiving the below message from the logs: 2022-07-14 13:03:18 ERROR (MainThread) [homeassistant.util.logging] Exception in message_received when handling msg on 'lollipop/cameraStatus/retu…

Sensor size limit - How to read long MQTT payloads?

I want to use text strings that are longer than 256 characters. I thought I could publish them to MQTT (I can) and then be able to do something with them in HA (I can’t). The only way I can think of to get them into HA is using an MQTT Sensor but I have now found that that also has a size limit of 256 characters Is there any way to ‘read’ a long payload? It doesn’t need to be stored, I can use it dynamically while it is in memory.

that might help ?

[yogi84]

broke my ZHA too… thanks for the tip

[FinnSistant]

Update 2023.2.3 broke my HA, some integrations seem to be stuck during the start. Lost bluetooth comms (RuuviTag, Xiaomi), Panasonic Comfort Cloud, Emporia energy integrations. Tried to downgrade back to 2023.2.2 but it got even worse. Restore from backup did not work. After restore tried to reboot but configuration.yaml (and others) are not found anymore. Hope I can reinstall the old version and restore the backup. Running HA OS in mini computer. Had many updates before without major issues.

[CChris (Christoph)]

you should check your log files.
From the description you provided (with configuration.yaml and others are not found) I think, that there are other reasons why your system broke…

Also, please provide some information about your Hardware Setup - like available disk space, what “mini computer” you are using, and so on.

[Yoyo42]

Phrasing it as ‘If you have switched from the default sqlite DB to MariaDB then…’ would have avoided the confusion for us tiny-bit-above-average users who do read release notes…

[JeffreyHA (Jeffrey)]

Thanks, sounds a bit different then my issue but will hope fixing it resolves mine too. Will have to try this latest update and check what errors I am getting again and compare.

[osre (Reinhard)]

I had this thought as well.
The question is: why is the message so much longer since one of these updates?
I Rember the messages for my thermostats being much shorter when I installed them.

[osre (Reinhard)]

I have set the log level to critical.
But even with only 1 message in the log (somehow 1 info message got logged right after startup) , HA still got unresponsive after about the same amount of time.
So I assume it is not the writing of the logs to file.

[CChris (Christoph)]

I don’t really know - it can’t be the update, since the message comes from the sensor - or at least, it is the MQTT payload…

You could probably check with MQTT Explorer what the payload of the message is… Maybe, there’s the root cause of this?
As far as I understand from the linked topics, the limitation in size does not came just with this update

[osre (Reinhard)]

I think the issue is the latest Zigbee2MQTT update, that for some reason packs way mor things into the message for this sensor now. Hopefully they fix that soon, Or can I go back to an older version of an addon?

[CChris (Christoph)]

hm… I don’t know, since I am not using Zigbee2Mqtt - but as far as I know, Z2Mqtt is a custom_component, or?
Did they update the integration at the same time?

If it is a custom component, you could roll back to a previous release within HACS…
There, you can select which version you want to download.

BUT:
I would expect:
If they have increased the information the sensor provides, you should probably consider to break the payload into sensor values + attributes…
I think, that should be the better option… ?!

[osre (Reinhard)]

Z2MQTT is a custom integration.
But I think there is only limited access on how the payload is created.
I have to check.
I think I carry my efforts over there. Thank you for your assistance.

[nickrout]

Z2m is not a custom integration. It is an external application which leverages the mqtt integration.

[osre (Reinhard)]

I have downgraded to z2mqtt 1.29.something (using the partial backup) and now the error in the log is gone, even so the payload looks the same.
Hopefully the system runs stable again

[kohai-ut (Kohai)]

Just in case my situation is useful to anyone having issues with the upgrades… I came from 2022-11-x.

UPDATE: After thinking about this issue in the middle of the night, I realized I did replace my internet firewall 6 weeks ago. I looked at the config this morning and noticed ipv6 is enabled on it and it did have dhcp6 giving out addresses but no ipv6 traffic actually gets through the firewall. So, the comments below seem to imply my rpi4 HA was pulling an address and then insisting on using it without failing over to ipv4 when it couldn’t get out to the internet for proper updates.

I found the following… I could not get Node Red to start in Home Assistant. I would get a 502 Bad Gateway if I clicked on the Node Red in HA. Maybe NR was running but I could not get to the GUI in HA. Much googling and messing around with disabling SSL didn’t seem to help.

I found if I used the RESET config in Add-ons → Node Red → configuration tab (save your secret and paste it back in plus other settings you may want) that it would reset everything on that page including the add on nodes and they disappeared. Now I could get into Node Red in HA and it would complain the add-ons were missing. The 502 bad gateway will show up for about the first 20-30 seconds of NR starting up so wait and then try to get in. THEN, once in Node Red, click in the top right menu and choose Manage Palette. In here, you can try to install nodes again which did seem to be missing from NR even though I had been using them before (most likely failed to install during the update due to the next issue).

However, I found I was getting network errors according to the View Log in Node Red (also in the top right menu in NR). It seems the HA upgrade (?) enabled an IPv6 interface (or it was always enabled but NR didn’t care?). In HA, go to settings and networking and disable the IPv6 interface. I did a lot of upgrades today to my network, my HA, my node red, etc, so I’m not exactly sure which thing made all this bad stuff happen. Very fiddly to get it going again.

In the old days I think I could edit a config file to add these add-ons but now the add-ons are managed inside of Node Red AND to be confusing the add-on page in HA under the config section has npm nodes and you can type in that field but you can’t save or submit anything in it. I dumbly spent 15 minutes trying to figure out why I could type in that field but not save anything (not knowing Manage Palette was now a thing in NR).