-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
ControllerX with PTM215XLightController and multiple independent lights #699
Comments
I'm still having an issue. I studied the examples, and based on the examples, I tried the following code as well (use mapping instead of merge mapping, and "quote" the on/off attributes.
Press_1/Press_2 appear to work ok. But Press_3/Press_4 don't seem to do anything. When looking at the logs, in the appdaemon "main" log, things look OK for both sets of buttons
But I see these messages in the "error" log. Messages seem to show an error for both office_cabinet and office_dimmer, but office_light does appear to work while office_cabinet doesn't.
Both paddles seem to generate the same error/warning, but one of them actually works, while the other doesn't switch the light on/off. One other thing to note is that the light that works is controlled by z2m (hue bulbs), while the other is a generic light controlled by HA (via ISY994 integration). Sean |
@xaviml Some more progress...
Calling the light service directly instead of defining the attributes seemed to allow me to get press_3/press_4 to work correctly. I'm not sure why it didn't work without this. The warnings about missing attributes in the prior tests went away for these presses. However, I still note the warnings on press_1/press_2. Strangely, they seem to refer to direction and mode "attributes" that are missing. So, I tried defining them, and then got a different message.
Here are the "errors". Note the difference between press_1/press_2. Press_2 complains that some attributes are not provided (since I commented them out), while press_1 says that "on" is not a valid option to the "click" action, even though it complained about it missing in a prior message
Thanks, Sean |
Question
Hi Xavi,
I've got this PTM215XL light controller, currently configured with 2 paddles. This provides the 4 buttons (press_1, press_2, press_3 and press_4 and their corresponding release events). I've successfully configured the switch when controlling a single light (which we've previously discussed). However, now I'm trying something different. I'd like press_1/press_2 to control 1 set of HUE light bulbs, and press_2/press_3 to control a different (non Hue, non zigbee2mqtt) light. Based on the examples, I thought the following would work
However, the result was that press_1/press_2 turned on/off both lights, and press_3/press_4 did dim/bright for both lights.
Do you have any recommendations for achieving my goal?
I'm on the latest of Home Assistant Core 2023.2.1, AppDaemon 0.11.0, and ControllerX 4.25.0.
Thanks,
Sean
Add here your question.
Additional information
z2m | deconz | zha
AppDaemon app configuration
Logs
Additional Context
Add any other context or screenshots about the question here.
The text was updated successfully, but these errors were encountered: