Shelly 1, 2.5 and Dimmer cant be loaded with 2024.1.1 #107275

H4rl3k1n · 2024-01-05T18:19:08Z

The problem

I installed 2024.1.1, all shellys 1, 2.5 and dimmer were not loaded, Plug S and RGBW worked.
All my shellys have latest, original, firmware.
Seems Tasmota flashed shellys are working (response from facebook-group).
Also it seems only docker version has a problem.

What version of Home Assistant Core has the issue?

2024.1.1

What was the last working version of Home Assistant Core?

2024.1.0

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Shelly

Link to integration documentation on our website

https://www.home-assistant.io/integrations/shelly/

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

home-assistant · 2024-01-05T18:19:15Z

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of shelly can trigger bot actions by commenting:

@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign shelly Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

shelly documentation
shelly source
_{^{(message by IssueLinks)}}

mbo18 · 2024-01-05T18:20:57Z

Any log? Just upgraded from 2023.12.3 to 2024.1.1 and the integration does not load anymore. Got these logs:

Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 19:11:52 (3 occurrences)
Last logged: 19:11:52

Error setting up entry Volet roulant Cuisine for shelly
Error setting up entry Shelly EM E4550e for shelly
Error setting up entry Volet roulant Salon 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'

I have 2 shelly 2.5 and one Shelly EM on latest firmware. All do not work now.

H4rl3k1n · 2024-01-05T18:22:46Z

yes i had the same log, keyError "gen"

jorgempinto · 2024-01-05T18:27:49Z

I have exactly the same issue after upgrading from 2024.1.0 -> 2024.1.1

mpepping · 2024-01-05T18:30:58Z

+1 .. OK after downgrading to 2024.1.0

crudolphy · 2024-01-05T18:51:19Z

Please see my comment in issue 107277

playabeach · 2024-01-05T18:55:12Z

Same problem here, since the update, I hope it will be solved soon

Cyrelion · 2024-01-05T19:00:23Z

downgrade via ssh "ha core update --version 2024.1.0" worked for now

lobolobo · 2024-01-05T19:01:42Z

Any log? Just upgraded from 2023.12.3 to 2024.1.1 and the integration does not load anymore. Got these logs:

Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 19:11:52 (3 occurrences)
Last logged: 19:11:52

Error setting up entry Volet roulant Cuisine for shelly
Error setting up entry Shelly EM E4550e for shelly
Error setting up entry Volet roulant Salon 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'

I have 2 shelly 2.5 and one Shelly EM on latest firmware. All do not work now.

Same problem here ...

g1za · 2024-01-05T19:04:28Z

Here as well (Shelly 2.5)
`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()

jduro · 2024-01-05T19:06:51Z

Any log? Just upgraded from 2023.12.3 to 2024.1.1 and the integration does not load anymore. Got these logs:

Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 19:11:52 (3 occurrences)
Last logged: 19:11:52

Error setting up entry Volet roulant Cuisine for shelly
Error setting up entry Shelly EM E4550e for shelly
Error setting up entry Volet roulant Salon 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'

I have 2 shelly 2.5 and one Shelly EM on latest firmware. All do not work now.

Same problem here, downgraded to 2024.1.0

thecode · 2024-01-05T19:09:11Z

Thanks, no need for additional "same problem", logs shows the problem, working on a fix

lobolobo · 2024-01-05T19:11:44Z

Thanks, no need for additional "same problem", logs shows the problem, working on a fix

@thecode, thanks for the info.

guillempages · 2024-01-05T19:58:15Z

If this helps, in my case only some of my Shelly 2.5 are having this issue, but others work normally. All of them are on the same FW, and I could not see any differences in the (on-device) configuration.

thecode · 2024-01-05T20:04:48Z

If this helps, in my case only some of my Shelly 2.5 are having this issue, but others work normally. All of them are on the same FW, and I could not see any differences in the (on-device) configuration.

Yes, if the device was added after we introduced support for Gen2 (although it is Gen1) it will work since we store the Gen.
The issue is due to a missing Gen value for older devices.

micium · 2024-01-05T20:07:43Z

The shelly integration didn't have a good start to the new year, first problem with the shelly 2nd gen powered on battery (like shelly smoke), after the 2024.1.1 patch .. total disaster, I restored the 2012.12.4 backup and everything works fine. I hope for a resolution soon since I have more than 30 shellies installed.

g1za · 2024-01-05T20:15:50Z

If this helps, in my case only some of my Shelly 2.5 are having this issue, but others work normally. All of them are on the same FW, and I could not see any differences in the (on-device) configuration.

Yes, if the device was added after we introduced support for Gen2 (although it is Gen1) it will work since we store the Gen. The issue is due to a missing Gen value for older devices.

If needed, as a quick workaround, I would be open to manually update some files, if possible, to add the 'gen' value before the next release (but also to align to the current approach those devices added before the support for Gen2 was introduced).

johndoe0815 · 2024-01-05T20:42:20Z

Will it work again with the pull request after updating from 2024.1 to the next 2024.2 or is this gen lost and can't be recovered?

salvisbh · 2024-01-05T20:42:24Z

I don't know if it helps to solve the problem: With 2024.1.0 a Shelly 2.5 was no longer loaded with a log entry that the firmware version was too old. In reality, the version was too new, I had installed the latest beta of Shelly. After a downgrade to the official Shelly version, the Shelly 2.5 was recognized correctly. I then installed 2024.1.1 with the result that my Shelly 1PM is no longer detected. In my opinion, these also run with a beta firmware 20230913-113709/v1.14.0-gcb84623

g1za · 2024-01-05T20:57:16Z

Don't worry guys, the PR above is being approved and is almost there to fix the problem. ;)
These are things that sometimes happen but be confident in the development team!

anpak · 2024-01-05T22:20:25Z

Don't worry guys, the PR above is being approved and is almost there to fix the problem. ;) These are things that sometimes happen but be confident in the development team!

Thank you! How long the PR takes? Have I to downgrade my Home Assistant or should I wait for the new HA version?

matthewharrington · 2024-01-05T22:22:44Z

I downgraded which was easy. There isn't anything in 2024.1.1 that is required for functionality

starkillerOG · 2024-01-05T22:26:43Z

The PR will be included in HA 2024.1.2 which is currently scheduled for Jan 12th, but this could always be a bit earlier or later.

If you want to solve it now, you can downgrade back to HA 2024.1.0 and wait for HA 2024.1.2 to be ready.

Or stay on HA 2024.1.1, remove the shelly integration, restart HomeAssistant, setup the shelly integration again. This will add the missing key in your configuration data and it schould work again. BE WARNED: this will reset the device and entity names and entity IDs, therefore you will need to set those back otherwise your automations may not work anymore.

bieniu · 2024-01-05T23:32:15Z

I apologise to everyone for this issue, it's my stupid mistake. Thanks to @thecode for the quick fix.

b3nj1 · 2024-01-05T23:37:10Z

If you are impatient and don't what to remove/add-back the device or go back to an older HA version, this worked for me. Using the SSH add-on, use the editor of your choice to add , "gen": 1 (don't forget the comma) to the device's corresponding data section in /root/config/.storage/core.config_entries, and restart HA.

Eg,

      {
        "entry_id": "b2ad817589a24c3ec816f0a8c1418da1",
        "version": 1,
        "minor_version": 1,
        "domain": "shelly",
        "title": "shellyswitch25-E8DB84A20CCA",
        "data": {
          "host": "10.0.1.59",
          "sleep_period": 0,
          "model": "SHSW-25",
          "gen": 1
        },
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "zeroconf",
        "unique_id": "E8DB84A20CCA",
        "disabled_by": null
      },

g1za · 2024-01-06T01:24:48Z

use the editor of your choice to add , "gen": 1 (don't forget the comma) to the device's corresponding data section in /root/config/.storage/core.config_entries, and restart HA.

Eg,
      {
        "entry_id": "b2ad817589a24c3ec816f0a8c1418da1",
        "version": 1,
        "minor_version": 1,
        "domain": "shelly",
        "title": "shellyswitch25-E8DB84A20CCA",
        "data": {
          "host": "10.0.1.59",
          "sleep_period": 0,
          "model": "SHSW-25",
          "gen": 1
        }

Thanks a lot; this is exactly what I was looking for.
It worked for me as well and now I am on 2024.1.1
Cheers!

doronazl · 2024-01-06T02:40:30Z

same here, had to remove and re-add the device.

micium · 2024-01-06T06:52:48Z

If you are impatient and don't what to remove/add-back the device or go back to an older HA version, this worked for me. Using the SSH add-on, use the editor of your choice to add , "gen": 1 (don't forget the comma) to the device's corresponding data section in /root/config/.storage/core.config_entries, and restart HA.

Eg,
      {
        "entry_id": "b2ad817589a24c3ec816f0a8c1418da1",
        "version": 1,
        "minor_version": 1,
        "domain": "shelly",
        "title": "shellyswitch25-E8DB84A20CCA",
        "data": {
          "host": "10.0.1.59",
          "sleep_period": 0,
          "model": "SHSW-25",
          "gen": 1
        },
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "zeroconf",
        "unique_id": "E8DB84A20CCA",
        "disabled_by": null
      },

Thanks a lot !! Can I add the "gen" key before the update to 2024.1.1 ?

mbo18 · 2024-01-06T08:32:44Z

Thanks a lot !! Can I add the "gen" key before the update to 2024.1.1 ?

Yes

Diegocampy · 2024-01-06T08:43:36Z

Only for infor other people, in my case, with update to 2024.1.1 all Shelly work fine in Shelly App, and in Home Assistant:

Shelly 1
Shelly Air
Shelly Plus 1 PM
Shelly 1 PM
Shelly EM3
Shelly Bulb 1
Don't ask me the reason, I have only update Home assistant 🤷🏻‍♂️

xpdm · 2024-01-06T09:54:24Z

see breakchange: https://www.home-assistant.io/blog/2024/01/03/release-20241/

"Shelly
The minimum supported firmware version for generation 1 devices is 1.11.0 (2021-07-15). The minimum supported firmware version for generation 2 devices is 1.0.0 (2023-08-03).

You must update your devices to the firmware versions listed or newer.

(@bieniu - #105384) (documentation)"

micium · 2024-01-06T09:54:56Z

Thanks a lot !! Can I add the "gen" key before the update to 2024.1.1 ?

Yes

It worked for me as well and now I am on 2024.1.1
Cheers!

DataBitz · 2024-01-06T10:20:58Z

Only for infor other people, in my case, with update to 2024.1.1 all Shelly work fine in Shelly App, and in Home Assistant:

Shelly 1

Shelly Air

Shelly Plus 1 PM

Shelly 1 PM

Shelly EM3

Shelly Bulb 1
Don't ask me the reason, I have only update Home assistant 🤷🏻‍♂️

Shelly Dimmer 2 were affected for me, but the workaround from @mclem fixed them.

CamFlyerCH · 2024-01-06T14:49:15Z

I confirm fixed with 2024.1.2 ! Thanks a lot for the quick fix ! It affected 4 of my 7 Shelly devices including also a 3EM.

fredtj · 2024-01-06T22:39:49Z

isn't fixed for me, i see the below. do you want a new bug report?

home-assistant            | Traceback (most recent call last):
home-assistant            |   File "/usr/local/lib/python3.11/site-packages/aioshelly/block_device/device.py", line 184, in _async_init
home-assistant            |     await self.initialize(True)
home-assistant            |   File "/usr/local/lib/python3.11/site-packages/aioshelly/block_device/device.py", line 123, in initialize
home-assistant            |     self._shelly = await get_info(
home-assistant            |                    ^^^^^^^^^^^^^^^
home-assistant            |   File "/usr/local/lib/python3.11/site-packages/aioshelly/common.py", line 103, in get_info
home-assistant            |     raise fw_error
home-assistant            | aioshelly.exceptions.FirmwareUnsupported: {'type': 'SHHT-1', 'mac': '44179321DC27', 'auth': False, 'fw': '20210710-130145/v1.11.0-g12a9327-master', 'sleep_mode': True}```

thecode · 2024-01-06T23:29:21Z

@fredtj as a general approach you should avoid commenting on a closed issue (as some developers stop following it when it is closed) and create a new issue, this specific case is a different issue anyhow.

btw, I checked with the core team they are not charged per issue 😄

home-assistant bot added the integration: shelly label Jan 5, 2024

home-assistant bot assigned balloob, bieniu, thecode and chemelli74 Jan 5, 2024

home-assistant bot assigned bdraco Jan 5, 2024

thecode mentioned this issue Jan 5, 2024

Error setting up entry shellyuni-E8DB84D23B4B for shelly #107277

Closed

thecode mentioned this issue Jan 5, 2024

Fix Shelly missing Gen value for older devices #107294

Merged

20 tasks

mib1185 mentioned this issue Jan 5, 2024

Shelly gen 1 KeyError: 'gen' in HA patch 2024.1.1, working in HA 2024.1.0 #107276

Closed

r0b3rt74 mentioned this issue Jan 5, 2024

All Shelly's offline after upgrade to 2024.1.1 #107314

Closed

bdraco closed this as completed in #107294 Jan 5, 2024

bdraco mentioned this issue Jan 6, 2024

Shelly EM and Shelly1PM no longer working after 2024.1.1 #107325

Closed

Voxxie mentioned this issue Jan 6, 2024

SHPLG-1: Shelly Plug not working with latest firmware (1.9.4) at 2024.1.x #107352

Closed

This was referenced Jan 6, 2024

Shelly devices are not working any more since 2024.01.1 update #107344

Closed

some of shelly devices stopped working after HA update #107359

Closed

This was referenced Jan 6, 2024

Retain support for Shelly 2.5 and 1PM running v1.8.5 #107235

Closed

Shelly Plug Gen 1 and Shelly Plug S Gen 1 no longer working in 2024.1.1 #107375

Closed

thecode mentioned this issue Jan 6, 2024

Change the minimum supported gen1 firmware to 1.9.0 home-assistant-libs/aioshelly#474

Merged

kiler129 mentioned this issue Jan 15, 2024

Shelly plus 1PM connectivity issues with FW version >1.0.0 #107220

Closed

github-actions bot locked and limited conversation to collaborators Feb 6, 2024

Shelly 1, 2.5 and Dimmer cant be loaded with 2024.1.1 #107275

Shelly 1, 2.5 and Dimmer cant be loaded with 2024.1.1 #107275

Comments

H4rl3k1n commented Jan 5, 2024

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

home-assistant bot commented Jan 5, 2024

mbo18 commented Jan 5, 2024 • edited Loading

H4rl3k1n commented Jan 5, 2024

jorgempinto commented Jan 5, 2024

mpepping commented Jan 5, 2024 • edited Loading

crudolphy commented Jan 5, 2024

playabeach commented Jan 5, 2024

Cyrelion commented Jan 5, 2024

lobolobo commented Jan 5, 2024 • edited Loading

g1za commented Jan 5, 2024 • edited Loading

jduro commented Jan 5, 2024

thecode commented Jan 5, 2024

lobolobo commented Jan 5, 2024 • edited Loading

guillempages commented Jan 5, 2024

thecode commented Jan 5, 2024

micium commented Jan 5, 2024

g1za commented Jan 5, 2024 • edited Loading

johndoe0815 commented Jan 5, 2024

salvisbh commented Jan 5, 2024

g1za commented Jan 5, 2024 • edited Loading

anpak commented Jan 5, 2024

matthewharrington commented Jan 5, 2024

starkillerOG commented Jan 5, 2024

bieniu commented Jan 5, 2024

b3nj1 commented Jan 5, 2024

g1za commented Jan 6, 2024 • edited Loading

doronazl commented Jan 6, 2024

micium commented Jan 6, 2024

mbo18 commented Jan 6, 2024

Diegocampy commented Jan 6, 2024

xpdm commented Jan 6, 2024

micium commented Jan 6, 2024

DataBitz commented Jan 6, 2024

CamFlyerCH commented Jan 6, 2024

fredtj commented Jan 6, 2024 • edited Loading

thecode commented Jan 6, 2024 • edited Loading

mbo18 commented Jan 5, 2024 •

edited

Loading

mpepping commented Jan 5, 2024 •

edited

Loading

lobolobo commented Jan 5, 2024 •

edited

Loading

g1za commented Jan 5, 2024 •

edited

Loading

lobolobo commented Jan 5, 2024 •

edited

Loading

g1za commented Jan 5, 2024 •

edited

Loading

g1za commented Jan 5, 2024 •

edited

Loading

g1za commented Jan 6, 2024 •

edited

Loading

fredtj commented Jan 6, 2024 •

edited

Loading

thecode commented Jan 6, 2024 •

edited

Loading