Let’s wait for my msg100 and i will post when a next version is available
Another update, maybe it helps finding: The device itself is still stated “offline”, but it gets the correct GaragedoorStatus (and sends email in my case). So the device is OfflineOnline.
Updated and testing:
As far as I can see, the status of the msg100 stays online. There are (correct) spikes to offline at my daily reboot and the daily internet reconnect. It seems to work.
Currently I have a problem that my ms310 wall outlet is stated as offline. Although I can control it.
This could be a side effect of a mail a got (so nothing for you to do):
This is meross cloud security team contacting you.
First of all, thanks for purchasing meross and we hope that you enjoy life with our smart products.
Recently our cloud security system has noticed that your devices are communicating with the could server at an extremely high frequency. We consider these behaviors abnormal and are concerned about the security of your devices.
Due to the security concerns and the intent to avoid any further potential damage, we will terminate the cloud services of these devices for now.
If you are sure that your devices are safe, NOT hacked, and are performing as expected. Please first lower your periodic request rate to no more than one message every ten seconds and then send an email to email@example.com. We will resume cloud service for you within 24 hours. Please note that any abnormal high cloud request frequency will cause cloud service termination again.
Should you have any information you would like to provide us with or would like to offer us any clarification, please contact us within 24 hours.
meross Cloud Security Team
Good that the Garagedoor is working. The changes i made for the msg100 i will also apply to the msg 210/310.
The msg310 is polling every 5 seconds for the electricity values, so that probably causes the security issue. I will change that to minimum 30 seconds
Updated and testing. Garagedoor seems to be (still) good. msg310 is still offline (in both - meross app and pimatic). I guess I have to wait until meross lifts the lock from my account. To be exactly, I think they lock on device level, not account level.
Meross wrote me, my services were put in normal mode automatically yesterday noon.
So, my first testing impressions:
- The GarageDoorStatus went offline with the internet reconnect at 4:29h in the morning and didn’t come back online by itself. After rebooting, the device is online again.
- The msg310 went offline with internet reconnect, too. But I can’t get it back online, even with deleting and discovering it again.
Maybe this log entry might be useful:
error [pimatic]: An uncaught exception occurred: TypeError: Cannot read property ‘getOnlineStatus’ of undefined
at MerossPlugin.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-meross/pimatic-meross.coffee:588:19)
at MerossPlugin.emit (events.js:203:15)
at MerossPlugin.EventEmitter.emit (domain.js:448:20)
at MerossCloudDevice.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-meross/pimatic-meross.coffee:46:12)
at MerossCloudDevice.emit (events.js:203:15)
at MerossCloudDevice.EventEmitter.emit (domain.js:448:20)
at MqttClient.client.on (/home/pi/pimatic-app/node_modules/pimatic-meross/node_modules/meross-cloud/index.js:296:18)
at MqttClient.emit (events.js:198:13)
at MqttClient.EventEmitter.emit (domain.js:448:20)
at MqttClient._reconnect (/home/pi/pimatic-app/node_modules/pimatic-meross/node_modules/meross-cloud/node_modules/mqtt/lib/client.js:931:8)
at Timeout._onTimeout (/home/pi/pimatic-app/node_modules/pimatic-meross/node_modules/meross-cloud/node_modules/mqtt/lib/client.js:952:12)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
This is most probably a bug in pimatic or in a module, please report it!
Thank you for the quick fix!
Installed 0.2.8 and testing.
First look after reboot is good, both devices online and operatable. Status of Garage and msg310 is transmitted correct and without delay.
Two weeks of testing:
- the devices are always online (except for daily internet reconnect)
- the daily reboot doesn’t trigger GarageDoorStatus-Mails anymore
- the internet reconnect now triggers GarageDoorStatus-Mails
- the GarageDoorStatus is always shown correctly
Once and only once I came across a slight missbehaviour: The device was online and also stated as online. When triggering to open the garage door, it said the device was offline (although still showing it as online - and it was physically online and controllable by meross app):
After all, I would say: we are currently on a stable build!