Skip to content
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

Home assistant - mug integrates, but can't write to it. #54

Open
vbrown202 opened this issue Apr 13, 2024 · 4 comments
Open

Home assistant - mug integrates, but can't write to it. #54

vbrown202 opened this issue Apr 13, 2024 · 4 comments

Comments

@vbrown202
Copy link

  • Home Assistant Version (2024.43):
  • Ember Mug Component Version firmware 352, hardware 10)
  • Which device(s) are you using for Bluetooth ( ESPHome Proxy):

Description

The integration is fine and I can see all the entities and they are correct.

I tried reinstalling the integration, also deleting my proxy data and reinstalling.

Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

Logs / Errors

I cannot change any (i.e. temperature) because I get this error message Failed to call service number/set_value. Unable to write to mug I get this error if I try to change to latte/coffee Failed to call service select/select_option. Bluetooth GATT Error address=F5:03:AB:05:4D:B3 handle=18 error=3 description=Write not permitted)

@sopelj
Copy link
Owner

sopelj commented Apr 14, 2024

Hey, that's weird. Do you have this issue with other attributes? (ie. LED colour, device name, temperature unit, etc.) What device are you using? Has your device been setup with the app?

@vbrown202
Copy link
Author

vbrown202 commented Apr 14, 2024 via email

@vbrown202
Copy link
Author

vbrown202 commented Apr 15, 2024 via email

@sopelj
Copy link
Owner

sopelj commented Apr 26, 2024

Hey, no worries. I'm glad you got it working! Don't need to delete the issue, but we can close it if it has resolved itself. It may have been the update that fixed it. I haven't been able to test many different versions, so I'm not sure if older versions could cause problems. If you are using the app at the same time it can be connection issues if the phone and the RPi are both using the mug at the same time. So, best to disable the device on the phone unless updating or something if you want to use it with the integration. It is a very finicky device and it doesn't like to share connections. 😅

Yeah, if the proxy is too far away it should stick with the closest. If you do want to use the proxy, just be sure you put the device into pairing mode near it at least once so it pairs with it. The mug will only work with a device it has been paired with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants