-
Notifications
You must be signed in to change notification settings - Fork 4
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
New ember mug does not connect #39
Comments
Hey, thank you very much for all this information. Much appreciated! |
Yes, Home Assistant OS 11.1, running on a Home Assistant Blue. Thanks for the quick response, I'll keep an eye on both issues and don't hesitate to request more info. Once v12 is available as a stable release I'll upgrade and try again. |
Oh interesting, those look like nice little machines. Thanks to you too! Yeah, I tried the 11.2rc but it doesn't seem to change anything. Maybe the 12 will. |
Hi! Out of curiosity, does removing the device via bluetoothctl, factory resetting the mug and reloading the integration work for you? |
Hey! That's a bit strange. It looks like it can't perform the initial connection to the device. It definitely shouldn't display a stack trace though. Is your device a Mug or a cup? It says Mug, but in the error it seems to say "cup27364825158". Are you using built-in Bluetooth, a dongle (a supported one?) or a proxy? Also, which version of this integration are you using? It might be worth tring the beta of 0.9.0. Did you try any of the troubleshooting steps? Thanks! |
Not sure how to find that out, it say ember mug when it finds it. I tried renaming it to something else, hence the name cup27364825158. Tried two bt adapters, inbuilt as well as one of the recommended by HA CSR8510. No proxy. Using 0.9.0 beta-2. Will try 0.8.0 and let you know, i think i tried it before with no luck |
Oh OK. Well, it's just the type of device you have. It should say on the box. If it has a handle it's mug. Hmm, OK. Well, proxies are definitely more reliable, built-in ones can be hit or miss, but at least one should work. Ideally just one at a time though or you might get connection issues as they could be fighting each other. If you could try enabling debug logging you may get a more helpful message in the log. Also, the troubleshooting steps like opening bluetoothctl and such and moving the device close to the adapter may help as well. |
I've got the same issue with the mug I got my wife for Christmas. It is a Mug 2. I am using a BT dongle, running the latest versions of HAOS, supervisor, core, etc. I am looking to get a ESPHome BT relay soon.. curious if that will work better, like what you said previously. |
@orywig if you are comfortable accessing the command line you can try opening |
Description
I've been using this integration successfully for a while now. Unfortunately, my Ember Mug died, so after looking at the market I got a new one (Ember Mug 2) since this is the (only?) coffee mug that integrates with HA. (so thank you for this integration!)
Unfortunately, I can't seem to get my new mug working, after repeated tries and debugging steps.
What I Did
Starting from a restart with the ember mug not added yet, I see the newly discovered mug. I tap configure, and get to the configuration screen where I change the unit to F, and then Submit. This takes a while, and then eventually reports "Success!". However, the success dialog does not show any new devices found which differs from the expected experience.
At this point, the Ember integration is listed, but it just keeps erroring repeatedly. I've tried putting the device into pairing mode, but that doesn't help. (I don't think pairing mode should be needed since I can confirm with bluetoothctl that the device is actually paired.
Logs / Errors
First, here's some out from bluetoothctl that shows the device as paired:
And here's logging from Home Assistant. I've trimmed the log to just keep relevant lines from Ember.
This issue is probably the same as some of the other issues, but I wanted to create a new issue just in case it is different. Please dupe if appropriate. Happy to provide any additional information on request. I'm just out of ideas on what to try next.
The text was updated successfully, but these errors were encountered: