[FEATURE REQUEST] Support for color/color_temp values from mqtt #236
Comments
|
Hi @ashp8i, The feature to use the Regarding the action groups, you can use example_app:
module: controllerx
class: LightController
controller: zigbee2mqtt/Ashish-Full-Remote/action
integration:
name: mqtt
action_group: [16388]
light: light.ashish_room_lamp
mapping:
"on": toggle
"off": toggle
brightness_down_click: click_brightness_down
brightness_down_hold: hold_brightness_down
brightness_down_release: release
brightness_up_click: click_brightness_up
brightness_up_hold: hold_brightness_up
brightness_up_release: release
color_temperature: *(color_temperature_value)
color: *(color_xy_value)
I will fix this, so you can add just the action group individually without a list if needed. In your example, if the controller fires an action group different from 16388, it will not fire the action that carries with it. So the mapping will just work if the action group is 16388. Hope it helps, and I will leave this request open to fix/add this feature request. Also, could you show me the mqtt messages where the xy color and color temp is shown? Thanks, |
|
Hi Xavi, Thanks for your response, it's the Müller-Licht 404010 and I also have a Aurora AU-A1ZBR1GW and AU-A1ZBR2GW which also output color values |
|
…_from_controller predefined actions related to #236
|
Hi @ashp8i, The support for this controller has been added to a pre-release v4.6.0b0. Could you please confirm that the support for Müller-Licht 404010 works as expected for z2m? I added the following predefined actions:
Thank you, |
|
Also, if you want the Aurora devices to be supported by ControllerX, you can create a new ticket with the specification of the mapping in here. Cheers, |
|
Hi Xavi, Thanks for your hard work, code looks to be doing the right thing but not quite there yet let me provide you with some logs, also could you help me to set highest output in logs, so we can get all the debugging info needed: - apps.yaml also can't seem to figure out what is wrong with action groups, other than that thanks for your help hope I can help with debugging let me know what you require from my side, so I can assist with the feature request Regards, |
|
Hi @ashp8i, You can activate the debugging logs by placing Also, the problem is that you set up the mqtt integration rather than the z2m one. So with the current config your config is listening only to bedfullremote1:
module: controllerx
# class: LightController
class: MLI404011LightController
controller: Ashish-Full-Remote
integration:
name: z2m
listen_to: mqtt
action_group: [16388]
light: light.ashish_test_lamp
mapping:
"on": toggle
"off": toggle
brightness_down_click: click_brightness_down
brightness_down_hold: hold_brightness_down
brightness_down_release: release
brightness_up_click: click_brightness_up
brightness_up_hold: hold_brightness_up
brightness_up_release: release
color_temp: colortemp_from_controller
color_wheel: xycolor_from_controllerAnd since you are now using the bedfullremote1:
module: controllerx
class: MLI404011LightController
controller: Ashish-Full-Remote
integration:
name: z2m
listen_to: mqtt
action_group: 16388
light: light.ashish_test_lampLet me know if this works for you. Regards, |
|
Hi Xavi, Many Thanks for getting this working, the colour wheel works as expected also action groups now work discretely so all good few gotchas, cannot seem to use color_temp control and cannot work out how to control all lights when all three LED's lit this is much better as I'm struggling to implement this in node-red got stuck at passing color values from z2m to tasmota Many Thanks, |
|
Apologies, figured out color_temp might not be mapped in the default template so this works now: - Regards, |
|
also noticed a brightness button issue the default mapping brightness_up_hold seems to be dimming overidding with seems to do the trick Many Thanks, |
|
Hi @ashp8i,
I will add this to the default mapping, thanks!
Indeed, you are right, I mapped to dim, rather than bright up, thank you for reporting it back :) Both changes will be reflected in the next stable release. Regards, |
|
This feature has been added to ControllerX v4.6.0 |
|
@xaviml
|
|
Hi @CorePoint Did you set up MQTT broker in appdaemon.yaml? You can see here how to do it in the Z2M section and MQTT one. Regards, |
|
@xaviml |
|
Hi @CorePoint, You did well, namespace should be "mqtt" so ControllerX can read from mqtt. The logs you showed are the ones including when you are pressing the controller? Could you please restart AppDaemon and share the logs when AppDaemon initializes? It should show in there the connection to MQTT. Additionally, could you share the z2m logs when you press the controller? Finally, you said that when not listening to mqtt, it works, right? Regards, |
Seems like the MQTT connection was successful. Yes it works when not listening to mqtt, but if I understood that right to use the color wheel it has to listen directly to mqtt right? edit: Forgot to answer one of your questions. When I press a button nothing appears in the appdeamon log. |
|
Hi @CorePoint, Thank you for your answer. I see in the configuration you share earlier that the Regards, |
|
@xaviml |
|
Hi @CorePoint, Interesting.. could you install ControllerX v4.6.0 and see if it works with that version. I don't think that will do much, but at least we will make sure that no breaking changes were added. You have everything well configured, so I don't have anything else left to recommend you for now. Make sure to restart AppDaemon after the downgrade. Regards, |
|
@xaviml Thank you anyway for your quick and friendly answers! |
|
No worries @CorePoint . Glad to help. I will investigate later the logs again on the computer and see if I missed something. If you have more questions, I prefer that you open a new ticket, this way is less likely I forget about it. Cheers, |
|
@xaviml Greetings |
|
Hi @CorePoint, I have checked the logs and compared them with mine, and I see everything the same as you do.. However, I come up with some questions for you to answer, and see if there are any differences between your setup and mine:
Regards, |
|
Sure @xaviml Yes config is exactly in that location. The Symfonisk controller is working, I'm using z2m with it, without the |
|
Hi @CorePoint, Thanks for the input. Everything is exactly the same as my setup, and I am not able to spot any differences. There is one more thing that we could try, and I believe that is the problem... I bet your configuration looks like: Tint:
module: controllerx
class: MLI404011LightController
controller: 0x00158d000361cf51
integration:
name: z2m
listen_to: mqtt
light: light.desk
log_level: DEBUGI know you shared this before with me, but the key in here is the Tint:
module: controllerx
class: MLI404011LightController
controller: "0x00158d000361cf51"
integration:
name: z2m
listen_to: mqtt
light: light.desk
log_level: DEBUGNot sure if this is the problem since you didn't share this exact configuration, but that could explain why no messages are shown in the logs, and the controller does not work. Regards, |
|
@xaviml Thank you again for your help and patience! |
|
Glad you got it working! I normally rename my devices, so I have never encountered this before, but it is good to know for the future since the default device id in z2m is a hexadecimal number. |
|
That's good that this problem surfaced something that could prevent future problems. |
Feature Request
I would like to be able to map color / color_temp values published from mqtt, also can you confirm if action groups from mqtt are supported
using the following yaml:
The text was updated successfully, but these errors were encountered: