I’ve only recently started using docker and I’m running Readarr, Soulseek, Calibre, Room-Assistant, Pi-Hole, Tiny Media Manager and nGinx so it would seem the obvious next step.
Just worried about the amount of outbound connections HASS has and what a PITA it might be to get everything talking.
In docker hass runs with --host net
Edit cancel my mis-type. The correct invocation is --network=host Raspberry Pi - Home Assistant
Actually I was reading the official documentation on how to use HASS in a docker on QNAP and it said Host. Just never clicked!
What this conversation has reminded me of is that when I moved over to the Python 3.9 framework I realised a week or so after that it was just one custom card that had killed my dashboard on 2021-12-10 as it happened again and I used method of elimination / last in - first out!
So… I’ve reinstalled the 3.8 framework, used the appropriate package for HASS, deleted that card and I’m up and running again.
Probably have to reverse a couple of changes but at least the bones are back. Still not ruling out docker if only to keep the version I want!!
By the way, is this our own good @frenck on the cover of one of those albums in the screenshot of the new media bar?
I don’t have time for livestreams, I spend it reading the release notes 
2022.2.4 seems to break mqtt:
Logger: homeassistant.components.binary_sensor
Source: components/mqtt/debug_info.py:82
Integration: Binary Sensor (documentation, issues)
First occurred: 11:10:58 (11 occurrences)
Last logged: 11:10:58
Error adding entities for domain binary_sensor with platform mqtt
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 614, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 778, in add_to_platform_finish
await self.async_added_to_hass()
File "/usr/src/homeassistant/homeassistant/components/mqtt/binary_sensor.py", line 121, in async_added_to_hass
await super().async_added_to_hass()
File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 657, in async_added_to_hass
await super().async_added_to_hass()
File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 247, in async_added_to_hass
await super().async_added_to_hass()
File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 320, in async_added_to_hass
await super().async_added_to_hass()
File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 509, in async_added_to_hass
debug_info.add_entity_discovery_data(
File "/usr/src/homeassistant/homeassistant/components/mqtt/debug_info.py", line 82, in add_entity_discovery_data
debug_info = hass.data[DATA_MQTT_DEBUG_INFO]
KeyError: 'mqtt_debug_info'
Logger: homeassistant.components.switch
Source: components/mqtt/debug_info.py:53
Integration: Switch (documentation, issues)
First occurred: 11:10:45 (7 occurrences)
Last logged: 11:10:45
Error adding entities for domain switch with platform mqtt
Error while setting up mqtt platform for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 614, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 778, in add_to_platform_finish
await self.async_added_to_hass()
File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 657, in async_added_to_hass
await super().async_added_to_hass()
File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 247, in async_added_to_hass
await super().async_added_to_hass()
File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 321, in async_added_to_hass
await self._availability_subscribe_topics()
File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 397, in _availability_subscribe_topics
self._availability_sub_state = await async_subscribe_topics(
File "/usr/src/homeassistant/homeassistant/components/mqtt/subscription.py", line 94, in async_subscribe_topics
await requested.resubscribe_if_necessary(hass, current)
File "/usr/src/homeassistant/homeassistant/components/mqtt/subscription.py", line 47, in resubscribe_if_necessary
debug_info.add_subscription(self.hass, self.message_callback, self.topic)
File "/usr/src/homeassistant/homeassistant/components/mqtt/debug_info.py", line 53, in add_subscription
debug_info = hass.data[DATA_MQTT_DEBUG_INFO]
KeyError: 'mqtt_debug_info'
EDIT: there’s an issue open,
2022.2.3 Mqtt worked
2022.2.4 Mqtt broken.
All mqtt communication dependent devices not updating HA
Look at post directly in front of yours
There was a change to MQTT in the .4 release. This change breaks mine as well as others. There is now an open Github issue.
https://github.com/home-assistant/core/issues/66128
Looks like .4 has been pulled
Yes, this update killed my MQTT server. I did not really need the data provided by MQTT right now, so I just disabled my MQTT server. That stopped all the error messages.
As scenes have states since 2022.2: will the state of a group of scenes also be calculated (like for a group of persons, switches, …)?
As the state of the scene is the last time it was activated, what do you propose the combined state of a group of scenes would be?
@varenderpsaround (maybe you aren’t listening any more, but i don’t think you answered my question about OS version. I found this that may confirm the relationship with the OS update 7.3
Should be the last time one of the group members/scenes was activated.
Makes sense, although I don’t make much use of scenes so I cannot test.
Would it make sense if I open a feature request for this?
That link leads to a dead-end (or my router blocked it as malware,) I found a ticket Here That talks about my issue. Wonderful. Doesn’t help me at all bc they just reverted a snapshot, which I tried, which didn’t work. I’ve tried reinstalling zha, won’t find coordinator. I’ve tried adding stuff to the config file, still won’t find coordinator. idk, If the zigbee hub I bought which someone recently said in my mention “is a solution” actually works then fine, but I genuinely think I have to rebuild my home assistant entirely or some shit because I can’t get zha to even recognize the coordinator right now.
(I really thought growing pains like these 100’s and 100’s of issues replying to this singular update were behind us)