Ember integration not working in Home Assistant OS #32
Comments
|
I'm able to replicate the exact same behavior on a Raspberry Pi 4 with the following system details:
Also followed all troubleshooting in readme to no avail, as well as uninstall/reinstall component and ran bluetoothctl. The device appears to be initially detected when instantiating the integration, as the configuration page with the MAC address and Celsius/Fahrenheit selector does appear. However, hitting submit results in a 'this integration has been successfully configured' message, after which it keeps getting stuck in this 'Failed to Connect / Operation already in progress' loop without generating any entities. |
|
Oh ok, thank you very much for your testing and confirming the issue. |
|
Hey @sopelj ; Deleted previous comment, sorry; it was a long day at work and the mug was inactive, so deleted errors were legit because it couldn't be detected. The following output is between 'failed to connect' errors after I actively re-paired the mug before it turned off: fwiw, I am aware the device addresses aren't obfuscated this round; this is my second comment attempt, I'm lazy, and it's a coffee mug not a server lol |
|
Can also confirm same issue - HAOS Intel NUC latest 2023.6. I have tried with stock bluetooth, dongle and espproxies on and off. |
|
Oh very interesting. Thanks for testing. Yeah, not much to worry with not masking the MAC address. That's very interesting. There is specifically a fix for a Bluetooth on both Intel NUC and Raspberry Pis in Home Assistant OS 10.3. Perhaps it introduced a regression? There are a couple issues open with Bluetooth on their github so it may be an OS error. Have you tried with a Bluetooth Proxy and without the Bluetooth adapter enabled? Do you have any related errors in the "Host" or "Supervisor" logs? |
|
Hi @sopelj I don't currently have any existing bluetooth proxy infrastructure set up, but I can try digging out an esp32 for testing. |
Oh ok, thank you very much! |
Hi again! It seems I misinformed you in my previous post, ESP proxies where/are not active on my installation, I just thought that they were. But they will for some reason not show up, allthough I have re-flashed them using serial as per documentation. But that is a separate issue/topic. So; only with Intel NUC bluetooth + StarTech Bluetooth dongle then. And it is still not working.. :) My bet is also on an Hass OS issue. |
|
Some time ago I tested this integration with my NUC and could not connect to the Mug either. But the BT module from the NUC is not good anyway and constantly found / invented random devices. Therefore, I have then given up at that time. |
Awesome! Thanks for testing and the update! Home Assistant OS 10.4 was released a couple weeks ago, perhaps that's what fixed it. Is that what you are running now? |
|
I actually had version 10.4 running. But to test it again, I just downgraded to 10.3 and was able to add the Ember Mug without any problems. So the Bluetooth proxies seem to have been the solution here. |
Oh, awesome! Thanks for your thorough testing! Perhaps it cleared something up just by upgrading? Is anyone still having troubles since upgrading to 10.4? |
|
Hi! Yes, still having problems. This is what I have done and tested; Deactivated Intel NUC's BT module inside BIOS. With this setup, no ember mugs are even discoverable. Both in 10.3 and 10.4. Now, when adding some ESP BT Proxies, they immediately become discoverable by HA. However, when trying to add them, they time out on either initializing, or never even get that far. 
I can try to provide logs on a new adding session (it takes some time from removing them before they become discoverable again also..). Which ones do you preferable need? From ESP BT module, or HASS? |
Hi! Sorry, I did not see your message. With either the Bluetooth Dongle or the Proxies does it detect your mug in pairing mode? Using both of the same time can cause frequent disconnects, but should function. That's very strange. I have never seen that error before. Yes, if you could perhaps try removing the entities related to the integration and trying again with more verbose logging enable that would be much appreciated. Which log depends on where the problem is. If there is a problem with the proxies you may find some information that could be helpful, but the logs related to this integration will be in Home Assistant's log. Also, worth noting that Home Assistant OS 10.5 is in beta right now. I don't see any specific fixes for the NUC though. But sometimes just kernel upgrades is enough. |
|
10.5 did not fix it. I will try to add verbose logging on full reset of mugs. Just a question in the mean time - it should work fine with two mugs, no? Also, answering your questions; Bluetooth dongle is now my only device in the Bluetooth integration. Once in this limbo above, it does not recognize them anymore. What seem to work (allthough not 100% reproducable) is to delete all Ember mug integration devices, factory reset mugs, and hardware restart home assistant. |
|
Doing the reset procedue above, I get this: No logs in either ESP proxies, so I am guessing it tries through the main dongle (on board chip disabled in BIOS). |
|
And in the odd case that it goes past the first add screen, I make them enter pairing mode (blue blinking) but only get these errors:
|
|
Now one of them suddenly connected, and after triggering "bluetoothctl" in terminal the other one got connected as well (this could be a concidence). Given that I have been able to connect them for a few days before they become unavailable again, I assume this will be a temporarily condition. By the way, my bluetoothctl prints like 50 lines a second repeating, is this normal behavior? I recall it being rather static before. |
Hi! Sorry, I've been away for a little bit. Depending on your setup and device sometimes, when using Bluetooth dongles instead of the ESPHome proxies, opening Do they remain unavailable and do you have any errors? Sometimes they will be unavailable when the battery gets very low, but unless the battery dies completely they should automatically reconnect when charged. I cannot be sure, not knowing what the output is, but given you had no devices before, it's normal that it is more dynamic now. 50 lines a second does seem like a lot. It does many queries to the mug to fetch the different attributes. I think that's like 10 or so every 30 seconds. Given you have two mugs, it may be triggering more often as the second may disconnect the first and vise versa. |
|
Have any of you had any luck with the above suggestions? |
|
Hi! I have had no issues since a few months back - unsure what made it work, probably a combination of ESPhome BT proxies being improved (I am solely using these), frequent reboots of said ESPs as they would drop connections after a while, as well as improvements on other BT integrations that may or may not have caused troubles with BT in general (particularly AirThings BLE) :) |
|
That's great! They have made great improvements with proxies, they wen't from barely working to being the recommended method in a few iterations. Thanks for the update. I'll close this issue, but feel free to create one if future if there are other prtoblems |
Home Assistant Version (eg. 2023.6.2):
Ember Mug Component Version (eg. 0.7.1):
Which device(s) are you using for Bluetooth (e.g. Bluetooth Dongle / ESPHome Proxy):
Intel NUC built in bluetooth
Description
Describe what you were trying to get done.
Trying to install ember mug integration after moving from Ubuntu 22.04 LTS to Home Assistant OS version 10.3
What I Did
I tried re-installing the inetgration
I tried running running command bluetoth ctl from terminal
Paste the command(s) you ran and the output.
Logs / Errors
Logger: ember_mug.mug
Source: custom_components/ember_mug/coordinator.py:62
Integration: Ember Mug (documentation, issues)
First occurred: June 22, 2023 at 7:40:09 PM (855 occurrences)
Last logged: 9:24:11 AM
xxxxxx: Ember Ceramic Mug: Failed to connect to the mug: xxxxx - xxxxxx: Failed to connect:
xxxxxx: Ember Ceramic Mug: Failed to connect to the mug: xxxxxx - xxxxxx: Failed to connect: [org.bluez.Error.Failed] Operation already in progress
The text was updated successfully, but these errors were encountered: