Open faanskit opened 3 years ago
First issue is being discussed in #186, let's continue there. Basically I agree - BLE disconnect should trigger available=OFF.
Q2: Stray commands: I'm guessing mqtt? AFAIK mqtt and BLE are the only two sources of info. Can you see with more verbose logging the origin?
Gone are the messages on MQTT, but now this comes in the logs instead. Strange. Repeats every restart of the app.
2021-05-11 21:01:52 INF [device-comm] startWriteQueue()
2021-05-11 21:01:52 DBG [device-comm] Write queue: Processing Relä (C061998B0B5F_0). Command Turn off. Total queue length: 2
2021-05-11 21:01:52 VRB [plejd-ble] Sending 6 byte(s) of data to Plejd. 0c0110009700
2021-05-11 21:01:52 DBG [device-comm] Write queue: Processing Dimmer_2_1 (D670E6FE619D_0). Command Turn off. Total queue length: 1
2021-05-11 21:01:52 VRB [plejd-ble] Sending 6 byte(s) of data to Plejd. 0f0110009700
2021-05-11 21:01:52 DBG [device-comm] Write queue: Processing Dimmer (C12D372125FD_0). Command Turn off. Total queue length: 0
Issue - devices online when they are surely offline
Even though a BT module is not present, or if there are now Plejd devices available (due to power off). The devices are reported to to be online, and with that available in the Ui.
Expected behavior is that ./online is only sent if there is an active BLE device. (I know about the issue with reconnect).
hassio-plej log
MQTT log
Question 2 - Stray commands?
Each startup I see these three stray commands. Can someone please explain them? They surely do not originate from the BLE in this case since Bluetooth is offline. They are send every start since some time back.