NEWS
Test Adapter radar2 v1.2.x GitHub
-
Hallo Leute,
der Adapter funktioniert soweit gut, aber ich habe noch das Problem das arp-scan nicht läuft.
Im log:Adapter not running as root or iobroker has no sudo right, cannot use arp-scan!Ich denke ich habe alle probiert:
sudors von iobroker passt,
iobroker fix gemacht,
als iobroker angemeldet -> arp-scan geht ohne passwort
Nur in iobroker kommt die warning von oben und doArp(false)...
Vielleicht fällt euch ja noch was ein, was ich probieren kann...Grüße
Megawaldi -
Hallo Leute,
der Adapter funktioniert soweit gut, aber ich habe noch das Problem das arp-scan nicht läuft.
Im log:Adapter not running as root or iobroker has no sudo right, cannot use arp-scan!Ich denke ich habe alle probiert:
sudors von iobroker passt,
iobroker fix gemacht,
als iobroker angemeldet -> arp-scan geht ohne passwort
Nur in iobroker kommt die warning von oben und doArp(false)...
Vielleicht fällt euch ja noch was ein, was ich probieren kann...Grüße
Megawaldiapr-scan sudo -u iobroker arp-scan sudo arp-scan -
apr-scan sudo -u iobroker arp-scan sudo arp-scan -
Hab ich schon probiert:
Auf alle drei Befehle kommt die normale help info von arp-scan.
Sollte also ansich laufen? Bin ein bischen ratlos...@megawaldi
Bitte Ein- und Ausgaben vollständig posten und nicht nacherzählen.
Der Adapterstart sieht im log file genau wie aus? -
[17:59][martin@xxx:~]$ arp-scan -interface=wlan0 Interface: wlan0, type: EN10MB, MAC: e4:5f:01:03:XX:XX, IPv4: 192.168.0.XXX Usage: arp-scan [options] [hosts...] Target hosts must be specified on the command line unless the --file option is given, in which case the targets are read from the specified file instead, or the --localnet option is used, in which case the targets are generated from the network interface IP address and netmask. You will need to be root, or arp-scan must be SUID root, in order to run arp-scan, because the functions that it uses to read and write packets require root privilege. The target hosts can be specified as IP addresses or hostnames. You can also specify the target as IPnetwork/bits (e.g. 192.168.1.0/24) to specify all hosts in the given network (network and broadcast addresses included), or IPstart-IPend (e.g. 192.168.1.3-192.168.1.27) to specify all hosts in the inclusive range, or IPnetwork:NetMask (e.g. 192.168.1.0:255.255.255.0) to specify all hosts in the given network and mask. These different options for specifying target hosts may be used both on the command line, and also in the file specified with the --file option. use "arp-scan --help" for detailed information on the available options. Report bugs or send suggestions at https://github.com/royhills/arp-scan See the arp-scan homepage at https://github.com/royhills/arp-scan [17:59][martin@xxx:~]$ sudo -u iobroker arp-scan -interface=wlan0 [sudo] password for martin: Interface: wlan0, type: EN10MB, MAC: e4:5f:01:03:XX:XX, IPv4: 192.168.0.XXX Usage: arp-scan [options] [hosts...] Target hosts must be specified on the command line unless the --file option is given, in which case the targets are read from the specified file instead, or the --localnet option is used, in which case the targets are generated from the network interface IP address and netmask. You will need to be root, or arp-scan must be SUID root, in order to run arp-scan, because the functions that it uses to read and write packets require root privilege. The target hosts can be specified as IP addresses or hostnames. You can also specify the target as IPnetwork/bits (e.g. 192.168.1.0/24) to specify all hosts in the given network (network and broadcast addresses included), or IPstart-IPend (e.g. 192.168.1.3-192.168.1.27) to specify all hosts in the inclusive range, or IPnetwork:NetMask (e.g. 192.168.1.0:255.255.255.0) to specify all hosts in the given network and mask. These different options for specifying target hosts may be used both on the command line, and also in the file specified with the --file option. use "arp-scan --help" for detailed information on the available options. Report bugs or send suggestions at https://github.com/royhills/arp-scan See the arp-scan homepage at https://github.com/royhills/arp-scan [17:59][martin@xxx:~]$ sudo arp-scan -interface=wlan0 Interface: wlan0, type: EN10MB, MAC: e4:5f:01:03:XX:XX, IPv4: 192.168.0.XXX Usage: arp-scan [options] [hosts...] Target hosts must be specified on the command line unless the --file option is given, in which case the targets are read from the specified file instead, or the --localnet option is used, in which case the targets are generated from the network interface IP address and netmask. You will need to be root, or arp-scan must be SUID root, in order to run arp-scan, because the functions that it uses to read and write packets require root privilege. The target hosts can be specified as IP addresses or hostnames. You can also specify the target as IPnetwork/bits (e.g. 192.168.1.0/24) to specify all hosts in the given network (network and broadcast addresses included), or IPstart-IPend (e.g. 192.168.1.3-192.168.1.27) to specify all hosts in the inclusive range, or IPnetwork:NetMask (e.g. 192.168.1.0:255.255.255.0) to specify all hosts in the given network and mask. These different options for specifying target hosts may be used both on the command line, and also in the file specified with the --file option. use "arp-scan --help" for detailed information on the available options. Report bugs or send suggestions at https://github.com/royhills/arp-scan See the arp-scan homepage at https://github.com/royhills/arp-scanradar2.0 2021-03-12 16:34:33.724 warn (2036) Adapter not running as root or iobroker has no sudo right, cannot use arp-scan! radar2.0 2021-03-12 16:34:33.541 info (2036) Connected with '0.0.0.0' for DHCP Scan radar2.0 2021-03-12 16:34:33.043 info (2036) Will run hcitool-mode and not noble on device [ [Object] ]! radar2.0 2021-03-12 16:34:32.933 info (2036) Will use l2Ping for BT scans. radar2.0 2021-03-12 16:34:32.916 info (2036) radar2 initialization started... radar2.0 2021-03-12 16:34:32.494 info (2036) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.radar2, node: v12.21.0, js-controller: 3.2.16Danach läuft er ohne Fehler und Warnungen bis zum:
radar2.0 2021-03-12 16:35:40.088 info (2036) Adapter initialization finished!Durch.
Ich denke das ich das dazwischen aus Datenschutzgründen hier nicht posten will. Ist aber nichts komisches dabei.Danke dir für deine Hilfe Thomas
-
[17:59][martin@xxx:~]$ arp-scan -interface=wlan0 Interface: wlan0, type: EN10MB, MAC: e4:5f:01:03:XX:XX, IPv4: 192.168.0.XXX Usage: arp-scan [options] [hosts...] Target hosts must be specified on the command line unless the --file option is given, in which case the targets are read from the specified file instead, or the --localnet option is used, in which case the targets are generated from the network interface IP address and netmask. You will need to be root, or arp-scan must be SUID root, in order to run arp-scan, because the functions that it uses to read and write packets require root privilege. The target hosts can be specified as IP addresses or hostnames. You can also specify the target as IPnetwork/bits (e.g. 192.168.1.0/24) to specify all hosts in the given network (network and broadcast addresses included), or IPstart-IPend (e.g. 192.168.1.3-192.168.1.27) to specify all hosts in the inclusive range, or IPnetwork:NetMask (e.g. 192.168.1.0:255.255.255.0) to specify all hosts in the given network and mask. These different options for specifying target hosts may be used both on the command line, and also in the file specified with the --file option. use "arp-scan --help" for detailed information on the available options. Report bugs or send suggestions at https://github.com/royhills/arp-scan See the arp-scan homepage at https://github.com/royhills/arp-scan [17:59][martin@xxx:~]$ sudo -u iobroker arp-scan -interface=wlan0 [sudo] password for martin: Interface: wlan0, type: EN10MB, MAC: e4:5f:01:03:XX:XX, IPv4: 192.168.0.XXX Usage: arp-scan [options] [hosts...] Target hosts must be specified on the command line unless the --file option is given, in which case the targets are read from the specified file instead, or the --localnet option is used, in which case the targets are generated from the network interface IP address and netmask. You will need to be root, or arp-scan must be SUID root, in order to run arp-scan, because the functions that it uses to read and write packets require root privilege. The target hosts can be specified as IP addresses or hostnames. You can also specify the target as IPnetwork/bits (e.g. 192.168.1.0/24) to specify all hosts in the given network (network and broadcast addresses included), or IPstart-IPend (e.g. 192.168.1.3-192.168.1.27) to specify all hosts in the inclusive range, or IPnetwork:NetMask (e.g. 192.168.1.0:255.255.255.0) to specify all hosts in the given network and mask. These different options for specifying target hosts may be used both on the command line, and also in the file specified with the --file option. use "arp-scan --help" for detailed information on the available options. Report bugs or send suggestions at https://github.com/royhills/arp-scan See the arp-scan homepage at https://github.com/royhills/arp-scan [17:59][martin@xxx:~]$ sudo arp-scan -interface=wlan0 Interface: wlan0, type: EN10MB, MAC: e4:5f:01:03:XX:XX, IPv4: 192.168.0.XXX Usage: arp-scan [options] [hosts...] Target hosts must be specified on the command line unless the --file option is given, in which case the targets are read from the specified file instead, or the --localnet option is used, in which case the targets are generated from the network interface IP address and netmask. You will need to be root, or arp-scan must be SUID root, in order to run arp-scan, because the functions that it uses to read and write packets require root privilege. The target hosts can be specified as IP addresses or hostnames. You can also specify the target as IPnetwork/bits (e.g. 192.168.1.0/24) to specify all hosts in the given network (network and broadcast addresses included), or IPstart-IPend (e.g. 192.168.1.3-192.168.1.27) to specify all hosts in the inclusive range, or IPnetwork:NetMask (e.g. 192.168.1.0:255.255.255.0) to specify all hosts in the given network and mask. These different options for specifying target hosts may be used both on the command line, and also in the file specified with the --file option. use "arp-scan --help" for detailed information on the available options. Report bugs or send suggestions at https://github.com/royhills/arp-scan See the arp-scan homepage at https://github.com/royhills/arp-scanradar2.0 2021-03-12 16:34:33.724 warn (2036) Adapter not running as root or iobroker has no sudo right, cannot use arp-scan! radar2.0 2021-03-12 16:34:33.541 info (2036) Connected with '0.0.0.0' for DHCP Scan radar2.0 2021-03-12 16:34:33.043 info (2036) Will run hcitool-mode and not noble on device [ [Object] ]! radar2.0 2021-03-12 16:34:32.933 info (2036) Will use l2Ping for BT scans. radar2.0 2021-03-12 16:34:32.916 info (2036) radar2 initialization started... radar2.0 2021-03-12 16:34:32.494 info (2036) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.radar2, node: v12.21.0, js-controller: 3.2.16Danach läuft er ohne Fehler und Warnungen bis zum:
radar2.0 2021-03-12 16:35:40.088 info (2036) Adapter initialization finished!Durch.
Ich denke das ich das dazwischen aus Datenschutzgründen hier nicht posten will. Ist aber nichts komisches dabei.Danke dir für deine Hilfe Thomas
@megawaldi sagte in Test Adapter radar2 v1.2.x GitHub:
Auf was für Hardware und OS läuft die Geschichte?
-
@megawaldi sagte in Test Adapter radar2 v1.2.x GitHub:
Auf was für Hardware und OS läuft die Geschichte?
-
Ist ein raspi 4 mit Ubuntu LTS
@megawaldi
Mit Raspberry OS funktioniert das einwandfrei hier.Warum setzt man Ubuntu LTS (Welches Release?) ein und nicht das viel besser an den Pi 4 angepasste Raspberry OS? (Ich hoffe nicht wegen 'des schöneren Desktops')
-
@megawaldi
Mit Raspberry OS funktioniert das einwandfrei hier.Warum setzt man Ubuntu LTS (Welches Release?) ein und nicht das viel besser an den Pi 4 angepasste Raspberry OS? (Ich hoffe nicht wegen 'des schöneren Desktops')
-
@thomas-braun
Das hat sich so ergeben. Nutze das ganze nur headless und bei raspian ist mir ehrlichgesagt zu viel "müll" dabei für ein server linux.@megawaldi
Der Müll funktioniert aber. -
@megawaldi
Der Müll funktioniert aber.@thomas-braun
Wenn du mir dann bitte mal erzälen kannst, was für einen Einfluss jetzt nen xserver desktop oder nen office auf mein Problem mit arp-scan hat bin ich beeindruckt. Übrigens ist Ubuntu arm auch ein auf nen raspi optimiertes Linux. Das beide also Ubuntu und rasperian nen debian port sind muss ich dir ja ned erklären. -
@thomas-braun
Wenn du mir dann bitte mal erzälen kannst, was für einen Einfluss jetzt nen xserver desktop oder nen office auf mein Problem mit arp-scan hat bin ich beeindruckt. Übrigens ist Ubuntu arm auch ein auf nen raspi optimiertes Linux. Das beide also Ubuntu und rasperian nen debian port sind muss ich dir ja ned erklären.@megawaldi was passiert denn, wenn du setcap einzeln absetzt
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which arp-scan`) -
@thomas-braun
Wenn du mir dann bitte mal erzälen kannst, was für einen Einfluss jetzt nen xserver desktop oder nen office auf mein Problem mit arp-scan hat bin ich beeindruckt. Übrigens ist Ubuntu arm auch ein auf nen raspi optimiertes Linux. Das beide also Ubuntu und rasperian nen debian port sind muss ich dir ja ned erklären.@megawaldi sagte in Test Adapter radar2 v1.2.x GitHub:
Einfluss jetzt nen xserver desktop oder nen office auf mein Problem mit arp-scan hat bin ich beeindruckt.
Keinen. Weil ja keines von beidem auf einem Server läuft.
Das beide also Ubuntu und rasperian nen debian port sind muss ich dir ja ned erklären.
Nee, brauchst du nicht. Das weiß ich. Trotzdem gibt es Unterschiede.
-
@megawaldi was passiert denn, wenn du setcap einzeln absetzt
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which arp-scan`)Geht ohne Probleme ändert aber nix..
[18:39][martin@xxx:~]$ sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which arp-scan`) [18:40][martin@xxx:~]$Als user iobroker gehts ohne sudo oder Passwort, also wie es sein sollte...
iobroker@xxx:~$ arp-scan -lgq --interface=wlan0 Interface: wlan0, type: EN10MB, MAC: e4:5f:01:03:54:4f, IPv4: 192.168.0.206 Starting arp-scan 1.9.7 with 256 hosts (https://github.com/royhills/arp-scan) 192.168.0.1 2c:3a:fd:9e:xx:xx 192.168.0.2 44:4e:6d:36:xx:xx 192.168.0.100 c4:9d:ed:1a:xx:xx .... 24 packets received by filter, 0 packets dropped by kernel Ending arp-scan 1.9.7: 256 hosts scanned in 1.884 seconds (135.88 hosts/sec). 17 responded -
Geht ohne Probleme ändert aber nix..
[18:39][martin@xxx:~]$ sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f `which arp-scan`) [18:40][martin@xxx:~]$Als user iobroker gehts ohne sudo oder Passwort, also wie es sein sollte...
iobroker@xxx:~$ arp-scan -lgq --interface=wlan0 Interface: wlan0, type: EN10MB, MAC: e4:5f:01:03:54:4f, IPv4: 192.168.0.206 Starting arp-scan 1.9.7 with 256 hosts (https://github.com/royhills/arp-scan) 192.168.0.1 2c:3a:fd:9e:xx:xx 192.168.0.2 44:4e:6d:36:xx:xx 192.168.0.100 c4:9d:ed:1a:xx:xx .... 24 packets received by filter, 0 packets dropped by kernel Ending arp-scan 1.9.7: 256 hosts scanned in 1.884 seconds (135.88 hosts/sec). 17 responded@megawaldi
Dann kann es eigentlich nur noch daran liegen wie sudo unter Ubuntu tickt. -
So mein Problem ist gelöst.
Falls es jemand interessiert, es ist entstanden dadurch das ich noch ein tunel interface auf dem System habe. Dadurch wirft arp-scan beim einfachen Aufruf einen Fehler, das das tunnel interface keine MAC Adresse hat.
Da radar2 auf den Fehler mit der fehlenden MAC Adresse reagiert hat, indem es meint es ist ein rechte Problem.
Lösung: Bei der Prüfung im Quellcode bei der Initialisierung des Adapters das interface angeben.Original:
if (arpcmd && await testLinux('arp-scan')) if (await A.exec('arp-scan')) doArp = `"${arpcmd}" on ${network.ip4addrs()}`; else A.W("Adapter not running as root or iobroker has no sudo right, cannot use arp-scan!");Änderung:
if (arpcmd && await testLinux('arp-scan')) if (await A.exec('arp-scan -I wlan0')) doArp = `"${arpcmd}" on ${network.ip4addrs()}`; else A.W("Adapter not running as root or iobroker has no sudo right, cannot use arp-scan!");Allen Beteiligten vielen Dank und einen schönen Abend
-
So mein Problem ist gelöst.
Falls es jemand interessiert, es ist entstanden dadurch das ich noch ein tunel interface auf dem System habe. Dadurch wirft arp-scan beim einfachen Aufruf einen Fehler, das das tunnel interface keine MAC Adresse hat.
Da radar2 auf den Fehler mit der fehlenden MAC Adresse reagiert hat, indem es meint es ist ein rechte Problem.
Lösung: Bei der Prüfung im Quellcode bei der Initialisierung des Adapters das interface angeben.Original:
if (arpcmd && await testLinux('arp-scan')) if (await A.exec('arp-scan')) doArp = `"${arpcmd}" on ${network.ip4addrs()}`; else A.W("Adapter not running as root or iobroker has no sudo right, cannot use arp-scan!");Änderung:
if (arpcmd && await testLinux('arp-scan')) if (await A.exec('arp-scan -I wlan0')) doArp = `"${arpcmd}" on ${network.ip4addrs()}`; else A.W("Adapter not running as root or iobroker has no sudo right, cannot use arp-scan!");Allen Beteiligten vielen Dank und einen schönen Abend
Hallo zusammen,
ich habe versucht mit diesen, sowie dem Vorgänger Thread mein Bluetooth Problem zu lösen, leider ohne Erfolg. Daher erlaube ich mir den Schwarm zu fragen, was ich noch machen könnte....
Mein Problem:
Radar 2 meldet beim Start "node-bluetooth not found!" genaues log siehe unten.Der Adapter hat schon mal funktioniert, allerdings auf einem Pi 3, bin umgezogen auf einen Pi4, und bin mir nicht sicher ob das problem seit dem besteht, Bluethooth brauche ich erst jetzt, also möchte es nutzen.
ICh habe den ble Adapter versuchsweise installiert, er läuft tadellos. Hab radar diverse male deinstalliert, und ich denke alles an anleitungen hier durchgeackert... bin kurz davor den ble zu nehmen, und dann mit blockly zu stricken, aber das fuchst mich... Bin für jede Idee zu haben!Hier das komplette Log:
pi@raspberrypi:~ $ sudo -u iobroker node /opt/iobroker/node_modules/iobroker.radar2/radar2.js --force --logs --nolazy info: got following adapter: { name: 'radar2' } 2021-03-17 22:53:20.957 - info: radar2.0 (13359) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v12.20.2, js-controller: 3.2.16 2021-03-17 22:53:21.125 - warn: radar2.0 (13359) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer! 2021-03-17 22:53:21.156 - info: radar2.0 (13359) radar2 initialization started... 2021-03-17 22:53:21.285 - info: radar2.0 (13359) Connected with '0.0.0.0' for DHCP Scan 2021-03-17 22:53:21.434 - info: radar2.0 (13359) found '@abandonware/noble' 2021-03-17 22:53:21.436 - warn: radar2.0 (13359) node-bluetooth not found! 2021-03-17 22:53:21.437 - info: radar2.0 (13359) radar2 set to flag items away if they are not seen for 2 minutes 2021-03-17 22:53:21.438 - info: radar2.0 (13359) use known BT list: [] 2021-03-17 22:53:21.440 - info: radar2.0 (13359) use known IP list: [ '1.1.1.1' ] 2021-03-17 22:53:21.441 - info: radar2.0 (13359) Remove name end for host names: .fritz.box 2021-03-17 22:53:21.442 - info: radar2.0 (13359) arp-scan will use the following interfaces: [ 'eth0' ] 2021-03-17 22:53:21.443 - info: radar2.0 (13359) radar2 set to scan every 20 seconds and printers every 720 minutes. 2021-03-17 22:53:21.498 - info: radar2.0 (13359) Will try to scan BT devices: true 2021-03-17 22:53:23.310 - info: radar2.0 (13359) Init item Ich- with {name: 'Ich-',id: 'Ich',type: 'IP',rip: [ '127.0.0.1' ],lasthere: '2021-03-17T21:53:09.589Z',anwesend: true} 2021-03-17 22:53:23.319 - warn: radar2.0 (13359) ip address 192.168.2.1 in Fritzbox was used already for another device Fritzbox, this is forbidden! 2021-03-17 22:53:23.447 - info: radar2.0 (13359) Init item Fritzbox with {name: 'Fritzbox',id: 'Fritzbox',type: 'IP',rip: [ '192.168.2.1', '192.168.2.1' ],lasthere: '2021-03-17T21:53:09.573Z',hasMAC: [ '2c:91:ab:bf:06:b3' ],anwesend: true} 2021-03-17 22:53:23.489 - info: radar2.0 (13359) Init item HP-7520- with {name: 'HP-7520-',ip: 'HPC56C03-PS7520',id: 'HP-7520',type: 'printer'} 2021-03-17 22:53:24.268 - info: radar2.0 (13359) New external IP address 0 2021-03-17 22:53:24.307 - info: radar2.0 (13359) Adapter identified macs: (2c:91:ab:bf:06:b3), ips: (127.0.0.1,192.168.2.1), bts: () 2021-03-17 22:53:24.309 - warn: radar2.0 (13359) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer! 2021-03-17 22:53:26.378 - info: radar2.0 (13359) will scan UWZ with code UWZDE49497 every 120 minutes 2021-03-17 22:53:26.384 - info: radar2.0 (13359) will scan printers [ 'HP-7520-' ] every 720 minutes 2021-03-17 22:53:26.472 - info: radar2.0 (13359) UWZ found the following (changed) warnings: No warnings 2021-03-17 22:53:26.606 - info: radar2.0 (13359) radar2 found 3 devices in config (Ich-,Fritzbox,HP-7520-) 2021-03-17 22:53:26.607 - info: radar2.0 (13359) radar2 set use of noble(true), doArp("-lgq --retry=5 --timeout=400" on eth0), btid(0) and doUwz(UWZDE49497,120,0,de,true). 2021-03-17 22:53:35.169 - info: radar2.0 (13359) first scan took 8.536 seconds 2021-03-17 22:53:35.170 - info: radar2.0 (13359) will scan external network every 60 minutes 2021-03-17 22:53:35.854 - info: radar2.0 (13359) New external IP address 0 2021-03-17 22:53:35.856 - warn: radar2.0 (13359) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer! 2021-03-17 22:53:36.646 - info: radar2.0 (13359) Adapter initialization finished! Vielen Dank!!! -
Hallo zusammen,
ich habe versucht mit diesen, sowie dem Vorgänger Thread mein Bluetooth Problem zu lösen, leider ohne Erfolg. Daher erlaube ich mir den Schwarm zu fragen, was ich noch machen könnte....
Mein Problem:
Radar 2 meldet beim Start "node-bluetooth not found!" genaues log siehe unten.Der Adapter hat schon mal funktioniert, allerdings auf einem Pi 3, bin umgezogen auf einen Pi4, und bin mir nicht sicher ob das problem seit dem besteht, Bluethooth brauche ich erst jetzt, also möchte es nutzen.
ICh habe den ble Adapter versuchsweise installiert, er läuft tadellos. Hab radar diverse male deinstalliert, und ich denke alles an anleitungen hier durchgeackert... bin kurz davor den ble zu nehmen, und dann mit blockly zu stricken, aber das fuchst mich... Bin für jede Idee zu haben!Hier das komplette Log:
pi@raspberrypi:~ $ sudo -u iobroker node /opt/iobroker/node_modules/iobroker.radar2/radar2.js --force --logs --nolazy info: got following adapter: { name: 'radar2' } 2021-03-17 22:53:20.957 - info: radar2.0 (13359) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v12.20.2, js-controller: 3.2.16 2021-03-17 22:53:21.125 - warn: radar2.0 (13359) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer! 2021-03-17 22:53:21.156 - info: radar2.0 (13359) radar2 initialization started... 2021-03-17 22:53:21.285 - info: radar2.0 (13359) Connected with '0.0.0.0' for DHCP Scan 2021-03-17 22:53:21.434 - info: radar2.0 (13359) found '@abandonware/noble' 2021-03-17 22:53:21.436 - warn: radar2.0 (13359) node-bluetooth not found! 2021-03-17 22:53:21.437 - info: radar2.0 (13359) radar2 set to flag items away if they are not seen for 2 minutes 2021-03-17 22:53:21.438 - info: radar2.0 (13359) use known BT list: [] 2021-03-17 22:53:21.440 - info: radar2.0 (13359) use known IP list: [ '1.1.1.1' ] 2021-03-17 22:53:21.441 - info: radar2.0 (13359) Remove name end for host names: .fritz.box 2021-03-17 22:53:21.442 - info: radar2.0 (13359) arp-scan will use the following interfaces: [ 'eth0' ] 2021-03-17 22:53:21.443 - info: radar2.0 (13359) radar2 set to scan every 20 seconds and printers every 720 minutes. 2021-03-17 22:53:21.498 - info: radar2.0 (13359) Will try to scan BT devices: true 2021-03-17 22:53:23.310 - info: radar2.0 (13359) Init item Ich- with {name: 'Ich-',id: 'Ich',type: 'IP',rip: [ '127.0.0.1' ],lasthere: '2021-03-17T21:53:09.589Z',anwesend: true} 2021-03-17 22:53:23.319 - warn: radar2.0 (13359) ip address 192.168.2.1 in Fritzbox was used already for another device Fritzbox, this is forbidden! 2021-03-17 22:53:23.447 - info: radar2.0 (13359) Init item Fritzbox with {name: 'Fritzbox',id: 'Fritzbox',type: 'IP',rip: [ '192.168.2.1', '192.168.2.1' ],lasthere: '2021-03-17T21:53:09.573Z',hasMAC: [ '2c:91:ab:bf:06:b3' ],anwesend: true} 2021-03-17 22:53:23.489 - info: radar2.0 (13359) Init item HP-7520- with {name: 'HP-7520-',ip: 'HPC56C03-PS7520',id: 'HP-7520',type: 'printer'} 2021-03-17 22:53:24.268 - info: radar2.0 (13359) New external IP address 0 2021-03-17 22:53:24.307 - info: radar2.0 (13359) Adapter identified macs: (2c:91:ab:bf:06:b3), ips: (127.0.0.1,192.168.2.1), bts: () 2021-03-17 22:53:24.309 - warn: radar2.0 (13359) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer! 2021-03-17 22:53:26.378 - info: radar2.0 (13359) will scan UWZ with code UWZDE49497 every 120 minutes 2021-03-17 22:53:26.384 - info: radar2.0 (13359) will scan printers [ 'HP-7520-' ] every 720 minutes 2021-03-17 22:53:26.472 - info: radar2.0 (13359) UWZ found the following (changed) warnings: No warnings 2021-03-17 22:53:26.606 - info: radar2.0 (13359) radar2 found 3 devices in config (Ich-,Fritzbox,HP-7520-) 2021-03-17 22:53:26.607 - info: radar2.0 (13359) radar2 set use of noble(true), doArp("-lgq --retry=5 --timeout=400" on eth0), btid(0) and doUwz(UWZDE49497,120,0,de,true). 2021-03-17 22:53:35.169 - info: radar2.0 (13359) first scan took 8.536 seconds 2021-03-17 22:53:35.170 - info: radar2.0 (13359) will scan external network every 60 minutes 2021-03-17 22:53:35.854 - info: radar2.0 (13359) New external IP address 0 2021-03-17 22:53:35.856 - warn: radar2.0 (13359) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer! 2021-03-17 22:53:36.646 - info: radar2.0 (13359) Adapter initialization finished! Vielen Dank!!!@dieckfr
Was ist das für ein komischer node-Befehl? -
Hallo zusammen,
ich habe versucht mit diesen, sowie dem Vorgänger Thread mein Bluetooth Problem zu lösen, leider ohne Erfolg. Daher erlaube ich mir den Schwarm zu fragen, was ich noch machen könnte....
Mein Problem:
Radar 2 meldet beim Start "node-bluetooth not found!" genaues log siehe unten.Der Adapter hat schon mal funktioniert, allerdings auf einem Pi 3, bin umgezogen auf einen Pi4, und bin mir nicht sicher ob das problem seit dem besteht, Bluethooth brauche ich erst jetzt, also möchte es nutzen.
ICh habe den ble Adapter versuchsweise installiert, er läuft tadellos. Hab radar diverse male deinstalliert, und ich denke alles an anleitungen hier durchgeackert... bin kurz davor den ble zu nehmen, und dann mit blockly zu stricken, aber das fuchst mich... Bin für jede Idee zu haben!Hier das komplette Log:
pi@raspberrypi:~ $ sudo -u iobroker node /opt/iobroker/node_modules/iobroker.radar2/radar2.js --force --logs --nolazy info: got following adapter: { name: 'radar2' } 2021-03-17 22:53:20.957 - info: radar2.0 (13359) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v12.20.2, js-controller: 3.2.16 2021-03-17 22:53:21.125 - warn: radar2.0 (13359) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer! 2021-03-17 22:53:21.156 - info: radar2.0 (13359) radar2 initialization started... 2021-03-17 22:53:21.285 - info: radar2.0 (13359) Connected with '0.0.0.0' for DHCP Scan 2021-03-17 22:53:21.434 - info: radar2.0 (13359) found '@abandonware/noble' 2021-03-17 22:53:21.436 - warn: radar2.0 (13359) node-bluetooth not found! 2021-03-17 22:53:21.437 - info: radar2.0 (13359) radar2 set to flag items away if they are not seen for 2 minutes 2021-03-17 22:53:21.438 - info: radar2.0 (13359) use known BT list: [] 2021-03-17 22:53:21.440 - info: radar2.0 (13359) use known IP list: [ '1.1.1.1' ] 2021-03-17 22:53:21.441 - info: radar2.0 (13359) Remove name end for host names: .fritz.box 2021-03-17 22:53:21.442 - info: radar2.0 (13359) arp-scan will use the following interfaces: [ 'eth0' ] 2021-03-17 22:53:21.443 - info: radar2.0 (13359) radar2 set to scan every 20 seconds and printers every 720 minutes. 2021-03-17 22:53:21.498 - info: radar2.0 (13359) Will try to scan BT devices: true 2021-03-17 22:53:23.310 - info: radar2.0 (13359) Init item Ich- with {name: 'Ich-',id: 'Ich',type: 'IP',rip: [ '127.0.0.1' ],lasthere: '2021-03-17T21:53:09.589Z',anwesend: true} 2021-03-17 22:53:23.319 - warn: radar2.0 (13359) ip address 192.168.2.1 in Fritzbox was used already for another device Fritzbox, this is forbidden! 2021-03-17 22:53:23.447 - info: radar2.0 (13359) Init item Fritzbox with {name: 'Fritzbox',id: 'Fritzbox',type: 'IP',rip: [ '192.168.2.1', '192.168.2.1' ],lasthere: '2021-03-17T21:53:09.573Z',hasMAC: [ '2c:91:ab:bf:06:b3' ],anwesend: true} 2021-03-17 22:53:23.489 - info: radar2.0 (13359) Init item HP-7520- with {name: 'HP-7520-',ip: 'HPC56C03-PS7520',id: 'HP-7520',type: 'printer'} 2021-03-17 22:53:24.268 - info: radar2.0 (13359) New external IP address 0 2021-03-17 22:53:24.307 - info: radar2.0 (13359) Adapter identified macs: (2c:91:ab:bf:06:b3), ips: (127.0.0.1,192.168.2.1), bts: () 2021-03-17 22:53:24.309 - warn: radar2.0 (13359) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer! 2021-03-17 22:53:26.378 - info: radar2.0 (13359) will scan UWZ with code UWZDE49497 every 120 minutes 2021-03-17 22:53:26.384 - info: radar2.0 (13359) will scan printers [ 'HP-7520-' ] every 720 minutes 2021-03-17 22:53:26.472 - info: radar2.0 (13359) UWZ found the following (changed) warnings: No warnings 2021-03-17 22:53:26.606 - info: radar2.0 (13359) radar2 found 3 devices in config (Ich-,Fritzbox,HP-7520-) 2021-03-17 22:53:26.607 - info: radar2.0 (13359) radar2 set use of noble(true), doArp("-lgq --retry=5 --timeout=400" on eth0), btid(0) and doUwz(UWZDE49497,120,0,de,true). 2021-03-17 22:53:35.169 - info: radar2.0 (13359) first scan took 8.536 seconds 2021-03-17 22:53:35.170 - info: radar2.0 (13359) will scan external network every 60 minutes 2021-03-17 22:53:35.854 - info: radar2.0 (13359) New external IP address 0 2021-03-17 22:53:35.856 - warn: radar2.0 (13359) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer! 2021-03-17 22:53:36.646 - info: radar2.0 (13359) Adapter initialization finished! Vielen Dank!!!
Support us
860
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge