Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Radar 2.0 Error

    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

    UNSOLVED Radar 2.0 Error

    This topic has been deleted. Only users with topic management privileges can see it.
    • Dominik F.
      Dominik F. last edited by

      Hallo zusammen,

      ich bin gestern vom RPI4 auf neue Hardware umgezogen und beim Radar Adapter tauchen nun folgende Errors auf und er bleibt Rot:

      host.IoBroker	2020-03-05 10:02:03.389	error	Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:61:11) errno: 19, code: 'ENODEV', syscall: 'bind' }
host.IoBroker	2020-03-05 10:02:03.389	error	Caught by controller[0]: at process.nextTick (/opt/iobroker/node_modules/@abandonware/noble/lib/noble.js:60:24)
host.IoBroker	2020-03-05 10:02:03.389	error	Caught by controller[0]: at NobleBindings.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
host.IoBroker	2020-03-05 10:02:03.389	error	Caught by controller[0]: at Hci.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
host.IoBroker	2020-03-05 10:02:03.389	error	Caught by controller[0]: { Error: ENODEV, No such device
radar2.0	2020-03-05 10:02:03.367	info	(18552) Adapter disconnected and stopped with dostop(false) and callback(true)
radar2.0	2020-03-05 10:02:03.366	error	(18552) Error: ENODEV, No such device at Hci.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35) at NobleBindings.init (/opt/iobroker/node_modules/@abandonware/no
radar2.0	2020-03-05 10:02:03.366	error	(18552) uncaught exception: ENODEV, No such device
radar2.0	2020-03-05 10:02:03.360	info	(18552) radar2 set to scan every 20 seconds and printers every 720 minutes.
radar2.0	2020-03-05 10:02:03.360	info	(18552) arp-scan will use the following interfaces: [ 'ens18' ]
radar2.0	2020-03-05 10:02:03.360	info	(18552) Remove name end for host names: .fritz.box
radar2.0	2020-03-05 10:02:03.359	info	(18552) use known IP list: [ '1.1.1.1' ]
radar2.0	2020-03-05 10:02:03.359	info	(18552) use known BT list: [ '01:12:23:34:45:56' ]
radar2.0	2020-03-05 10:02:03.359	info	(18552) radar2 set to flag items away if they are not seen for 2 minutes
radar2.0	2020-03-05 10:02:03.359	info	(18552) found 'node-bluetooth'
radar2.0	2020-03-05 10:02:03.355	info	(18552) found '@abandonware/noble'
radar2.0	2020-03-05 10:02:03.292	info	(18552) Connected with '0.0.0.0' for DHCP Scan
radar2.0	2020-03-05 10:02:03.238	info	(18552) radar2 initialization started...
radar2.0	2020-03-05 10:02:03.202	info	(18552) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v10.19.0

      Hat jemand eine Idee?

      1 Reply Last reply Reply Quote 0
      • cbund
        cbund last edited by

        Selbe nachdem ich auf Debian10 und alles geupdatet habe bekomme ich diese Fehler. Habe auch die Zeilen eingegeben die in der Anleitung stehen ohne Erfolg.
        Adapter wird kurz grün und dann rot.

        Dominik F. 1 Reply Last reply Reply Quote 0
        • Dominik F.
          Dominik F. @cbund last edited by Dominik F.

          [gelöscht]

          1 Reply Last reply Reply Quote 0
          • lobomau
            lobomau last edited by

            Habt ihr schon die Zeilen in die Konsole getippt?

            sudo apt-get install libcap2-bin arp-scan bluetooth bluez libbluetooth-dev libudev-dev net-tools
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which arp-scan`)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which node`)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which arp`)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which hcitool`)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which hciconfig`)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which l2ping`)
            Dominik F. 1 Reply Last reply Reply Quote 0
            • Dominik F.
              Dominik F. @lobomau last edited by Dominik F.

              @lobomau

              Ja, bekomme ich beim ausführen folgendes:

              root@IoBroker:/home/thebermud# sudo apt-get install libcap2-bin arp-scan bluetooth bluez libbluetooth-dev libudev-dev net-tools
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which hcitool`)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which hciconfig`)
Paketlisten werden gelesen... Fertigw,cap_net_bind_service=+eip $(eval readlink -f `which l2ping`)
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
arp-scan ist schon die neueste Version (1.9.5-1).
bluetooth ist schon die neueste Version (5.50-1).
bluez ist schon die neueste Version (5.50-1).
libbluetooth-dev ist schon die neueste Version (5.50-1).
libcap2-bin ist schon die neueste Version (1:2.25-2).
net-tools ist schon die neueste Version (1.60+git20180626.aebd88e-1).
libudev-dev ist schon die neueste Version (241-7~deb10u3).
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  libc-ares2 libuv1 nodejs-doc
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
root@IoBroker:/home/thebermud# sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which arp-scan`)
readlink: fehlender Operand
„readlink --help“ liefert weitere Informationen.
usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]

 Note <filename> must be a regular (non-symlink) file.
