Navigation

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

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    O
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 4
    • Best 0
    • Groups 0

    Olaf

    @Olaf

    0
    Reputation
    5
    Profile views
    4
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Olaf Follow

    Latest posts made by Olaf

    • RE: [Frage] Xiaomi Vacuum cleaner

      ich habe den Token erneut ausgelesen und einfach aus dem Tokenfenster kopiert. Damit sollte eigentlich ein Formatierungsfehler ausgeschlossen sein. Nach dem Neustart hat mit das log file folgendes angezeigt:

      ! ````
      mihome-vacuum.0 2017-08-20 20:57:45.547 info Connected
      mihome-vacuum.0 2017-08-20 20:57:45.545 warn Timedifference between Mihome Vacuum and ioBroker: -2 Sec
      mihome-vacuum.0 2017-08-20 20:57:45.401 info Crate state clean_home for controlling by cloud Adapter
      mihome-vacuum.0 2017-08-20 20:57:45.397 info Expretmode disabled, states deleded
      mihome-vacuum.0 2017-08-20 20:57:45.378 info starting. Version 0.5.7 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v6.11.2
      host.pi-iobroker 2017-08-20 20:57:43.676 info instance system.adapter.mihome-vacuum.0 started with pid 9027
      host.pi-iobroker 2017-08-20 20:57:41.204 info instance system.adapter.mihome-vacuum.0 terminated with code 0 (OK)
      mihome-vacuum.0 2017-08-20 20:57:41.164 info terminating
      host.pi-iobroker 2017-08-20 20:57:41.118 info stopInstance system.adapter.mihome-vacuum.0 killing pid 5733
      host.pi-iobroker 2017-08-20 20:57:41.116 info stopInstance system.adapter.mihome-vacuum.0
      host.pi-iobroker 2017-08-20 20:57:41.100 info object change system.adapter.mihome-vacuum.0

      
      Hier steht etwas von 2 sec. Zeitdifferenz.
      posted in ioBroker Allgemein
      O
      Olaf
    • RE: [Frage] Xiaomi Vacuum cleaner

      Danke, jetzt sollte der komplette Auszug von Start des Adapters sein:

      ! ````
      mihome-vacuum.0 2017-08-20 17:17:06.186 debug sendMsgRaw >>> 2131005000000000034c7b675999a7f24b1364bed98a37a627db945b1fe39c6b11eb7ba5a35afa791ab686570193dcabbbcce0da41a0bb2723ec62a3d43545a8b9a2cda11773a775d16659f31312ce98
      mihome-vacuum.0 2017-08-20 17:17:06.186 debug sendMsg >>> {"id":1005,"method":"get_clean_summary"}
      mihome-vacuum.0 2017-08-20 17:17:06.184 debug lastid{"get_status":1003,"get_consumable":1004,"get_clean_summary":1005,"get_clean_record":0,"X_send_command":0}
      mihome-vacuum.0 2017-08-20 17:17:05.185 debug sendMsgRaw >>> 2131005000000000034c7b675999a7f1796c4a325ea9fe379ac046c2ea901c872746950fe9c9db082fe141afd134508e829e37ec6dcff29314f4038b6157e523f370133043b0e00f57572b2e533525ad
      mihome-vacuum.0 2017-08-20 17:17:05.185 debug sendMsg >>> {"id":1004,"method":"get_consumable"}
      mihome-vacuum.0 2017-08-20 17:17:05.183 debug lastid{"get_status":1003,"get_consumable":1004,"get_clean_summary":1002,"get_clean_record":0,"X_send_command":0}
      mihome-vacuum.0 2017-08-20 17:17:04.213 debug Receive <<< Helo <<< 2131002000000000034c7b675999a7f0ffffffffffffffffffffffffffffffff
      mihome-vacuum.0 2017-08-20 17:17:04.183 debug sendMsgRaw >>> 2131005000000000034c7b675999a7f02036f98fcd8a6dad3bbf96736169bad1fc1650e518718539c05f2476e2d26ae53b4e6729e45262942a0dee132e721b8585a78631b155fadf48d567482f8232dd
      mihome-vacuum.0 2017-08-20 17:17:04.182 debug sendMsg >>> {"id":1003,"method":"get_status"}
      mihome-vacuum.0 2017-08-20 17:17:04.182 debug lastid{"get_status":1003,"get_consumable":1001,"get_clean_summary":1002,"get_clean_record":0,"X_send_command":0}
      mihome-vacuum.0 2017-08-20 17:17:04.181 debug request params all: 60 Sec
      mihome-vacuum.0 2017-08-20 17:16:44.247 debug Receive <<< Helo <<< 2131002000000000034c7b675999a7dcffffffffffffffffffffffffffffffff
      mihome-vacuum.0 2017-08-20 17:16:24.273 debug Receive <<< Helo <<< 2131002000000000034c7b675999a7c8ffffffffffffffffffffffffffffffff
      mihome-vacuum.0 2017-08-20 17:16:06.160 debug sendMsgRaw >>> 2131005000000000034c7b675999a7b688b01622da848c8bbb757ba77e072823aaa021e9485ea2147922700c96721f033bcac905f3435292ace1e76802cb791a3a3f0b6ecf80f0d022a3fca861d4675f
      mihome-vacuum.0 2017-08-20 17:16:06.160 debug sendMsg >>> {"id":1002,"method":"get_clean_summary"}
      mihome-vacuum.0 2017-08-20 17:16:06.158 debug lastid{"get_status":1000,"get_consumable":1001,"get_clean_summary":1002,"get_clean_record":0,"X_send_command":0}
      mihome-vacuum.0 2017-08-20 17:16:05.160 debug sendMsgRaw >>> 2131005000000000034c7b675999a7b52606684cfcaa4adf465f91e319ae16286b46910167181cbe6152a72786a653f76535b040d9975332ee9f3f339e75015b554426d9a7294088fd690818d79b4d92
      mihome-vacuum.0 2017-08-20 17:16:05.159 debug sendMsg >>> {"id":1001,"method":"get_consumable"}
      mihome-vacuum.0 2017-08-20 17:16:05.154 debug lastid{"get_status":1000,"get_consumable":1001,"get_clean_summary":0,"get_clean_record":0,"X_send_command":0}
      mihome-vacuum.0 2017-08-20 17:16:04.203 debug Receive <<< Helo <<< 2131002000000000034c7b675999a7b4ffffffffffffffffffffffffffffffff
      mihome-vacuum.0 2017-08-20 17:16:04.152 debug sendMsgRaw >>> 2131005000000000034c7b675999a7b4ccad5ab5aed36596870ddc542f14757f5296d8137adfc7b6e82a2cb3a5085cb6233e21e41d941ff73332ab81666e5b8acf3648e493a8ca2a4f4d6cdbab00d395
      mihome-vacuum.0 2017-08-20 17:16:04.151 debug sendMsg >>> {"id":1000,"method":"get_status"}
      mihome-vacuum.0 2017-08-20 17:16:04.142 debug lastid{"get_status":1000,"get_consumable":0,"get_clean_summary":0,"get_clean_record":0,"X_send_command":0}
      mihome-vacuum.0 2017-08-20 17:16:04.140 debug request params all: 60 Sec
      mihome-vacuum.0 2017-08-20 17:15:44.236 debug Receive <<< Helo <<< 2131002000000000034c7b675999a7a0ffffffffffffffffffffffffffffffff
      mihome-vacuum.0 2017-08-20 17:15:24.165 debug Receive <<< Helo <<< 2131002000000000034c7b675999a78cffffffffffffffffffffffffffffffff
      mihome-vacuum.0 2017-08-20 17:15:04.311 debug inMem message mihome-vacuum.0.* mihome-vacuum.0.info.connection val=true, ack=true, ts=1503242104305, q=0, from=system.adapter.mihome-vacuum.0, lc=1503242104305
      mihome-vacuum.0 2017-08-20 17:15:04.303 info Connected
      mihome-vacuum.0 2017-08-20 17:15:04.301 debug Receive <<< Helo <<< 2131002000000000034c7b675999a778ffffffffffffffffffffffffffffffff
      mihome-vacuum.0 2017-08-20 17:15:04.141 debug server started on 0.0.0.0:53421
      mihome-vacuum.0 2017-08-20 17:15:04.113 info Crate state clean_home for controlling by cloud Adapter
      mihome-vacuum.0 2017-08-20 17:15:04.110 info Expretmode disabled, states deleded
      mihome-vacuum.0 2017-08-20 17:15:04.099 info starting. Version 0.5.7 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v6.11.2
      mihome-vacuum.0 2017-08-20 17:15:04.010 debug statesDB connected
      mihome-vacuum.0 2017-08-20 17:15:03.936 debug objectDB connected
      host.pi-iobroker 2017-08-20 17:15:02.450 info instance system.adapter.mihome-vacuum.0 started with pid 5657
      host.pi-iobroker 2017-08-20 17:15:02.426 info object change system.adapter.mihome-vacuum.0
      host.pi-iobroker 2017-08-20 17:14:52.522 info instance system.adapter.mihome-vacuum.0 terminated with code 0 (OK)
      mihome-vacuum.0 2017-08-20 17:14:52.487 debug inMem message mihome-vacuum.0.* mihome-vacuum.0.info.connection val=false, ack=true, ts=1503242092481, q=0, from=system.adapter.mihome-vacuum.0, lc=1503242092481
      host.pi-iobroker 2017-08-20 17:14:52.465 info stopInstance system.adapter.mihome-vacuum.0 killing pid 5644
      host.pi-iobroker 2017-08-20 17:14:52.464 info stopInstance system.adapter.mihome-vacuum.0
      host.pi-iobroker 2017-08-20 17:14:52.463 info object change system.adapter.mihome-vacuum.0
      mihome-vacuum.0 2017-08-20 17:14:40.040 debug inMem message mihome-vacuum.0.* mihome-vacuum.0.info.connection val=true, ack=true, ts=1503242080035, q=0, from=system.adapter.mihome-vacuum.0, lc=1503242080035
      mihome-vacuum.0 2017-08-20 17:14:40.033 info Connected
      mihome-vacuum.0 2017-08-20 17:14:40.031 debug Receive <<< Helo <<< 2131002000000000034c7b675999a760ffffffffffffffffffffffffffffffff
      mihome-vacuum.0 2017-08-20 17:14:39.927 debug server started on 0.0.0.0:53421
      mihome-vacuum.0 2017-08-20 17:14:39.900 info Crate state clean_home for controlling by cloud Adapter
      mihome-vacuum.0 2017-08-20 17:14:39.898 info Expretmode disabled, states deleded
      mihome-vacuum.0 2017-08-20 17:14:39.887 info starting. Version 0.5.7 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v6.11.2
      mihome-vacuum.0 2017-08-20 17:14:39.803 debug statesDB connected
      mihome-vacuum.0 2017-08-20 17:14:39.735 debug objectDB connected
      host.pi-iobroker 2017-08-20 17:14:38.185 info instance system.adapter.mihome-vacuum.0 started with pid 5644
      host.pi-iobroker 2017-08-20 17:14:35.718 info instance system.adapter.mihome-vacuum.0 terminated with code 0 (OK)
      mihome-vacuum.0 2017-08-20 17:14:35.654 info terminating
      host.pi-iobroker 2017-08-20 17:14:35.620 info stopInstance system.adapter.mihome-vacuum.0 killing pid 5537
      host.pi-iobroker 2017-08-20 17:14:35.618 info stopInstance system.adapter.mihome-vacuum.0
      host.pi-iobroker 2017-08-20 17:14:35.602 info object change system.adapter.mihome-vacuum.0

      
      geändert: code in code-tags und spoiler gesetzt (****Homoran, Mod.****)
      posted in ioBroker Allgemein
      O
      Olaf
    • RE: [Frage] Xiaomi Vacuum cleaner

      Bin mir nicht ganz sicher, ob du damit diesen Auszug gemeint hast:

      mihome-vacuum.0 2017-08-20 17:06:36.130 info Connected

      mihome-vacuum.0 2017-08-20 17:06:36.071 info Crate state clean_home for controlling by cloud Adapter

      mihome-vacuum.0 2017-08-20 17:06:36.067 info Expretmode disabled, states deleded

      mihome-vacuum.0 2017-08-20 17:06:36.047 info starting. Version 0.5.7 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v6.11.2

      host.pi-iobroker 2017-08-20 17:06:34.425 info instance system.adapter.mihome-vacuum.0 started with pid 5537

      host.pi-iobroker 2017-08-20 17:06:34.400 info object change system.adapter.mihome-vacuum.0

      host.pi-iobroker 2017-08-20 17:06:25.945 info instance system.adapter.mihome-vacuum.0 terminated with code 0 (OK)

      mihome-vacuum.0 2017-08-20 17:06:25.909 info terminating

      host.pi-iobroker 2017-08-20 17:06:25.876 info stopInstance system.adapter.mihome-vacuum.0 killing pid 5471

      host.pi-iobroker 2017-08-20 17:06:25.875 info stopInstance system.adapter.mihome-vacuum.0

      host.pi-iobroker 2017-08-20 17:06:25.874 info object change system.adapter.mihome-vacuum.0

      Falls es nicht stimmt, müsstest du mir sagen, wie ich den log richtig erstelle.

      posted in ioBroker Allgemein
      O
      Olaf
    • RE: [Frage] Xiaomi Vacuum cleaner

      Hallo zusammen,

      ich habe leider das gleiche Problem, dass sich die Daten von meinem mihome-vacuum nicht mehr aktualisieren. Ich habe wie in der Anleitung beschrieben, das main.js upgedatet (habe ich mit winscp gemacht) und danach die Version 0.5.7 des Adapters installiert (Version 0.5.6 war bereits installiert).

      In den Instanzen des iobrokers läuft mein mihome-vacumm zwar, aber in den Objekten aktualisieren sich die Daten des Roboters nicht.

      Ich habe auch mehrmals den Token ausgelesen. Auch nach Neuanmeldung konnte keine Änderung des Tokens festgestellt werden.

      Bin im Moment leider mit meinem Latein am Ende.

      Vielleicht kann mir ja noch jemand Tipps geben, was ich versuchen könnte oder an was es liegen könnte.

      Danke!

      posted in ioBroker Allgemein
      O
      Olaf
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo