Config entry has already been setup for Shelly devices after 2024.5.1 with Gen1 devices #116975

coserotondo · 2024-05-07T07:50:50Z

❗ Please do not post "me too" or "I have the same issue comments" as it clutters this issue and notifies everyone who is subscribed to it, which will drive people away who could have helped solve the problem. Instead, give this issue a thumbs up, and post logs requested in #116975 (comment)

The problem

Starting with 2024.5.1 at any HA restart I've [homeassistant.config_entries] Error and the entities are related to Shelly Integration. After HA restart, the affected entities are unavailable and I have to manually reload the integration to make them available again.
Attached the diagnostics of one Shelly affected devices: Letto Monte Camera Rosa.

What version of Home Assistant Core has the issue?

core-2024.5.2

What was the last working version of Home Assistant Core?

core-2024.4.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

config_entry-shelly-696dfd20befd67dcebd37c4a7aea8378.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-05-07 09:24:17.075 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Letto Monte Camera Rosa for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 234, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2024-05-07 09:24:17.128 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Letto Monte Camera Rosa for button
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/button/__init__.py", line 69, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2024-05-07 09:24:17.180 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Letto Monte Camera Rosa for cover
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/cover/__init__.py", line 241, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2024-05-07 09:24:17.190 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Letto Monte Camera Rosa for event
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/event/__init__.py", line 67, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2024-05-07 09:24:17.241 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Letto Monte Camera Rosa for light
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 675, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2024-05-07 09:24:17.260 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Letto Monte Camera Rosa for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 134, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2024-05-07 09:24:17.284 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Letto Monte Camera Rosa for switch
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/switch/__init__.py", line 94, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2024-05-07 09:24:17.296 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Letto Monte Camera Rosa for update
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 118, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2024-05-07 09:24:17.313 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Letto Monte Camera Rosa for valve
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/valve/__init__.py", line 111, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!

Additional information

No response

The text was updated successfully, but these errors were encountered:

home-assistant · 2024-05-07T08:58:50Z

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)}}

thecode · 2024-05-07T11:09:06Z

Thanks @coserotondo. We have seen this error but couldn't find why it happen. Maybe with additional info from you we can identify the root cause better.

Does it happen only on Gen1 devices?
How often does it happen? (For me it takes hours to reproduce so if someone can reproduce faster maybe we can get more data)
Do you have automations related to the problematic devices?
Does it happen on different devices each time?

Can you reproduce it with debug logging enabled for Shelly integration?
Please add the following to configuration.yaml, restart home assistant and if the error occurs attach the log.

logger:
  default: info
  logs:
    aioshelly: debug 
    homeassistant.components.shelly: debug

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

Thanks.

coserotondo · 2024-05-07T11:57:18Z

It happened 2 times only after HA update and consequent HA restart (first 2024.5.1 and then 2024.5.2).

Not always the same Shelly devices but all Gen1. I've automations attached to some of them.

I put the debug options and tried to manual restart HA. Logs attached but I had no issue this time.

Now I stopped the debug (I've 51 Shellyes...). What I can do is to enable the debug option before the next update to observe what happens after the restart.

Any other suggestions? Maybe the logs contains useful info?

Thanks.

home-assistant_shelly_2024-05-07T11-47-54.099Z.log

ChirpyTurnip · 2024-05-08T01:35:19Z

I have the same problem (only Gen1 devices) but want to note that immediately after the HA restart (when it says "Home Assistant has Started!") all the Shelly devices are found and random testing shows that they appear to work as expected when operated.

Within 60 seconds however they are all lost again - so it is not the case that they never get found after a restart.....they are found and then lost, and then found again after reloading the integrations.

In the meantime is there an easy/automated way to cause the Shelly devices to reload? Doing them one at a time is rather painful, especially from mobile.

thecode · 2024-05-08T07:14:36Z

@ChirpyTurnip please follow #116975 (comment) and provide log. Thanks 👍

zollak · 2024-05-08T09:23:05Z

hi all, exactly the same here. I have had no issues with HA Core 2024.4 and this comes with 2024.5.x...

I have 24 Shelly devices. Here is the same log entry one of them:

2024-05-07 23:07:03.744 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry ZS11-Shutter Bedroom Girls Door for update
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 118, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!

The name of the shelly device here is: ZS11-Shutter Bedroom Girls Door

Versions I have (supervisors updated couple of minutes ago):
Core: 2024.5.2
Supervisor: 2024.05.1
Operating System: 12.2
Frontend: 20240501.1

Based on the log entry, it seems the issue relates for async_setup_entry, that might changed in 2024.5.0. I have found this blog post that might helps:
https://developers.home-assistant.io/blog/2024/04/13/deprecate_async_track_state_change/

thecode · 2024-05-08T10:22:04Z

@zollak please follow #116975 (comment) and provide log. Thanks 👍

thecode · 2024-05-08T12:13:14Z

Please no need to comment that you have it also, it just spams the issue. Follow #116975 (comment) and provide logs.

Thanks 👍

zollak · 2024-05-08T13:17:38Z

@zollak please follow #116975 (comment) and provide log. Thanks 👍

I did the debugging. I don't want to attach here my log, it contains too much sensitive info. I'm trying to filter it somehow...

We are currently tracking down a problem with duplicate config entry setup in #117088 and #116975, however since the error does now show which config entry has the issue, finding the source has been difficult.

ChirpyTurnip · 2024-05-08T19:48:14Z

For me the reproduction of the issue is fast and reliable --> Restart, count to 100, instant chaos! :-)

Here are my logs from running to restart to config reloads.....

home-assistant_shelly_2024-05-08T01-24-19.494Z_CLEAN.log

bdraco · 2024-05-08T20:33:24Z

A handful of the shelly code owners have reviewed the code and can't find a path to allow this to happen under normal circumstances. Some of us have spent a few hours staring at the code, looking for a problem. At this point, it might be something corrupting the internal asyncio state.

Can you try running in safe mode to see if you can still reproduce the problem?

Additionally, if it is an unsafe thread operation corrupting the asyncio state, https://community.home-assistant.io/t/2024-5-tracking-down-instability-issues-caused-by-integrations/724441 can help you uncover it. Follow the steps in Enabling asyncio debug mode at run time (preferred) and Using Home Assistant's built-in debug mode in 2024.5.x or later (preferred)

ChirpyTurnip · 2024-05-09T00:10:36Z

That doesn't sound super ideal - it would be better if it was an easy fix. :-)

The problem does not appear to occur in safe mode....but then in safe mode many things are broken. In normal mode I noted that not all the Shellies were impacted - some (a very small number) continued to operate.

I have attached what is hopefully the information are after:
HA_Safe Mode.zip
HA_Normal.zip

I hope this helps!

bdraco · 2024-05-09T01:33:09Z

Your callgrind files are impressive assuming they are 60s long. You have on of the busiest systems I have ever seen.

Normal Mode

solarcastapi is using quite a bit of cpu time
Some integration is encoding lots of json data with the stdlib python encoder
24227x state writes per minute
128859x debug log writes
watchman utils is using quite a bit of cpu time

Safe Mode

22812x state writes per minute
26983x debug log writes

bdraco · 2024-05-09T01:42:48Z

It might be that whichever integration is causing the issue is only doing the non-thread-safe operations at startup.

You might have to go the debugpy route instead to get asyncio debug enabled soon enough to catch it: https://community.home-assistant.io/t/2024-5-tracking-down-instability-issues-caused-by-integrations/724441 Enabling asyncio debug mode before startup (fallback plan)

ChirpyTurnip · 2024-05-09T02:11:18Z

Your callgrind files are impressive assuming they are 60s long. You have on of the busiest systems I have ever seen.

I can't claim a record...they are 600s long.....I wanted to make sure I captured the process of the Shelly devices coming on line, dropping off, and reloading... :-)

I will have a look at debugpy to see what it gives me.....just need to wrap up work so it will take me a couple of hours to get back to it....

ChirpyTurnip · 2024-05-09T04:30:12Z

OK....so this is all a little bit weird. It actually behaves better with the debugpy: entry in the configuration.yaml....like basically no issue. At one point one device dropped off (and came back by itself a few seconds later without intervention):

2024-05-09 15:55:20.921 ERROR (MainThread) [homeassistant.components.shelly] Error fetching Shelly-BookcaseLights data: Error fetching data: DeviceConnectionError()

Over several restart tests I still lost the occasional device (2 -3) and these needed to be reloaded, but not what I had previously where almost all of them had tapped out. However, I'm not actually 100% sure I'm doing it right as I'm not getting extra log files or anything. There was a weird console 'thing' that showed on the screen but it didn't linger. I have also (briefly set) this in the config before restarting:

#Logging
logger:
  default: info
  logs:
    homeassistant.core: debug
    custom_components.shelly: debug

That caused significantly more logging that just having the recommended entry in the config:

homeassistant:
  debug: true

