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

[muibeta]

The problem

I started using four Shelly H&T Plus Gen 2 under Home Assistant 2025.5.3. Each Shelly H&T independently was displayed as unavailable very 15-30 minutes for 15-30 minutes. Typically, two of the four were unavailable at any moment. As a workaround, I restored back to 2024.4 and configure the four Shelly H&T. (They were not in use in that backup.) All four Shelly H&T have consistently reported their readings in Home Assistant since. I am running Home Assistant in virtual machine on a Synology NAS. The IP address of each Shelly H&T has been reserved in my home router. The LAN is a simple 192.168.1.2 - 192.168.1.255 range. The Shelly H&T Plus have up to date firmware (20240425-141825/1.3.0-ga3fdd3d).

What version of Home Assistant Core has the issue?

2024.5.3

What was the last working version of Home Assistant Core?

2024.4.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

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[bot]]

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

[muibeta]

When the issue was occurring in 2024.5.3, the logs were showing 8 Shelly timeout errors after only an hour. I attempted to duplicate the issue this morning and save any error logs. This was now as an update from 2024.4.4 to 2024.5.4. After several hours the unavailable issue has not reoccurred, and the logs do not report any Shelly errors! Apart from the change from 2024.5.3 to 2024.5.4, the only other difference this time was the order of configuring the outbound websockets and adding each Shelly H&T in the Shelly integration. When first trying out the Shelly H&Ts in 2024.5.3, they were added in the Shelly integration before the outbound websockets were configured. (The Shelly integration showed devices but no entities.) For the restore to 2024.4.4, the websockets were configured so, on adding the Shelly H&Ts, the Shelly integration showed entries as well as devices. In the update from 2024.4.4 to 2024.5.4, the websockets were pre-configured and all the Shelly H&Ts carried over in the Shelly integration (devices and entities).

[micclfr]

same here, loosing Shelly devices since 2024.5.3

[thecode]

Please do not post "same" without logs, while it might be the same it also might be different. There is one issue identified in https://github.com/home-assistant/core/issues/116975 and will be fixed in the next major release - 2024.6.0, however I can't guarantee that everyone is having the same issue. If you want someone to look at your logs please follow https://github.com/home-assistant/core/issues/116975#issuecomment-2098151285 and provide logs. Otherwise wait for next major release and create a new issue with logs if it still happen.