-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot turn on Delonghi Primadonna anymore #89
Comments
What Bluetooth adapter are you using? How many other Bluetooth devices are you accessing in HA? Are you using Bluetooth Proxies? Is the coffee machine far away from your HA device? |
I have the same issue as @mannipulator with the same machine (Delonghi Primadonna). This integration is the only one using bluetooth on my home assistant system. The machine is aprox. 6m away from my bluetooth adapter which worked fine with this integration for the last months. I am using a TP Link UB400 Nano bluetooth dongle. EDIT: It seeems like the entity ID changed! Setting it to "button.kaffeemaschine_turn_on" (kaffeemaschine is the name of the device as I set it up in the integration) instead of the old "button.turn_on_ecam" brought everything back to work! |
In my case, the problem has probably solved itself and everything is working as usual again. Nevertheless, here is some more information about my setup: HassOS on RPi4 |
Ok it is back again here is the log: Logger: homeassistant Error doing job: Task exception was never retrieved |
Is the app working for you? Not being able to find the MAC address at all suggests that the coffee machine itself is not broadcasting or not within range of your Bluetooth adapter. |
No, it stopped to work now completely, I cannot get any connection to the device. |
Hello, thanks for this great integration, I love it !
Since the last release my Primadonna stopped working, which means I cannot turn it on by Home Assistant any more.
The status, like descaling, is it running or not seems to work, these entities update if I turn the Primadonna on manually.
In the protocols I have after each try to turn it on 2 logs, a warning and and error:
this is the warning log:
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.delonghi_primadonna.device
Source: custom_components/delonghi_primadonna/device.py:355
Integration: DeLonghi BLE (documentation, issues)
First occurred: 7. November 2023 um 22:10:00 (9 occurrences)
Last logged: 07:34:47
BleakDBusError: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Unlikely Error)
BleakDBusError: [org.bluez.Error.Failed] Operation already in progress
and this is the error-log:
Logger: homeassistant
Source: components/bluetooth/wrappers.py:292
First occurred: 07:33:17 (9 occurrences)
Last logged: 07:34:47
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/delonghi_primadonna/device.py", line 294, in power_on
await self.send_command(BYTES_POWER)
File "/config/custom_components/delonghi_primadonna/device.py", line 377, in send_command
await self._connect()
File "/config/custom_components/delonghi_primadonna/device.py", line 222, in _connect
raise error
File "/config/custom_components/delonghi_primadonna/device.py", line 216, in _connect
await self._client.connect()
File "/usr/src/homeassistant/homeassistant/components/bluetooth/wrappers.py", line 292, in connect
connected = await super().connect(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/bleak/init.py", line 605, in connect
return await self._backend.connect(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 249, in connect
assert_reply(reply)
File "/usr/local/lib/python3.11/site-packages/bleak/backends/bluezdbus/utils.py", line 22, in assert_reply
raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.Failed] br-connection-canceled
I hope this helps ;)
The text was updated successfully, but these errors were encountered: