The MSS310 is not supported yet but i can add it.
Are you using only the on/off function or more?
-
ON / OFF in Step 1 asap is fine.
Current Power in Step 2 and perhaps the Power Consumtion, if possible.
For the future, access to the scenes will be fine.
Planned scenario:
If the power consumtion per time (minutes, hours or day) < limited value then start action (eg. send message)Newcomer of pimatic
-
@bertreb I’m sorry, but immediately after updating to 1.6, it lost contact to my garage door opener, disabling the linked rules. I deleted the device and tried to rediscover, but it shows nothing. Seems like there is something broken…
-
Hi, I changed very little in version 1.6, only allowing a mss310 to be added. Just as an on/off device like a mss210.
There where/are some problems with meross cloud the last week.
Is your meross app still working fine and do you have any debug log? (from daemon.log) -
One of the dependencies of the used meross-cloud lib was not installed. That prevented the plugin to load. Don’t know why that happend but i corrected that in the plugin package. Version 0.1.8 should work again. Let me know if its working again.
-
@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.
-
@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.