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
Lutron failure in 0.84.1 #19273
Comments
Please fill out the template. |
Was in process, thanks. |
needs to change to
|
Blame #18650 |
I'm new to this process. Is there anything else I need to do to make sure this gets seen? |
Was already seen. |
any workaround for this currently? All ~90 of my lutron lights are down :( maybe downgrade hass? |
If you take the file from the linked commit https://github.com/marchingphoenix/home-assistant/commit/9ba07029738bbae1329e1723af69a79bfb7c3e29, add it to |
After applying this fix, the issue remains on my system as can be seen below:
|
The stacktrace still looks like the old code. |
had a mistake in the commit that was sent, use the latest file from the pr: |
The latest file works. Thanks for the fix |
* home-assistant#19273: fix call to super() * home-assistant#19273: adjust to python3 standards. * home-assistant#19273: remove bad test.
Home Assistant release with the issue: 0.84.1
Last working Home Assistant release (if known): 0.83.3
Operating environment (Hass.io/Docker/Windows/etc.): RPi3, Hass.io
Component/platform: https://www.home-assistant.io/components/lutron/
Description of problem:
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
Lutron RA2 has a static assigned IP.
The text was updated successfully, but these errors were encountered: