-
-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
Control 4 lights no longer with C4 3.3 #73353
Comments
control4 documentation |
Hey there @lawtancool, mind taking a look at this issue as it has been labeled with an integration ( |
Can confirm same issue have rolled back my Control4 to 3.2.4 no issues. |
Same-ish issue. For me, after the update to OS3.3, the valid user no longer authenticates in the HA integration. Gives me an auth error but I am able to log onto the C4 system without any issues using the same credentials. Because of this, the entire integration is busted. |
Instead of rolling back I'm now using the Control4 2way web driver |
Same issue since control4 3.3. Can someone point out where to find roll back info? |
for anyone looking, it requires Control4 dealer access at control4. A utility called "C4 Device Image Updater V2" |
Thanks for the hint. If you have a jailbroken controller, then you are out of luck? |
It's not as easy to use but the 2way webdriver is written by the same person who made this integration and it still works to turn lights on and off and set/get brightness levels. Probably quite a bit easier than rolling back C4 unless you have a friendly dealer to help you. |
I was having the same issue as everyone else in this thread. I went digging around to see if lawtancool was showing any signs of activity and came across his hacs-enabled development repo. It hasn't been updated since January, but just for fun, I tried installing it, figuring maybe I'd at least get alarm and door/window sensor support out of it. But what do you know, as soon as I installed it, my lights started working again! I don't know if there's anything light-related that's different from the HA core version, so it may be that just deleting my existing C4 integration and replacing it is what fixed it. I'd be curious to hear if any folks have tried that with the Core integration. But either way, my lights are now working again without resorting to the 2way web driver. |
Here's the repo in question, btw: https://github.com/lawtancool/hass-control4 |
Just had a read of the info on that Repo. Interesting part of the disclaimer.
Decided to install and it worked even without deleting the Core integration. Thanks @bdonohoe Did you get the alarm or any sensors working with it? |
Sadly, no. No sensors or the alarm showed up as entities. Just the same set of lights showed up that I had before. Happy to have that fixed, but sad that no other devices come through yet. |
So for now the best solution to this issue is as @bdonohoe said above:
Install that repo from HACS either over the previous integration or instead of it. All the previous lights come back as they were before. The 2way web driver allows you to read the status of a variety of other things - so I have used it to create a display of the status of my alarm - but doesn't work as well with the lights as the HACS integration. |
Hi everyone, As some of you have noticed, the integration at https://github.com/lawtancool/hass-control4 works with newer C4 versions. This is because it uses a new Websockets communication protocol with Control4, and it seems that C4 3.3 has limited the REST API that was used by the old integration. (actually, the new Websockets integration does call the REST API once during first setup and every time the Websocket is disconnected/reconnected, so I'm not sure how that works...) If this works, it is the solution I would recommend for now. Unfortunately, I do not have the ability or time to jailbreak my C4 and update it to the latest OS version to test. Perhaps one day I will find some free time to get the Websockets changes merged into the official HA integration, but it requires quite a bit of refactoring. |
The solution is a life saver and works great for lights. Lesson learned though. |
Maybe i can help, the change that Control 4 made in 3.3.0 is they changed the variable LIGHT_LEVEL with Brightness Percent so i guess that if you change this in the code it should work. in the pre 3.3.0 this variable was LIGHT_LEVEL on V2 lights in control4. On some V1 lights witch proxy was not updated to the latest are still LIGHT_LEVEL and those work fine in Home Assistant i can dim them unlike the new one with Brightness Percentage that i can only turn them on /off best regards …. never mind i tried the custom integration and it works better than the official one :) |
I had to change my Control4 account password and obviously I lost the connection... |
For what it's worth, the fact the lights don't show dimming support appears to be a bug downstream of the Control4 integration. Because when creating automations, you can set the brightness percentage as a device action, and it works! So the fact the rest of light controls are not registering as dimming-supported is some other bug unrelated to the C4 integration protocol. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem
Control 4 lights no longer working in HA since C4 update to version 3.3. Get two errors in the logs:
Unexpected error fetching light data: Empty response recieved from Director! The variable LIGHT_LEVEL doesn't seem to exist for any items.
Error while setting up control4 platform for light
What version of Home Assistant Core has the issue?
2022.6.5
What was the last working version of Home Assistant Core?
2022.6.5
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Control 4
Link to integration documentation on our website
https://www.home-assistant.io/integrations/control4
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: