-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Add color functionality to Muller Licht Remote Control #111
Comments
Hi @ASNNetworks, This seems a very interesting controller. In general, I see that the controller sends the same event_id for different actions, which will make its integration not as easy as other controllers. To address this, could you send for each event, the event JSON you see in the Developer Tools? Maybe the event_id is the same, but other attributes might change. For the non-continuous firing events (like the brightness buttons), I will be able to easily integrate since there is an event for each action (press, hold and release) and no firings when holding the button. However, for the continuous firing, the integration will consist of calling the "click" actions and everytime is fired while hold, it will change the value, rather than ControllerX doing it with a "hold" action. I will comment for each button:
For this button, I will be giving only the action for toggle when pressing, so there should be no problems. The only problem could be that if you hold the button, then the light will toggle on and off for every event sent from the controller.
I will need to think on how to make this work, it will depend on how the full event looks like.
I will apply a "click" action to it, instead of a "hold" one as I said before related to continuous firing events.
No problems, easy to integrate with a "click" and "hold" action.
Since they are custom settings, I will leave them without any associated action and user will be able to set their actions through the Regarding the group button, it probably changes a variable in each of the events sent through deCONZ, normally the "endpoint_id" or something like this. Let me know if this is true. Cheers, |
@xaviml thank you for your quick response! So I've fired all events and copy/pasted the JSON's, see below. Also, the group button does not fire off events. Using that button lights up 1 of the 3 leds (or all three together). It doesn;t matter which one is lit up, gives the same events. However, lighting up all three blocks all events entirely. I think we cannot use that button and it has some functionality for Muller Licht's own devices/hub. Power button. Only support press events, no hold or double/triple. Releasing after hold give press event`button_color_ring_press: event: 1002 RGB color ring. The ring consists of multiple areas you can press, but all gave same event. There is press and hold, but both give same event and there is no continous firing. Holding fires event later than press. So works like a delayed press.`button_color_ring_press: event: 6002 `button_color_ring_hold event: 6002 **Edit: To fully test this button ring, I also pressed other sides of the ring. Though I am convinced all sides fire the same event (sadly).Top:** Left: Right: Tint/hue down (left). There is press and hold for continue firing, no separate events for hold and release after hold. Continue firing is not consistent I noticed.`button_tint_down_press: event: 4002 `button_tint_down_hold event: 4002 Tint/hue up (right). There is press and hold for continue firing, no separate events for hold and release after hold. Continue firing is not consistent I noticed.`button_tint_up_press: event: 5002 `button_tint_up_hold event: 5002 Brightness down (left). There is no continuous fire, only press, hold or release after hold.`button_brightness_down_press: event: 3002 `button_brightness_down_hold event: 3001 `button_brightness_down_release event: 3003 Brightness up (right). There is no continuous fire, only press, hold or release after hold.`button_brightness_down_press: event: 2002 `button_brightness_down_hold event: 2001 `button_brightness_down_release event: 2003 Scene buttons. Only support press events, no hold or double/triple. Releasing after hold give press eventbutton_scene_reading_press: event: 7002 `button_scene_sunset_press: event: 8002 `button_scene_party_press: event: 9002 button_scene_night_press: event: 10002 `button_scene_fire_press: event: 11002 `button_scene_heart_press: event: 12002 |
Hi @ASNNetworks, Thanks for the answer. I will let you know when I look at it closely and what I can integrate in ControllerX. Cheers, |
Add deCONZ support for new controller: MLI-404011 (Müller Licht) related to #111
This has been released in ControllerX v3.5.0. You can find the details in here. You will see that some actions were not added since hold actions are not supported for some buttons. |
Hi Xaviml, just received this controller. dresden-elektronik/deconz-rest-plugin#1209 Pressing or holding the colour wheel results in a Move to Color command. The xy values depend on the last values sent and where on the wheel you press or hold. I think the wheel has four different contacts (let's call them North, East, South, West). Each press "moves" the xy values towards the corresponding point on the CIE 1931 colour space: North: (0.3010, 0.1487) - pink-ish, East: (0.7, 0.3) - red, South: (0.3726, 0.5885) - green-ish, and West: (0.1164, 0.3473) Turquoise-ish. A hold "moves" directly to the corresponding point.
|
Hi @ASNNetworks, Could you show me a deCONZ event from HA? So I can see how the angle or XY color is passed through there? Regards, |
i think you mean me:) I'll get it for you shortly. |
Yes, sorry.. haha I got the name of the OP instead of yours.. it was meant to you @hdejongh Thanks, |
ok i did 12 presses: and those correspond with (top to down) :
|
Thanks @hdejongh for the answer. I will reopen this ticket, and change the title. There are some internal changes that need to happen to implement this, so it won't be straight away. Regards, |
how about i send you a remote which you can keep so you can test it your self? |
Hi @hdejongh, Thank you for the offering. I am happy if you are able to test this functionality once I release some beta versions. I have a way of developing this in an easy way and I am confident in developing it without the need of the controller itself. Thanks again and very kind of you :) |
np i would love to test! |
Hi @hdejongh, ControllerX v4.4.0b0 will be released in 5-10 minutes from now. It ships this functionality. It reads the deconz event to get the xy color when pressing the color wheel (6002 event). You can toggle "Show beta" in HACS to get this release. Regards, |
Did you create a default mapping or should i do that? cause nothing happens when i press the ring... |
I did add it to the default mapping. Did you restart AppDaemon addon after updating? |
Check AppDaemon logs for errors or warning if possible as well. Thank you :) |
restarted HA, no joy for the ring. |
What do you see in the AppDaemon logs when pressing the ring? |
there are no appdaemon logs:) |
log: that's probably wrong... |
How did you install AppDaemon? Was it through the addon? If so, you can go to the addon and click to the "Logs" tab you will see on the top (if you are in a computer). You will see a "refresh" button that you can use to refresh the logs. |
stupid me doing 2 things at the same time. I actually looked already here a couple of days ago while using a debug log feature in our app:). I added the log_level Woonkamer_Muller: 2021-01-05 20:24:13.027549 DEBUG Woonkamer_Muller: Calling listen_event for Woonkamer_Muller |
No worries, I assumed you knew where to find the logs, my fault. Thank you for adding the debug log as well. I see that it does not recognize the 6002 event. When initializing AppDaemon, do you see something like:
Regards, |
I just saw your message:
You need to restart AppDaemon addon, not Home Assistant. |
ok it works but if you press multiple times on the same spot the color keeps changing... so its not instant... |
better explanation: first i set the light with my regular hue dimmer on orange: then i press multiple times on the muller remote to the right (red) 2021-01-05 20:53:50.632367 INFO Woonkamer_Muller: 🎮 Button event triggered: so the last 3 presses its red |
Thank you for reporting back with logs. I see that the xy_color is not consistent even when pressing right (red) multiple times. Could you check in "Developer Tools > Events", then start listening for |
i already did that this afternoon. in my initial post: #111 (comment) ill try multiple times again cause i think eventually it will stay the same color |
ok tried it again, if you keep pressing the same spot multiple times then eventually it stops changing the xy_color. but that can take over. if i go from bottom to top it will take at least 20 presses to reach the final (correct) color... |
I missed that, sorry. I see now that the only consistent one is when clicking up multiple times, but for the rest, the xy color seems to be random. The only thing I did in ControllerX was to read that xy color and use light.on service by passing |
not really random its always connected the angle.. |
Oh!!! it needs to be a long press! if you do a long press its working fine. short press will just add "10 degrees" and keep doing that until you reach the right color |
Which event does it send? just the 6002 one time? You can see that in the AppDaemon logs |
yes only one time |
So is everything working fine? Let me know if you find anything not working properly. I will release the v4.4.0 in a couple of days. |
yes its working fine, but the remote isn't very high quality... so its kinda hard to select the right color. |
Color ring functionality has been added to ControllerX v4.4.0. |
New Device Support
Device Information
Device Model: Tint Remote Control
Device Description: Remote Control
Device Manufacturer: Muller Licht
Integrations
If possible, provide the event mappings for the different actions that can be performed on the controller. Specify the integration.
If you can provide mappings for multiple integrations, copy the section below as many times as needed.
Integration: deconz
Actions
Power button. There is press and release after hold, not hold event.
RGB color ring. The ring consists of multiple areas you can press, but all gave same event. There is press and hold, but both give same event and there is no continous firing. Holding fires event later than press. So works like a delayed press.
Tint/hue down (left). There is press and hold for continue firing, no separate events for hold and release after hold. Continue firing is not consistent I noticed.
Tint/hue up (right). There is press and hold for continue firing, no separate events for hold and release after hold. Continue firing is not consistent I noticed.
Brightness down (left). There is no continuous fire, only press, hold or release after hold.
Brightness up (right). There is no continuous fire, only press, hold or release after hold.
Scene buttons. Only support press events, no hold or double/triple.
button_scene_reading_press
: event: 7002button_scene_night_press
: event: 10002Notes
I notice that the hold function of events 4002 and 5002 have some kind of internal counter or bug. For instance: if I continue holding 4002, it wil stop at a point. If I try again, it will not continue fire. If I then press or hold 5002, for 2 or more times events (s not just once) I can again continue firing 4002, until it reaches some kind of limit and then again.
Also the button at the buttom (group button) doesn't work. It also doesn't change the behaviour of the buttons or events (sadly). It has 4 toggles (1, 2, 3 and ALL). BUT if you select ALL, then the remote does not work (nog events fired)
The text was updated successfully, but these errors were encountered: