Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Alpha Homekit-Controller 0.0.x

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    Test Alpha Homekit-Controller 0.0.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tklein @apollon77 last edited by

      @apollon77 said in Test Alpha Homekit-Controller 0.0.x:

      1.) EHOSTUNREACH bedeutet das das gerät in deinem Netzwerk nicht erreichbar war zu dem Zeitpunkt
      --> thx für die Info
      2.) Was heisst "in Vocolinc App konfiguriert"? Hast du es dann dort gepaired? Naja dann kanns nicht nochmal sein
      --> nachdem es nach dem reset nicht geklappt hatte, habe ich das Device in der entsprechende App angelernt. Mir war/ist nicht bekannt, wie nach einem Device ohne konfigurierten WLAN nur mit dem Code eine Verbindung mit dem IOB erstellt werden kann
      3.) Ich denke das Gerät hat mit dem Reset (oder dem pairing) seine ID gendert, damit kennt der Adapter beide. Kannst du in den Adapter-Objekten löschen
      --> ok, werde ich dann löschen

      1 Reply Last reply Reply Quote 0
      • P
        pql @apollon77 last edited by

        @apollon77 Versuche ein Eve Energy zu koppeln, aber ohne Erfolg.
        Hardware ist ein RPI4 mit integriertem Bluetooth.

        Noch eine Idee?

        2022-02-13 12:30:06.032  - debug: homekit-controller.0 (17060) Discovered BLE device up: 0d:30:8f:xx:xx:xx/Eve Energy EA06
2022-02-13 12:30:06.033  - debug: homekit-controller.0 (17060) BLE-0D:30:8F:xx:xx:xx Discovered BLE device: {"name":"Eve Energy EA06","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"0d:30:8f:xx:xx:xx","ACID":7,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"0d:30:8f:xx:xx:xx","ci":7,"availableToPair":true}
2022-02-13 12:30:06.035  - info: homekit-controller.0 (17060) BLE-0D:30:8F:xx:xx:xx (Eve Energy EA06) found without pairing data but available for pairing: Create basic objects
2022-02-13 12:30:06.036  - debug: homekit-controller.0 (17060) Service: {"name":"Eve Energy EA06","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"0d:30:8f:xx:xx:xx","ACID":7,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"0d:30:8f:xx:xx:xx","ci":7,"availableToPair":true}
2022-02-13 12:30:06.088  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.info.connectionType changed: BLE (ack = true)
2022-02-13 12:30:06.114  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.info.id changed: 0d:30:8f:xx:xx:xx (ack = true)
2022-02-13 12:30:06.136  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.info.connected changed: false (ack = true)
2022-02-13 12:30:06.158  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.admin.isPaired changed: false (ack = true)
2022-02-13 12:30:06.171  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.info.lastDiscovered changed: 1644751806037 (ack = true)
2022-02-13 12:30:36.166  - debug: homekit-controller.0 (17060) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":77,"ack":false,"time":1644751836163},"_id":61388363})
2022-02-13 12:30:36.167  - debug: homekit-controller.0 (17060) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-0D:30:8F:xx:xx:xx","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Energy EA06","discoveredCategory":"Outlet","pairedWithThisInstance":false},{"id":"BLE-14:36:5E:xx:xx:xx","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Nuki_XXXXX","discoveredCategory":"Lock","pairedWithThisInstance":false}]}
2022-02-13 12:30:36.169  - debug: homekit-controller.0 (17060) sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0
2022-02-13 12:30:48.359  - debug: homekit-controller.0 (17060) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx","pin":"yyy-yy-yyy"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx","pin":"yyy-yy-yyy"},"id":78,"ack":false,"time":1644751848356},"_id":61388364})
  hap-controller:gatt-connection connect peripheral +0ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Write for characteristic 0000004f0000100080000026bb765291 0003001100 +857ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Received data for characteristic 0000004f0000100080000026bb765291 0200000300010102 +58ms
  hap-controller:gatt-connection disconnect peripheral +1ms
  hap-controller:gatt-connection Peripheral disconnected +16ms
2022-02-13 12:30:49.301  - info: homekit-controller.0 (17060) Use PairMethod 0 to pair BLE-0D:30:8F:xx:xx:xx
2022-02-13 12:30:49.303  - debug: homekit-controller.0 (17060) BLE-0D:30:8F:xx:xx:xx Start Homekit Device Client initialization
  hap-controller:gatt-connection connect peripheral +8ms
  hap-controller:gatt-connection Peripheral disconnected +308ms
2022-02-13 12:30:49.616  - debug: homekit-controller.0 (17060) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-0D:30:8F:xx:xx:xx because of error undefined (undefined): undefined"}
2022-02-13 12:30:49.617  - debug: homekit-controller.0 (17060) sendTo "pairDevice" to system.adapter.admin.0 from system.adapter.homekit-controller.0
        apollon77 1 Reply Last reply Reply Quote 0
        • apollon77
          apollon77 @pql last edited by

          @pql In dem Fall bekommt das Adapter keine Antwort vom Gerät. Geht ein Identify? Ich hab inzwischen so bissl da sGefühl das der RPI "Onboard" BLE zickig ist ... ggf mal mit nem BLE USB Stick versuchen?

          P 1 Reply Last reply Reply Quote 0
          • P
            pql @apollon77 last edited by

            @apollon77 Identify funktioniert, Gerät blinkt entsprechend und der Debug bestätigt dies auch mit einem "Success"

            2022-02-13 13:36:36.527  - debug: homekit-controller.0 (28302) Message identify received: {"command":"identify","message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx"},"id":95,"ack":false,"time":1644755796524},"_id":61388381})
2022-02-13 13:36:36.529  - debug: homekit-controller.0 (28302) Device BLE-0D:30:8F:xx:xx:xx: Identify triggered
  hap-controller:gatt-connection connect peripheral +0ms
  hap-controller:tlv Add 1 bytes for tag 1: 01 +0ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Write for characteristic 000000140000100080000026bb765291 00020002000300010101 +924ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Received data for characteristic 000000140000100080000026bb765291 020000 +59ms
  hap-controller:gatt-connection disconnect peripheral +0ms
  hap-controller:gatt-connection Peripheral disconnected +17ms
2022-02-13 13:36:37.538  - debug: homekit-controller.0 (28302) Response to Command identify: {"success":true,"error":false}
2022-02-13 13:36:37.542  - debug: homekit-controller.0 (28302) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0

            USB BLE Stick hab ich nicht zur Hand, müsste mir dann erst einen besorgen

            apollon77 1 Reply Last reply Reply Quote 0
            • apollon77
              apollon77 @pql last edited by apollon77

              @pql Also beimn Pairen sieht man das das Gerät auf den Connect versuch antwortet wo die unterstützten Pairing Methoden gelesen werden.Danach aber eine zweite Verbindung nicht annimmt um das eigentliche Pairing zu machen. Ich schaue nachher nochmal

              EDIT: Code Seitig sieht an sich alles korrekt aus ... keine Ahnung warum das zickt und kann es auch nicht nachstellen

              P 1 Reply Last reply Reply Quote 0
              • P
                pql @apollon77 last edited by

                @apollon77 Hab jetzt einen USB Stick, gleiches Spiel; Identify funktioniert, Pairing nicht.

                Log-Output ist diesmal aber etwas mehr was den Pairing Connect an geht.. Es kommt auf jeden Fall etwas zurück

                2022-02-15 17:46:01.425  - debug: homekit-controller.0 (3773) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx","pin":"xxx-xx-xxx"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx","pin":"xxx-xx-xxx"},"id":16,"ack":false,"time":1644943561422},"_id":32016392})
  hap-controller:gatt-connection connect peripheral +16s
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Write for characteristic 0000004f0000100080000026bb765291 0003001100 +538ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Received data for characteristic 0000004f0000100080000026bb765291 0200000300010102 +75ms
  hap-controller:gatt-connection disconnect peripheral +0ms
  hap-controller:gatt-connection Peripheral disconnected +2s
2022-02-15 17:46:04.048  - info: homekit-controller.0 (3773) Use PairMethod 0 to pair BLE-0D:30:8F:xx:xx:xx
2022-02-15 17:46:04.051  - debug: homekit-controller.0 (3773) BLE-0D:30:8F:xx:xx:xx Start Homekit Device Client initialization
  hap-controller:gatt-connection connect peripheral +7ms
  hap-controller:tlv Add 1 bytes for tag 6: 01 +19s
  hap-controller:tlv Add 1 bytes for tag 0: 00 +1ms
  hap-controller:tlv Add 6 bytes for tag 1: 060101000100 +0ms
  hap-controller:tlv Add 1 bytes for tag 9: 01 +0ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Write for characteristic 0000004c0000100080000026bb765291 0002000f000b000106060101000100090101 +435ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Received data for characteristic 0000004c0000100080000026bb765291 0200009d0101ff06010203ff78b224faeea2de3cf805707ecd32546d248663b4689e88ff20ccefbeb56632d66398a9baea47555684b3b09ec4afe72c4ed3c33f5ce78c69fa7191cad76c879e22e51321de66442d9c89850c39546c8e3643679ac751d8d539b0c73c56dd8280be4d14215ee81e1eeb14cc05061cb6e486aeb00699207138d0577e288bba6fb6c23c97c3157f69f2ba8da537ad274cab0d5f76cff5b4ae9a828cdac434a42bcbe0132f8c3638a48de223a01d2ba06c92284efbaa3b25c3742ac138b1ad182fa614d12fdfa44cb89ccf3323cf92e8d7627dcdb1ba27403853fea875693785a68ee6731e96172ad3f04677bc57a36352f5b0ff5e +583ms
  hap-controller:gatt-connection Peripheral disconnected +45ms
2022-02-15 17:46:05.118  - debug: homekit-controller.0 (3773) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-0D:30:8F:xx:xx:xx because of error undefined (undefined): undefined"}
2022-02-15 17:46:05.119  - debug: homekit-controller.0 (3773) sendTo "pairDevice" to system.adapter.admin.0 from system.adapter.homekit-controller.0
                apollon77 1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @pql last edited by apollon77

                  @pql Inndem Fall kommt er etwas weiter aber das Gerät macht immer noch einen Disconnect. IST es vllt zu nah oder zu weit weg? mal frisch resetten?

                  Also wenn ich es richtig verstehe, dann sagen die Daten das 500 Byte kommen, es sind aber nur 150 und dann disconnect ...

                  P 1 Reply Last reply Reply Quote 0
                  • P
                    pql @apollon77 last edited by

                    @apollon77 frisch resettet (mehrfach) und näher dran leider ohne Erfolg. Gleiche Thematik.

                    Aber ok, dann wird das wohl am Eve Energy liegen. Direktes Pairing mit iOS funktioniert tadelos.

                    apollon77 1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 @pql last edited by

                      @pql ich hab auch einen eve Energy undeniable mir tut alles - aber von nem Mac aus.

                      Also du könntest jetzt nochmal das hci debugging parallel laufen lassen. Siehe troubleshooting in der readme. Vllt sieht man da noch was.

                      F 1 Reply Last reply Reply Quote 0
                      • F
                        Fortune95 @apollon77 last edited by

                        @apollon77
                        So bin gerade mal wieder mit Eve am testen aber mit gleichem Ergebnis....😞
                        Über BLE zickt er immer noch.

                        2022-02-16 19:05:03.537 - debug: homekit-controller.0 (115079) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-16 19:05:03.642 - debug: homekit-controller.0 (115079) Objects client ready ... initialize now
2022-02-16 19:05:03.647 - debug: homekit-controller.0 (115079) Objects create System PubSub Client
2022-02-16 19:05:03.650 - debug: homekit-controller.0 (115079) Objects create User PubSub Client
2022-02-16 19:05:03.753 - debug: homekit-controller.0 (115079) Objects client initialize lua scripts
2022-02-16 19:05:03.779 - debug: homekit-controller.0 (115079) Objects connected to redis: 127.0.0.1:9001
2022-02-16 19:05:03.816 - debug: homekit-controller.0 (115079) Redis States: Use Redis connection: 127.0.0.1:6379
2022-02-16 19:05:03.828 - debug: homekit-controller.0 (115079) States create System PubSub Client
2022-02-16 19:05:03.830 - debug: homekit-controller.0 (115079) States create User PubSub Client
2022-02-16 19:05:03.846 - debug: homekit-controller.0 (115079) States connected to redis: 127.0.0.1:6379
2022-02-16 19:05:03.913 - debug: homekit-controller.0 (115079) Plugin sentry Initialize Plugin (enabled=true)
2022-02-16 19:05:04.430 - info: homekit-controller.0 (115079) starting. Version 0.4.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.10
2022-02-16 19:05:04.709 - debug: homekit-controller.0 (115079) state homekit-controller.0.info.connection changed: false (ack = true)
2022-02-16 19:05:04.710 - debug: homekit-controller.0 (115079) Init 2 known devices without discovery ...
2022-02-16 19:05:04.711 - debug: homekit-controller.0 (115079) Init IP-10:92:E9:E7:AE:8F as known device
2022-02-16 19:05:04.713 - info: homekit-controller.0 (115079) IP-10:92:E9:E7:AE:8F (Eve Extend C054) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:05:04.714 - debug: homekit-controller.0 (115079) Service: {"name":"Eve Extend C054","address":"192.168.95.50","port":8080,"c#":12,"ff":1,"id":"10:92:E9:E7:AE:8F","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":1,"ci":2,"availableToPair":true}
2022-02-16 19:05:04.765 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.connectionType changed: IP (ack = true)
2022-02-16 19:05:04.778 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.id changed: 10:92:E9:E7:AE:8F (ack = true)
2022-02-16 19:05:04.792 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.address changed: 192.168.95.50 (ack = true)
2022-02-16 19:05:04.804 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.connected changed: false (ack = true)
2022-02-16 19:05:04.827 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.admin.isPaired changed: false (ack = true)
2022-02-16 19:05:04.841 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.lastDiscovered changed: 1645034704716 (ack = true)
2022-02-16 19:05:04.860 - debug: homekit-controller.0 (115079) Init BLE-EA:80:43:5F:2E:FE as known device
2022-02-16 19:05:04.861 - info: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:05:04.862 - debug: homekit-controller.0 (115079) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":true}
2022-02-16 19:05:04.900 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connectionType changed: BLE (ack = true)
2022-02-16 19:05:04.913 - debug: homekit-controller.0 (115079) Discovered IP device up: 10:92:E9:E7:AE:8F/Eve Extend C054
2022-02-16 19:05:04.914 - debug: homekit-controller.0 (115079) IP-10:92:E9:E7:AE:8F Discovered IP device: {"name":"Eve Extend C054","address":"192.168.95.50","port":8080,"c#":14,"ff":1,"id":"10:92:E9:E7:AE:8F","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:05:04.915 - info: homekit-controller.0 (115079) IP-10:92:E9:E7:AE:8F (Eve Extend C054) found without known pairing data and already paired: ignoring
2022-02-16 19:05:04.930 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.id changed: ea:80:43:5f:2e:fe (ack = true)
2022-02-16 19:05:04.943 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connected changed: false (ack = true)
2022-02-16 19:05:04.966 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.admin.isPaired changed: false (ack = true)
2022-02-16 19:05:04.979 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.lastDiscovered changed: 1645034704863 (ack = true)
2022-02-16 19:05:05.002 - debug: homekit-controller.0 (115079) Discovered IP device up: 47:FB:8F:AA:80:82/Eve Extend 726E
2022-02-16 19:05:05.003 - debug: homekit-controller.0 (115079) IP-47:FB:8F:AA:80:82 Discovered IP device: {"name":"Eve Extend 726E","address":"169.254.182.94","port":8080,"c#":5,"ff":1,"id":"47:FB:8F:AA:80:82","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:05:05.004 - info: homekit-controller.0 (115079) IP-47:FB:8F:AA:80:82 (Eve Extend 726E) found without known pairing data and already paired: ignoring
2022-02-16 19:05:05.636 - debug: homekit-controller.0 (115079) Discovered BLE device up: f6:36:ed:19:09:14/Eve Thermo 8FE8
2022-02-16 19:05:05.636 - debug: homekit-controller.0 (115079) BLE-F6:36:ED:19:09:14 Discovered BLE device: {"name":"Eve Thermo 8FE8","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f6:36:ed:19:09:14","ACID":9,"GSN":8861,"CN":5,"CV":2,"c#":5,"id":"f6:36:ed:19:09:14","ci":9,"availableToPair":false}
2022-02-16 19:05:05.637 - info: homekit-controller.0 (115079) BLE-F6:36:ED:19:09:14 (Eve Thermo 8FE8) found without known pairing data and already paired: ignoring
2022-02-16 19:05:05.951 - debug: homekit-controller.0 (115079) Discovered IP device up: 77:a2:42:96:a1:50/ioBroker B13E
2022-02-16 19:05:05.951 - debug: homekit-controller.0 (115079) IP-77:A2:42:96:A1:50 Discovered IP device: {"name":"ioBroker B13E","address":"192.168.95.212","port":44763,"c#":21,"ff":0,"id":"77:a2:42:96:a1:50","md":"not configured","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:05:05.952 - info: homekit-controller.0 (115079) IP-77:A2:42:96:A1:50 (ioBroker B13E) found without known pairing data and already paired: ignoring
2022-02-16 19:05:07.173 - debug: homekit-controller.0 (115079) Discovered BLE device up: ea:80:43:5f:2e:fe/Eve
2022-02-16 19:05:07.174 - debug: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE Discovered BLE device: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":true}
2022-02-16 19:05:07.174 - info: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE (Eve) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:05:07.175 - debug: homekit-controller.0 (115079) Service: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":true}
2022-02-16 19:05:07.218 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connectionType changed: BLE (ack = true)
2022-02-16 19:05:07.237 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.id changed: ea:80:43:5f:2e:fe (ack = true)
2022-02-16 19:05:07.268 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connected changed: false (ack = true)
2022-02-16 19:05:07.334 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.admin.isPaired changed: false (ack = true)
2022-02-16 19:05:07.354 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.lastDiscovered changed: 1645034707176 (ack = true)
2022-02-16 19:05:07.736 - debug: homekit-controller.0 (115079) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":51,"ack":false,"time":1645034707733},"_id":61965836})
2022-02-16 19:05:07.738 - debug: homekit-controller.0 (115079) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-EA:80:43:5F:2E:FE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-10:92:E9:E7:AE:8F","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend C054","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-47:FB:8F:AA:80:82","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend 726E","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-F6:36:ED:19:09:14","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Thermo 8FE8","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"IP-77:A2:42:96:A1:50","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"ioBroker B13E","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2022-02-16 19:05:12.329 - debug: homekit-controller.0 (115079) Message identify received: {"command":"identify","message":{"deviceId":"BLE-EA:80:43:5F:2E:FE"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-EA:80:43:5F:2E:FE"},"id":52,"ack":false,"time":1645034712328},"_id":61965837})
2022-02-16 19:05:12.330 - debug: homekit-controller.0 (115079) Device BLE-EA:80:43:5F:2E:FE: Identify triggered
2022-02-16 19:05:17.002 - debug: homekit-controller.0 (115079) Response to Command identify: {"success":true,"error":false}
2022-02-16 19:05:18.514 - debug: homekit-controller.0 (115079) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":53,"ack":false,"time":1645034718512},"_id":61965838})
2022-02-16 19:05:18.515 - debug: homekit-controller.0 (115079) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-EA:80:43:5F:2E:FE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-10:92:E9:E7:AE:8F","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend C054","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-47:FB:8F:AA:80:82","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend 726E","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-F6:36:ED:19:09:14","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Thermo 8FE8","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"IP-77:A2:42:96:A1:50","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"ioBroker B13E","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2022-02-16 19:05:34.097 - debug: homekit-controller.0 (115079) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-EA:80:43:5F:2E:FE","pin":"843-54-008"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-EA:80:43:5F:2E:FE","pin":"843-54-008"},"id":54,"ack":false,"time":1645034734094},"_id":61965839})
2022-02-16 19:05:38.076 - info: homekit-controller.0 (115079) Use PairMethod 0 to pair BLE-EA:80:43:5F:2E:FE
2022-02-16 19:05:38.078 - debug: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE Start Homekit Device Client initialization
2022-02-16 19:05:47.900 - debug: homekit-controller.0 (115079) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-EA:80:43:5F:2E:FE because of error undefined (undefined): undefined"}
2022-02-16 19:05:48.355 - debug: homekit-controller.0 (115079) Discovered BLE device changed: ea:80:43:5f:2e:fe/Eve Degree 5980
2022-02-16 19:05:48.357 - debug: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":false}
2022-02-16 19:05:48.358 - info: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE (Eve Degree 5980) found without known pairing data and already paired: ignoring
2022-02-16 19:06:32.001 - debug: homekit-controller.0 (115079) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":58,"ack":false,"time":1645034791999},"_id":61965843})
2022-02-16 19:06:32.002 - debug: homekit-controller.0 (115079) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-10:92:E9:E7:AE:8F","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend C054","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-EA:80:43:5F:2E:FE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-47:FB:8F:AA:80:82","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend 726E","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-F6:36:ED:19:09:14","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Thermo 8FE8","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"IP-77:A2:42:96:A1:50","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"ioBroker B13E","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2022-02-16 19:06:58.307 - info: homekit-controller.0 (115079) Got terminate signal TERMINATE_YOURSELF
2022-02-16 19:06:58.322 - info: homekit-controller.0 (115079) terminating
2022-02-16 19:06:58.325 - debug: homekit-controller.0 (115079) Plugin sentry destroyed
2022-02-16 19:06:58.326 - info: homekit-controller.0 (115079) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-02-16 19:07:04.162 - debug: homekit-controller.0 (115115) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-16 19:07:04.275 - debug: homekit-controller.0 (115115) Objects client ready ... initialize now
2022-02-16 19:07:04.282 - debug: homekit-controller.0 (115115) Objects create System PubSub Client
2022-02-16 19:07:04.286 - debug: homekit-controller.0 (115115) Objects create User PubSub Client
2022-02-16 19:07:04.375 - debug: homekit-controller.0 (115115) Objects client initialize lua scripts
2022-02-16 19:07:04.393 - debug: homekit-controller.0 (115115) Objects connected to redis: 127.0.0.1:9001
2022-02-16 19:07:04.471 - debug: homekit-controller.0 (115115) Redis States: Use Redis connection: 127.0.0.1:6379
2022-02-16 19:07:04.489 - debug: homekit-controller.0 (115115) States create System PubSub Client
2022-02-16 19:07:04.490 - debug: homekit-controller.0 (115115) States create User PubSub Client
2022-02-16 19:07:04.501 - debug: homekit-controller.0 (115115) States connected to redis: 127.0.0.1:6379
2022-02-16 19:07:04.551 - debug: homekit-controller.0 (115115) Plugin sentry Initialize Plugin (enabled=true)
2022-02-16 19:07:05.037 - info: homekit-controller.0 (115115) starting. Version 0.4.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.10
2022-02-16 19:07:05.299 - debug: homekit-controller.0 (115115) state homekit-controller.0.info.connection changed: false (ack = true)
2022-02-16 19:07:05.311 - debug: homekit-controller.0 (115115) Init 2 known devices without discovery ...
2022-02-16 19:07:05.312 - debug: homekit-controller.0 (115115) Init IP-10:92:E9:E7:AE:8F as known device
2022-02-16 19:07:05.314 - info: homekit-controller.0 (115115) IP-10:92:E9:E7:AE:8F (Eve Extend C054) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:07:05.315 - debug: homekit-controller.0 (115115) Service: {"name":"Eve Extend C054","address":"192.168.95.50","port":8080,"c#":12,"ff":1,"id":"10:92:E9:E7:AE:8F","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":1,"ci":2,"availableToPair":true}
2022-02-16 19:07:05.367 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.connectionType changed: IP (ack = true)
2022-02-16 19:07:05.384 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.id changed: 10:92:E9:E7:AE:8F (ack = true)
2022-02-16 19:07:05.405 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.address changed: 192.168.95.50 (ack = true)
2022-02-16 19:07:05.417 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.connected changed: false (ack = true)
2022-02-16 19:07:05.441 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.admin.isPaired changed: false (ack = true)
2022-02-16 19:07:05.456 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.lastDiscovered changed: 1645034825317 (ack = true)
2022-02-16 19:07:05.485 - debug: homekit-controller.0 (115115) Init BLE-EA:80:43:5F:2E:FE as known device
2022-02-16 19:07:05.486 - info: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE (Eve) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:07:05.487 - debug: homekit-controller.0 (115115) Service: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":true}
2022-02-16 19:07:05.527 - debug: homekit-controller.0 (115115) Discovered IP device up: 10:92:E9:E7:AE:8F/Eve Extend C054
2022-02-16 19:07:05.528 - debug: homekit-controller.0 (115115) IP-10:92:E9:E7:AE:8F Discovered IP device: {"name":"Eve Extend C054","address":"192.168.95.50","port":8080,"c#":14,"ff":1,"id":"10:92:E9:E7:AE:8F","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:07:05.529 - info: homekit-controller.0 (115115) IP-10:92:E9:E7:AE:8F (Eve Extend C054) found without known pairing data and already paired: ignoring
2022-02-16 19:07:05.547 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connectionType changed: BLE (ack = true)
2022-02-16 19:07:05.553 - debug: homekit-controller.0 (115115) Discovered IP device up: 47:FB:8F:AA:80:82/Eve Extend 726E
2022-02-16 19:07:05.554 - debug: homekit-controller.0 (115115) IP-47:FB:8F:AA:80:82 Discovered IP device: {"name":"Eve Extend 726E","address":"169.254.182.94","port":8080,"c#":5,"ff":1,"id":"47:FB:8F:AA:80:82","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:07:05.555 - info: homekit-controller.0 (115115) IP-47:FB:8F:AA:80:82 (Eve Extend 726E) found without known pairing data and already paired: ignoring
2022-02-16 19:07:05.571 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.id changed: ea:80:43:5f:2e:fe (ack = true)
2022-02-16 19:07:05.585 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connected changed: false (ack = true)
2022-02-16 19:07:05.606 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.admin.isPaired changed: false (ack = true)
2022-02-16 19:07:05.618 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.lastDiscovered changed: 1645034825487 (ack = true)
2022-02-16 19:07:05.750 - debug: homekit-controller.0 (115115) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":59,"ack":false,"time":1645034825748},"_id":61965844})
2022-02-16 19:07:05.752 - debug: homekit-controller.0 (115115) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-EA:80:43:5F:2E:FE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-10:92:E9:E7:AE:8F","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend C054","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-47:FB:8F:AA:80:82","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend 726E","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2022-02-16 19:07:06.006 - debug: homekit-controller.0 (115115) Discovered IP device up: 77:a2:42:96:a1:50/ioBroker B13E
2022-02-16 19:07:06.007 - debug: homekit-controller.0 (115115) IP-77:A2:42:96:A1:50 Discovered IP device: {"name":"ioBroker B13E","address":"192.168.95.212","port":44763,"c#":21,"ff":0,"id":"77:a2:42:96:a1:50","md":"not configured","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:07:06.008 - info: homekit-controller.0 (115115) IP-77:A2:42:96:A1:50 (ioBroker B13E) found without known pairing data and already paired: ignoring
2022-02-16 19:07:07.862 - debug: homekit-controller.0 (115115) Discovered BLE device up: ea:80:43:5f:2e:fe/Eve Degree 5980
2022-02-16 19:07:07.863 - debug: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":false}
2022-02-16 19:07:07.864 - info: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE (Eve Degree 5980) found without known pairing data and already paired: ignoring
2022-02-16 19:07:12.512 - debug: homekit-controller.0 (115115) Message identify received: {"command":"identify","message":{"deviceId":"BLE-EA:80:43:5F:2E:FE"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-EA:80:43:5F:2E:FE"},"id":60,"ack":false,"time":1645034832511},"_id":61965845})
2022-02-16 19:07:12.514 - debug: homekit-controller.0 (115115) Device BLE-EA:80:43:5F:2E:FE: Identify triggered
2022-02-16 19:07:23.539 - debug: homekit-controller.0 (115115) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-EA:80:43:5F:2E:FE because of error undefined: Identify returned error status: 5"}
2022-02-16 19:07:27.848 - debug: homekit-controller.0 (115115) Discovered BLE device up: f6:36:ed:19:09:14/Eve Thermo 8FE8
2022-02-16 19:07:27.849 - debug: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 Discovered BLE device: {"name":"Eve Thermo 8FE8","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f6:36:ed:19:09:14","ACID":9,"GSN":8861,"CN":5,"CV":2,"c#":5,"id":"f6:36:ed:19:09:14","ci":9,"availableToPair":false}
2022-02-16 19:07:27.850 - info: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 (Eve Thermo 8FE8) found without known pairing data and already paired: ignoring
2022-02-16 19:07:27.861 - debug: homekit-controller.0 (115115) Discovered BLE device changed: f6:36:ed:19:09:14/Eve Thermo 8FE8
2022-02-16 19:07:27.862 - debug: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 Discovered BLE device: {"name":"Eve Thermo 8FE8","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f6:36:ed:19:09:14","ACID":9,"GSN":8862,"CN":5,"CV":2,"c#":5,"id":"f6:36:ed:19:09:14","ci":9,"availableToPair":false}
2022-02-16 19:07:27.862 - info: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 (Eve Thermo 8FE8) found without known pairing data and already paired: ignoring
2022-02-16 19:08:47.689 - debug: homekit-controller.0 (115115) Discovered BLE device changed: f6:36:ed:19:09:14/Eve Thermo 8FE8
2022-02-16 19:08:47.691 - debug: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 Discovered BLE device: {"name":"Eve Thermo 8FE8","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f6:36:ed:19:09:14","ACID":9,"GSN":8863,"CN":5,"CV":2,"c#":5,"id":"f6:36:ed:19:09:14","ci":9,"availableToPair":false}
2022-02-16 19:08:47.692 - info: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 (Eve Thermo 8FE8) found without known pairing data and already paired: ignoring
2022-02-16 19:09:35.906 - debug: homekit-controller.0 (115115) Discovered BLE device up: 9b:3d:c6:d0:82:9b/Eve
2022-02-16 19:09:35.907 - debug: homekit-controller.0 (115115) BLE-9B:3D:C6:D0:82:9B Discovered BLE device: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"9b:3d:c6:d0:82:9b","ACID":9,"GSN":8239,"CN":5,"CV":2,"c#":5,"id":"9b:3d:c6:d0:82:9b","ci":9,"availableToPair":false}
2022-02-16 19:09:35.907 - info: homekit-controller.0 (115115) BLE-9B:3D:C6:D0:82:9B (Eve) found without known pairing data and already paired: ignoring
2022-02-16 19:09:51.356 - debug: homekit-controller.0 (115115) Discovered BLE device up: 91:90:ed:a6:89:85/Eve
2022-02-16 19:09:51.357 - debug: homekit-controller.0 (115115) BLE-91:90:ED:A6:89:85 Discovered BLE device: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"91:90:ed:a6:89:85","ACID":9,"GSN":6582,"CN":5,"CV":2,"c#":5,"id":"91:90:ed:a6:89:85","ci":9,"availableToPair":false}
2022-02-16 19:09:51.357 - info: homekit-controller.0 (115115) BLE-91:90:ED:A6:89:85 (Eve) found without known pairing data and already paired: ignoring
2022-02-16 19:10:59.889 - debug: homekit-controller.0 (115115) Discovered BLE device changed: ea:80:43:5f:2e:fe/Eve Degree 5980
2022-02-16 19:10:59.891 - debug: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":3,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":false}
2022-02-16 19:10:59.893 - info: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE (Eve Degree 5980) found without known pairing data and already paired: ignoring
                        apollon77 1 Reply Last reply Reply Quote 0
                        • apollon77
                          apollon77 @Fortune95 last edited by

                          @fortune95 sagte in Test Alpha Homekit-Controller 0.0.x:

                          2022-02-16 19:07:23.539 - debug: homekit-controller.0 (115115) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-EA:80:43:5F:2E:FE because of error undefined: Identify returned error status: 5"}

                          Also Fehler 5 sagt laut Specs

                          Server reached its maximum number of authentication attempts.

                          Resette mal ...

                          F 2 Replies Last reply Reply Quote 0
                          • F
                            Fortune95 @apollon77 last edited by

                            @apollon77
                            So kurz zum setup, habe jetzt eine VM mit externen USB BLE von Edimax. Debian Bullseye und js-controller 4.0.10.
                            Den Eve Degree kann ich im adapter sehen (habe ihn zuvor frisch resettet)kann ihn aber nicht identifizieren.
                            Erhalte dann diese Fehlermeldung:
                            Fehler.JPG

                            Danach habe ich den Adapter gestoppt.
                            Und über die Shell den Debug wie oben erwähnt gestartet.
                            Hier das Log:

                            iobroker@iobroker:~DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debugug
2022-02-17 18:44:50.094  - debug: homekit-controller.0 (2380) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-17 18:44:50.129  - debug: homekit-controller.0 (2380) Objects client ready ... initialize now
2022-02-17 18:44:50.130  - debug: homekit-controller.0 (2380) Objects create System PubSub Client
2022-02-17 18:44:50.131  - debug: homekit-controller.0 (2380) Objects create User PubSub Client
2022-02-17 18:44:50.147  - debug: homekit-controller.0 (2380) Objects client initialize lua scripts
2022-02-17 18:44:50.149  - debug: homekit-controller.0 (2380) Objects connected to redis: 127.0.0.1:9001
2022-02-17 18:44:50.162  - debug: homekit-controller.0 (2380) Redis States: Use Redis connection: 127.0.0.1:6379
2022-02-17 18:44:50.164  - debug: homekit-controller.0 (2380) States create System PubSub Client
2022-02-17 18:44:50.165  - debug: homekit-controller.0 (2380) States create User PubSub Client
2022-02-17 18:44:50.168  - debug: homekit-controller.0 (2380) States connected to redis: 127.0.0.1:6379
2022-02-17 18:44:50.182  - debug: homekit-controller.0 (2380) Plugin sentry Initialize Plugin (enabled=true)
2022-02-17 18:44:50.244  - error: homekit-controller.0 (2380) adapter disabled
2022-02-17 18:44:50.299  - info: homekit-controller.0 (2380) starting. Version 0.4.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.10
2022-02-17 18:44:50.370  - debug: homekit-controller.0 (2380) state homekit-controller.0.info.connection changed: false (ack = true)
2022-02-17 18:44:50.373  - debug: homekit-controller.0 (2380) Init 1 known devices without discovery ...
2022-02-17 18:44:50.373  - debug: homekit-controller.0 (2380) Init BLE-BA:0A:DB:84:F2:CE as known device
2022-02-17 18:44:50.374  - info: homekit-controller.0 (2380) BLE-BA:0A:DB:84:F2:CE (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects
2022-02-17 18:44:50.374  - debug: homekit-controller.0 (2380) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ba:0a:db:84:f2:ce","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ba:0a:db:84:f2:ce","ci":10,"availableToPair":true}
2022-02-17 18:44:50.384  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connectionType changed: BLE (ack = true)
2022-02-17 18:44:50.388  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.id changed: ba:0a:db:84:f2:ce (ack = true)
2022-02-17 18:44:50.391  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connected changed: false (ack = true)
2022-02-17 18:44:50.395  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.admin.isPaired changed: false (ack = true)
2022-02-17 18:44:50.399  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.lastDiscovered changed: 1645119890375 (ack = true)
2022-02-17 18:44:51.467  - debug: homekit-controller.0 (2380) Discovered BLE device up: ba:0a:db:84:f2:ce/Eve Degree 5980
2022-02-17 18:44:51.467  - debug: homekit-controller.0 (2380) BLE-BA:0A:DB:84:F2:CE Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ba:0a:db:84:f2:ce","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ba:0a:db:84:f2:ce","ci":10,"availableToPair":true}
2022-02-17 18:44:51.467  - info: homekit-controller.0 (2380) BLE-BA:0A:DB:84:F2:CE (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects
2022-02-17 18:44:51.468  - debug: homekit-controller.0 (2380) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ba:0a:db:84:f2:ce","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ba:0a:db:84:f2:ce","ci":10,"availableToPair":true}
2022-02-17 18:44:51.476  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connectionType changed: BLE (ack = true)
2022-02-17 18:44:51.479  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.id changed: ba:0a:db:84:f2:ce (ack = true)
2022-02-17 18:44:51.482  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connected changed: false (ack = true)
2022-02-17 18:44:51.487  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.admin.isPaired changed: false (ack = true)
2022-02-17 18:44:51.490  - debug: homekit-controller.0 (2380) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.lastDiscovered changed: 1645119891468 (ack = true)
2022-02-17 18:45:09.680  - debug: homekit-controller.0 (2380) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":25,"ack":false,"time":1645119909679},"_id":16181572})
2022-02-17 18:45:09.680  - debug: homekit-controller.0 (2380) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-BA:0A:DB:84:F2:CE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2022-02-17 18:45:11.831  - debug: homekit-controller.0 (2380) Message identify received: {"command":"identify","message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE"},"id":26,"ack":false,"time":1645119911830},"_id":16181573})
2022-02-17 18:45:11.831  - debug: homekit-controller.0 (2380) Device BLE-BA:0A:DB:84:F2:CE: Identify triggered
  hap-controller:gatt-connection connect peripheral +0ms
  hap-controller:gatt-connection disconnect peripheral +3s
  hap-controller:gatt-connection Peripheral disconnected +47ms
2022-02-17 18:45:14.949  - debug: homekit-controller.0 (2380) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-BA:0A:DB:84:F2:CE because of error undefined: undefined"}

                            Kannst Du damit was anfangen?

                            1 Reply Last reply Reply Quote 0
                            • F
                              Fortune95 @apollon77 last edited by

                              @apollon77
                              So habe noch eine Ergänzung nach Google Recherche... im Bluetooth Service vorgenommen.
                              Zumindest lieferte der Bluetooth Service danach keine Fehler mehr.
                              Und auch das identifizieren ging dann wieder.

                              Habe diese Zeile so abgeändert

                              ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap

                              Nur das pairen will einfach nicht.
                              Hier das Log:

                              iobroker@iobroker:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-02-17 18:58:26 CET; 13s ago
       Docs: man:bluetoothd(8)
   Main PID: 2443 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 7090)
     Memory: 740.0K
        CPU: 9ms
     CGroup: /system.slice/bluetooth.service
             └─2443 /usr/libexec/bluetooth/bluetoothd --noplugin=sap

Feb 17 18:58:26 iobroker systemd[1]: Starting Bluetooth service...
Feb 17 18:58:26 iobroker bluetoothd[2443]: Bluetooth daemon 5.55
Feb 17 18:58:26 iobroker systemd[1]: Started Bluetooth service.
Feb 17 18:58:26 iobroker bluetoothd[2443]: Starting SDP server
Feb 17 18:58:26 iobroker bluetoothd[2443]: Excluding (cli) sap
Feb 17 18:58:26 iobroker bluetoothd[2443]: Bluetooth management interface 1.18 initialized
iobroker@iobroker:~$ DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debug
2022-02-17 19:00:01.818  - debug: homekit-controller.0 (2501) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-17 19:00:01.856  - debug: homekit-controller.0 (2501) Objects client ready ... initialize now
2022-02-17 19:00:01.857  - debug: homekit-controller.0 (2501) Objects create System PubSub Client
2022-02-17 19:00:01.858  - debug: homekit-controller.0 (2501) Objects create User PubSub Client
2022-02-17 19:00:01.879  - debug: homekit-controller.0 (2501) Objects client initialize lua scripts
2022-02-17 19:00:01.881  - debug: homekit-controller.0 (2501) Objects connected to redis: 127.0.0.1:9001
2022-02-17 19:00:01.896  - debug: homekit-controller.0 (2501) Redis States: Use Redis connection: 127.0.0.1:6379
2022-02-17 19:00:01.898  - debug: homekit-controller.0 (2501) States create System PubSub Client
2022-02-17 19:00:01.899  - debug: homekit-controller.0 (2501) States create User PubSub Client
2022-02-17 19:00:01.901  - debug: homekit-controller.0 (2501) States connected to redis: 127.0.0.1:6379
2022-02-17 19:00:01.917  - debug: homekit-controller.0 (2501) Plugin sentry Initialize Plugin (enabled=true)
2022-02-17 19:00:01.992  - error: homekit-controller.0 (2501) adapter disabled
2022-02-17 19:00:02.039  - info: homekit-controller.0 (2501) starting. Version 0.4.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.10
2022-02-17 19:00:02.112  - debug: homekit-controller.0 (2501) state homekit-controller.0.info.connection changed: false (ack = true)
2022-02-17 19:00:02.114  - debug: homekit-controller.0 (2501) Init 1 known devices without discovery ...
2022-02-17 19:00:02.115  - debug: homekit-controller.0 (2501) Init BLE-BA:0A:DB:84:F2:CE as known device
2022-02-17 19:00:02.116  - info: homekit-controller.0 (2501) BLE-BA:0A:DB:84:F2:CE (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects
2022-02-17 19:00:02.116  - debug: homekit-controller.0 (2501) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ba:0a:db:84:f2:ce","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ba:0a:db:84:f2:ce","ci":10,"availableToPair":true}
2022-02-17 19:00:02.128  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connectionType changed: BLE (ack = true)
2022-02-17 19:00:02.134  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.id changed: ba:0a:db:84:f2:ce (ack = true)
2022-02-17 19:00:02.138  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connected changed: false (ack = true)
2022-02-17 19:00:02.145  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.admin.isPaired changed: false (ack = true)
2022-02-17 19:00:02.149  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.lastDiscovered changed: 1645120802117 (ack = true)
2022-02-17 19:00:02.689  - debug: homekit-controller.0 (2501) Discovered BLE device up: ba:0a:db:84:f2:ce/Eve Degree 5980
2022-02-17 19:00:02.689  - debug: homekit-controller.0 (2501) BLE-BA:0A:DB:84:F2:CE Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ba:0a:db:84:f2:ce","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ba:0a:db:84:f2:ce","ci":10,"availableToPair":true}
2022-02-17 19:00:02.690  - info: homekit-controller.0 (2501) BLE-BA:0A:DB:84:F2:CE (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects
2022-02-17 19:00:02.690  - debug: homekit-controller.0 (2501) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ba:0a:db:84:f2:ce","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ba:0a:db:84:f2:ce","ci":10,"availableToPair":true}
2022-02-17 19:00:02.698  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connectionType changed: BLE (ack = true)
2022-02-17 19:00:02.701  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.id changed: ba:0a:db:84:f2:ce (ack = true)
2022-02-17 19:00:02.705  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connected changed: false (ack = true)
2022-02-17 19:00:02.710  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.admin.isPaired changed: false (ack = true)
2022-02-17 19:00:02.714  - debug: homekit-controller.0 (2501) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.lastDiscovered changed: 1645120802690 (ack = true)
2022-02-17 19:00:07.994  - debug: homekit-controller.0 (2501) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":33,"ack":false,"time":1645120807993},"_id":16181580})
2022-02-17 19:00:07.994  - debug: homekit-controller.0 (2501) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-BA:0A:DB:84:F2:CE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2022-02-17 19:00:09.643  - debug: homekit-controller.0 (2501) Message identify received: {"command":"identify","message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE"},"id":34,"ack":false,"time":1645120809642},"_id":16181581})
2022-02-17 19:00:09.643  - debug: homekit-controller.0 (2501) Device BLE-BA:0A:DB:84:F2:CE: Identify triggered
  hap-controller:gatt-connection connect peripheral +0ms
  hap-controller:tlv Add 1 bytes for tag 1: 01 +0ms
  hap-controller:gatt-connection ff4feaecc339/ff:4f:ea:ec:c3:39 Write for characteristic 000000140000100080000026bb765291 00020003000300010101 +4s
  hap-controller:gatt-connection ff4feaecc339/ff:4f:ea:ec:c3:39 Received data for characteristic 000000140000100080000026bb765291 020000 +224ms
  hap-controller:gatt-connection disconnect peripheral +1ms
  hap-controller:gatt-connection Peripheral disconnected +45ms
2022-02-17 19:00:13.890  - debug: homekit-controller.0 (2501) Response to Command identify: {"success":true,"error":false}
2022-02-17 19:00:15.413  - debug: homekit-controller.0 (2501) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":35,"ack":false,"time":1645120815413},"_id":16181582})
2022-02-17 19:00:15.414  - debug: homekit-controller.0 (2501) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-BA:0A:DB:84:F2:CE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2022-02-17 19:00:25.994  - debug: homekit-controller.0 (2501) Message identify received: {"command":"identify","message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE"},"id":36,"ack":false,"time":1645120825994},"_id":16181583})
2022-02-17 19:00:25.995  - debug: homekit-controller.0 (2501) Device BLE-BA:0A:DB:84:F2:CE: Identify triggered
  hap-controller:gatt-connection connect peripheral +12s
  hap-controller:gatt-connection disconnect peripheral +5s
2022-02-17 19:01:00.829  - debug: homekit-controller.0 (2501) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-BA:0A:DB:84:F2:CE because of error undefined: Unknown Connection Identifier (0x2)"}
^Ciobroker@iobroker:~$ DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debug
2022-02-17 19:01:16.958  - debug: homekit-controller.0 (2526) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-17 19:01:16.994  - debug: homekit-controller.0 (2526) Objects client ready ... initialize now
2022-02-17 19:01:16.995  - debug: homekit-controller.0 (2526) Objects create System PubSub Client
2022-02-17 19:01:16.996  - debug: homekit-controller.0 (2526) Objects create User PubSub Client
2022-02-17 19:01:17.016  - debug: homekit-controller.0 (2526) Objects client initialize lua scripts
2022-02-17 19:01:17.018  - debug: homekit-controller.0 (2526) Objects connected to redis: 127.0.0.1:9001
2022-02-17 19:01:17.031  - debug: homekit-controller.0 (2526) Redis States: Use Redis connection: 127.0.0.1:6379
2022-02-17 19:01:17.033  - debug: homekit-controller.0 (2526) States create System PubSub Client
2022-02-17 19:01:17.034  - debug: homekit-controller.0 (2526) States create User PubSub Client
2022-02-17 19:01:17.036  - debug: homekit-controller.0 (2526) States connected to redis: 127.0.0.1:6379
2022-02-17 19:01:17.049  - debug: homekit-controller.0 (2526) Plugin sentry Initialize Plugin (enabled=true)
2022-02-17 19:01:17.110  - error: homekit-controller.0 (2526) adapter disabled
2022-02-17 19:01:17.159  - info: homekit-controller.0 (2526) starting. Version 0.4.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.10
2022-02-17 19:01:17.232  - debug: homekit-controller.0 (2526) state homekit-controller.0.info.connection changed: false (ack = true)
2022-02-17 19:01:17.235  - debug: homekit-controller.0 (2526) Init 1 known devices without discovery ...
2022-02-17 19:01:17.236  - debug: homekit-controller.0 (2526) Init BLE-BA:0A:DB:84:F2:CE as known device
2022-02-17 19:01:17.237  - info: homekit-controller.0 (2526) BLE-BA:0A:DB:84:F2:CE (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects
2022-02-17 19:01:17.238  - debug: homekit-controller.0 (2526) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ba:0a:db:84:f2:ce","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ba:0a:db:84:f2:ce","ci":10,"availableToPair":true}
2022-02-17 19:01:17.248  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connectionType changed: BLE (ack = true)
2022-02-17 19:01:17.252  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.id changed: ba:0a:db:84:f2:ce (ack = true)
2022-02-17 19:01:17.255  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connected changed: false (ack = true)
2022-02-17 19:01:17.259  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.admin.isPaired changed: false (ack = true)
2022-02-17 19:01:17.262  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.lastDiscovered changed: 1645120877239 (ack = true)
2022-02-17 19:01:20.744  - debug: homekit-controller.0 (2526) Discovered BLE device up: ba:0a:db:84:f2:ce/Eve Degree 5980
2022-02-17 19:01:20.745  - debug: homekit-controller.0 (2526) BLE-BA:0A:DB:84:F2:CE Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ba:0a:db:84:f2:ce","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ba:0a:db:84:f2:ce","ci":10,"availableToPair":true}
2022-02-17 19:01:20.745  - info: homekit-controller.0 (2526) BLE-BA:0A:DB:84:F2:CE (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects
2022-02-17 19:01:20.745  - debug: homekit-controller.0 (2526) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ba:0a:db:84:f2:ce","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ba:0a:db:84:f2:ce","ci":10,"availableToPair":true}
2022-02-17 19:01:20.752  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connectionType changed: BLE (ack = true)
2022-02-17 19:01:20.755  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.id changed: ba:0a:db:84:f2:ce (ack = true)
2022-02-17 19:01:20.759  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.connected changed: false (ack = true)
2022-02-17 19:01:20.766  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.admin.isPaired changed: false (ack = true)
2022-02-17 19:01:20.769  - debug: homekit-controller.0 (2526) state homekit-controller.0.BLE-BA:0A:DB:84:F2:CE.info.lastDiscovered changed: 1645120880745 (ack = true)
2022-02-17 19:01:25.279  - debug: homekit-controller.0 (2526) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":37,"ack":false,"time":1645120885278},"_id":16181584})
2022-02-17 19:01:25.280  - debug: homekit-controller.0 (2526) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-BA:0A:DB:84:F2:CE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2022-02-17 19:01:26.989  - debug: homekit-controller.0 (2526) Message identify received: {"command":"identify","message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE"},"id":38,"ack":false,"time":1645120886988},"_id":16181585})
2022-02-17 19:01:26.990  - debug: homekit-controller.0 (2526) Device BLE-BA:0A:DB:84:F2:CE: Identify triggered
  hap-controller:gatt-connection connect peripheral +0ms
  hap-controller:tlv Add 1 bytes for tag 1: 01 +0ms
  hap-controller:gatt-connection ff4feaecc339/ff:4f:ea:ec:c3:39 Write for characteristic 000000140000100080000026bb765291 00020003000300010101 +3s
  hap-controller:gatt-connection ff4feaecc339/ff:4f:ea:ec:c3:39 Received data for characteristic 000000140000100080000026bb765291 020000 +225ms
  hap-controller:gatt-connection disconnect peripheral +0ms
  hap-controller:gatt-connection Peripheral disconnected +45ms
2022-02-17 19:01:30.649  - debug: homekit-controller.0 (2526) Response to Command identify: {"success":true,"error":false}
2022-02-17 19:01:32.166  - debug: homekit-controller.0 (2526) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":39,"ack":false,"time":1645120892163},"_id":16181586})
2022-02-17 19:01:32.167  - debug: homekit-controller.0 (2526) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-BA:0A:DB:84:F2:CE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2022-02-17 19:01:51.108  - debug: homekit-controller.0 (2526) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE","pin":"843-54-008"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-BA:0A:DB:84:F2:CE","pin":"843-54-008"},"id":40,"ack":false,"time":1645120911107},"_id":16181587})
  hap-controller:gatt-connection connect peripheral +20s
  hap-controller:gatt-connection disconnect peripheral +7s
2022-02-17 19:02:27.867  - info: homekit-controller.0 (2526) Cannot retrieve BLE PairMethod for device BLE-BA:0A:DB:84:F2:CE because of error undefined: Unknown Connection Identifier (0x2), try default
2022-02-17 19:02:27.868  - info: homekit-controller.0 (2526) Use PairMethod 0 to pair BLE-BA:0A:DB:84:F2:CE
2022-02-17 19:02:27.868  - debug: homekit-controller.0 (2526) BLE-BA:0A:DB:84:F2:CE Start Homekit Device Client initialization
  hap-controller:gatt-connection disconnect peripheral to reconnect +30s
