-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Orvibo Smart Sockets Config YAML No Longer Working #106923
Comments
The problem seems to be with the underlying Either copy attached files to: Or to manually apply the patch yourself: Modify manifest.json to include a version (
Modify switch.py to force a string type for the MAC Address: Hopefully someone can fix this properly for us? |
The issue is that the mac isn't a string anymore and this check is failing. https://github.com/happyleavesaoc/python-orvibo/blob/master/orvibo/s20.py#L139-L142 |
* Bump python-orvibo version Fixes #106923 * Add version number * Remove version * Bump python-orvibo version
* Bump python-orvibo version Fixes #106923 * Add version number * Remove version * Bump python-orvibo version
The problem
I have lost access to my Orvibo smart sockets since the 28th December which was also the day I installed the first beta of 2024.1.0b5
The error in the logs (full log included further down):
I tried to change the format of the YAML, adding quotes around the MAC address, changing the file encoding from UTF8 but nothing has made a difference.
The latest beta 2024.1.0b5 still has this issue.
What version of Home Assistant Core has the issue?
core-2024.1.0b5
What was the last working version of Home Assistant Core?
core-2022.12.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Orvibo
Link to integration documentation on our website
https://www.home-assistant.io/integrations/orvibo/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: