@reste_narquois Chris Warne
I have done everything you said and now all are back to normal. Dehumidifer is working, System monitor also working.
Today I update the HA OS with 11.3 and again my world is down 
. After OS update, the Zigbee2MQTT (witch is the most important for me) is down. Did you know something about this ? Sorry for not been in correct thread, but you prove to know what you do 
Thanks in advance
Strange behavior in the new automation UI.
I try to use Number Set but I can’t then select which entity to set there are no options.
Is this the official Zigbee2MQTT addon? I’m afraid I don’t use that, so can’t be of much help here.
If it is the addon you are using, I would go through a standard checklist (but no guarantees!):
It should tell you if the addon has started properly, and especially if it has found the Zigbee coordinator. A HAOS update might have affected this, so a restart of the machine could help here.
Otherwise, i would suggest posting or searching the threads in the Zigbee area of the forum where someone with more direct knowledge should be able to help.
I do and after a restart they are showing again which is also weird !
The OS 11.3 updates & Z2M conflictions are most likely related to this issue here
You should only have to refresh the page, not restart.
I tried refresh and clear cache before the restart
But they only came back after a restart
Please create an issue if you can replicate the bug again. Thank!
Hello Maciek,
I skipped the 2024.1.0 version and I’ve just updated to 2024.1.1 but all my shelly devices have stopped communication with HA. All of them (Gen1) updated to the latest available firmware.
Below the error I see in the log.
Any advice or should I roll back to the latest 2023 version for the moment?
Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 18:34:15 (8 occurrences)
Last logged: 18:38:08
Error setting up entry Tapparella studio for shelly
Error setting up entry Tapparella camera for shelly
Error setting up entry Tapparella bagno for shelly
Error setting up entry Tapparella soggiorno for shelly
Error setting up entry Irrigazione for shelly
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/shelly/__init__.py", line 131, in async_setup_entry
return await _async_setup_block_entry(hass, entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/shelly/__init__.py", line 201, in _async_setup_block_entry
await _async_block_device_setup()
File "/usr/src/homeassistant/homeassistant/components/shelly/__init__.py", line 168, in _async_block_device_setup
shelly_entry_data.block.async_setup()
File "/usr/src/homeassistant/homeassistant/components/shelly/coordinator.py", line 338, in async_setup
super().async_setup()
File "/usr/src/homeassistant/homeassistant/components/shelly/coordinator.py", line 139, in async_setup
hw_version=f"gen{self.entry.data[CONF_GEN]} ({self.model})",
~~~~~~~~~~~~~~~^^^^^^^^^^
KeyError: 'gen'
Logger: homeassistant.components.shelly
Source: helpers/update_coordinator.py:332
Integration: Shelly (documentation, issues)
First occurred: 18:37:42 (3 occurrences)
Last logged: 18:38:27
Error fetching Tapparella studio data: Error fetching data: DeviceConnectionError()
Even without entities, the target selector should be present.
For example, I have no fan, yet I have the selector for fan related services
I think sometimes the schema of a service takes a bit of time to load and you end up with a blank bloc without selectors. Usually this is sporadic, and waiting or refreshing the page fixes it.
It has been said already but please read the noteworthy changes before upgrading. You will find your answer there.
I read the noteworthy changes and it is stated which minimum firmware is required. Which I have as mentioned in my message.
Also there was a “bug” that was fixed with release 2024.1.1 but I still have this problem.
But please let me know where I can find the answer to my problem and I’m happy to go through it.
Sorry, i was too quick with my faulty conclusions.
Identified some strange behaviour with system monitor. Either due to OS update or 2024.1 update deactivated entities increased from 215 to 315, almost 10% of all my entities… There were various new veth entities, no idea what this is. Removing the complete system monitor integration and installing it again led to 215 entities. I think there is some bug.
In any case, wouldn’t some kind of system monitor selection/filterung during setup not be better? For example on high level: Ethernet, temperature, load, Disks, etc.
Happy New Year and thanks for another great release!
I am also experiencing the Shelly gen1 problem…the firmware was new enough, according to the changelog, but it seems they should have also been updated to use unicast instead of mcast (they were configured years ago and left alone). The problem is, though, that even with the newest firmware and the unicast set according to instructions, they’re still not working. Perhaps the integration requires an update?
seeing this:
Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 19:23:34 (1 occurrences)
Last logged: 19:23:34
Error setting up entry Dorm Studenten for shelly
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/shelly/__init__.py", line 131, in async_setup_entry
return await _async_setup_block_entry(hass, entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/shelly/__init__.py", line 201, in _async_setup_block_entry
await _async_block_device_setup()
File "/usr/src/homeassistant/homeassistant/components/shelly/__init__.py", line 168, in _async_block_device_setup
shelly_entry_data.block.async_setup()
File "/usr/src/homeassistant/homeassistant/components/shelly/coordinator.py", line 338, in async_setup
super().async_setup()
File "/usr/src/homeassistant/homeassistant/components/shelly/coordinator.py", line 139, in async_setup
hw_version=f"gen{self.entry.data[CONF_GEN]} ({self.model})",
~~~~~~~~~~~~~~~^^^^^^^^^^
KeyError: 'gen'
but only on 1 Shelly Switch, the others are/seem ok
dont think I had this on 2024.1.0 or in the betas.
edit/update
yep, downgrading to 2024.1.0 brings the switch back to life, no errors anymore and all functional
I have also issues with shelly. Multiple issues have been opened on Github, for example : Shelly 1, 2.5 and Dimmer cant be loaded with 2024.1.1 · Issue #107275 · home-assistant/core · GitHub
Nice that the Trend integration can be setup from the GUI! What I am missing is the sensor which is being watched. You have to specify it when creating the helper but after that it isn’t visible anywhere.
If you have several Trend helper and you have to check them out after some time it is not clear which helper belongs to which sensor.