Open klow7777 opened 5 years ago
It’s the same error of MSS310 v1. They don’t use “togglex”, but ”toggle”. I know Carlo is working in order to correct the plugin... Stato tuned😉
Thanks Gianky, I hadn't picked that up in the issues when I went through them prior. Sorry for the redundancy, Carlo.
Anyone know if this is the same reason why there are similar errors on the MSS210 plug. I have not found anyone reporting attempts to configure with this plug variant.
Anyone know if this is the same reason why there are similar errors on the MSS210 plug. I have not found anyone reporting attempts to configure with this plug variant.
You'll have to check the errors and compare it to this one. More than likely, yes.
I have two Meross MSS110 that are single plugs, no sensors.
The addon can recognize these devices but seems to have some errors.
Using Node-Red debug, I viewed and then published this JSON to try and turn on the switch.
{"name":"John’s Corner","state":1,"device":{"name":"John’s Corner","sw_version":"1.1.26","identifiers":["1712216531717925131334298f10b237"]}}
to the topic
homeassistant/switch/1712215321760125131334298f10b22d_0/state
But this JSON payload did not turn on the switch. If I turn on the switch from the Meross app, the state does not change to "1" in my debug viewer.
I used a man in the middle proxy to see that when I turn on the switch from the app, this is the raw data:
The JSON data is here:
I am not a programmer but I would like to help if it is necessary or feasible. Thank you for your work on this so far.