Hi all, i’m trying to configure my shelly devices with the new shelly integration.
Everything goes well,i created shelly entities but i notice a little problem…
If my devices lose wi-fi connection (i have some shelly 1 and a shelly em) they stay unavailables until i reboot Hassio.
For example, i disconnect wi-fi at 2 AM and reconnect at 7AM and my shellys are unavailables. I have a lot of devices (Xiaomi Aqara,Yeelight,etc) and the related entities become available again when wi-fi come back…
Any idea and help is very appreciate,maybe is my mistake…
Thanks
2 Likes
I have the same problem.
The best solution i have found is reloading the integrations true a script.
(i created a rest_command for each integration)
I got de device id from the [ha config]/.storage/core_config.entities file.
rst_lifx:
url: http://[home assistant addres:port]/api/config/config_entries/entry/[device id]/reload
method: POST
headers:
authorization: 'Bearer [long live token goes here]'
content-type: 'application/json'
1 Like
Do you have to have an automation for each and every shelly device or can you the device id for the integration?
I’m planning heavily on Shellies, have about 30 of em waiting for install…
Same issue here, a reboot does allow them to reconnect. Will using the MQTT integration handle these differently? I’m very new to HA and Shellies, and have not attempted to connect via MQTT.
Welcome to the community @Essavant !!
MQTT connection to the Shellies is rock solid.
I tried the integration out of curiousity but as switch inputs on the Shelly1 weren’t exposed as an entity, I’m sticking with MQTT until the integration matures.
This issue should be solved with 0.116.0
2 Likes
I have 1 rest_command and 1 automation for every shelly.
As far as I know off (which doesn’t mean much) there is now way to read the device id’s from home assistant. (except with python I guess but I don’t know anything about that)
So you need to have 1 rest command for every device.
You could probably get them all in 1 automation but that would involve an if then else construct with 30 steps (1 per device id).
That’s a good news! Thanks
Good News. Thanks
Still have a same problem.
For me, with last update (0.116),it works pretty well now.
The problem seems to be in shelly 1.8 firmware
I bought quite many Shelly 1/2.5/i3 issue, and tried them out in the last 2 weeks, with the latest firmware (till the time I wrote this post), they leave me a conclusion, Shelly wifi connections sucks… their support enginner always give an explanation that the wifi is not strong enough, but actually, they still go offline they are just <1m away(no wall in between) from my wifi equipment.
I would say, that Shelly product really have wonderful features. but wifi is a big issue: especially when they were put into wall…
Strongly suggest they go into Zigbee solution ASAP…
I currently have around 10 Shelly’s and have had zero wifi issues.
Are they dropping off the network completely or just not accessible through Home Assistant ?
I only have a single Shelly with this issue, it is on 1.9 and the issue exists, but it was worse on 1.8.3.
The kicker here is just how BAD the wifi signal is… it is very bad, the other device in the same room is almost as bad but does not have the problem, the difference in signal strength is 2 or 3dB, that is enough to cause it to reboot.
The signal strength varies considerably throughout the day, probably interference from neighboring wifi setups, but it gets as bad as -83dB, though this will not always be the cause of the reboot, as it can happen with better signal.
The path to the access point goes through 3 walls and a full closet. There is also a nearby metal trash can that may be causing signal reflection issues. Either way, the fact that it is working mostly reliably, even with such harsh conditions, speaks to the reliability of the ESP platform.
If issues persist on multiple devices even in proximity to the access point, you have a different problem. Maybe another wifi device is out of compliance with the spec and poisoning the signal, or the access point has issues (cough netgear cough).
Might be helpful, might not be helpful: I only seem to be having the issue when the Shelly 1 is using the 5GHz Network, not when using the 2.4 GHz my Fritzbox provides.
Shelly devices do not support 5GHz wifi at all
The last beta firmware released last week is supposed to finally correct all wifi disconnection problems.
“Suppose to…” 
The latest beta firmware bricked one of my devices (the only one i tried), so I would not play with that yet
Humm 
No issue so far for me, I’ve updated 7 devices I guess but not the 9 others.