homebridge-meross: MSG 200 not working please help

Describe The Bug: MSG 200 not working on the latest version of the plugin

After upgrading this plugin to version 4.0.0+ my MSG 200 garage door opener will not work from homebridge

To Reproduce: Not sure as I don’t know whats wrong

Expected behavior: The garage to open and states to be correct

Logs:

Homebridge Config:

    "accessories": [
        {
            "name": "Hot Plate",
            "deviceUrl": "192.168.2.**",
            "channel": 0,
            "messageId": "-----------------------",
            "timestamp": -----------------------,
            "sign": "-----------------------",
            "accessory": "Meross"
        },
        {
            "channel": 0,
            "deviceUrl": "192.168.2.**",
            "sign": "-----------------------",
            "name": "Crock Pot",
            "accessory": "Meross",
            "messageId": "-----------------------",
            "timestamp": -----------------------
        },
        {
            "model": "MSG200",
            "name": "Garage Door",
            "firmwareRevision": "4.1.3",
            "deviceUrl": "192.168.2.**",
            "channel": 1,
            "messageId": "-----------------------",
            "timestamp": -----------------------,
            "sign": "-----------------------",
            "garageDoorOpeningTime": 15,
            "accessory": "Meross"
        }

Screenshots:

Environment:

Node.js Version: <Latest>
NPM Version: <Latest→
Homebridge Version: <1.3.3-→- Homebridge Meross Plugin Version:
Homebridge Config UI X Plugin Version: v4.40.0
Operating System:

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 17

Most upvoted comments

PushRate is the time that the plugin will wait before pushing the requested changes. So if you send and on action and then change your mind and push off, and you have your pushRate set higher it would only pickup the push off. It could also be used as a delay feature.

donavanbecker on Mar 19, 2021

I have figured out the issue (for me at least) for some reason the static IP i set for the MSG200 changed and i had the incorrect IP in the config however i have updated it the correct one now 😃

yonigold1 on Mar 15, 2021