Could not connect to device, token might be wrong"

[Fastigit]

I'm shure that the Token I'm using is correct as it works with FHEM. I can control my RoborockS5max from FHEM using exactly this token. But in NodeRed, if I look at the debug window, the serve node of this contrib says: "Miio Roborock Error: Could not connect to device, token might be wrong" A nebug node at the output of the Roborock: command node says: "TypeError: Cannot read property 'call' of undefined"

[jerome83136]

Hello, I have the same problem with my Roborock S5 The retrieved token from node red is the same as the one I get from this tool: https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor/releases/latest/download/token_extractor.exe The robot is registered on the "de" server.

By using this token in node red; I cannot interact with the robot (event and actions KO) Node red error: TypeError: Cannot read properties of undefined (reading 'call') But using the same token on another home automation solution (Jeedom + Xiaomi home plugin) it works.

Could be usefull for the diag:

• My other robot "Roborock S7 pro ultra" works with node red
• The Roborock S5 worked with Node Red until I did a wifi reset and tried to enroll it with the "Roborock APP" (not the legacy Xiaomi Home APP)
• I tried deleting the robot from my profil and enrolling it again from Xiaomi Home APP; but still not working

What can I do ? Thank you for your help Best regards

[jerome83136]

UPDATE: restarting Node Red fixed the problem for me. Regards

[LokiMidgard]

I have the same problem with a Roborock S7 Max Ultra. Sometimes the system will start working again, but most of the time, I need to restart the server, so it will work for a few hours…