I have installed two Shelly 1 Gen 3 mini switches. When I installed them I updated the firmware to the latest. They work and all looks good connected directly to the ip, but in Home Assistant they keep going unavailable and then back online without any intervention. It is not a wifi signal issue because the two are right next to each other and do not go unavailable at the same time. Any guesses on the cause and the fix?
Do those Shelly have the CoIOT settings? Remove “mcast” in this settign and enter the static IP of your HA instance with port 5683.
Perhaps this link from Shelly support forum can help you.
The set up for these do not have those options to control.
Thank you for the link. I will wait a few days after the release to see how “stable” it truly is because the 1.4.0 was not so good.
Sometimes it is just a timeout setting that makes it seem unavailable.
The HA integration might have a timeout setting a bit lower than the Shelly’s interval for reporting in.
This means it will be marked as unavailable because it has not heard from the Shelly and then shortly after marked as available again, because the Shelly then report in by itself.
The longer interval between reporting in is sometimes used by firmware developers to increase battery life and mains powered devices get hit by this change too, because they share the code.
1 Like
I have 3 Gen3 mini devices (2 x 1PM mini and 1x PM mini). For switches I do not see any issues, but PM mini ocassionally goes off network. It is sitting next to Access Point (<1m), so connectivity is not an issue. It is not just the HA and pulling frequency, as I’m using Fing Box to monitor my LAN and this issue is reported by this device. It is using ping to detect device presence on network, though I’m not sure what is the check frequency. Just yesterday I updated FW to 1.4.0, so yet need to see if this changes situation.
It was related to a disconnect with the Home Assistant and the Shelly update. See Shelly 1.4.0 version, HA is now trying to reach IPv6 only · Issue #122958 · home-assistant/core · GitHub. Since I updated to HA 2024.8.1 I have not had the issue.
Thanks for your responses.
I’m currently running 8.2 and seeing this with a lot of my Shelly devices. I know it can’t be a network issue as Unifi tracks the connectivity status of each device and that shows the Shelly’s with 100% uptime.
I have three mini 1pm’s doing this now - every 2-3 mins they become unavailable, go off and then come back. The Shelly app all looks ok, other units all look ok on same network. I have tried to lock them to an access point,set them on static IP’s, reboot and re-setup - all results in the same issue.
HA is on 2024.10.4 and the Firmware is 1.4.4
1 Like
did you find any solution to this?
Yes - the answer is rather dull - I found that the wifi point (I use unifi) was meshing as the ethernet feed to it had a bad connection. It seems that the Shelly’s did not like it. Corrected the ethernet cable and they then worked fine.
As a side note I have stopped using Mini’s as their relay seems to be sub par - they keep welding the contacts (even with a snubber) so have used the standard 1PM’s for everything (and relegated my mini’s to a power monitoring role only).
What loads and devices are you running where you are seeing the welding on the relay?
LED lighting - 100-200W max so well below any max limits. However, it had a high switch frequency e.g 100 times per day which I assumed was the issue. Funnily, I have a couple of Zigbee units from Sonoff with a similar load profile and have had zero issues with the switching (range is a whole other issue).
Ah - 100 to 200W of LED’s might have quite a considerable capacitance. Are they individual LED’s or larger fittings?
Bit of a mixture - but the same as the zigbee device which are not having the same issues.
I’m occationally having the same issue, also with unifi.
Logging in to unifi console and clicking reconnect on the shelly device gets it back online.
(Just discovered this)
And what does you UniFi logs tell you?
As far as I can tell, they tell me nothing.
apart from a disconnect and reconnect when I reconnected it from unifi.
