Anwesenheitserkennung Bluetooth PebbleBee

[Atze]

da steht das hier:

Code Auswählen Erweitern

May 20 12:21:35 aliendeb blescan.pl[15287]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:21:38 aliendeb blescan.pl[15197]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:21:40 aliendeb blescan.pl[15289]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:21:40 aliendeb blescan.pl[15287]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:21:43 aliendeb blescan.pl[15197]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:21:44 aliendeb blescan.pl[15195]: Did NOT receive an advertisement from bluetooth mac address '7C:2F:80:91:72:18'.
May 20 12:21:45 aliendeb blescan.pl[15287]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:21:46 aliendeb blescan.pl[15289]: Received advertisement from desired bluetooth mac address '7C:2F:80:91:71:A3' with name '(unknown)' after 1 seconds.
May 20 12:21:48 aliendeb blescan.pl[15197]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:21:50 aliendeb blescan.pl[15287]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:21:51 aliendeb blescan.pl[15289]: Timeout (5s) occured while closing hcitool handle. Sending SIGTERM to hcitool process.
May 20 12:21:51 aliendeb fhem[347]: refcnt: fd -1 < 0
May 20 12:21:53 aliendeb blescan.pl[15197]: Received 'Set scan parameters failed: Input/output error', resetting...
May 20 12:21:55 aliendeb blescan.pl[15197]: Received advertisement from desired bluetooth mac address '7C:2F:80:91:71:A3' with name '(unknown)' after 1 seconds.
May 20 12:21:55 aliendeb blescan.pl[15287]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:22:00 aliendeb blescan.pl[15197]: Timeout (5s) occured while closing hcitool handle. Sending SIGTERM to hcitool process.
May 20 12:22:00 aliendeb fhem[347]: refcnt: fd -1 < 0
May 20 12:22:00 aliendeb blescan.pl[15287]: Received 'Set scan parameters failed: Input/output error', resetting...
May 20 12:22:32 aliendeb blescan.pl[15360]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:91:72:18, duration: 60).
May 20 12:22:32 aliendeb blescan.pl[15360]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:22:37 aliendeb blescan.pl[15360]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:22:42 aliendeb blescan.pl[15360]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:22:47 aliendeb blescan.pl[15360]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:22:51 aliendeb blescan.pl[15371]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:91:71:A3, duration: 60).
May 20 12:22:51 aliendeb blescan.pl[15371]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:22:52 aliendeb blescan.pl[15360]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:22:56 aliendeb blescan.pl[15371]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:22:57 aliendeb blescan.pl[15360]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:23:01 aliendeb blescan.pl[15371]: blescan.pl is already running. Sleeping 5 seconds.
May 20 12:23:01 aliendeb blescan.pl[15287]: Did NOT receive an advertisement from bluetooth mac address '7C:2F:80:91:72:18'.
May 20 12:23:06 aliendeb blescan.pl[15371]: blescan.pl is already running. Sleeping 5 seconds.

[PatrickR]

@Atze:
Welche Intervalle hast Du in FHEM eingestellt?
Wie viele Geräte fragst Du ab? 2?

Patrick

[Atze]

2 Geräte, 60 60 60.

ich glaube die Fehler beginnen sobald das erste Device nicht mehr pingbar (abwesend) ist.

[PatrickR]

@Atze:
Also das Problem ist, dass alle 60 Sekunden blescan.pl aufgerufen wird und im worst case, d. h. wenn ein Gerät nicht erreichbar ist, volle 60 Sekunden läuft. Da aber nur ein Scan gleichzeitig statt finden kann sammeln sich die Prozesse und bauen eine riesige Warteschlange auf bis der Scharfrichter kommt (in diesem Fall FHEM) und sie zu Grunde richtet.

Lösung: Scanzeit von blescan.pl heruntersetzen oder das Intervall in FHEM hochsetzen.

Patrick

[Atze]

Is schon spät und ich steh ein wenig auf der Leitung.

<para1> Bluescript wird mit alle x Sekunden aufgerufen, egal was passiert
<para2> check-interval - Das normale Prüfinterval in Sekunden für eine Anwesenheitsprüfung
<para3> present-check-interval - Das Prüfinterval in Sekunden, wenn ein Gerät anwesend (present) ist

angenommen 15 60 60  sollte dann doch eigentlich für 2 Geräte ausreichend sein, oder ?

[StefanW]

Also, bei mir läuft es auch noch nicht rund.
Interval bei 2 Geräten ist 15 60 60

Code Auswählen Erweitern

May 20 23:21:43 localhost bluetoothd[2373]: Adapter /org/bluez/2373/hci0 has been enabled
May 20 23:21:44 localhost blescan.pl[22246]: Received advertisement from desired bluetooth mac address '7C:2F:80:8E:FA:51' with name '(unknown)' after 0 seconds.
May 20 23:22:06 localhost blescan.pl[22252]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:8E:95:FE, duration: 15).
May 20 23:22:07 localhost blescan.pl[22252]: Received advertisement from desired bluetooth mac address '7C:2F:80:8E:95:FE' with name '(unknown)' after 1 seconds.
May 20 23:22:45 localhost blescan.pl[22288]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:8E:FA:51, duration: 15).
May 20 23:22:45 localhost blescan.pl[22288]: Received 'Set scan parameters failed: Input/output error', resetting...
May 20 23:22:45 localhost bluetoothd[2373]: HCI dev 0 down
May 20 23:22:45 localhost bluetoothd[2373]: Adapter /org/bluez/2373/hci0 has been disabled
May 20 23:22:45 localhost bluetoothd[2373]: Error parsing EIR data: Invalid argument (22)
May 20 23:22:56 localhost blescan.pl[22288]: Received 'Invalid device: Network is down', resetting...
May 20 23:23:07 localhost blescan.pl[22288]: Received 'Invalid device: Network is down', resetting...
May 20 23:23:08 localhost blescan.pl[22298]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:8E:95:FE, duration: 15).
May 20 23:23:08 localhost blescan.pl[22298]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:23:13 localhost blescan.pl[22298]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:23:18 localhost blescan.pl[22298]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:23:18 localhost blescan.pl[22288]: Received 'Invalid device: Network is down', resetting...
May 20 23:23:23 localhost blescan.pl[22298]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:23:28 localhost blescan.pl[22298]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:23:29 localhost blescan.pl[22288]: Maximum number of retries (5) exceeded.
May 20 23:23:33 localhost blescan.pl[22298]: Received 'Invalid device: Network is down', resetting...
May 20 23:23:44 localhost blescan.pl[22298]: Received 'Invalid device: Network is down', resetting...
May 20 23:23:55 localhost blescan.pl[22298]: Received 'Invalid device: Network is down', resetting...
May 20 23:24:06 localhost blescan.pl[22298]: Received 'Invalid device: Network is down', resetting...
May 20 23:24:17 localhost blescan.pl[22298]: Maximum number of retries (5) exceeded.
May 20 23:24:18 localhost blescan.pl[22343]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:8E:95:FE, duration: 15).
May 20 23:24:18 localhost blescan.pl[22343]: Received 'Invalid device: Network is down', resetting...
May 20 23:24:29 localhost blescan.pl[22343]: Received 'Invalid device: Network is down', resetting...
May 20 23:24:29 localhost bluetoothd[2373]: Device is already marked as connected
May 20 23:24:29 localhost blescan.pl[22350]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:8E:FA:51, duration: 15).
May 20 23:24:29 localhost blescan.pl[22350]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:24:34 localhost blescan.pl[22350]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:24:39 localhost blescan.pl[22350]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:24:40 localhost blescan.pl[22343]: Received 'Invalid device: Network is down', resetting...
May 20 23:24:44 localhost blescan.pl[22350]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:24:49 localhost blescan.pl[22350]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:24:51 localhost blescan.pl[22343]: Received 'Invalid device: Network is down', resetting...
May 20 23:24:54 localhost blescan.pl[22350]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:24:59 localhost blescan.pl[22350]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:25:02 localhost blescan.pl[22343]: Maximum number of retries (5) exceeded.
May 20 23:25:04 localhost blescan.pl[22350]: Received 'Invalid device: Network is down', resetting...
May 20 23:25:15 localhost blescan.pl[22350]: Received 'Invalid device: Network is down', resetting...
May 20 23:25:26 localhost blescan.pl[22350]: Received 'Invalid device: Network is down', resetting...
May 20 23:25:26 localhost bluetoothd[2373]: Device is already marked as connected
May 20 23:25:37 localhost blescan.pl[22350]: Received 'Invalid device: Network is down', resetting...
May 20 23:25:39 localhost blescan.pl[22429]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:8E:FA:51, duration: 15).
May 20 23:25:39 localhost blescan.pl[22429]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:25:44 localhost blescan.pl[22429]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:25:48 localhost blescan.pl[22350]: Maximum number of retries (5) exceeded.
May 20 23:25:49 localhost blescan.pl[22429]: Received 'Invalid device: Network is down', resetting...
May 20 23:26:00 localhost blescan.pl[22429]: Received 'Invalid device: Network is down', resetting...
May 20 23:26:02 localhost blescan.pl[22436]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:8E:95:FE, duration: 15).
May 20 23:26:02 localhost blescan.pl[22436]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:26:07 localhost blescan.pl[22436]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:26:11 localhost blescan.pl[22429]: Received 'Invalid device: Network is down', resetting...
May 20 23:26:12 localhost blescan.pl[22436]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:26:17 localhost blescan.pl[22436]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:26:22 localhost blescan.pl[22436]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:26:22 localhost blescan.pl[22429]: Received 'Invalid device: Network is down', resetting...
May 20 23:26:23 localhost bluetoothd[2373]: Device is already marked as connected
May 20 23:26:27 localhost blescan.pl[22436]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:26:32 localhost blescan.pl[22436]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:26:33 localhost blescan.pl[22429]: Maximum number of retries (5) exceeded.
May 20 23:26:37 localhost blescan.pl[22436]: Received 'Invalid device: Network is down', resetting...
May 20 23:26:48 localhost blescan.pl[22436]: Received 'Invalid device: Network is down', resetting...
May 20 23:26:59 localhost blescan.pl[22436]: Received 'Invalid device: Network is down', resetting...
May 20 23:27:10 localhost blescan.pl[22436]: Received 'Invalid device: Network is down', resetting...
May 20 23:27:12 localhost blescan.pl[22483]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:8E:95:FE, duration: 15).
May 20 23:27:12 localhost blescan.pl[22483]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:27:17 localhost blescan.pl[22483]: blescan.pl is already running. Sleeping 5 seconds.
May 20 23:27:21 localhost blescan.pl[22436]: Maximum number of retries (5) exceeded.

Code Auswählen Erweitern

2015.05.20 23:17:38 2: PRESENCE (GTag_Fahrrad) - error while processing check: unexpected script output (expected 0 or 1): ERROR: Maximum number of retries exceeded.
2015.05.20 23:23:29 2: PRESENCE (GTag_Fahrrad) - error while processing check: unexpected script output (expected 0 or 1): ERROR: Maximum number of retries exceeded.
2015.05.20 23:24:07 1: Timeout for PRESENCE_DoLocalShellScriptScan reached, terminated process 22296
2015.05.20 23:24:07 2: PRESENCE (GTag_Auto) - device could not be checked (retrying in 10 seconds)
2015.05.20 23:25:02 2: PRESENCE (GTag_Auto) - check returned a valid result after 1 unsuccesful retry
2015.05.20 23:25:02 2: PRESENCE (GTag_Auto) - error while processing check: unexpected script output (expected 0 or 1): ERROR: Maximum number of retries exceeded.
2015.05.20 23:25:29 1: Timeout for PRESENCE_DoLocalShellScriptScan reached, terminated process 22348
2015.05.20 23:25:29 2: PRESENCE (GTag_Fahrrad) - device could not be checked (retrying in 10 seconds)
2015.05.20 23:26:33 2: PRESENCE (GTag_Fahrrad) - check returned a valid result after 1 unsuccesful retry
2015.05.20 23:26:33 2: PRESENCE (GTag_Fahrrad) - error while processing check: unexpected script output (expected 0 or 1): ERROR: Maximum number of retries exceeded.
2015.05.20 23:27:02 1: Timeout for PRESENCE_DoLocalShellScriptScan reached, terminated process 22434
2015.05.20 23:27:02 2: PRESENCE (GTag_Auto) - device could not be checked (retrying in 10 seconds)
2015.05.20 23:28:06 2: PRESENCE (GTag_Auto) - check returned a valid result after 1 unsuccesful retry
2015.05.20 23:28:06 2: PRESENCE (GTag_Auto) - error while processing check: unexpected script output (expected 0 or 1): ERROR: Maximum number of retries exceeded.
2015.05.20 23:28:33 1: Timeout for PRESENCE_DoLocalShellScriptScan reached, terminated process 22520
2015.05.20 23:28:33 2: PRESENCE (GTag_Fahrrad) - device could not be checked (retrying in 10 seconds)
2015.05.20 23:29:38 2: PRESENCE (GTag_Fahrrad) - check returned a valid result after 1 unsuccesful retry
2015.05.20 23:29:38 2: PRESENCE (GTag_Fahrrad) - error while processing check: unexpected script output (expected 0 or 1): ERROR: Maximum number of retries exceeded.

[PatrickR]

@Atze:

So sind die Einstellungen schonmal gut. Die verwende ich auch, sogar mit 3 G-Tags.

Das Log sieht so aus als würde sich das Script mit allen zur Verfügung stehenden Möglichkeiten (und das ist nur hciconfig reset) versuchen, den Scan hinzubekommen aber durch bluez mit variierenden Fehlermeldungen totgeworfen werden. Hier führt wohl kein Weg dran vorbei, außerhalb des Skripts Lösungen durchzuprobieren: reboot, Paketupdate, rpi-update, anderer USB-Dongle. Vielleicht hat ja einer der anderen RPi-Nutzer noch eine Idee oder einen Tipp.

Patrick

[gero]

Vor allem würde ich den bluetoothd deaktivieren. Er ist für das hcitool völlig unnötig. Das einzige, was du evtl. brauchst, wenn es nicht ohnehin durch das Script erledigt wird, ist ein hciconfig hci0 up.
Wenn sich auch noch der bluetoothd die ganze Zeit einmischt, wird es schwer ein stabiles System zu bekommen.

Gruß,
Gero

[Atze]

Wenn bluettothd deaktiviert ist, funktioniert das script aber nicht mehr.

Code Auswählen Erweitern

$
May 21 20:51:33 aliendeb blescan.pl[5291]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:91:71:A3, duration: 15).
May 21 20:51:33 aliendeb blescan.pl[5291]: Received unknown output: 'Invalid device: No such device'!
May 21 20:51:34 aliendeb blescan.pl[5291]: Received unknown output: 'Invalid device: No such device'!
May 21 20:51:35 aliendeb blescan.pl[5291]: Received unknown output: 'Invalid device: No such device'!
May 21 20:51:36 aliendeb blescan.pl[5291]: Received unknown output: 'Invalid device: No such device'!
May 21 20:51:37 aliendeb blescan.pl[5291]: Maximum number of retries (5) exceeded.
May 21 20:51:49 aliendeb blescan.pl[5321]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:91:72:18, duration: 15).
May 21 20:51:49 aliendeb blescan.pl[5321]: Received unknown output: 'Invalid device: No such device'!
May 21 20:51:50 aliendeb blescan.pl[5321]: Received unknown output: 'Invalid device: No such device'!
May 21 20:51:51 aliendeb blescan.pl[5321]: Received unknown output: 'Invalid device: No such device'!
May 21 20:51:52 aliendeb blescan.pl[5321]: Received unknown output: 'Invalid device: No such device'!
May 21 20:51:53 aliendeb blescan.pl[5321]: Maximum number of retries (5) exceeded.
May 21 20:52:38 aliendeb blescan.pl[5384]: Version 0.8 started (device: hci0, mac address: 7C:2F:80:91:71:A3, duration: 15).
May 21 20:52:38 aliendeb blescan.pl[5384]: Received unknown output: 'Invalid device: No such device'!
May 21 20:52:39 aliendeb blescan.pl[5384]: Received unknown output: 'Invalid device: No such device'!
May 21 20:52:40 aliendeb blescan.pl[5384]: Received unknown output: 'Invalid device: No such device'!
May 21 20:52:41 aliendeb blescan.pl[5384]: Received unknown output: 'Invalid device: No such device'!
May 21 20:52:42 aliendeb blescan.pl[5384]: Maximum number of retries (5) exceeded.


[gero]

Wie schon geschrieben, fehlt ein  "hciconfig hci0 up" um den Bluetoothadapter zu aktivieren.
Das Script sollte prüfen, ob der Bluetoothadapter verfügbar ist, und ihn ggfls. aktivieren.

Gruß,
Gero

[steven]

Hallo,


kann jemand was zu dieser Ausgabe sagen?

Code Auswählen Erweitern


2015.05.22 20:32:56 5: PRESENCE (BLE_tag) - stopping timer
2015.05.22 20:32:56 5: PRESENCE (BLE_tag) - starting blocking call for mode shellscript
2015.05.22 20:32:56 5: PRESENCE (BLE_tag) - execute local shell script: BLE_tag|sudo /opt/fhem/pr/blescan.pl 84:EB:18:7B:93:14 15|0
2015.05.22 20:32:56 5: PRESENCE (BLE_tag) - script output:
2015.05.22 20:32:56 5: Cmd: >{PRESENCE_ProcessLocalScan('BLE_tag|0|error|unexpected script output (expected 0 or 1): ')}<
2015.05.22 20:32:56 5: PRESENCE (BLE_tag) - blocking scan result: BLE_tag|0|error|unexpected script output (expected 0 or 1):
2015.05.22 20:32:56 2: PRESENCE (BLE_tag) - error while processing check: unexpected script output (expected 0 or 1):
2015.05.22 20:32:56 4: PRESENCE (BLE_tag) - rescheduling next check in 60 seconds


in der Shell kommt der entsprechende Wert 1 o. 0 zurück.

danke

[steven]

der Eintrag in der /etc/sudoers fehlte
fhem ALL=NOPASSWD: /opt/fhem/pr/blescan.pl

[Markus M.]

Leider nach wie vor unbrauchbar für BLE Tracker mit Advertise im Minutenbereich (55sec).
Nach einem halben Tag sieht die Prozessliste so aus:

[PatrickR]

Leider nach wie vor unbrauchbar für BLE Tracker mit Advertise im Minutenbereich (55sec).
Nach einem halben Tag sieht die Prozessliste so aus:

Ich fürchte, das wird sich mit dem gewählten Ansatz auch nicht ändern, zumal Du mit 5 Trackern im worst case erst nach 5 Minuten eine Änderung mitbekommst.

Es hat nicht zufällig schon jemand im stillen Kämmerlein einen Daemon in Arbeit, der permanent mitlauscht?

Patrick

[justme1968]

die version die ständig mit lauscht gibt es im prinzip weiter oben im
thread. die müsste man 'nur' schön machen. man braucht dafür hält einen dedizierten le dongle.

gruß
  andre