@bertreb Thank you - with 1.8 everything is back to normal. Meross is detecting again (wasn’t detecting at all) and found the garage opener. Status and control are working normally.
-
Plugin for Meross Devices
-
@bertreb Sorry to bring up the bugs, but since v.0.2.2, the status of the garage door is never updated.
It is always closed (so you can once open the garage, but never close it, as it is seen as closed).It doesn’t matter, if I use pimatic, the meross app or the rf-sender, the status won’t change.
The log doesn’t say anything about it - I’ll send it by mail anyway, maybe you see something. -
@bertreb Unfortunately, version 0.2.4 doesn’t help on the long run. It did work immediately after the installation, but the device went offline at 00:00h and came back online after the daily reboot at 02:00h. After the reboot, no door status change was recognized. I sent you the log by mail.
Coming back to my original offer: Can I gift you a Meross Garage Opener for your work? Maybe if you have one at hand and can monitor it at all times, you’ll find a solution quicker?
-
That’s a pity. I published version 0.2.5 with small change on reconnect.
It’s to be sure that its not caused by a wrong reconnect.
And i can get hold of a msg100, so i a few day i can do better testing. -
Thank you! Updated and testing…
-
@wolfpack said in Plugin for Meross Devices:
Thank you! Updated and testing…
For convenience, I made an email rule, so I get an email on every change of GaragedoorStatus.
After installing, the status was taken correctly and the emails came in.
At 02:00h (daily restart), I got the last mail GaragedoorStatus closed (as it already was, I think the reboot made the rule execute and send the mail).
From this time on, in the morning I opened and closed the garage two times, but got no more mails. -
Update:
The device also went offline at 04:38h with the following log:
04:38:36.717 [pimatic-meross] debug: DEV: 1909180522859190801948xxxxxxxxxx reconnected: undefined
04:38:36.949 [pimatic-meross] debug: DEV: 1909180522859190801948xxxxxxxxxx connected
04:38:56.728 [pimatic-meross] debug: Error getSystemAllData for device ‘1909180522859190801948xxxxxxxxxx’ Error: Timeout
04:38:56.952 [pimatic-meross] debug: Error getSystemAllData for device ‘1909180522859190801948xxxxxxxxxx’ Error: Timeout…this means that maybe the GaragedoorStatus could be working, but the device was simply offline…
-
Take your time!
By the way: Currently, I’m unable to bring the device online again. Restart, reboot… no way, it is always offline now.
It seems like your fix from yesterday caused some side-issues. -
I tried it: The status of the device stays “offline”, but the mail-rule is triggered and i get a mail that the GaragedoorStatus is closed.
-
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):Dear Customer,
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 cloudservice@meross.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.Thanks!
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.