Two Instances of Adapter, Second Robot "Helo Message Timeout"

[thedd1337]

I have two instances of mihome-vacuum running on my Pi4 First instance i used for my Roborock S5 and working fine Now i have a new Roborock S7 which can be choosen by the new second instance without any Problems. The S7 has ip address reservation so it will always receive the same ip.

In the Mihome App the Netzwork informtion says 100% strength, no paket loss but in the Adapter i have always a timeout for the Hello Message

Just made another test: If i choose the S7 in the first mihome adapter instance it is working and if i then choose the S5 in the second instance i am having the same issue. So it seems the issue is related to having two instances running at the same time even if they use different ports.

Versions:

• Adapter version: 3.3.1
• JS-Controller version: 3.3.22
• Node version: 12.22.10
• vacuum cleaner: Roborock S7

[ThorstenBoettler]

Same problem here. First instance with standard parameters is working fine. (roborock S50) Second instance (roborock S7) does not connect. It's also not connecting with only one instance. For the second instance I set the port to --> 53425

Logoutput: mihome-vacuum.1 | 2022-04-27 20:03:09.004 | debug | Helo message Timeout mihome-vacuum.1 | 2022-04-27 20:02:57.004 | debug | Helo message Timeout mihome-vacuum.1 | 2022-04-27 20:02:45.003 | debug | Helo message Timeout mihome-vacuum.1 | 2022-04-27 20:02:33.002 | debug | Helo message Timeout mihome-vacuum.1 | 2022-04-27 20:02:31.001 | debug | server started on 0.0.0.0:53425 mihome-vacuum.1 | 2022-04-27 20:02:30.999 | info | IOT enabled, create state mihome-vacuum.1 | 2022-04-27 20:02:30.997 | debug | MIIO: Config: ip:172.16.4.7 token: 5943xxxxxxxxxxxxxxxxxxxx4263746f mihome-vacuum.1 | 2022-04-27 20:02:30.997 | debug | Create State for deviceInfowifi_signal mihome-vacuum.1 | 2022-04-27 20:02:30.997 | debug | Create State for deviceInfofw_ver mihome-vacuum.1 | 2022-04-27 20:02:30.997 | debug | Create State for deviceInfomodel mihome-vacuum.1 | 2022-04-27 20:02:30.996 | debug | Create State for deviceInfomac mihome-vacuum.1 | 2022-04-27 20:02:30.996 | debug | Create State for deviceInfo mihome-vacuum.1 | 2022-04-27 20:02:30.945 | silly | States system redis pmessage system.adapter.mihome-vacuum.1.logLevel/system.adapter.mihome-vacuum.1.logLevel:{"val":"silly","ack":true,"ts":1651082550939,"q":0,"from":"system.adapter.mihome-vacuum.1","lc":1651082550939} mihome-vacuum.1 | 2022-04-27 20:02:30.938 | debug | load Map creator... true mihome-vacuum.1 | 2022-04-27 20:02:30.908 | info | starting. Version 3.3.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.1, js-controller: 4.0.23 mihome-vacuum.1 | 2022-04-27 20:02:30.712 | debug | Plugin sentry Initialize Plugin (enabled=true)

Output of the ports on linux shows: sudo lsof -i -P -n | grep io.mihome io.mihome 7834 iobroker 20u IPv4 11201042 0t0 TCP 127.0.0.1:60250->127.0.0.1:9001 (ESTABLISHED) io.mihome 7834 iobroker 21u IPv4 11201043 0t0 TCP 127.0.0.1:60258->127.0.0.1:9001 (ESTABLISHED) io.mihome 7834 iobroker 22u IPv4 11201044 0t0 TCP 127.0.0.1:60260->127.0.0.1:9001 (ESTABLISHED) io.mihome 7834 iobroker 23u IPv4 11201045 0t0 TCP 127.0.0.1:35632->127.0.0.1:9000 (ESTABLISHED) io.mihome 7834 iobroker 24u IPv4 11201046 0t0 TCP 127.0.0.1:35634->127.0.0.1:9000 (ESTABLISHED) io.mihome 7834 iobroker 25u IPv4 11201047 0t0 TCP 127.0.0.1:35636->127.0.0.1:9000 (ESTABLISHED) io.mihome 7834 iobroker 27u IPv4 11203860 0t0 UDP :53425 io.mihome 26575 iobroker 20u IPv4 10068740 0t0 TCP 127.0.0.1:50126->127.0.0.1:9001 (ESTABLISHED) io.mihome 26575 iobroker 21u IPv4 10068743 0t0 TCP 127.0.0.1:50134->127.0.0.1:9001 (ESTABLISHED) io.mihome 26575 iobroker 22u IPv4 10068744 0t0 TCP 127.0.0.1:50136->127.0.0.1:9001 (ESTABLISHED) io.mihome 26575 iobroker 23u IPv4 10068745 0t0 TCP 127.0.0.1:53736->127.0.0.1:9000 (ESTABLISHED) io.mihome 26575 iobroker 24u IPv4 10070856 0t0 TCP 127.0.0.1:53750->127.0.0.1:9000 (ESTABLISHED) io.mihome 26575 iobroker 25u IPv4 10070857 0t0 TCP 127.0.0.1:53752->127.0.0.1:9000 (ESTABLISHED) io.mihome 26575 iobroker 27u IPv4 10072464 0t0 UDP :53421

Even in a complete fresh installed ioBroker the adapter can not connect the S7. (only one adapter) maybe as an hint, the Xiaomi Cloud Server location is USA. --> moved to Germany, same problem

Roborock has fixed IP and is useable with the xiaomi app. The IP is also reachable (Ping) from the iobroker device (before the roborock was used withe the roborock app, but I removed it there)

[dirkhe]

For the second instance you only have to change the own port (eigener Port) not the robot port. Also the s7 must be in the same subnet as iobroker

[dirkhe]

is the problem still exist?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[stale[bot]]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions. Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.