Hello, for almost a year now, I’ve had an issue with the Shelly integration, for which I’ve requested help on discord multiple times, to no avail.
Basically, the official Shelly integration will not work with any Shelly device that spends most of its time in sleep mode (the Shelly H&T, H&T plus and the magnetic door sensor).
If I manually wake up such a device, the Shelly integration works perfectly and data is continually collected.
However, once they enter sleep mode, no data will ever be sent again to the integration, no matter how long I wait.
The devices work as they should, they wake up, connect to wifi, send data and then go back to sleep, but the Shelly integration will never again see them and will never get this data.
This is especially evident with the Shelly H&T Plus, which has a screen that shows you when it collects data and flashes a symbol when it connects to wifi to send that data.
I’ve checked the router and the sensors do connect to wifi for a moment, before going dark again, as they should.
I have the same problem with a shelly TRV. I use CoIoT with unicast configured but the device is unavailable after some hours after waking it up manually. It is really annoying because I can basically not use any automation with that behavior.
This is the case with my “Morning” routine where I want to set the bathroom to be ready for the family. I have now put all settings in a script that I then start from my automation. Not the normal “call” a script, because that will then just also fail. I use the Script Tun On service. That starts the script in parallel to the automation sequence. The sequence then waits. This Script Turn On is captured in a while loop that checks is a certain boolean is set. That boolean is set as the last step in the script. So if the script fails, this boolean does not get set - and the whole sequence is tried again. So far it is always ready to rock with the second run through the script – so it is possibly some time-out in the Shelly integration that is too short.
I think that is not cause by integration. Almost 3 months it worked correctly to me, but now I have the same problem. I did not change anything special and all the time I have set coIot in the same way.
That is pitty that is so unpredictable and cannot be solve anyway.