Shelly devices suddenly offline after 2024.9.0

[wessa66]

The problem

Suddenly after 2024.9.0, my some (3 out 32) of the shelly devices doesn´t get online

Attached debug log from one of my devices shelly dimmer 2 on firmware 20230913-114008/v1.14.0-gcb84623
and now I don´t want to downgrade as there was a major DB update done or is that possible to do?

What version of Home Assistant Core has the issue?

2024.9.0

What was the last working version of Home Assistant Core?

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

Document.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

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

[wessa66]

I downgraded to 2024.8.3 now they are online again , but I was forced to move them to another Access point

[bieniu]

@wessa66 Please check if the problem occurs if you restart HA to safe mode. If so, please attach a longer log, a log that describes only 30 seconds is not representative.

I was forced to move them to another Access point

So it could be a network issue and not integration related?

@kryanth @ekalle-swe Open post is about DeviceConnectionTimeoutError in log, your errors/behavior are completely different. Please open separate issue, attach debug log for Shelly integration and diagnostics file.

Thanks

[wessa66]

@wessa66 Please check if the problem occurs if you restart HA to safe mode. If so, please attach a longer log, a log that describes only 30 seconds is not representative.

I was forced to move them to another Access point

So it could be a network issue and not integration related?

@kryanth @ekalle-swe Open post is about DeviceConnectionTimeoutError in log, your errors/behavior are completely different. Please open separate issue, attach debug log for Shelly integration and diagnostics file.

Thanks

Hi
will try this on Friday as I´m out and travling at the moment (doesn´t want to interupt my prod environment remotely) and need to upgrade to 2024.9.1 again as I downgraded it to 2024.8.3.

[wessa66]

Hi
I have rebooted the system (not in safe mode) with 2024.9.1 and what I can see I doesn´t have any problems at the moment(what I can see),
however I have attached my log from a reboot with shellydebug enabled, currently I have eight shelly devices offline (this is done on purpose)

home-assistant_shelly_2024-09-16T06-40-29.216Z.log

[wessa66]

Hi now I upgraded to 2024.9.2 and three of my shelly was not avail/offline , so I started i safe mode and had debugging on in Shelly, attached is the log
Tried to downgrade with "ha core update --version 2024.8.3" but this didn´t work as those shelly devices was deleted from "core.config_entries" so I rolled back a snapshot (running in VmWare) and they worked for 5 minutes then they was not responsive as they where unplugged.

I got them to work under 2024.8.3 by unplugging them for approx 60 sec and then connected them again

home-assistant_shelly_2024-09-17T06-30-18.031Z.log

[thecode]

@wessa66 from your previous comments:

Suddenly after 2024.9.0, my some (3 out 32) of the shelly devices doesn´t get online
I downgraded to 2024.8.3 now they are online again , but I was forced to move them to another Access point
I got them to work under 2024.8.3 by unplugging them for approx 60 sec and then connected them again

Are these the same 3 devices all the time?
Why do you need to reconnect or unplug the devices if the problem is in Home Assistant?
When you are on 2024.8.3 all the devices work correctly?

The attached log show that 9 different devices has communication errors, HA retry to connect to them without success.
Can you download the diagnostics from the device card in Home Assistant and attach it in a comment.

Thanks

[thecode]

Having a similar issue.

@davidrpfarinha This is a different issue, please create a new issue

[davidrpfarinha]

Having a similar issue.

@davidrpfarinha This is a different issue, please create a new issue

Thanks for the heads-up, @thecode. I thought the original issue was for the device disconnected.

[wessa66]

This is most anoying , I upgraded to 2024.9.3 and lost three devices , I unpugged them for 1-2 minutes and replugged them and they came back,
now I rebooted again and lost three again,not the same as last time ?! (debug log attached)
these below is lost this time is (IP):
10.33.124.126
10.33.124.106
10.33.124.110
and those are online as I can surf to them and access the shelly webpage , ColoT is configured ok

home-assistant_shelly_2024-09-26T11-51-40.351Z.log

Edit
Now I downgraded to 2024.08.3 (again) these devices above that was offline , the only one that came up was 10.33.124.106
the other two I was forced to unplug for 1-2 minutes after that they are online again and now I have restarted HA several times all shelly´s are coming back after reboot every time.....

[wessa66]

Hi I have now found my issue with this problem,
The problem in my case was UDP session that was still active in my fw after I rebooted HA (some of the sessions didn´t get time to timeout)

I´m using PaloAlto and my IoT(shelly) devices is on one subnet and HA in another subnet so all traffic is routed over my PA fw.

What I did was that decreased UDP session timeout from 30 to 15 sec for the applications "coap base" and "coap-get-request" after that everything works after rebooting HA.

So one way around this from HA perspective can be to increase the retry connection in shelly integration if HA can´t connect to a shelly device.

so for me this can be closed

[wessa66]

see my previous post