Hi, the plugin worked for a long lont time perfectly, and recently I had to reset the wifi of the roborock, I retrieved and change the token in the server.sh script. it is the good token because it works with flolevac or with a command like that: "sudo mirobo --ip 192.168.0.23 --token "thenewtoken start"
but when i put it in domoticz i don't have any error in the log, (execpt 'onDeviceModified' not callable, ignored) but I cannot use the swich command, or i don't have the infos about battery, or other stuffs about the robot. (by the way it's the same devices on domoticz even after create a new hardware)
when i use test.py, it tries to connect to ther server, but with no answer from the device... I don't know why, only the token had change...
edit: maybe it is because of a new update for the robot, that blocks the info from the server... I tried to downgrade with flolevac but I cannot do it anymore... ^^
Hi, the plugin worked for a long lont time perfectly, and recently I had to reset the wifi of the roborock, I retrieved and change the token in the server.sh script. it is the good token because it works with flolevac or with a command like that: "sudo mirobo --ip 192.168.0.23 --token "thenewtoken start"
but when i put it in domoticz i don't have any error in the log, (execpt 'onDeviceModified' not callable, ignored) but I cannot use the swich command, or i don't have the infos about battery, or other stuffs about the robot. (by the way it's the same devices on domoticz even after create a new hardware)
when i use test.py, it tries to connect to ther server, but with no answer from the device... I don't know why, only the token had change...
edit: maybe it is because of a new update for the robot, that blocks the info from the server... I tried to downgrade with flolevac but I cannot do it anymore... ^^