Shelly device ConnectionError from time to time, using OLD IP-Addr.

[el-Presi]

The problem

For one of my Shelly devices, I get an error about every 1,5-2 weeks, since I moved this Shelly to another subnet (another IP so). I reconfigured the device as well as removed it and added it again (with its new IP). The device then works fine for about 1,5-2 weeks. Then I get the following error:

New IP is in 10.8.0.0/24 Network, accessable (for sure) from HA (10.3.0.23). The old IP in the 10.3.0.0/24 does not exist anymore.

What version of Home Assistant Core has the issue?

core-2024.10.0 and core-2024.9.x

What was the last working version of Home Assistant Core?

No response

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

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

[bieniu]

VLAN configuration for Shelly devices is not recommended. You must take care of proper forwarding of CoIoT packets between subnets and proper configuration of CoIoT in the device.

[thecode]

Home Assistant can only store a single IP, so once the device is working if it switch back to an old IP it means it is advertised by something. From previous similar issues this was found to be a problem of the router sending mDNS advertisements using the old IP address of the device. I recommend restarting both the affected device and the router and see if it still happen.

[el-Presi]

Thanks for your Comments! Restart has been done in the meanwhile, but no change - I would try to let HA think, this is a whole new/different device by trying to change also the devicename in Shelly and HA. I let you know :)

By the way: I have about 5 other Shellys, that are working on fine, being in VLAN 8, while HA is in VLAN 3 - the only issue comes up for this Shelly 1-Gen Product (which is maybe the "cause" here).

[kevlacross]

same problem here. After Changing the IP Adress, Shelly drops this error in HA. Only GEN1 Devices. CoIoT works.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.