Open vbrown202 opened 5 months ago
sopelj
commented
5 months ago 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
commented
5 months ago I have a raspberry pi 4. All other integrations I can both read and write. ALL of the items on my mug I can see beautifully but get a write error on all.I integrated from HACS with no issues. I've had the mug for 3+ years and have been using the app without issue.My life is mostly user error, so if you can imagine a setting I may have messed up, let me know. Here's a screenshotThe mug is seen by HA. What else do you need to diagnose? Thank you so much for your time.VbOn Apr 14, 2024 9:34 AM, Jesse Sopel @.***> wrote: 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?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
vbrown202
commented
5 months ago I cleared cache and data on phone. Signed onto app with Google rather than email. Was surprised by a mug update. Updated mug. I actually think the mug is using my pi4's bluetooth cause my proxy is in the basement. Works fine. Had the epiphany early this morning, sorry I did not have it before I posted on git. Would you like me to delete it?VbOn Apr 14, 2024 10:13 AM, Valerie @.> wrote:I have a raspberry pi 4. All other integrations I can both read and write. ALL of the items on my mug I can see beautifully but get a write error on all.I integrated from HACS with no issues. I've had the mug for 3+ years and have been using the app without issue.My life is mostly user error, so if you can imagine a setting I may have messed up, let me know. Here's a screenshotThe mug is seen by HA. What else do you need to diagnose? Thank you so much for your time.VbOn Apr 14, 2024 9:34 AM, Jesse Sopel @.> wrote: 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?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
sopelj
commented
4 months ago 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.
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.
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)