Closed arneroen closed 1 year ago
I got an external BT unit (ASUS USB-BT500), and tried using it. Initially, I saw the same errors, but then it suddenly found the characteristics it was looking for, and was able complete the connection...! I retried (power-cycled the raspi), and I had to manually power-cycle the BT device (bluetoothctl power off
and bluetoothctl power on
), after which it immediately was able to set up the connection.
I removed the BT adapter, and tried the same with the built-in raspi BT adapter, without luck. When i power-cycled the raspi, re-adding the external BT adapter, the add-on was able to power right up, setting up the connection without having to power-cycle the adapter (bluetoothctl power off
and on
).
So, no idea what's going on, but replacing the built-in raspi BT adapter that has been working for half a year seems to have fixed the issue. 🤷
Hello! After a recent (at least for me..!) round of updates to HA, this add-on has stopped working for me :/ Previously everything was working perfectly.
I can see from the logs that it connects to the plejd-servers just fine, and the connection to mtqq is also fine. It also seems to find the bluetooth device, but then it fails when it's missing some "characteristic" (not overly familiar with BT..).
Here is (what I think is) the relevant log snippet:
Running on a RasPi3, using the onboard BT Home Assistant 2023.5.3 Supervisor 2023.04.1 Operating System 10.1
I've since attempted to downgrade both Core, supervisor and the OS several versions, but the error still occurs, so maybe it's not related to the update..? So really not sure what has changed.. The Plejd actuator did not get power-cycled before it happened (but I have restarted it afterwards, to check if that fixed the issue)
Any help is greatly appreciated!