-
Notifications
You must be signed in to change notification settings - Fork 14
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 Deprecation warnings #32
Comments
Thanks for letting me know I hadn't had a chance to update to 2023.8 yet. Looks like I'll need to make a slight change to the MQTT auto-discovery code. I'll work on getting an updated version out at some point over the next few days. |
I've made the code updates and verified they are working on my end. Can someone else test the (discoveryUpdates)[https://github.com/1mckenna/esp32_iGrill/tree/discoveryUpdates] branch and verify it looks good on your end as well? |
@1mckenna this looks like its working as its gone off the repair list on HA. Thank you |
I'll update my device today. It's been a busy week. EDIT: I failed at updating my device yesterday, aiming for today again :| |
I have updated my device as well, and after a restart of HomeAssistant, that warning has been cleared. I see probe temps and battery levels and all the goodies. |
well, of course, as soon as I send that message, it starts behaving itself. I see two probe temperatures now as soon as I plug them in. I must've caught it in an upset state or something. |
Awesome thanks for testing! I'll go ahead and push out these changes to the main branch shortly. |
Code has been pushed to main |
I updated to Homeassistant 2023.8.0 today, and this warning showed up. I'm not sure yet if it's a problem I can just fix, or if it should be brought up here, but I'll go ahead and start this issue and update it if I figure something out, or if it gets fixed here :)
HomeAssistant developers blog link
Thanks!
The text was updated successfully, but these errors were encountered: