I am afraid that is yet not possible, but it something in my list to do. Right now ControllerX is able to read from MQTT directly, but the device communication is all done through HA call services.
I see then. You want that next day when you turn on the light, you want scene A to be activated back again, rather than the scene C, correct?
If so, my recommendation would be to solve this with a HA automation that changes the input_select to C after X seconds/minutes of having changed.
I said to Scene C (the last one you put in the list) because when pressing the on button the first thing that the ControllerX config does is to change the input_select to the next option.
I havenāt changed the firmware as I donāt have a Hue hub and for the same reason updating is likely to be an issue. ( as it could potentially be for many others as the beauty of zigbee and HA is not having to own multiple hubs ).
I did see that post on Github but didnāt think it relevant as I hadnāt noticed anything in the changelog. What confuses me about your suggested workaround is where you sayā¦
With the old firmware, it is not possible to hold the on and off buttons as you can see in the mapping.
ā¦which my config shows was working and is rather fundamental to my setup?
What confuses me about your suggested workaround is where you sayā¦
With the old firmware, it is not possible to hold the on and off buttons as you can see in the mapping.
ā¦which my config shows was working and is rather fundamental to my setup?
I see from the configuration you sent that you were using the up-to-date mapping on_short_release rather than on. So I am expecting that you could hold the on button. The mapping for this controller was updated in ControllerX v3.4.0 (Aug 17th 2020) because of this issue (with an original comment in here).
I am guessing then, that there has been an update from ZHA (zigpy or zha-device-handlers), since the ON button should send on_short_release and not on command.
Could you check the rest of the commands? Maybe they just change the on and off. I checked both repositories, but I could not find any relevant changes to this.
First of all, @xaviml, thank you for all your hard work. ControllerX is pretty impressive and powerful piece of tech. Love it.
I have started to use ControllerX together with my Niko91004LightController and Deconz. I have almost got it working like I want to but Iām running into the limitation of my knowledge and Iām hoping to get some pointers here.
What Iām trying to achieve: Iām trying to use button 2 as followed:
When pressed - switch off light
When hold - bring brightness down
As you probably already can guess, Iām running into the issue that the light already gets switched off because the āpressā action gets triggered before the āholdā action gets triggered. Does anybody know how to tackle this small issue? Would really appreciate any tips you could share!
Looking at getting some of these, how do I ābuildā a controller class for them for z2m Is there base template I can tweak and play with, or is it way more involved?
The easiest way to play around is by using a generic controller (e.g. LightController) with the mapping attribute. There is no need for the controller to be supported in order to use it with ControlllerX. However, I would appreciate you share this, so we can create a default mapping for the controller.
If what you want is to collaborate to the project, then you could add the support to this device in the corresponding Python file of this device (if it does not exists, you will need ti create one).
Happy to help further with whichever path you choose. However, as I said, the easiest is to play around with the YAML config, since you do not need to play around with Python code and restar AppDaemon every time.
This minor change contains breaking changes for Lutron Caseta devices. Note: Remember to restart the AppDaemon addon/server after updating to a new version.
Hi @xaviml
Iāve got HA in docker, zigbee2mqtt as well as mosquitto (no containers) are installed on the same host. HA got integration via MQTT to get the job done. The question isā¦ is there any way to still use z2m in controllerx or only direct connection via appdaemon to mqtt broker will work?
To use ControllerX you must install AppDaemon since it runs on top of it. Once AppDaemon is installed, then it should be connected to HA (via HA plugin from AppDaemon). Additionally, you could also use the MQTT plugin to gain speed with the controller events.
Hope this answers your question, let me know if further explanation is needed
Is this controler the E1810? ControllerX offers a default mapping for this remote, but you can customise the mapping to your liking. If you let me know what is your use case, I will help you out with the configuration.