radar 2.0 crashes

[axelrathey]

radar 2.0 does not work any more. It becomes shortly green, then it went to red.

There are some debug messages von radar 2.0

Thanks for your help

adar2.0 2020-02-23 14:19:27.010 info (17800) radar2 set to scan every 20 seconds and printers every 720 minutes.
radar2.0 2020-02-23 14:19:27.008 info (17800) arp-scan will use the following interfaces: [ 'br0' ]
radar2.0 2020-02-23 14:19:27.005 info (17800) Remove name end for host names: .fritz.box
radar2.0 2020-02-23 14:19:27.003 info (17800) use known IP list: [ '1.1.1.1' ]
radar2.0 2020-02-23 14:19:27.000 info (17800) use known BT list: [ '01:12:23:34:45:56' ]
radar2.0 2020-02-23 14:19:26.995 info (17800) radar2 set to flag items away if they are not seen for 2 minutes
radar2.0 2020-02-23 14:19:26.993 info (17800) found 'node-bluetooth'
radar2.0 2020-02-23 14:19:26.961 info (17800) found '@abandonware/noble'
radar2.0 2020-02-23 14:19:26.425 info (17800) Adapter disconnected and stopped with dostop(false) and callback(true)
radar2.0 2020-02-23 14:19:26.419 error at process._tickCallback (internal/process/next_tick.js:63:19)
radar2.0 2020-02-23 14:19:26.419 error at state.handle.lookup (dgram.js:242:18)
radar2.0 2020-02-23 14:19:26.419 error (17800) Error: bind EACCES 0.0.0.0:67
radar2.0 2020-02-23 14:19:26.417 error (17800) uncaught exception: bind EACCES 0.0.0.0:67
radar2.0 2020-02-23 14:19:25.829 info (17800) net-ping not available! Will try to use normal ping!
radar2.0 2020-02-23 14:19:25.797 info (17800) radar2 initialization started...
radar2.0 2020-02-23 14:19:25.583 info (17800) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v10.19.0

[Martin-int01]

same problem here after update node.js to 12.16.3 and npm to 6.14.4

[frankjoke]

As listed in readme, you need to rerun the scripts after updating node or even after updating system with some new versions of BT or other drivers because the new versions do not have authority!

[axelrathey]

what do you mean with rerun scripts?

[frankjoke]

In the readme of the adapter you find installation section where you are asked to do this:
`sudo apt-get install -y coreutils libcap2-bin arp-scan bluetooth bluez libbluetooth-dev libudev-dev net-tools

and below need to be run whenever you update nodejs!

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)`

You need to rerun the commands below the second line!

[Martin-int01]

Hi Frank,

ok. I'll try this. Thanks!!
Have you any news about the adapter without bluetooth device? I've a virtual machine without bluetooth device. Unfortunately the adapter crashes because of this.

thank you in advance

best regards

[frankjoke]

I tested this on one of my VMs without BT and it works if you switch noble off (use hcitool instead of noble) for me. Did you test this?

[Martin-int01]

Hi,

it works both (without bluetooth and after nodejs update). Thank you very much!!

best regards

[axelrathey]

Hi,
It works for me now too.

First I copied the above setcap lines but there were some missing " ' ".
So I copied them from the radar2 readme in github. After this restart radar2 failed again.

Then I switched from noble to hcitool in the radar2 config and now radar2 works fine.

My BananaPI M3 has BT onboard, but this BT is not supported with raspbian on the bananapi.

Thanks for your help
Axel

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.
Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.