This gave me this log dump, but ironically this also caused all the Shelly devices to fall off again:
home-assistant.zip

There is a pattern there.....but what it is a mystery!

Regardless, how do I actually use debugpy:? Adding it by itself doesn't seem to do much....

bdraco · 2024-05-09T12:02:12Z

OK....so this is all a little bit weird. It actually behaves better with the debugpy: entry in the configuration.yaml....like basically no issue.

Once debugpy is enable, it will turn on asyncio debug mode at startup https://docs.python.org/3/library/asyncio-dev.html which will log any unsafe operations and event loop blocks that it can detect. We need the log for when that is enabled. You'll see a lot of asyncio in the log when its turned on.

ChirpyTurnip · 2024-05-17T07:58:08Z

Needless to say the problem persists (not expecting it to be any different as nothing has changed). But a semi-off topic question from us sufferers.....

Is there any way to automate the reload of all the Shelly integrations?

Hitting them one at a time is a major drag.....I'm actively configuring things so HA is being restarted 10 - 20 times a day to load new configs....you can do the math on the number of clicks needed to restart 38 shellies manually every time....I'll need a new mouse by the end of this.... :-(

Thanks!

thecode · 2024-05-17T14:40:07Z

I am running a change that will be released on the next major release (2025.6.0) and it looks good for few days.
If you want I can explain how to patch your current version for it, but beware that if it doesn't work it will be hard to get back to an operational state on HA OS if it doesn't work.

ChirpyTurnip · 2024-05-17T22:38:51Z

I'm happy to wait....June is not too far away and the last thing I need is to completely break everything....it would take me longer to fix it than to wait :-)

coserotondo · 2024-05-18T06:15:05Z

I am running a change that will be released on the next major release (2025.6.0) and it looks good for few days. If you want I can explain how to patch your current version for it, but beware that if it doesn't work it will be hard to get back to an operational state on HA OS if it doesn't work.

June 24 or 25 ???

thecode · 2024-05-18T21:50:35Z

I am running a change that will be released on the next major release (2025.6.0) and it looks good for few days. If you want I can explain how to patch your current version for it, but beware that if it doesn't work it will be hard to get back to an operational state on HA OS if it doesn't work.

June 24 or 25 ???

24 😸

vistalba · 2024-05-19T05:32:15Z

Since the update which added the debugg logging I didn‘t run into this issue again. May something else in this update fixed that issue?

met67 · 2024-05-24T16:18:28Z

I have the same problem (only Gen1 devices) but want to note that immediately after the HA restart (when it says "Home Assistant has Started!") all the Shelly devices are found and random testing shows that they appear to work as expected when operated.

Within 60 seconds however they are all lost again - so it is not the case that they never get found after a restart.....they are found and then lost, and then found again after reloading the integrations.

In the meantime is there an easy/automated way to cause the Shelly devices to reload? Doing them one at a time is rather painful, especially from mobile.

@ChirpyTurnip I made a Auto Entities card to streamline the reloading of unavailable devices:

type: custom:auto-entities
card:
  type: entities
  title: Shelly devices unavailable
  show_header_toggle: false
filter:
  include:
    - domain: light
      integration: shelly
      state: unavailable
      options:
        tap_action:
          action: call-service
          service: homeassistant.reload_config_entry
          data:
            entity_id: this.entity_id
    - domain: switch
      integration: shelly
      state: unavailable
      options:
        tap_action:
          action: call-service
          service: homeassistant.reload_config_entry
          data:
            entity_id: this.entity_id
    - domain: cover
      integration: shelly
      state: unavailable
      options:
        tap_action:
          action: call-service
          service: homeassistant.reload_config_entry
          data:
            entity_id: this.entity_id
  exclude: []

bdraco · 2024-05-24T21:07:43Z

2024.5.5 has a stripped down version of the changes coming in 2024.6.x. There is a chance it might improve the situation while we are waiting for 2024.6.x to ship.

thecode · 2024-05-25T20:33:36Z

Hi @ChirpyTurnip @zollak @met67 can you update to 2024.5.5 and verify if it still happen? it would be good to know before next release.

Thanks 👍

coserotondo · 2024-05-25T21:48:21Z

So far all good ! Il giorno sab 25 mag 2024 alle 22:34 Shay Levy ***@***.***> ha scritto:

…

Hi @ChirpyTurnip <https://github.com/ChirpyTurnip> @zollak <https://github.com/zollak> @met67 <https://github.com/met67> can you update to 2024.5.5 and verify if it still happen? it would be good to know before next release. Thanks 👍 — Reply to this email directly, view it on GitHub <#116975 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5CAQBAJ2KBOINZKUGO4U6TZEDYTRAVCNFSM6AAAAABHKOEDVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGQZTANZQGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

vistalba · 2024-05-26T04:55:23Z

@thecode For me it still happens. Today morning a USB powered Shelly H&T is unavailable.

met67 · 2024-05-26T06:06:35Z

Hi @ChirpyTurnip @zollak @met67 can you update to 2024.5.5 and verify if it still happen? it would be good to know before next release.

Thanks 👍

After a couple of restart, everything’s fine…

ChirpyTurnip · 2024-05-26T06:50:57Z

Hi!

Sorry for the delay in responding I've not be around much this weekend. I can however (happily) confirm that after about 6 restarts and a couple of full reboots the Shelly devices all come back online and stay online!! Yay!!

@vistalba - I have some H&T units too.....I need to leave it for a bit to see if they phone home as expected. If they do not I will post an update, if you hear nothing than all is well on my end.

Special thanks to @met67 - it's a tidy solution! I have a few other things that sometimes need a kick so I will be keeping your snippet as it works perfectly! :-)

:-)

vistalba · 2024-05-26T07:01:01Z

Slightly updated the above snipped to also include Sensors (H&T, D&W) which also are affected:

type: custom:auto-entities
card:
  type: entities
  title: Shelly devices unavailable
  show_header_toggle: false
filter:
  include:
    - domain: light
      integration: shelly
      state: unavailable
      options:
        tap_action:
          action: call-service
          service: homeassistant.reload_config_entry
          data:
            entity_id: this.entity_id
    - domain: switch
      integration: shelly
      state: unavailable
      options:
        tap_action:
          action: call-service
          service: homeassistant.reload_config_entry
          data:
            entity_id: this.entity_id
    - domain: cover
      integration: shelly
      state: unavailable
      options:
        tap_action:
          action: call-service
          service: homeassistant.reload_config_entry
          data:
            entity_id: this.entity_id
    - domain: sensor
      integration: shelly
      state: unavailable
      options:
        tap_action:
          action: call-service
          service: homeassistant.reload_config_entry
          data:
            entity_id: this.entity_id
  exclude: []

zollak · 2024-05-27T08:55:12Z

Hi @ChirpyTurnip @zollak @met67 can you update to 2024.5.5 and verify if it still happen? it would be good to know before next release.

Thanks 👍

Hi, I have updated today my HA to 2024.5.5 and also came updates for Shelly devices v1.3.2 (the previous was v1.3.1). I also updated all my Shelly devices and HA as well.

I made system reboot as well and after a couple of restart, everything’s fine…

thecode · 2024-06-07T08:13:23Z

I am closing this issue for now, if anyone still experiencing Config entry has already been setup after 2024.6.0 please create a new issue with logs.

Thanks everyone for helping with logs

bieniu added the integration: shelly label May 7, 2024

home-assistant bot assigned balloob, bieniu, thecode and chemelli74 May 7, 2024

home-assistant bot assigned bdraco May 7, 2024

bieniu changed the title ~~[homeassistant.config_entries] Error for some Shelly devices after 2024.5.1~~ Config entry has already been setup for Shelly devices after 2024.5.1 May 7, 2024

bdraco changed the title ~~Config entry has already been setup for Shelly devices after 2024.5.1~~ Config entry has already been setup for Shelly devices after 2024.5.1 with Gen1 devices May 7, 2024

bdraco mentioned this issue May 8, 2024

Improve config entry has already been setup error message #117091

Merged

20 tasks

This comment was marked as duplicate.

Sign in to view

bdraco added the non-thread-safe operation label May 9, 2024

thecode mentioned this issue May 10, 2024

Add debug logging home-assistant-libs/aioshelly#563

Merged

bdraco mentioned this issue May 11, 2024

Ensure config entry operations are always holding the lock #117214

Merged

20 tasks

thecode mentioned this issue May 13, 2024

Shelly Door/Window 2 (battery operated, gen1) goes unavailable and stops working until integration reload #116948

Closed

davesmeghead mentioned this issue May 13, 2024

Panel disconnects every 15 mins with 150+ log messages davesmeghead/visonic#112

Closed

bieniu mentioned this issue May 15, 2024

Shelly disconnecting randomly #117430

Closed

thecode mentioned this issue May 18, 2024

Shelly Gen1 devices going offline in 2024.5.* #117710

Closed

thecode mentioned this issue May 19, 2024

Shelly H&T Plus Gen 2 intermittently unavailable in 2024.5.x #117670

Closed

bdraco mentioned this issue May 20, 2024

Fix race in config entry setup #117756

Merged

20 tasks

bieniu mentioned this issue May 20, 2024

result = await component.async_setup_entry(hass, self) For Shelly Devices #117803

Closed

thecode mentioned this issue May 20, 2024

Shelly Plus Smoke configured but without entities #117818

Closed

thecode mentioned this issue May 26, 2024

Shelly Motion sensors unavailable while CoAP messages are coming in #117734

Closed

thecode closed this as completed Jun 7, 2024

mpartoglou mentioned this issue Jun 28, 2024

Device Connection Error - Shelly devices after 2024.6.4 with Gen1 devices #120787

Closed

github-actions bot locked and limited conversation to collaborators Jul 7, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Config entry has already been setup for Shelly devices after 2024.5.1 with Gen1 devices #116975

Config entry has already been setup for Shelly devices after 2024.5.1 with Gen1 devices #116975

coserotondo commented May 7, 2024 •

edited by bdraco

Loading

home-assistant bot commented May 7, 2024

thecode commented May 7, 2024

coserotondo commented May 7, 2024

ChirpyTurnip commented May 8, 2024

thecode commented May 8, 2024

zollak commented May 8, 2024 •

edited

Loading

thecode commented May 8, 2024

thecode commented May 8, 2024

zollak commented May 8, 2024

This comment was marked as duplicate.

ChirpyTurnip commented May 8, 2024

bdraco commented May 8, 2024

ChirpyTurnip commented May 9, 2024

bdraco commented May 9, 2024 •

edited

Loading

bdraco commented May 9, 2024

ChirpyTurnip commented May 9, 2024

ChirpyTurnip commented May 9, 2024

bdraco commented May 9, 2024

ChirpyTurnip commented May 17, 2024

thecode commented May 17, 2024

ChirpyTurnip commented May 17, 2024

coserotondo commented May 18, 2024

thecode commented May 18, 2024

vistalba commented May 19, 2024

met67 commented May 24, 2024

bdraco commented May 24, 2024

thecode commented May 25, 2024

coserotondo commented May 25, 2024 via email

vistalba commented May 26, 2024

met67 commented May 26, 2024

ChirpyTurnip commented May 26, 2024

vistalba commented May 26, 2024

zollak commented May 27, 2024

thecode commented Jun 7, 2024

Config entry has already been setup for Shelly devices after 2024.5.1 with Gen1 devices #116975

Config entry has already been setup for Shelly devices after 2024.5.1 with Gen1 devices #116975

Comments

coserotondo commented May 7, 2024 • edited by bdraco Loading

❗ Please do not post "me too" or "I have the same issue comments" as it clutters this issue and notifies everyone who is subscribed to it, which will drive people away who could have helped solve the problem. Instead, give this issue a thumbs up, and post logs requested in #116975 (comment)

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 May 7, 2024

thecode commented May 7, 2024

coserotondo commented May 7, 2024

ChirpyTurnip commented May 8, 2024

thecode commented May 8, 2024

zollak commented May 8, 2024 • edited Loading

thecode commented May 8, 2024

thecode commented May 8, 2024

zollak commented May 8, 2024

This comment was marked as duplicate.

ChirpyTurnip commented May 8, 2024

bdraco commented May 8, 2024

ChirpyTurnip commented May 9, 2024

bdraco commented May 9, 2024 • edited Loading

bdraco commented May 9, 2024

ChirpyTurnip commented May 9, 2024

ChirpyTurnip commented May 9, 2024

bdraco commented May 9, 2024

ChirpyTurnip commented May 17, 2024

thecode commented May 17, 2024

ChirpyTurnip commented May 17, 2024

coserotondo commented May 18, 2024

thecode commented May 18, 2024

vistalba commented May 19, 2024

met67 commented May 24, 2024

bdraco commented May 24, 2024

thecode commented May 25, 2024

coserotondo commented May 25, 2024 via email

vistalba commented May 26, 2024

met67 commented May 26, 2024

ChirpyTurnip commented May 26, 2024

vistalba commented May 26, 2024

zollak commented May 27, 2024

thecode commented Jun 7, 2024

coserotondo commented May 7, 2024 •

edited by bdraco

Loading

zollak commented May 8, 2024 •

edited

Loading

bdraco commented May 9, 2024 •

edited

Loading