Hi folks,
the newest things are repair-alerts for all my shelly_v1 devices.
The curiosity is, that everything is configured as recommended
What’s wrong suddenly?
I also get this warning, I just clicked ignore as the shelly is working fine 
Yep, I started getting the “push update failure” repair for my Shellies as well. I was previously on mcast, but after this repair came up I configured to unicast as suggested, but the warnings keep coming back.
Everything seems to be working normally though.
Same with me
I found the solution.
switch to unicast and enable firmare entitiy on the device.
See the shelly configuration Generation 1 guide.device. Shelly - Home Assistant
1 Like
Small Advice: You have to restart the shelly device after chnage the ColoT peer.
Mine is already like that …
I was already in unicast. I enabled the firmware update sensor, not sure why that should matter but we’ll see if that works as a workaround.
My firmware sensor was already enabled.
working fo rme opening the communication UDP on 5683 on the firewall
i update today from lastes .7 to latest .8 (8.2) and that error appears same problem with 8.1
Seems change mcast to unicast (ip/port) and restart the shelly fix the problem
Same for me.
Must be related to some changes in recent Homassistant releases.
Still get several error messages according to allmost all of my shelly devices.
I read that it could be related to bad wifi, but my wifi is consistently good.
Allthough ther are som curiousities…
In the shelly-webif the wifi RSSI is at -80 dBm
In my wifi-software (UniFi Cloudkey) the wifi-experience is excelent.
Mine -57dBm on similar setup, so it’s definitely not bad Wi-Fi (in my case)
1 Like
Same issue here for over a month. Already changed mcast to unicast (ip:port) and restart. It solved until the next day when it appears again. Not an WIFI problem for sure.
This “error” has been in my logs for a long time.
It is not until now that it appears in “repair” because an update of homeassistant has enabled that function.
I think the reason is something in the wifi environment.
Since I didn’t discover anything wrong with the function, I have ignored it.
I think that this “repair” suggestion comes up when there is a slow response from shelly.
Therefore a suggestion is to check unicast.