I just flipped my sensor over to a different hub. To test it I put my finger on the top and the temperature changed almost instantly. Turns out that about three weeks ago the handler was updated to cope with a different model number and the reporting was also tweaked.
I haven’t examined things too closely but it looks like temperature and humidity can report every ten seconds instead of every hour, but subject to a 0.5 degree change for temperature.
The checkInterval is still a bit out of bonk so presumably the device is frequently on the cusp of going offline.
That was a bit ambiguous. I have two v2 hubs in my Location and I switched the sensor from one to the other in the IDE, thus requiring it to be paired again and so picking up the changes in the handler.
I do have a different hub in another sense, but that is just an IKEA Gateway. I am not about to abandon ship.
Thanks for the replay, I already connect my sonoff sensor with Sonoff/SONOFF multi-functional and the result was the same…after some hours they went down. Could the problem is my smartthings hub is close to my router? I read zigbee goes in conflict with router wifi?!
It is close to the hub, 2 meters away and the hub is 30 cm from the router.
My wifi channel is 6 and the zigbee channel is 24, I don’t have any interference problems.
I use it as the main thermostat and I left the beko, which had as a backup 2°c below the sonoff and in more than 2 months it has never failed
What I have seen on this device is that the installation configuration response it well, answering success, but subsequent configuration changes, for changes in reporting intervals, do not always answer as accepted.
Therefore, it is very important that it is close to the hub in the installation process, because if it is not configured correctly, it will not periodically send battery, temperature and humidity reports and may become offline after a while.
Something similar also happens to the sonoff contact sensor
However the samjim sensors always accept configuration changes