homebridge-meross: Error: Invalid URI

Hello,

I get the following error message when I try to configure the meross plug “mss310”:

[4/12/2020, 11:25:27 AM] [Meross_device] Failed to POST to the Meross Plug: Error: Invalid URI "192.168.178.35/config"
    at Request.init (/usr/local/lib/node_modules/homebridge-meross/node_modules/request/request.js:273:31)
    at new Request (/usr/local/lib/node_modules/homebridge-meross/node_modules/request/request.js:127:8)
    at request (/usr/local/lib/node_modules/homebridge-meross/node_modules/request/index.js:53:10)
    at /usr/local/lib/node_modules/homebridge-meross/index.js:9:5
    at new Promise (<anonymous>)
    at doRequest (/usr/local/lib/node_modules/homebridge-meross/index.js:8:10)
    at MerossPlug.getOnCharacteristicHandler (/usr/local/lib/node_modules/homebridge-meross/index.js:175:24)
    at Characteristic.On.emit (events.js:310:20)
    at Characteristic.On.Characteristic.getValue (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Characteristic.js:164:10)
    at Bridge.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:771:20)

This is the configuration:

{
            "name": "Meross_device",
            "deviceUrl": "192.168.178.35",
            "hardwareVersion": 2,
            "channel": 0,
            "messageId": "242afa8372dd827e10ee53de77fdfc35",
            "timestamp": 1586678958,
            "sign": "40f1117a6bf82cae9757915ff8a9a564",
            "accessory": "Meross"
        }

I got the informations from the Charles ios app.

Thanks in advance!

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 23

Commits related to this issue

fix sign error Fix the problem that the following devices cannot be configured due to an error when sending MQTT messages. - Device : mss110 us mt7682 (hardware:2.0.0 firmware:2.1.19) - Error : ... — committed to nao-pon/meross_lan by nao-pon 3 years ago

Most upvoted comments

Done and can confirm works for me

On 29 Apr 2020, at 4:50 am, Donavan Becker <notifications@github.commailto:notifications@github.com> wrote:

Just released Version 1.1.0https://github.com/donavanbecker/homebridge-meross/releases/tag/v1.1.0, if you want to give it a try.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/donavanbecker/homebridge-meross/issues/20#issuecomment-620847234, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACTZWLHZWA4LGZTWZPS2PG3RO46QLANCNFSM4MGLCACQ.

arohl on Apr 29, 2020

Can confirm it works!

Once you have updated the repo, I just need to

sudo npm install -g --homebridge-meross

to get back on the release version?

arohl on Apr 20, 2020

OK - its all working now! - thanks!!

I hand edited the config to add the http and also to simplify it (it didn’t work with the http added to my previous config); it looks like

"accessories": [
    {
        "accessory": "Meross",
        "name": "amp",
        "deviceUrl": "http://192.168.178.139",
        "hardwareVersion": 2,
        "channel": 0,
        "messageId": "17cfbf76eb100a721715de2c617f87fd",
        "timestamp": 1587218340,
        "sign": "XXXXXXXXXX"
    }
],

arohl on Apr 18, 2020

I think the issue is with your config file. I believe JSON strings can only be declared with double quotes as opposed to single quotes and almost every key/value pair must be wrapped with double quotes. I think there is an issue with the layout in general as well. If you want you can post your entire config with a couple things redacted and I can look over it if you would like? The bridge’s mac-address username value as well as any device’s messageID and sign values can be removed or edited. If you don’t feel comfortable posting feel free to message me on twitter and we can figure something out. 🙂

Here’s an example from my config that can hopefully help.

"accessories": [
    {
        "accessory": "Meross",
        "name": "Bedroom lamp",
        "deviceUrl": "http://192.168.101.xxx",
        "hardwareVersion": 1,
        "channel": 0,
        "messageId": "xxx",
        "timestamp": 1000000048,
        "sign": "xxx"
    }
]

dylanfrankcom on Apr 17, 2020