2022-02-17 19:02:57.870  - debug: homekit-controller.0 (2526) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-BA:0A:DB:84:F2:CE because of error undefined (undefined): undefined"}
                              1 Reply Last reply Reply Quote 0
                              • apollon77
                                apollon77 last edited by

                                Interessant, den Fehler hatte ich in einem Issue schonmal gesehen, aber tja dann wirds ganz interessant. Bitte schaumal da durch https://github.com/Apollon77/ioBroker.homekit-controller/#for-ble-devices und versuche es blt mach dieses Log parallel

                                F 1 Reply Last reply Reply Quote 0
                                • F
                                  Fortune95 @apollon77 last edited by

                                  @apollon77
                                  Habe den Adapter wie im Issue beschrieben von Gihub installiert und das Log erstellt:

                                  iobroker@iobroker:~$ DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debug --logs
2022-02-18 16:07:47.793  - debug: homekit-controller.0 (6682) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-18 16:07:47.815  - debug: homekit-controller.0 (6682) Objects client ready ... initialize now
2022-02-18 16:07:47.816  - debug: homekit-controller.0 (6682) Objects create System PubSub Client
2022-02-18 16:07:47.817  - debug: homekit-controller.0 (6682) Objects create User PubSub Client
2022-02-18 16:07:47.838  - debug: homekit-controller.0 (6682) Objects client initialize lua scripts
2022-02-18 16:07:47.840  - debug: homekit-controller.0 (6682) Objects connected to redis: 127.0.0.1:9001
2022-02-18 16:07:47.854  - debug: homekit-controller.0 (6682) Redis States: Use Redis connection: 127.0.0.1:6379
2022-02-18 16:07:47.856  - debug: homekit-controller.0 (6682) States create System PubSub Client
2022-02-18 16:07:47.857  - debug: homekit-controller.0 (6682) States create User PubSub Client
2022-02-18 16:07:47.860  - debug: homekit-controller.0 (6682) States connected to redis: 127.0.0.1:6379
2022-02-18 16:07:47.872  - debug: homekit-controller.0 (6682) Plugin sentry Initialize Plugin (enabled=true)
2022-02-18 16:07:47.933  - error: homekit-controller.0 (6682) adapter disabled
2022-02-18 16:07:47.978  - info: homekit-controller.0 (6682) starting. Version 0.4.3 (non-npm: Apollon77/ioBroker.homekit-controller#c614463e84bfe9c4e7d5d6038d0babdbcb55b852) in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.12
2022-02-18 16:07:48.050  - debug: homekit-controller.0 (6682) state homekit-controller.0.info.connection changed: false (ack = true)
2022-02-18 16:07:53.221  - debug: homekit-controller.0 (6682) Discovered BLE device up: 25:3e:f0:cc:4c:64/Eve
2022-02-18 16:07:53.221  - debug: homekit-controller.0 (6682) BLE-25:3E:F0:CC:4C:64 Discovered BLE device: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"25:3e:f0:cc:4c:64","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"25:3e:f0:cc:4c:64","ci":10,"availableToPair":true}
2022-02-18 16:07:53.222  - info: homekit-controller.0 (6682) BLE-25:3E:F0:CC:4C:64 (Eve) found without pairing data but available for pairing: Create basic objects
2022-02-18 16:07:53.222  - debug: homekit-controller.0 (6682) Service: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"25:3e:f0:cc:4c:64","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"25:3e:f0:cc:4c:64","ci":10,"availableToPair":true}
2022-02-18 16:07:53.235  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.info.connectionType changed: BLE (ack = true)
2022-02-18 16:07:53.237  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.info.connectionType changed: BLE (ack = true)
2022-02-18 16:07:53.240  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.info.id changed: 25:3e:f0:cc:4c:64 (ack = true)
2022-02-18 16:07:53.243  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.info.connected changed: false (ack = true)
2022-02-18 16:07:53.248  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.admin.isPaired changed: false (ack = true)
2022-02-18 16:07:53.251  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.info.lastDiscovered changed: 1645196873223 (ack = true)
2022-02-18 16:07:53.255  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.admin.pairWithPin changed:  (ack = true)
2022-02-18 16:07:53.258  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.admin.identify changed: false (ack = true)
2022-02-18 16:08:10.833  - debug: homekit-controller.0 (6682) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":112,"ack":false,"time":1645196890832},"_id":85128405})
2022-02-18 16:08:10.833  - debug: homekit-controller.0 (6682) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-25:3E:F0:CC:4C:64","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2022-02-18 16:08:12.873  - debug: homekit-controller.0 (6682) Message identify received: {"command":"identify","message":{"deviceId":"BLE-25:3E:F0:CC:4C:64"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-25:3E:F0:CC:4C:64"},"id":113,"ack":false,"time":1645196892872},"_id":85128406})
2022-02-18 16:08:12.873  - debug: homekit-controller.0 (6682) Device BLE-25:3E:F0:CC:4C:64: Identify triggered
  hap-controller:gatt-connection connect peripheral +0ms
  hap-controller:tlv Add 1 bytes for tag 1: 01 +0ms
  hap-controller:gatt-connection e60614286935/e6:06:14:28:69:35 Write for characteristic 000000140000100080000026bb765291 00020003000300010101 +6s
  hap-controller:gatt-connection e60614286935/e6:06:14:28:69:35 Received data for characteristic 000000140000100080000026bb765291 020000 +180ms
  hap-controller:gatt-connection disconnect peripheral +0ms
  hap-controller:gatt-connection Peripheral disconnected +45ms
2022-02-18 16:08:18.600  - debug: homekit-controller.0 (6682) Response to Command identify: {"success":true,"error":false}
2022-02-18 16:08:20.110  - debug: homekit-controller.0 (6682) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":114,"ack":false,"time":1645196900109},"_id":85128407})
2022-02-18 16:08:20.110  - debug: homekit-controller.0 (6682) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-25:3E:F0:CC:4C:64","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2022-02-18 16:08:46.277  - debug: homekit-controller.0 (6682) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-25:3E:F0:CC:4C:64","pin":"843-54-008"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-25:3E:F0:CC:4C:64","pin":"843-54-008"},"id":115,"ack":false,"time":1645196926277},"_id":85128408})
  hap-controller:gatt-connection connect peripheral +28s
  hap-controller:gatt-connection e60614286935/e6:06:14:28:69:35 Write for characteristic 0000004f0000100080000026bb765291 0003000f00 +4s
  hap-controller:gatt-connection e60614286935/e6:06:14:28:69:35 Received data for characteristic 0000004f0000100080000026bb765291 0200000300010101 +225ms
  hap-controller:gatt-connection disconnect peripheral +0ms
  hap-controller:gatt-connection Peripheral disconnected +46ms
