Open ErikThorsell opened 1 year ago
ErikThorsell
commented
1 year ago An acquaintance mentioned that:
Operation failed with ATT error: 0x0eis called GATT_ERR_UNLIKELY and could be the consequence of "sending data too fast".
I don't know if this information is helpful, but I figured I'd add it.
SweVictor
commented
1 year ago Hardware issues are always very tricky and not much we can do from the Addon, unfortunately.
I suppose the retry loop was "never-ending" in both cases? It goes through a couple of different state, in the end after 100 (I think) retries, it tries to power toggle the BLE adapter. In my system, those changes (probably versions 0.8 or 0.9) made a huge change in the resiliency of the addon.
Apart from that (and depending on your setup) you could try changing the timeouts in the settings:
Those will affect how "fast" we deem things as non-functional.
/Victor
ErikThorsell
commented
1 year ago I understand that the add-on cannot take height for hardware issues, but I find it very peculiar that this error appeared out of nowhere.
I suppose the retry loop was "never-ending" in both cases?
Yes. The power toggling happens after 10 retries.
The configuration was set to 2 and 400 respectively. I have changed to 10 / 400 and will see if I experience a difference.
ErikThorsell
commented
1 year ago I made the change above and started the plugin (I turned it off after creating my issue) and it worked!
But I still had logLevel set to silly so I modified the logLevel and pressed Save (which caused a restart of the add-on).
This caused me to go back into the loop behavior...
I then turned off the add-on and let it be for a couple of minutes, before turning it on again.
Now it seems to work again.
sliter mitt hår
This might be the start of my RPi going into retirement. As a fellow swede could you recommend a good Bluetooth USB-dongel that is available on our market?
piemar
commented
1 year ago @ErikThorsell I am a swede and am using this, as the internal one was not was not stable.
Another option is the below, as its recommended and tested according to the add on creator.
Mats1717
commented
1 year ago I put a Plejd smartplugg next to RPi and used 2 and 400 and now I have a stable connection. With the smartplug with 10 and 400 is was reconecting all the time as before.
ErikThorsell
commented
1 year ago I did not mention this in my original post, because I thought it was unrelated, but I had issues updating HA from 2023.8.4 to 2023.9.0 -> https://github.com/home-assistant/core/issues/99909.
2023.9.1 was released yesterday and I was able to update from 2023.8.4 to 2023.9.1 without any issues. I have not had any Plejd-issues since I updated this morning.
Will keep you posted.
ErikThorsell
commented
1 year ago Updated to 2023.9.2 same day as it was made available. After three days, my bluetooth issues reappeared. I will consider reverting to 2023.9.1 tomorrow.
d96moe
commented
1 year ago Plejd has been working like a charm for a very long time. One hour ago I updated to the latest hassio.os, and now I seem to have the same issue☹️ I usually always update both the os and the core when updates are available (running on pi4 with internal bt)
ErikThorsell
commented
1 year ago Updated to 2023.10.0 (OS 10.5) and it has been working for three days now.
Thank you for your update @d96moe, I'd urge you to have a look at: https://github.com/home-assistant/core/issues/99909 and see if you have the same issues.
TorulfDanielsson
commented
1 year ago After updating to OS 11.0 I seem to be in the same situation. Has been working without problems from a very long time. Running on Intel NUC with Intel wifi/Bluetooth.
Home Assistant 2023.10.3 Supervisor 2023.10.0 Operating System 11.0
Mats1717
commented
1 year ago Not working for me, reconnects every 2 minuts. Has a plejd 1 meter from HA on a RPI. Had it working 4-5 weeks ago. Tried separate bluetooth USB dongle with sama problem. se logs below
2023-10-14 08:11:33 INF [plejd-ble] BLE Connected to Plejd Smartplugg 1
2023-10-14 08:11:33 INF [plejd-ble] Plejd clock updates disabled in configuration.
2023-10-14 08:11:33 INF [plejd-ble] startPing()
2023-10-14 08:11:33 INF [device-comm] Bluetooth connected. Plejd BLE up and running!
2023-10-14 08:11:33 INF [device-comm] startWriteQueue()
2023-10-14 08:12:54 WRN [plejd-ble] Write error indicates BLE is disconnected. Retry count 5. Reconnecting...
2023-10-14 08:12:54 INF [plejd-ble] Starting reconnect loop...
2023-10-14 08:12:54 INF [device-comm] Bluetooth reconnecting...
2023-10-14 08:12:59 INF [plejd-ble] Reconnecting BLE...
2023-10-14 08:12:59 INF [plejd-ble] init()
2023-10-14 08:13:04 INF [plejd-ble] disconnecting /org/bluez/hci0/dev_CC_54_0E_CD_B2_40. This can take up to 180 seconds
2023-10-14 08:13:07 ERR [plejd-ble] 'Unlikely error' (0x0e) writing to Plejd. Will retry. Operation failed with ATT error: 0x0e
DBusError: Operation failed with ATT error: 0x0e
at _methodReturnHandlers.
piemar
commented
1 year ago I am having similar issues after the update, ai can't turn off lights.
Running version
Home Assistant 2023.10.3 Supervisor 2023.10.0 Operating System 11.0 Frontend 20231005.0 - latest Mosquito add on version:6.3.1 Plejd Addon version: 0.11.0 Blue tooth adapter:
When trying to turn on turn off I am getting below error:
2023-10-14 13:56:41 ERR [plejd-ble] Error handling /org/bluez/hci1/dev_E9_01_5A_0F_8B_5E Does Not Exist
DBusError: Does Not Exist
at _methodReturnHandlers.
d96moe
commented
1 year ago Updated to 2023.10.0 (OS 10.5) and it has been working for three days now.
Thank you for your update @d96moe, I'd urge you to have a look at: home-assistant/core#99909 and see if you have the same issues.
Seems not to be the same issue. Hassos 11 updates to the bt stack broke hassio-plejd. https://github.com/icanos/hassio-plejd/issues/292
piemar
commented
1 year ago Updated to 2023.10.0 (OS 10.5) and it has been working for three days now. Thank you for your update @d96moe, I'd urge you to have a look at: home-assistant/core#99909 and see if you have the same issues.
Seems not to be the same issue. Hassos 11 updates to the bt stack broke hassio-plejd. #292
I downgraded to below versions and everything started working.
HassiOS ha os update --version 10.5
HassioCore ha core update --version 2023.10.3
Two days ago, without making any (known) changes to my Home Assistant installation nor to the Plejd Addon, I became unable to control my Plejd devices from Home Assistant. Everything still works as expected through the Plejd application on my phone.
Symptoms
In Home Assistant, if I toggle a light, the HA UI will indicate that it's attempting to toggle the light but shortly thereafter the UI will "go back" to just showing the light being off.
I have attached a video where I show how I attempt to toggle three lights. Two of them (Spotlights and hall bv) are Plejd devices. The third one (Hall Lamp Kallax, which works as expected) is a Zigbee light.
https://youtube.com/shorts/RgFabFhBjBI
As far as I can tell, no other parts of Home Assistant are missbehaving.
System
Hardware: Raspberry Pi 4 8GB Bluetooth device: Built-in Home Assistant: 2023.8.4 Supervisor: 2023.08.3 Operating System: 10.5
The Home Assistant system was originally deployed a little bit more than a year ago. The system has been reasonably stable in the past but I have experienced similar issues with Plejd, maybe once or twice. However, the past few issues have always been resolved after a reboot.
Troubleshooting steps taken
Thusfar I have:
Observations
Looking through my Home Assistant logs for
plejd-ble, I can see that something happened after 2023-09-06T15:00.Upon closer inspection, I see that things were working as usual, until I get an
onWriteFailederror (which actually seems to be a debug-message, which is weird in itself).Looking at what follows the
onWriteFailed(included again for completeness) I see another two of the same error followed by a'Not connected' writing to Plejdmessage.I have removed the timestamps to make the logs easier to read. Everything happens within a minute or so.
The above then goes into "the usual" loop where it attempts to reconnect, but the addon never seem to settle in a working state.
I also looked at the logs from the perspective of a reboot of the addon. There are A LOT of rows, but I have truncated the output in a reasonable way (I hope).
My guess would be that there's an hardware issue, but it seems so weird that a bluetooth chip would just stop working. Maybe it's not so far fetched?
Help needed
Any assistance in troubleshooting this further is greately appreciated.