root@IoBroker:/home/thebermud# sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which node`)
root@IoBroker:/home/thebermud# sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which arp`)
readlink: fehlender Operand
„readlink --help“ liefert weitere Informationen.
usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]

 Note <filename> must be a regular (non-symlink) file.
root@IoBroker:/home/thebermud# sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which hcitool`)
root@IoBroker:/home/thebermud# sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which hciconfig`)
root@IoBroker:/home/thebermud# sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which l2ping`)

              Radar lässt sich weiter nicht starten bzw wird nicht grün

              host.IoBroker	2020-03-07 18:02:20.585	error	Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:61:11) errno: 19, code: 'ENODEV', syscall: 'bind' }
host.IoBroker	2020-03-07 18:02:20.585	error	Caught by controller[0]: at process.nextTick (/opt/iobroker/node_modules/@abandonware/noble/lib/noble.js:60:24)
host.IoBroker	2020-03-07 18:02:20.585	error	Caught by controller[0]: at NobleBindings.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
host.IoBroker	2020-03-07 18:02:20.585	error	Caught by controller[0]: at Hci.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
host.IoBroker	2020-03-07 18:02:20.585	error	Caught by controller[0]: { Error: ENODEV, No such device
radar2.0	2020-03-07 18:02:20.564	info	(7136) Adapter disconnected and stopped with dostop(false) and callback(true)
radar2.0	2020-03-07 18:02:20.564	error	at process._tickCallback (internal/process/next_tick.js:61:11)
radar2.0	2020-03-07 18:02:20.564	error	at process.nextTick (/opt/iobroker/node_modules/@abandonware/noble/lib/noble.js:60:24)
radar2.0	2020-03-07 18:02:20.564	error	at NobleBindings.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
radar2.0	2020-03-07 18:02:20.564	error	at Hci.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
radar2.0	2020-03-07 18:02:20.564	error	(7136) Error: ENODEV, No such device
radar2.0	2020-03-07 18:02:20.563	error	(7136) uncaught exception: ENODEV, No such device
              1 Reply Last reply Reply Quote 0
              • cbund
                cbund last edited by

                Gelöst: Habe einen Nuc und muss den Bluetoothadapter weiterschleifen an die VM

                Dominik F. 1 Reply Last reply Reply Quote 0
                • Dominik F.
                  Dominik F. @cbund last edited by

                  @cbund

                  erklärst du noch wie du das gemacht hast? Vielleicht ist das ja auch die Lösung für mich

                  1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User last edited by

                    Ich klinke mich mal in den Threat ein.
                    Ich habe exakt das gleiche Problem nach einem Umzug von einer Qnap-Debian VM auf ein Odroid N2.
                    Eine De- und Neuinstallation nebst der Befehlseingabe aus der Radar-Doku hat leider nichts gebracht.

                    Gemäß des Logs scheint Radar ein Gerät nicht zu finden. Die weiteren Logeinträge weisen auf hci hin,
                    so dass Radar scheinbar nach einem Bluetooth-Device sucht. Doch weder die frühere VM noch der aktuelle Odroid hatten bzw. haben ein Bluetooth-Gerät.
                    Daher irritiert mich, dass im Log in Zeile 20 steht: "found node-bluetooth"
                    Muss aber natürlich nichts heißen, ich habe diesbezüglich leider keine Ahnung.
                    Ich habe in der Config unter "Bei Linux: Nummer des Bluetooth Adapters" sowohl versucht, das Feld auf "-1" zu lassen, als auch es zu löschen. Leider bleibt in beiden Fällen der Fehler und die Instanz bleibt "Rot".
                    Vielleicht hat ja ein anderer dieses Problem bereits lösen können.

                    Viele Grüße

                    Fritz

                    2020-03-08 21:12:10.880  - ^[[32minfo^[[39m: host.odroid instance system.adapter.radar2.0 started with pid 24545
2020-03-08 22:12:11.661  - ^[[34mdebug^[[39m: radar2.0 (24545) Redis Objects: Use Redis connection: 127.0.0.1:9001
2020-03-08 22:12:11.694  - ^[[34mdebug^[[39m: radar2.0 (24545) Objects client ready ... initialize now
2020-03-08 22:12:11.698  - ^[[34mdebug^[[39m: radar2.0 (24545) Objects create System PubSub Client
2020-03-08 22:12:11.699  - ^[[34mdebug^[[39m: radar2.0 (24545) Objects create User PubSub Client
2020-03-08 22:12:11.700  - ^[[34mdebug^[[39m: radar2.0 (24545) Objects client initialize lua scripts
2020-03-08 22:12:11.710  - ^[[34mdebug^[[39m: radar2.0 (24545) Objects connected to redis: 127.0.0.1:9001
2020-03-08 22:12:11.716  - ^[[34mdebug^[[39m: radar2.0 (24545) objectDB connected
2020-03-08 22:12:11.718  - ^[[34mdebug^[[39m: radar2.0 (24545) Redis States: Use Redis connection: 127.0.0.1:9000
2020-03-08 22:12:11.724  - ^[[34mdebug^[[39m: radar2.0 (24545) States create User PubSub Client
2020-03-08 22:12:11.726  - ^[[34mdebug^[[39m: radar2.0 (24545) States create System PubSub Client
2020-03-08 22:12:11.735  - ^[[34mdebug^[[39m: radar2.0 (24545) States connected to redis: 127.0.0.1:9000
2020-03-08 22:12:11.736  - ^[[34mdebug^[[39m: radar2.0 (24545) statesDB connected
2020-03-08 22:12:12.274  - ^[[32minfo^[[39m: radar2.0 (24545) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v10.19.0
2020-03-08 22:12:12.338  - ^[[32minfo^[[39m: radar2.0 (24545) debug: radar2 received undefined objects and 1 states, with config devices,scandelay,arp_scan_cmd,btadapterid,printerdelay,removeEnd,knownIPs,knownBTs,external,delayaway,delayuwz,numuwz,longuwz,lang,latitude,longitude,adapterConf,loglevel
2020-03-08 22:12:12.339  - ^[[32minfo^[[39m: radar2.0 (24545) radar2 initialization started...
2020-03-08 22:12:12.354  - ^[[32minfo^[[39m: radar2.0 (24545) debug: mtime of /opt/iobroker/node_modules/iobroker.radar2/lib/vendors.json is Sat Oct 26 1985 09:15:00 GMT+0100 (Central European Standard Time) stats are 418.417990876929
2020-03-08 22:12:12.476  - ^[[32minfo^[[39m: radar2.0 (24545) Connected with '0.0.0.0' for DHCP Scan
2020-03-08 22:12:12.592  - ^[[32minfo^[[39m: radar2.0 (24545) found '@abandonware/noble'
2020-03-08 22:12:12.599  - ^[[32minfo^[[39m: radar2.0 (24545) found 'node-bluetooth'
2020-03-08 22:12:12.600  - ^[[32minfo^[[39m: radar2.0 (24545) radar2 set to flag items away if they are not seen for 5 minutes
2020-03-08 22:12:12.601  - ^[[32minfo^[[39m: radar2.0 (24545) use known BT list: []
2020-03-08 22:12:12.601  - ^[[32minfo^[[39m: radar2.0 (24545) use known IP list: []
2020-03-08 22:12:12.601  - ^[[32minfo^[[39m: radar2.0 (24545) Remove name end for host names: .fritz.box
2020-03-08 22:12:12.602  - ^[[32minfo^[[39m: radar2.0 (24545) arp-scan will use the following interfaces: [ 'eth0' ]
2020-03-08 22:12:12.603  - ^[[32minfo^[[39m: radar2.0 (24545) radar2 set to scan every 120 seconds and printers every 100 minutes.
2020-03-08 22:12:12.616  - ^[[31merror^[[39m: radar2.0 (24545) uncaught exception: ENODEV, No such device
2020-03-08 22:12:12.617  - ^[[31merror^[[39m: radar2.0 (24545) Error: ENODEV, No such device
    at Hci.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
    at NobleBindings.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
    at process.nextTick (/opt/iobroker/node_modules/@abandonware/noble/lib/noble.js:60:24)
    at process._tickCallback (internal/process/next_tick.js:61:11)
2020-03-08 22:12:12.618  - ^[[32minfo^[[39m: radar2.0 (24545) Adapter disconnected and stopped with dostop(false) and callback(true)
2020-03-08 21:12:12.681  - ^[[31merror^[[39m: host.odroid Caught by controller[0]: { Error: ENODEV, No such device
2020-03-08 21:12:12.683  - ^[[31merror^[[39m: host.odroid Caught by controller[0]:     at Hci.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
2020-03-08 21:12:12.683  - ^[[31merror^[[39m: host.odroid Caught by controller[0]:     at NobleBindings.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
2020-03-08 21:12:12.683  - ^[[31merror^[[39m: host.odroid Caught by controller[0]:     at process.nextTick (/opt/iobroker/node_modules/@abandonware/noble/lib/noble.js:60:24)
2020-03-08 21:12:12.683  - ^[[31merror^[[39m: host.odroid Caught by controller[0]:     at process._tickCallback (internal/process/next_tick.js:61:11) errno: 19, code: 'ENODEV', syscall: 'bind' }
2020-03-08 21:12:12.683  - ^[[32minfo^[[39m: host.odroid instance system.adapter.radar2.0 terminated with code 0 (NO_ERROR)
2020-03-08 21:12:12.684  - ^[[32minfo^[[39m: host.odroid Restart adapter system.adapter.radar2.0 because enabled
2020-03-08 21:12:21.174  - ^[[32minfo^[[39m: host.odroid "system.adapter.radar2.0" disabled
                    1 Reply Last reply Reply Quote 0
                    • cbund
                      cbund last edited by

                      Ich habe unter Proxmox den USB freigegeben. Als Hardware in deiner VM.

                      1 Reply Last reply Reply Quote 0
                      • etv
                        etv last edited by etv

                        Liebe Leute,

                        möchte mich da dran hängen - selbes Problem - Raspi alles auf neuesten Strand gebracht, Node V10.20.0. und seither den Fehler beim Radar 2.0 Adapter - davor alles kein Problem - hab noch ein zweites System exakt gleich aufgesetzt, da tut noch alles....

                        Der LOG ( von unten nach oben, weil direkt aus dem Browser kopiert)

                        
host.etv-iobroker-mediarack	2020-04-10 19:05:52.352	info	Restart adapter system.adapter.radar2.0 because enabled
host.etv-iobroker-mediarack	2020-04-10 19:05:52.350	info	instance system.adapter.radar2.0 terminated with code 0 (NO_ERROR)
host.etv-iobroker-mediarack	2020-04-10 19:05:52.345	error	Caught by controller[0]: port: 67 }
host.etv-iobroker-mediarack	2020-04-10 19:05:52.341	error	Caught by controller[0]: address: '0.0.0.0',
host.etv-iobroker-mediarack	2020-04-10 19:05:52.339	error	Caught by controller[0]: syscall: 'bind',
host.etv-iobroker-mediarack	2020-04-10 19:05:52.337	error	Caught by controller[0]: code: 'EACCES',
host.etv-iobroker-mediarack	2020-04-10 19:05:52.336	error	Caught by controller[0]: errno: 'EACCES',
host.etv-iobroker-mediarack	2020-04-10 19:05:52.336	error	Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:63:19)
host.etv-iobroker-mediarack	2020-04-10 19:05:52.335	error	Caught by controller[0]: at state.handle.lookup (dgram.js:242:18)
host.etv-iobroker-mediarack	2020-04-10 19:05:52.332	error	Caught by controller[0]: { Error: bind EACCES 0.0.0.0:67

                        Alle Zeilen von oben (iobomau 7. März 2020, 17:57) eingegeben - ohne Fehler duchgelaufen - Trotzdem tut der Radar Adapter nix mehr

                        Liebe Grüße
                        Tom

                        1 Reply Last reply Reply Quote 0
                        • C
                          csamaggi last edited by csamaggi

                          Kann man das BT im Adapter deaktivieren?

                          Da ich im Moment kein Device dran habe und er im Log meckert und nicht startet

                          
host.iobroker	2020-04-12 12:39:48.678	info	Do not restart adapter system.adapter.radar2.0 because disabled or deleted
host.iobroker	2020-04-12 12:39:48.678	error	instance system.adapter.radar2.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
radar2.0	2020-04-12 12:39:48.169	warn	(9677) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
radar2.0	2020-04-12 12:39:48.165	error	(9677) adapter disabled
host.iobroker	2020-04-12 12:39:46.739	info	"system.adapter.radar2.0" disabled
host.iobroker	2020-04-12 12:39:46.739	info	"system.adapter.radar2.0" disabled
host.iobroker	2020-04-12 12:39:46.739	info	"system.adapter.radar2.0" disabled
host.iobroker	2020-04-12 12:39:46.739	info	"system.adapter.radar2.0" disabled
host.iobroker	2020-04-12 12:39:46.739	info	"system.adapter.radar2.0" disabled
host.iobroker	2020-04-12 12:39:46.739	info	"system.adapter.radar2.0" disabled
host.iobroker	2020-04-12 12:39:46.739	info	"system.adapter.radar2.0" disabled
host.iobroker	2020-04-12 12:39:46.127	info	Restart adapter system.adapter.radar2.0 because enabled
host.iobroker	2020-04-12 12:39:46.127	info	instance system.adapter.radar2.0 terminated with code 0 (NO_ERROR)
host.iobroker	2020-04-12 12:39:46.127	error	Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:61:11) errno: 19, code: 'ENODEV', syscall: 'bind' }
host.iobroker	2020-04-12 12:39:46.127	error	Caught by controller[0]: at process.nextTick (/opt/iobroker/node_modules/@abandonware/noble/lib/noble.js:60:24)
host.iobroker	2020-04-12 12:39:46.127	error	Caught by controller[0]: at NobleBindings.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
host.iobroker	2020-04-12 12:39:46.127	error	Caught by controller[0]: at Hci.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
host.iobroker	2020-04-12 12:39:46.127	error	Caught by controller[0]: { Error: ENODEV, No such device
radar2.0	2020-04-12 12:39:46.102	info	(9655) Adapter disconnected and stopped with dostop(false) and callback(true)
radar2.0	2020-04-12 12:39:46.102	error	(9655) Error: ENODEV, No such device at Hci.init (/opt/iobroker/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35) at NobleBindings.init (/opt/iobroker/node_modules/@abandonware/nob
radar2.0	2020-04-12 12:39:46.101	error	(9655) uncaught exception: ENODEV, No such device
radar2.0	2020-04-12 12:39:46.096	info	(9655) radar2 set to scan every 20 seconds and printers every 720 minutes.
radar2.0	2020-04-12 12:39:46.096	info	(9655) arp-scan will use the following interfaces: [ 'enp1s0' ]
radar2.0	2020-04-12 12:39:46.096	info	(9655) Remove name end for host names: .fritz.box
radar2.0	2020-04-12 12:39:46.095	info	(9655) use known IP list: [ '1.1.1.1' ]
radar2.0	2020-04-12 12:39:46.095	info	(9655) use known BT list: [ '01:12:23:34:45:56' ]
radar2.0	2020-04-12 12:39:46.095	info	(9655) radar2 set to flag items away if they are not seen for 2 minutes
radar2.0	2020-04-12 12:39:46.094	info	(9655) found 'node-bluetooth'
radar2.0	2020-04-12 12:39:46.092	info	(9655) found '@abandonware/noble'
radar2.0	2020-04-12 12:39:46.048	info	(9655) Connected with '0.0.0.0' for DHCP Scan
radar2.0	2020-04-12 12:39:46.000	info	(9655) radar2 initialization started...
radar2.0	2020-04-12 12:39:45.923	info	(9655) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v10.20.0

                          MFG Maggi

                          1 Reply Last reply Reply Quote 0
                          • A
                            amnesia106 last edited by

                            Gibts da schon was neues? Mein Radar2 bringt die gleichen Fehler.

                            1 Reply Last reply Reply Quote 0
                            • S
                              Supermicha last edited by

                              Moin zusammen.
                              Hatte zwar nicht die gleichen Fehlermeldungen, aber nach dem Update auf 1.2.5 wurde mein Radar2 auch nicht mehr grün und das log lief über.

                              Bei mir hat es geholfen in den Adaptereinstellungen
                              "hcitool lescan anstelle von 'Noble' verwenden"
                              zu aktivieren.

                              Adapter war sofort grün und Fehlermeldungen sind seitdem weg.

                              1 Reply Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active last edited by

                                https://forum.iobroker.net/post/435884

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

                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                468
                                Online

                                31.8k
                                Users

                                80.0k
                                Topics

                                1.3m
                                Posts

                                radar2 adapter radar2.0 error
                                9
                                14
                                1614
                                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