Closed Goopdegooo closed 6 months ago
I think the issue is related to the device being unable to synchronize its internal time at boot (query of NTP servers) as suggested by several similar issues where the power readings are zeroed (#300 - #318 - #367 - and many others ;)
All of these issues seems to confirm that if the device doesn't have a correct time it is unable to report powert and energy readings. Several users, were able to keep the device 'out of the internet' by spoofing the public NTP servers queried by the device firmware and using their own private NTP service.
Beside the NTP query, if the device is Meross paired, it also tries to connect to the mqtt broker and could likely stall indefinitely if it is unable to reach the intended Meross MQTT broker (but this more vague...)