Shelly Gen1 devices going offline in 2024.5.*

[mpartoglou]

The problem

Hi,

I recently upgraded to 2024.5.* (and am currently on 2024.5.4). As part of this upgrade, I noticed that my Shelly Gen 1 devices (Shelly 1, Shelly Dimmers) are having intermittent connection issues, which appear as the following:

1. Shelly device moves into a state where it becomes unresponsive in the front-end, but is still showing as active. The error is DeviceConnectionError
2. Shelly device still operates and responds via hitting the Shelly device URL
3. Shelly device, when hit via the URL directly still updates inside Home Assistant (i.e. I can receive new status updates)
4. After some period of this, the Shelly devices go offline fully in Home Assistant and via URL
5. I can force reconnect the devices (via Unifi) to start the cycle again

Initially I thought it was my Shelly units and/or my Unifi network (based on other posts i've read), however I can hit the Shelly via URL long after they go offline / unresponsive inside Home Assistant. This is also only happening to gen 1 devices (I have Shelly 1 Plus devices which are rock solid).

Currently, I have 18 devices offline, however I have some devices still operating as expected - I cannot see any discernable difference between those online this morning vs. offline (e.g. connected to same Unifi point, running same F/W, CoIoT Enabled).

Notes:

• Shelly devices firmware: 20230913-112003/v1.14.0-gcb84623 (I have kept a few on v1.11 and am experiencing the same issues)
• Shelly devices us CoIoT connected via ip:port to HASS
• Shelly devices are all fixed IPs (but I put some to roaming and same issue)
• Unifi devices are UDR, U6 Pro, Nano-HD, U6-Lite (all running latest available firmware)
• I have disabled every firewall rule, all running on a single network
• HASS Version: 2024.5.4

I've run out of ideas to test myself, my last idea was that the Gen 1 devices are getting overwhelmed by too many requests (I know they only support two concurrent connections); then my unifi reconnect command resets this back to normal

What version of Home Assistant Core has the issue?

2024.5.4

What was the last working version of Home Assistant Core?

2024.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Shelly

Link to integration documentation on our website

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

Diagnostics information

Unifi Entry for the device - Living Room Dimmer
config_entry-unifi-5364ff83f7300048c3319173367d1068 (1).json

Shelly Entry for same device
[config_entry-shelly-445d0d281f721c56d3ad74de6dc6882e.json](https://github.com/home-assi

Full logs from current session
home-assistant_2024-05-18T21-38-18.184Z.log
stant/core/files/15366901/config_entry-shelly-445d0d281f721c56d3ad74de6dc6882e.json)

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

• I had previously used Shelly4HASS (for a number of years), but upgraded to Core Shelly a few months ago. I had no issues once I moved (but noting this in-case something in my legacy Shelly4HASS install could be causing an issue.

• I have logging enabled on some of the Shelly devices and can share the logs.

• I notice the issue occurs in the evening more commonly when interacting with the shelly devices (e.g. they will work for an hour or two then drop off)

[home-assistant]

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]

Hi @mpartoglou thanks for providing a long because it saves times going over the same questions. You have exactly the same issue as in #116975

Duplicate of #116975