Shelly Gen1 H&T measurements are not updated

[tush80]

The problem

Shelly H&T devices (gen 1) measurements are not updated in HA; H&T Plus, Flood, TRVs all seem to be working fine. That was not observed with version 2024.4.x and and seems to be happening on 2024.5.x Debug log and diagnostic data from some H&T devices is attached. The device with IP 192.168.88.54 was removed and added again, this is why there are more recent temperature updates in the screenshot but it did stop updating again. Reloading integration/restarting HA does not help. All have static IP addresses, CoIoT is setup as IP:Port

What version of Home Assistant Core has the issue?

core-2024.5.1

What was the last working version of Home Assistant Core?

core-2024.4.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Shelly

Link to integration documentation on our website

No response

Diagnostics information

config_entry-shelly-e8d255aeead21a964c48f741cba495ba.json config_entry-shelly-ff3189ceab3ae5ffc7336434856ddb2a.json config_entry-shelly-7aa429689fbe0f3d2fd35827a86ad87a.json home-assistant_shelly_2024-05-05T14-52-02.252Z.log

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

[bieniu]

Diagnostics files show that devices are not initialized. Please wake up the device before save a diagnostics file.

[tush80]

Hi @bieniu Even after waking the device, the diagnostics file still says not initialized. Anything else I can do? Thank you!

config_entry-shelly-ff3189ceab3ae5ffc7336434856ddb2a (1).json

[bieniu]

This means that data from the device does not reach the HA server. Is HT on the same subnet as the HA server? Has the IP address of the HA server not changed? Is unicast properly configured on the device?

[tush80]

HTs are on another subnet together with a working HT Plus; the IP of the HA server is static/verified correct, unicast is confgured according to the documentation - IP:port.

Based on the following part of the debug log, I assumed the communication to the HA server works:

Thanks for looking into this!

[bieniu]

Which firmware version do the devices use?

[tush80]

1.14.0

[thecode]

@tush80 can you provide a longer debug log that starts from HA startup and has messages from this device? The log you provided in the first post doesn't contain any messages from this device. I would like to see the full init flow of the device. Thanks

[tush80]

Hi @thecode After enabling debug logging, HA was restarted. The collected log for almost 12 hours is here, hopefully containing something useful: home-assistant_shelly_2024-05-06T08-43-31.828Z.log The devices that have the problem are with IPs 192.168.88.51 to 54; 192.168.88.50 (HT Plus) works fine. Thank you!

[thecode]

Hi @thecode After enabling debug logging, HA was restarted. The collected log for almost 12 hours is here, hopefully containing something useful: home-assistant_shelly_2024-05-06T08-43-31.828Z.log The devices that have the problem are with IPs 192.168.88.51 to 54; 192.168.88.50 (HT Plus) works fine. Thank you!

I checked two devices and they both timeout on fetching settings from the device (10 seconds timeout):

2024-05-06 02:43:02.124 DEBUG (MainThread) [aioshelly.block_device.device] host 192.168.88.54: http request: /settings (params=None)
2024-05-06 02:43:12.126 DEBUG (MainThread) [aioshelly.block_device.device] host 192.168.88.54: error: DeviceConnectionError(TimeoutError())

The only devices that succeeds are the ones on the 87 network:

2024-05-06 01:44:00.850 DEBUG (MainThread) [aioshelly.block_device.device] host 192.168.87.51: http request: /settings (params=None)
2024-05-06 01:44:00.877 DEBUG (MainThread) [aioshelly.block_device.device] aiohttp response: {'device': {'type': 'SHTRV-01',

I don't think we can do anything from here, you need to verify why the HTTP call fails to the other network, might be routing issue. Please also note that in general we do not support working with VLANs.

[tush80]

@thecode thank you for the directions, I'll investigate further for possible network issues. In the mean time I downgraded to 2024.4.4 and downloaded the debug log for reference home-assistant_shelly_2024-05-07T05-05-01.221Z.log

[muibeta]

I also am experiencing unavailable messages with four recently purchased Shelly H&T Gen 2 devices under Home Assistant version 2024.5.3. On reading this post, I restored back 2024.4.4 and the four Shelly H&T Gen 2 have remained available consistently for the last 24 hours. The Firmware in the Shelly H&T Gen 2s is up to date and I have configured the websockets to point to the instance of Home Assistant. Under version 2024.5.3 each Shelly H&T would separately show as unavailable very 15-30 minutes for 15-30 minutes. The Shelly app displayed their readings consistently throughout. I am running Home Assistant in virtual machines on a Synology NAS and in Windows 11. The IP addresses of each Shelly H&Ts has been reserved in my home router. The LAN is a simple 192.168.1.2 - 192.168.1.255 range.