2022-02-18 16:08:50.462  - info: homekit-controller.0 (6682) Use PairMethod 0 to pair BLE-25:3E:F0:CC:4C:64
2022-02-18 16:08:50.463  - debug: homekit-controller.0 (6682) BLE-25:3E:F0:CC:4C:64 Start Homekit Device Client initialization
  hap-controller:gatt-connection connect peripheral +2ms
2022-02-18 16:08:55.788  - debug: homekit-controller.0 (6682) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-25:3E:F0:CC:4C:64 because of error undefined (undefined): Unknown Connection Identifier (0x2)"}
2022-02-18 16:11:45.843  - debug: homekit-controller.0 (6682) Discovered BLE device changed: 25:3e:f0:cc:4c:64/Eve Degree 5980
2022-02-18 16:11:45.843  - debug: homekit-controller.0 (6682) BLE-25:3E:F0:CC:4C:64 Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"25:3e:f0:cc:4c:64","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"25:3e:f0:cc:4c:64","ci":10,"availableToPair":true}
2022-02-18 16:11:45.843  - info: homekit-controller.0 (6682) BLE-25:3E:F0:CC:4C:64 (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects
2022-02-18 16:11:45.844  - debug: homekit-controller.0 (6682) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"25:3e:f0:cc:4c:64","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"25:3e:f0:cc:4c:64","ci":10,"availableToPair":true}
2022-02-18 16:11:45.852  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.info.connectionType changed: BLE (ack = true)
2022-02-18 16:11:45.854  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.info.id changed: 25:3e:f0:cc:4c:64 (ack = true)
2022-02-18 16:11:45.858  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.info.connected changed: false (ack = true)
2022-02-18 16:11:45.863  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.admin.isPaired changed: false (ack = true)
2022-02-18 16:11:45.866  - debug: homekit-controller.0 (6682) state homekit-controller.0.BLE-25:3E:F0:CC:4C:64.info.lastDiscovered changed: 1645197105844 (ack = true)
                                  apollon77 1 Reply Last reply Reply Quote 0
                                  • apollon77
                                    apollon77 @Fortune95 last edited by

                                    @fortune95 Hi,

                                    sorry für die späte Antwort ... Kannst Du es nochmal machen und das zweite log mit dem hcitool auch parallel holen? Das ist denke ich dann interessant in Kombi

                                    F 1 Reply Last reply Reply Quote 0
                                    • F
                                      Fortune95 @apollon77 last edited by

                                      @apollon77

                                      Hi, hab es jetzt mal über die Shell versucht, hier bekomme ich ein Authentication Fehler.
                                      Hast Du eine Idee wie ich den beheben kann.

                                      iobroker@iobroker:~$ bluetoothctl
Agent registered
[CHG] Controller 08:BE:AC:20:8E:F2 Pairable: yes
[bluetooth]# devices
Device 4D:C8:A4:58:F8:96 4D-C8-A4-58-F8-96
Device 09:CB:9E:AF:84:DF 09-CB-9E-AF-84-DF
Device FE:4F:B0:DD:AA:22 Eve Degree 5980
Device 71:B7:B8:6D:37:1D 71-B7-B8-6D-37-1D
Device 51:DA:80:04:EA:0C 51-DA-80-04-EA-0C
Device 50:2D:26:B8:7F:B1 50-2D-26-B8-7F-B1
[DEL] Device 50:2D:26:B8:7F:B1 50-2D-26-B8-7F-B1
[DEL] Device 71:B7:B8:6D:37:1D 71-B7-B8-6D-37-1D
[DEL] Device 09:CB:9E:AF:84:DF 09-CB-9E-AF-84-DF
[DEL] Device 51:DA:80:04:EA:0C 51-DA-80-04-EA-0C
[DEL] Device 4D:C8:A4:58:F8:96 4D-C8-A4-58-F8-96
[bluetooth]# pair FE:4F:B0:DD:AA:22
Attempting to pair with FE:4F:B0:DD:AA:22
[CHG] Device FE:4F:B0:DD:AA:22 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationFailed
[CHG] Device FE:4F:B0:DD:AA:22 Connected: no
                                      apollon77 1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @Fortune95 last edited by

                                        @fortune95 Denke diese bluetooth kommandos brauchen root ... also rum das mit sudo auf

                                        F 1 Reply Last reply Reply Quote 0
                                        • F
                                          Fortune95 @apollon77 last edited by

                                          @apollon77
                                          Mit sudo bekomme ich die gleiche Fehlermeldung😞

                                          apollon77 1 Reply Last reply Reply Quote 0
                                          • apollon77
                                            apollon77 @Fortune95 last edited by

                                            @fortune95 aber duuuuuuu. In der obigen Anleitung steht nichts von dem Kommando oder?‘

                                            Ich meine das du das parallel zum Adapter laufen lassen sollst: „ sudo hcidump -t -x >log.txt“

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            921
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            24
                                            255
                                            25373
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo