[gelöst] Anwesenheitserkennung verursacht Device is not available.

Begonnen von Burny4600, 18 Dezember 2017, 16:32:51

Vorheriges Thema - Nächstes Thema

Burny4600

Ich habe eine Anwesenheitserkennung eingericht die bisher immer funktioniert hat.
Seit kurzem ist mit Aufgefallen das PRESENCE immer eine Fehlermeldung generiert bei der ich nicht weiter kann woher diese verursacht wird.

2017.12.18 11:05:02.647 5: PRESENCE (HandyCSC1_AB_LAN) - blocking scan result: HandyCSC1_AB_LAN|0|absent
2017.12.18 11:05:02.650 4: PRESENCE (HandyCSC1_AB_LAN) - rescheduling next check in 10 seconds
2017.12.18 11:05:02.653 5: PRESENCE (HandyCSC2_AB_LAN) - blocking scan result: HandyCSC2_AB_LAN|0|absent
2017.12.18 11:05:02.655 4: PRESENCE (HandyCSC2_AB_LAN) - rescheduling next check in 10 seconds
2017.12.18 11:05:04.237 5: PRESENCE (HandyFST_AB_LAN) - ping command returned with output:
PING 192.168.17.153 (192.168.17.153) 56(84) bytes of data.
From 192.168.17.186 icmp_seq=1 Destination Host Unreachable
From 192.168.17.186 icmp_seq=2 Destination Host Unreachable
From 192.168.17.186 icmp_seq=3 Destination Host Unreachable
From 192.168.17.186 icmp_seq=4 Destination Host Unreachable

--- 192.168.17.153 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3122ms
pipe 4
2017.12.18 11:05:04.766 5: PRESENCE (HandyFST_AB_LAN) - blocking scan result: HandyFST_AB_LAN|0|absent
2017.12.18 11:05:04.769 4: PRESENCE (HandyFST_AB_LAN) - rescheduling next check in 10 seconds
2017.12.18 11:05:05.473 5: PRESENCE (HandyBSC_AB_BT) - stopping timer
2017.12.18 11:05:05.474 5: PRESENCE (HandyBSC_AB_BT) - starting blocking call for mode local-bluetooth
2017.12.18 11:05:05.500 5: PRESENCE (HandyBSC_AB_BT) - starting bluetooth scan: HandyBSC_AB_BT|00:21:08:0d:7c:e9|0|
2017.12.18 11:05:05.514 5: PRESENCE (HandyBSC_AB_BT) - found standard variant of ps command, using "ax" as parameter
2017.12.18 11:05:05.515 4: PRESENCE (HandyBSC_AB_BT) - executing: which hcitool
2017.12.18 11:05:05.523 4: PRESENCE (HandyBSC_AB_BT) - 'which hcitool' returns: /usr/bin/hcitool

2017.12.18 11:05:05.559 5: PRESENCE (HandyBSC_AB_BT) - executing: hcitool name 00:21:08:0d:7c:e9
Device is not available.
2017.12.18 11:05:05.569 4: PRESENCE (HandyBSC_AB_BT) - hcitool returned:
2017.12.18 11:05:05.572 5: PRESENCE (HandyBSC_AB_BT) - blocking scan result: HandyBSC_AB_BT|0|absent
2017.12.18 11:05:05.574 4: PRESENCE (HandyBSC_AB_BT) - rescheduling next check in 10 seconds
2017.12.18 11:05:12.653 5: PRESENCE (HandyCSC1_AB_LAN) - stopping timer
2017.12.18 11:05:12.654 5: PRESENCE (HandyCSC1_AB_LAN) - starting blocking call for mode lan-ping
2017.12.18 11:05:12.662 5: PRESENCE (HandyCSC2_AB_LAN) - stopping timer
2017.12.18 11:05:12.664 5: PRESENCE (HandyCSC2_AB_LAN) - starting blocking call for mode lan-ping
2017.12.18 11:05:12.704 5: PRESENCE (HandyCSC1_AB_LAN) - starting ping scan: HandyCSC1_AB_LAN|192.168.17.150|0|4
2017.12.18 11:05:12.714 5: PRESENCE (HandyCSC2_AB_LAN) - starting ping scan: HandyCSC2_AB_LAN|192.168.17.152|0|4
2017.12.18 11:05:14.771 5: PRESENCE (HandyFST_AB_LAN) - stopping timer
2017.12.18 11:05:14.773 5: PRESENCE (HandyFST_AB_LAN) - starting blocking call for mode lan-ping
2017.12.18 11:05:14.820 5: PRESENCE (HandyFST_AB_LAN) - starting ping scan: HandyFST_AB_LAN|192.168.17.153|0|4
2017.12.18 11:05:15.576 5: PRESENCE (HandyBSC_AB_BT) - stopping timer
2017.12.18 11:05:15.578 5: PRESENCE (HandyBSC_AB_BT) - starting blocking call for mode local-bluetooth
2017.12.18 11:05:15.624 5: PRESENCE (HandyBSC_AB_BT) - starting bluetooth scan: HandyBSC_AB_BT|00:21:08:0d:7c:e9|0|
2017.12.18 11:05:15.648 5: PRESENCE (HandyBSC_AB_BT) - found standard variant of ps command, using "ax" as parameter
2017.12.18 11:05:15.649 4: PRESENCE (HandyBSC_AB_BT) - executing: which hcitool
2017.12.18 11:05:15.665 4: PRESENCE (HandyBSC_AB_BT) - 'which hcitool' returns: /usr/bin/hcitool

2017.12.18 11:05:15.705 5: PRESENCE (HandyBSC_AB_BT) - executing: hcitool name 00:21:08:0d:7c:e9
Device is not available.
2017.12.18 11:05:15.716 4: PRESENCE (HandyBSC_AB_BT) - hcitool returned:
2017.12.18 11:05:15.719 5: PRESENCE (HandyBSC_AB_BT) - blocking scan result: HandyBSC_AB_BT|0|absent
2017.12.18 11:05:15.721 4: PRESENCE (HandyBSC_AB_BT) - rescheduling next check in 10 seconds
2017.12.18 11:05:17.997 5: PRESENCE (HandyFST_AB_LAN) - ping command returned with output:
PING 192.168.17.153 (192.168.17.153) 56(84) bytes of data.
From 192.168.17.186 icmp_seq=1 Destination Host Unreachable
From 192.168.17.186 icmp_seq=2 Destination Host Unreachable
From 192.168.17.186 icmp_seq=3 Destination Host Unreachable
From 192.168.17.186 icmp_seq=4 Destination Host Unreachable

--- 192.168.17.153 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3078ms
pipe 4


2017.12.18 16:44 Änderung
Der Fehler wurde vom Bluetooth verursacht weil der Bluetooth Teil abgeschaltet war.
Mfg Chris

Raspberry Pi 2/2+/3/3+/4 / Betriebssystem: Bullseye Lite
Schnittstellen: RFXtrx433E, SIGNALduino, MQTT, nanoCUL, HM-MOD-UART, 1-Wire, LAN, ser2net, FHEM2FEHEM
Devices: S.USV, APC-USV, Fronius Datalogger Web 2, FS20, IT, Resol VBUS & DL2, TEK603, WMR200, YouLess, Homematic, MQTT