I am monitoring the ping response on all my powered Shelly devices, mainly due to issues with the bulbs. Doing this, I noticed something odd on the Shelly Motion I have.
All the other Shellies are responding as expected, but the Motion is very tardy. The Motion has an RSSI of around -55 dBm (so, very good). To note again, all these devices are connected to mains, not battery. Is the Motion always slow to reply simply because it has a batter, even when powered?
I mentioned twice (to make sure it was very clear) that this Motion is on mains, powered, with a cable. So it could be the Shelly doesn't actually know it's on mains, but that would be a shame, a Motion on mains should not go to sleep at all, to provide optimal response time to commands.
Update: to add to this, the Motion actually does not go to sleep. This is easy to verify by opening the device's web page, which is instant when and while the device is cabled.
it's not a full DeepSleep like Shelly H&T or ShellyDW2.. ShellyMotion is most of the time in LowPowerMode, this blocks incoming Data such as Ping to protect battery usage..
Is the Motion always slow to reply simply because it has a batter, even when powered?
yes, it is (and will be) always slow .. This is by design because the vendor sold it with a battery and cannot know someone is removing the battery and use it with mains..
it's not a full DeepSleep like Shelly H&T or ShellyDW2.. ShellyMotion is most of the time in LowPowerMode, this blocks incoming Data such as Ping to protect battery usage..
yes, it is (and will be) always slow .. This is by design because the vendor sold it with a battery and cannot know someone is removing the battery and use it with mains..
Hi there, thanks for the explanation. Still there was something odd, as after 1-2 hours of high-ping replies, the Motion has now settled around 60ms average. Anyway, it works fine otherwise.
