-
Notifications
You must be signed in to change notification settings - Fork 20
Plug keeps blinking green forever #64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Does this work for you? #57 (comment) |
Wow, in deed! I sent Now, when I press the plug's button, I can see in the broker and the attached subscriber that an Appliance.Control.ToggleX message comes in: Now, for the other way around, i.e. controlling the plug, I tried to send a similar message towards the plug:
The plug only reacts on the message
So far so good. I understand that to do it properly, I must use a random messageId, a correct timestamp, the correct key and a signing value equal to md5(messageId + key + timestamp). This should be doable without too much programming effort, analogue to the code fragment which is posted here for Symcon. However, I would assume that there is tool or library around to do this, just couldn't find something. Could you possibly point me into the right direction? I am looking for a simple plain command line tool, without an integration in HomeAssistant or the like. |
If you want to do this with python 3, here are some tips: To generate random messageId:
To calculate the timestamp:
To calculate the sign:
As an example here is how I generate the JSON for my use cases (unfortunately I don't use ToggleX, so I added a short section at the end that should help you):
|
Dear all,
after spending many hours I still have no success in connecting my new smart WiFi plugs Refoss MSS210W to Mosquitto.
I am following the procedure by Rob Griffiths, but am stuck at where the meross-setup utility is used. After I try to bind the plug to my Mosquitto broker at 192.168.188.30 with the command
./meross-setup --gateway 10.10.10.1 --wifi-ssid assid162 --wifi-pass 3438XXXXXXXXXXXX7725 --mqtt mqtts://192.168.188.30 --mqtt mqtts://192.168.188.30
the plug
The plug remains in this state forever. I have no clue on how to proceed and would highly appreciate any suggestions.
The plugs work correctly when connected to the Meross cloud / eHomeLife-App.
The Mosquitto server was installed from mosquitto-2.0.15-install-windows-x64.exe on a Windows10 machine with IP 192.168.188.30. The instance uses the following mosquitto.conf, which corresponds to that of Rob Griffiths:
The three certificate files have been created on WSL/Ubuntu with this script makeCerts.sh, based on the one from ElBobo:
Note that it does not use the
-des3
option which Rob uses. I also made sure that the Organisational Names are not identical, as pointed out by sheran29.I have opened a second commandline window on the PC and successfully attached a subscriber to the running Mosquitto broker:
mosquitto_sub -h 192.168.188.30 -t "#" -t "/#" --cafile ssl/ca.crt
It successfully receives messages that I send from a third commandline window, e.g.:
mosquitto_pub -h 192.168.188.30 -p 8883 -t "test7" -m "message7" --cafile ssl/ca.crt
Here is a screenshot of the broker with three blocks:
From this I would say that Mosquitto and the certificates are OK.
Now, as I said in the beginning, after the plug is reconfigured with
./meross-setup --gateway 10.10.10.1 --wifi-ssid assid162 --wifi-pass 3438XXXXXXXXXXXX7725 --mqtt mqtts://192.168.188.30 --mqtt mqtts://192.168.188.30
it behaves as stated above. The Mosquitto broker and hence the subscriber see messages of types Appliance.Control.Bind and Appliance.System.Report, and this continues forever. What can I do?
Output from the broker:
Output from the subscriber:
The same in prettyfied form:
What can I do?
The text was updated successfully, but these errors were encountered: