Meross Power Strip (MSS420F) Not Working about homebridge-meross HOT 16 CLOSED

@donavanbecker FWIW... I've managed to successfully setup this exact power strip today using the guide on the WiKi and the correct model number in the config.

I used channel 1-4 and grabbed the credentials from the /config url using the Charles app

from homebridge-meross.

I wanted to post an update, I got it working!
Following the 4 channel guide, I altered the config and switched the model back to 420F.

Thank you for all your help.

        {
            "model": "MSS420F",
            "name": "Outlet 1",
            "deviceUrl": "192.168.1.199",
            "channel": 1,
            "messageId": "xxx",
            "timestamp": xxx,
            "sign": "xxx",
            "accessory": "Meross"
        },
        {
            "model": "MSS420F",
            "name": "Outlet 2",
            "deviceUrl": "192.168.1.199",
            "channel": 2,
            "messageId": "xxx",
            "timestamp": xxx,
            "sign": "xxx",
            "accessory": "Meross"
        },
        {
            "model": "MSS420F",
            "name": "Outlet 3",
            "deviceUrl": "192.168.1.199",
            "channel": 3,
            "messageId": "xxx",
            "timestamp": xxx,
            "sign": "xxx",
            "accessory": "Meross"
        },
        {
            "model": "MSS420F",
            "name": "Outlet 4",
            "deviceUrl": "192.168.1.199",
            "channel": 4,
            "messageId": "xxx",
            "timestamp": xxx,
            "sign": "xxx",
            "accessory": "Meross"
        }

from homebridge-meross.

@Lukabratzee can you change your channel to 1 and let me know what you see?

from homebridge-meross.

I've made the change, no joy unfortunatly.

I get a similar error on the console log:

(node:10413) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'digest' of undefined
    at Meross.getOnCharacteristicHandler (/usr/lib/node_modules/homebridge-meross/index.js:327:34)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:10413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

from homebridge-meross.

I need more info on your setup.

from homebridge-meross.

Sure, what do you need?

I'm running Homebridge, all over devices like Tuya, LifX run fine.
Not sure what else I can mention, you put me on the spot haha.

from homebridge-meross.

issue template has all questions in it.

• Node.js Version:
• NPM Version:
• Homebridge Version:
• Homebridge Meross Plugin Version:
• Homebridge Config UI X Plugin Version:
• Operating System:

from homebridge-meross.

I've made the change, no joy unfortunatly.

I get a similar error on the console log:

(node:10413) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'digest' of undefined
    at Meross.getOnCharacteristicHandler (/usr/lib/node_modules/homebridge-meross/index.js:327:34)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:10413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

also please provide updated config

from homebridge-meross.

Node.js Version: 12.8.0
NPM Version: 6.14.4
Homebridge Version: 1.1.1(latest)
Homebridge Meross Plugin Version: 2.3.0
Homebridge Config UI X Plugin Version: 4.23.0
Operating System: Ubuntu 18.04.4 LTS (GNU/Linux 5.3.0-59-generic x86_64)

Config:

        {
            "model": "MSS420F",
            "name": "Meross Strip",
            "deviceUrl": "192.168.1.199",
            "channel": 1,
            "messageId": "69f51bd4a3cee4bb3a0c9df9b5",
            "timestamp": 1592957079,
            "sign": "ef7dbc1e630b7242376bbacea5e3c89",
            "accessory": "Meross"
        }

from homebridge-meross.

can you post everything you get from using one these methods? make sure you go into the merls app and turn each plug on and off for the power strip. Then send the requests for each plug. Thanks!

from homebridge-meross.

Sure thing, I toggled all 5 switches from OFF to ON (ALL, SW1/2/3/4) and ON to OFF (SW1/2/3/4) and found their responses in HTTP Catcher.
Screenshotted them from iOS and uploaded here.

First batch are OFF to ON

Second batch are ON to OFF

from homebridge-meross.

@Lukabratzee Can you try changing the model to MS110, and see if it works? If it does we can try changing this for your model.

from homebridge-meross.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from homebridge-meross.

Apologies for taking so long to reply.
I changed my channel to 1-4, and I’ve made sure it’s MSS-110 1.0
There hasn’t been a change. I think the best thing for me to do is scrub the config part and set it up fresh from scratch, to see if I’m missing anything.

I’ve followed the wiki with HTTP Catcher but for a sanity check, I’ll use Charles.
I’ll do that tonight after work and update with my progress.

from homebridge-meross.

I wanted to post an update, I got it working!

Following the 4 channel guide, I altered the config and switched the model back to 420F.

Thank you for all your help.

Good to hear! Glad you got it!

from homebridge-meross.

Hi guys,
I have the same error for Meross Power Strip, but for MSS425F:

(node:2645) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'digest' of undefined
    at Meross.getOnCharacteristicHandler (/homebridge/node_modules/homebridge-meross/src/index.ts:352:34)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:2645) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

My Config is:

"accessories": [
        {
            "model": "MSS425F",
            "name": "Living Room Outlet 1",
            "deviceUrl": "192.168.1.95",
            "channel": 1,
            "messageId": "xxxx",
            "timestamp": xxx,
            "sign": "xxx",
            "accessory": "Meross"
        },
        {
            "model": "MSS425F",
            "name": "Living Room Outlet 2",
            "deviceUrl": "192.168.1.95",
            "channel": 2,
            "messageId": "xxx",
            "timestamp": xxx,
            "sign": "xxx",
            "accessory": "Meross"
        },
        {
            "model": "MSS425F",
            "name": "Living Room Outlet 3",
            "deviceUrl": "192.168.1.95",
            "channel": 3,
            "messageId": "xxx",
            "timestamp": xxx,
            "sign": "xxx",
            "accessory": "Meross"
        },
        {
            "model": "MSS425F",
            "name": "Living Room Outlet 4",
            "deviceUrl": "192.168.1.95",
            "channel": 4,
            "messageId": "xxx",
            "timestamp": xxx,
            "sign": "xxx",
            "accessory": "Meross"
        },
        {
            "model": "MSS425F",
            "name": "Living Room Outlet 5",
            "deviceUrl": "192.168.1.95",
            "channel": 5,
            "messageId": "xxx",
            "timestamp": xxx,
            "sign": "xxx",
            "accessory": "Meross"
        }
    ],

My Versions:
Node.js Version: v12.19.0
NPM Version: 6.14.8
Homebridge Version: v1.2.3
Homebridge Meross Plugin Version: v3.2.0
Homebridge Config UI X Plugin Version: 4.29.0
Operating System: Alpine Linux v3.12

Could someone help me please?
I've read all comments, but didn't find out how did you resolve it.

Update:
I tried to change name to "MSS110-1", but no luck, it threw an error

(node:2560) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'control' of undefined
    at Meross.getOnCharacteristicHandler (/homebridge/node_modules/homebridge-meross/src/index.ts:340:46)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:2560) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:2560) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Update 2.
I got resolved it by retrieving messageId, timestamp and sign one more time from HTTP Catcher. Not sure why, but they were different. So sorry for offtop, maybe it would be useful for someone, so let's try first to retrieve data one more time if it doesn't work for you.

Thanks,
Vasili

from homebridge-meross.