Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. moviehunter

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    M
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 9
    • Best 0
    • Groups 1

    moviehunter

    @moviehunter

    Starter

    -1
    Reputation
    6
    Profile views
    9
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    moviehunter Follow
    Starter

    Latest posts made by moviehunter

    • RE: Test Adapter mihome-vacuum v2.0.x

      @meistertr said in Test Adapter mihome-vacuum v2.0.x:

      @moviehunter lies mal 2 Posts weiter oben!! du hast auch die viomi modelle die aufgrund der geänderten api nicht mit der version 2 gehen, lad mal diese version (ACHTUNG ALPHA) https://github.com/MeisterTR/ioBroker.mihome-vacuum

      @meistertr

      Moin,
      planst du zu der Alpha noch eine Weiterentwicklung?
      Denn einige Punkte fehlen ja noch.

      Und was mir aufgefallen ist:
      Wenn ich den Sauger über den Adapter starte fährt er komische Wellen. Einmal vor, dann zurück und dann schräg rechts vor, dann wieder zurück, dann wieder schräg links vor usw...
      Wenn ich den Sauger über die Xiaomi App starte fährt er ganz normal.

      Würde mich über eine Weiterentwicklung sehr freuen. Stehe auch gerne als Testperson zur Verfügung. 🙂

      posted in Tester
      M
      moviehunter
    • RE: Test Adapter mihome-vacuum v2.0.x

      @Meistertr @weimaraner
      hat geklappt. Hab den falschen Port angepasst gehabt.
      Danke.

      posted in Tester
      M
      moviehunter
    • RE: Test Adapter mihome-vacuum v2.0.x

      @Meistertr

      super, das hat geklappt. Danke.
      Aber mehrere Instanzen sind noch nicht möglich..oder?
      Zumindest bekomme ich sobald ich eine zweite anlege bei keiner mehr eine Verbindung.

      posted in Tester
      M
      moviehunter
    • RE: Test Adapter mihome-vacuum v2.0.x

      Moin,

      ich habe mittlerweile zwei Sauger an zwei Standorten (somit auch verschiedenen Routern und verschiedenen Installationen vom ioborker)
      Bei beiden bekomme ich keine Verbindung zum Sauger.
      In der Xiaomi Home App laufen beide einwandfrei.
      Über mein Konto kann ich sie auch beide in den iobroker einbinden.
      Aber weiter geht es nicht. Unter Objekte kann ich zwar auf Start drücken, aber es kommt nichts beim Sauger an.
      Zum einen habe ich den Xiaomi Mi Robot Vacuum Mop und zum anderen den Xiaomi Mi Robot Vacuum Mop Pro.

      Ländereinstellung/Server steht im Adapter, sowie in der App auf Deutschland. Habe mal gelesen, dass es da sinnvoll ist auf China zu stellen...ist das so?

      Hier ein Auszug aus meinem log.

      mihome-vacuum.0	2020-10-22 07:30:31.700	debug	(628) no answer for get_status(id:13410) received, giving up
      mihome-vacuum.0	2020-10-22 07:30:30.037	debug	(628) system.adapter.admin.0: logging true
      mihome-vacuum.0	2020-10-22 07:30:25.727	info	(628) should trigger cleaning all null, but is currently active. Add to queue
      mihome-vacuum.0	2020-10-22 07:30:25.719	debug	(628) sendTo "startVacuuming" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-10-22 07:30:25.719	debug	(628) stateChange mihome-vacuum.0.control.start {"val":true,"ack":false,"ts":1603344625718,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1603262874086}
      mihome-vacuum.0	2020-10-22 07:30:25.278	debug	(628) requesting params every: 60 Sec
      mihome-vacuum.0	2020-10-22 07:30:25.277	info	(628) Connected
      mihome-vacuum.0	2020-10-22 07:30:25.253	info	(628) Disconnect
      mihome-vacuum.0	2020-10-22 07:30:23.253	info	(628) should trigger cleaning all null, but is currently active. Add to queue
      mihome-vacuum.0	2020-10-22 07:30:23.252	debug	(628) sendTo "startVacuuming" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-10-22 07:30:23.252	debug	(628) stateChange mihome-vacuum.0.control.start {"val":true,"ack":false,"ts":1603344623218,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1603262874086}
      mihome-vacuum.0	2020-10-22 07:30:19.828	debug	(628) no answer for get_sound_volume(id:13408) received, giving up
      mihome-vacuum.0	2020-10-22 07:30:19.629	debug	(628) no answer for get_clean_summary(id:13407) received, giving up
      mihome-vacuum.0	2020-10-22 07:30:19.429	debug	(628) no answer for get_consumable(id:13406) received, giving up
      mihome-vacuum.0	2020-10-22 07:30:11.699	debug	(628) no answer for get_status(id:13405) received, giving up
      mihome-vacuum.0	2020-10-22 07:30:04.426	debug	(628) requesting params every: 60 Sec
      mihome-vacuum.0	2020-10-22 07:29:52.200	debug	(628) no answer for get_sound_volume(id:13403) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:52.000	debug	(628) no answer for get_clean_summary(id:13402) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:51.800	debug	(628) no answer for get_consumable(id:13401) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:51.799	debug	(628) no answer for get_status(id:13400) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:36.798	debug	(628) requesting params every: 60 Sec
      mihome-vacuum.0	2020-10-22 07:29:36.797	info	(628) Connected
      mihome-vacuum.0	2020-10-22 07:29:36.697	info	(628) Disconnect
      mihome-vacuum.0	2020-10-22 07:29:31.698	debug	(628) no answer for get_status(id:13399) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:19.830	debug	(628) no answer for get_sound_volume(id:13397) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:19.630	debug	(628) no answer for get_clean_summary(id:13396) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:19.430	debug	(628) no answer for get_consumable(id:13395) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:12.265	debug	(628) no answer for get_sound_volume(id:13393) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:12.065	debug	(628) no answer for get_clean_summary(id:13392) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:11.864	debug	(628) no answer for get_consumable(id:13391) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:11.864	debug	(628) no answer for get_status(id:13390) received, giving up
      mihome-vacuum.0	2020-10-22 07:29:04.427	debug	(628) requesting params every: 60 Sec
      mihome-vacuum.0	2020-10-22 07:28:56.862	debug	(628) requesting params every: 60 Sec
      mihome-vacuum.0	2020-10-22 07:28:56.861	info	(628) Connected
      mihome-vacuum.0	2020-10-22 07:28:56.695	info	(628) Disconnect
      mihome-vacuum.0	2020-10-22 07:28:51.697	debug	(628) no answer for get_status(id:13389) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:49.733	debug	(628) no answer for undefined(id:13388) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:43.183	debug	(628) no answer for get_sound_volume(id:13386) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:42.984	debug	(628) no answer for get_clean_summary(id:13385) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:42.781	debug	(628) no answer for get_consumable(id:13384) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:42.781	debug	(628) no answer for get_status(id:13383) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:38.666	debug	(628) system.adapter.admin.0: logging false
      mihome-vacuum.0	2020-10-22 07:28:34.693	info	(628) trigger cleaning all null
      mihome-vacuum.0	2020-10-22 07:28:34.443	debug	(628) sendTo "startVacuuming" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-10-22 07:28:34.367	debug	(628) stateChange mihome-vacuum.0.control.start {"val":true,"ack":false,"ts":1603344514357,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1603262874086}
      mihome-vacuum.0	2020-10-22 07:28:27.780	debug	(628) requesting params every: 60 Sec
      mihome-vacuum.0	2020-10-22 07:28:27.779	info	(628) Connected
      mihome-vacuum.0	2020-10-22 07:28:27.698	info	(628) Disconnect
      mihome-vacuum.0	2020-10-22 07:28:22.699	debug	(628) no answer for get_status(id:13382) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:19.830	debug	(628) no answer for get_sound_volume(id:13380) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:19.628	debug	(628) no answer for get_clean_summary(id:13379) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:19.427	debug	(628) no answer for get_consumable(id:13378) received, giving up
      mihome-vacuum.0	2020-10-22 07:28:04.426	debug	(628) requesting params every: 60 Sec
      mihome-vacuum.0	2020-10-22 07:28:02.698	debug	(628) no answer for get_status(id:13377) received, giving up
      mihome-vacuum.0	2020-10-22 07:27:43.100	debug	(628) no answer for get_sound_volume(id:13375) received, giving up
      mihome-vacuum.0	2020-10-22 07:27:42.902	debug	(628) no answer for get_clean_summary(id:13374) received, giving up
      mihome-vacuum.0	2020-10-22 07:27:42.701	debug	(628) no answer for get_consumable(id:13373) received, giving up
      mihome-vacuum.0	2020-10-22 07:27:42.700	debug	(628) no answer for get_status(id:13372) received, giving up
      mihome-vacuum.0	2020-10-22 07:27:27.699	debug	(628) requesting params every: 60 Sec
      mihome-vacuum.0	2020-10-22 07:27:27.698	info	(628) Connected
      mihome-vacuum.0	2020-10-22 07:27:27.695	info	(628) Disconnect
      mihome-vacuum.0	2020-10-22 07:27:22.697	debug	(628) no answer for get_status(id:13371) received, giving up
      mihome-vacuum.0	2020-10-22 07:27:19.829	debug	(628) no answer for get_sound_volume(id:13369) received, giving up
      mihome-vacuum.0	2020-10-22 07:27:19.629	debug	(628) no answer for get_clean_summary(id:13368) received, giving up
      mihome-vacuum.0	2020-10-22 07:27:19.428	debug	(628) no answer for get_consumable(id:13367) received, giving up
      mihome-vacuum.0	2020-10-22 07:27:04.426	debug	(628) requesting params every: 60 Sec
      mihome-vacuum.0	2020-10-22 07:27:02.695	debug	(628) no answer for get_status(id:13366) received, giving up
      mihome-vacuum.0	2020-10-22 07:26:43.169	debug	(628) no answer for get_sound_volume(id:13364) received, giving up
      mihome-vacuum.0	2020-10-22 07:26:42.969	debug	(628) no answer for get_clean_summary(id:13363) received, giving up
      mihome-vacuum.0	2020-10-22 07:26:42.770	debug	(628) no answer for get_consumable(id:13362) received, giving up
      

      Habt ihr eine Lösung dafür?

      posted in Tester
      M
      moviehunter
    • RE: Test Adapter mihome-vacuum v2.0.x

      @moviehunter said in Test Adapter mihome-vacuum v2.0.x:

      @dirkhe Ja klar...im iobroker habe ich den Adapter mihome-vacuum Version 2.2.3
      Also Android App nutze ich die Xiaomi Home App Version 5.8.7

      Den Token beziehe ich ja durch das Eingeben meiner Zugangsdaten aus der Android App.
      Dann muss ich den Token ja unten nochmal manuell eingeben oder sehe ich das falsch? Jedenfalls wenn ich das nicht tue, bekomme ich immer eine Fehlermeldung beim speichern.

      Was genau bedeuten denn die drei Zeilen, wenn man über den bei mir gelben Button geht bei Instanzen?
      Verbunden mit Host: wahr
      Lebenszeichen: wahr
      Verbunden mit mihome-vacuum: falsch

      Habe jetzt nochmal die stable 2.0.7 installiert. Dort ist die Lampe wieder grün aber trotzdem keine Reaktion vom Sauber...

      Hier mal ein Auszug ausm Log:

      mihome-vacuum.0	2020-09-01 20:50:41.069	debug	(1229) no answer for get_sound_volume(id:62) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:40.869	debug	(1229) no answer for get_clean_summary(id:61) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:40.669	debug	(1229) no answer for get_consumable(id:60) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:39.126	debug	(1229) no answer for get_sound_volume(id:58) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:38.930	debug	(1229) no answer for get_clean_summary(id:57) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:38.724	debug	(1229) no answer for get_consumable(id:56) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:38.525	debug	(1229) no answer for get_status(id:54) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:26.619	debug	(1229) no answer for get_status(id:53) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:25.461	debug	(1229) requesting params every: 60 Sec
      mihome-vacuum.0	2020-09-01 20:50:23.517	debug	(1229) requesting params every: 60 Sec
      mihome-vacuum.0	2020-09-01 20:50:23.514	info	(1229) Connected
      mihome-vacuum.0	2020-09-01 20:50:23.402	info	(1229) Disconnect
      mihome-vacuum.0	2020-09-01 20:50:21.401	info	(1229) should trigger cleaning all null, but is currently active. Add to queue
      mihome-vacuum.0	2020-09-01 20:50:21.396	debug	(1229) sendTo "startVacuuming" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-09-01 20:50:21.395	debug	(1229) stateChange mihome-vacuum.0.control.start {"val":true,"ack":false,"ts":1598986221392,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1598986056217}
      mihome-vacuum.0	2020-09-01 20:50:16.618	debug	(1229) no answer for get_status(id:52) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:07.258	debug	(1229) no answer for get_sound_volume(id:51) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:07.057	debug	(1229) no answer for get_clean_summary(id:50) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:06.857	debug	(1229) no answer for get_consumable(id:49) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:06.653	debug	(1229) no answer for get_status(id:47) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:56.590	debug	(1229) no answer for get_status(id:46) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:51.649	debug	(1229) requesting params every: 60 Sec
      mihome-vacuum.0	2020-09-01 20:49:51.646	info	(1229) Connected
      mihome-vacuum.0	2020-09-01 20:49:51.586	info	(1229) Disconnect
      mihome-vacuum.0	2020-09-01 20:49:46.589	debug	(1229) no answer for get_status(id:45) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:41.072	debug	(1229) no answer for get_sound_volume(id:44) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:40.870	debug	(1229) no answer for get_clean_summary(id:43) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:40.668	debug	(1229) no answer for get_consumable(id:42) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:37.255	debug	(1229) no answer for get_sound_volume(id:40) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:37.055	debug	(1229) no answer for get_clean_summary(id:39) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:36.853	debug	(1229) no answer for get_consumable(id:38) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:36.651	debug	(1229) no answer for get_status(id:36) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:26.583	debug	(1229) no answer for get_status(id:35) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:25.461	debug	(1229) requesting params every: 60 Sec
      

      Ist der Adapter für alle Xiaomi Roboter kompatibel?

      posted in Tester
      M
      moviehunter
    • RE: Test Adapter mihome-vacuum v2.0.x

      @dirkhe Ja klar...im iobroker habe ich den Adapter mihome-vacuum Version 2.2.3
      Also Android App nutze ich die Xiaomi Home App Version 5.8.7

      Den Token beziehe ich ja durch das Eingeben meiner Zugangsdaten aus der Android App.
      Dann muss ich den Token ja unten nochmal manuell eingeben oder sehe ich das falsch? Jedenfalls wenn ich das nicht tue, bekomme ich immer eine Fehlermeldung beim speichern.

      Was genau bedeuten denn die drei Zeilen, wenn man über den bei mir gelben Button geht bei Instanzen?
      Verbunden mit Host: wahr
      Lebenszeichen: wahr
      Verbunden mit mihome-vacuum: falsch

      Habe jetzt nochmal die stable 2.0.7 installiert. Dort ist die Lampe wieder grün aber trotzdem keine Reaktion vom Sauber...

      Hier mal ein Auszug ausm Log:

      mihome-vacuum.0	2020-09-01 20:50:41.069	debug	(1229) no answer for get_sound_volume(id:62) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:40.869	debug	(1229) no answer for get_clean_summary(id:61) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:40.669	debug	(1229) no answer for get_consumable(id:60) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:39.126	debug	(1229) no answer for get_sound_volume(id:58) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:38.930	debug	(1229) no answer for get_clean_summary(id:57) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:38.724	debug	(1229) no answer for get_consumable(id:56) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:38.525	debug	(1229) no answer for get_status(id:54) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:26.619	debug	(1229) no answer for get_status(id:53) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:25.461	debug	(1229) requesting params every: 60 Sec
      mihome-vacuum.0	2020-09-01 20:50:23.517	debug	(1229) requesting params every: 60 Sec
      mihome-vacuum.0	2020-09-01 20:50:23.514	info	(1229) Connected
      mihome-vacuum.0	2020-09-01 20:50:23.402	info	(1229) Disconnect
      mihome-vacuum.0	2020-09-01 20:50:21.401	info	(1229) should trigger cleaning all null, but is currently active. Add to queue
      mihome-vacuum.0	2020-09-01 20:50:21.396	debug	(1229) sendTo "startVacuuming" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-09-01 20:50:21.395	debug	(1229) stateChange mihome-vacuum.0.control.start {"val":true,"ack":false,"ts":1598986221392,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1598986056217}
      mihome-vacuum.0	2020-09-01 20:50:16.618	debug	(1229) no answer for get_status(id:52) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:07.258	debug	(1229) no answer for get_sound_volume(id:51) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:07.057	debug	(1229) no answer for get_clean_summary(id:50) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:06.857	debug	(1229) no answer for get_consumable(id:49) received, giving up
      mihome-vacuum.0	2020-09-01 20:50:06.653	debug	(1229) no answer for get_status(id:47) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:56.590	debug	(1229) no answer for get_status(id:46) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:51.649	debug	(1229) requesting params every: 60 Sec
      mihome-vacuum.0	2020-09-01 20:49:51.646	info	(1229) Connected
      mihome-vacuum.0	2020-09-01 20:49:51.586	info	(1229) Disconnect
      mihome-vacuum.0	2020-09-01 20:49:46.589	debug	(1229) no answer for get_status(id:45) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:41.072	debug	(1229) no answer for get_sound_volume(id:44) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:40.870	debug	(1229) no answer for get_clean_summary(id:43) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:40.668	debug	(1229) no answer for get_consumable(id:42) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:37.255	debug	(1229) no answer for get_sound_volume(id:40) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:37.055	debug	(1229) no answer for get_clean_summary(id:39) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:36.853	debug	(1229) no answer for get_consumable(id:38) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:36.651	debug	(1229) no answer for get_status(id:36) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:26.583	debug	(1229) no answer for get_status(id:35) received, giving up
      mihome-vacuum.0	2020-09-01 20:49:25.461	debug	(1229) requesting params every: 60 Sec
      
      posted in Tester
      M
      moviehunter
    • RE: Test Adapter mihome-vacuum v2.0.x

      @dirkhe

      danke für die Rückmeldung.
      Das mit dem App öffnen klappt leider nicht. Nutze die App regelmäßig um den Sauber zu starten, teilweise von zu Hause, teilweise von unterwegs. Somit kann ich auf jeden Fall gewährleisten, dass der Sauger Internet hat.
      Den Token habe ich nun 3mal neu eingegeben, ohne Besserung.
      Bekomme bei "Verbunden mit mihome-vacuum" einfach keine Verbindung.
      Hatte vorher die stable Version 2.0.7 installiert.
      Dort hatte ich bei "Verbunden mit mihome-vacuum" ein true...trotzdem hat sich der Sauger nicht gerührt.
      Nun bei der aktuell installierten 2.2.3 habe ich bei "Verbunden mit mihome-vacuum" ein false und natürlich tut sich beim Sauger auch nichts... Hast du weitere Lösungsvorschläge?

      Viele Grüße

      posted in Tester
      M
      moviehunter
    • RE: Test Adapter mihome-vacuum v2.0.x

      @moviehunter said in Test Adapter mihome-vacuum v2.0.x:

      @haselchen @Meistertr @dirkhe

      ich habe das gleiche Problem allerdings mit Version 2.2.3
      Token sind bei mir beide identisch

      Hier ein Auszug meines logs...

      mihome-vacuum.0	2020-08-25 21:13:38.365	debug	(6318) sendMsg[1] >>> {"id":2,"method":"get_status"}
      mihome-vacuum.0	2020-08-25 21:13:38.360	debug	(6318) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-08-25 21:13:38.359	info	(6318) connecting, this can take up to 10 minutes ...
      mihome-vacuum.0	2020-08-25 21:13:38.357	debug	(6318) Receive <<< Helo <<< 213100200000000013d62eac5f4562e2ffffffffffffffffffffffffffffffff
      mihome-vacuum.0	2020-08-25 21:13:33.412	debug	(6318) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-08-25 21:13:33.411	debug	(6318) no answer for id:1 received, giving up
      mihome-vacuum.0	2020-08-25 21:13:28.410	debug	(6318) sendMsg[3] >>> {"id":1,"method":"get_status"}
      mihome-vacuum.0	2020-08-25 21:13:23.408	debug	(6318) sendMsg[2] >>> {"id":1,"method":"get_status"}
      mihome-vacuum.0	2020-08-25 21:13:18.836	info	(6318) set nächster Timer: Nicht verfügbar
      mihome-vacuum.0	2020-08-25 21:13:18.407	debug	(6318) sendMsg[1] >>> {"id":1,"method":"get_status"}
      mihome-vacuum.0	2020-08-25 21:13:18.396	debug	(6318) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-08-25 21:13:18.395	info	(6318) connecting, this can take up to 10 minutes ...
      mihome-vacuum.0	2020-08-25 21:13:18.393	debug	(6318) Receive <<< Helo <<< 213100200000000013d62eac5f4562ceffffffffffffffffffffffffffffffff
      mihome-vacuum.0	2020-08-25 21:13:18.377	debug	(6318) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      mihome-vacuum.0	2020-08-25 21:13:18.341	debug	(6318) server started on 0.0.0.0:53421
      mihome-vacuum.0	2020-08-25 21:13:18.316	info	(6318) Cloud control disabled
      mihome-vacuum.0	2020-08-25 21:13:18.314	info	(6318) Expert mode disabled, states deleted
      mihome-vacuum.0	2020-08-25 21:13:18.258	info	(6318) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.21.0, js-controller: 3.1.6
      

      kannst du mir auch weiter helfen? Bekomme keine Verbindung zum Sauger...

      Welche Informationen benötigt ihr, um mir helfen zu können?

      posted in Tester
      M
      moviehunter
    • RE: Test Adapter mihome-vacuum v2.0.x

      @haselchen @Meistertr @dirkhe

      ich habe das gleiche Problem allerdings mit Version 2.2.3
      Token sind bei mir beide identisch

      Hier ein Auszug meines logs...

      mihome-vacuum.0	2020-08-25 21:13:38.365	debug	(6318) sendMsg[1] >>> {"id":2,"method":"get_status"}
      mihome-vacuum.0	2020-08-25 21:13:38.360	debug	(6318) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-08-25 21:13:38.359	info	(6318) connecting, this can take up to 10 minutes ...
      mihome-vacuum.0	2020-08-25 21:13:38.357	debug	(6318) Receive <<< Helo <<< 213100200000000013d62eac5f4562e2ffffffffffffffffffffffffffffffff
      mihome-vacuum.0	2020-08-25 21:13:33.412	debug	(6318) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-08-25 21:13:33.411	debug	(6318) no answer for id:1 received, giving up
      mihome-vacuum.0	2020-08-25 21:13:28.410	debug	(6318) sendMsg[3] >>> {"id":1,"method":"get_status"}
      mihome-vacuum.0	2020-08-25 21:13:23.408	debug	(6318) sendMsg[2] >>> {"id":1,"method":"get_status"}
      mihome-vacuum.0	2020-08-25 21:13:18.836	info	(6318) set nächster Timer: Nicht verfügbar
      mihome-vacuum.0	2020-08-25 21:13:18.407	debug	(6318) sendMsg[1] >>> {"id":1,"method":"get_status"}
      mihome-vacuum.0	2020-08-25 21:13:18.396	debug	(6318) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
      mihome-vacuum.0	2020-08-25 21:13:18.395	info	(6318) connecting, this can take up to 10 minutes ...
      mihome-vacuum.0	2020-08-25 21:13:18.393	debug	(6318) Receive <<< Helo <<< 213100200000000013d62eac5f4562ceffffffffffffffffffffffffffffffff
      mihome-vacuum.0	2020-08-25 21:13:18.377	debug	(6318) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
      mihome-vacuum.0	2020-08-25 21:13:18.341	debug	(6318) server started on 0.0.0.0:53421
      mihome-vacuum.0	2020-08-25 21:13:18.316	info	(6318) Cloud control disabled
      mihome-vacuum.0	2020-08-25 21:13:18.314	info	(6318) Expert mode disabled, states deleted
      mihome-vacuum.0	2020-08-25 21:13:18.258	info	(6318) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.21.0, js-controller: 3.1.6
      

      kannst du mir auch weiter helfen? Bekomme keine Verbindung zum Sauger...

      posted in Tester
      M
      moviehunter
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo