That brightness issue is back. Other than that it turns them on and off as expected.
1 Like
If I add back in that code you gave me yesterday all good.
add_transition: false
Okay. Thanks @bdb1. I think I will remove the transition from the following actions âonâ, âoffâ and âtoggleâ, since the transition is not that important for those actions. However, I will add a flag so users will be able to add the transition back as before.
I will add this fix as soon as possible, so no add_transition: false will be necessary.
Thank you for the debugging! 
All good mate. No stress. You have a day job. Will look forward to hearing back when fixed.
Take care for now
1 Like
Hi, Can you please let me know how I can use the E1743 controller for Cover? I can add the controller into Hassio and it creates 2 sensors: 1 battery and 1 Open/Close sensor. But when pushing a button, no event is triggered in Hassio (when listening to zha_event) and therefore I assume I am also unable to use the controller with ControllerX. Any help will be appreciated
Hi @Botap,
I understand by context that you integrated E1743 with ZHA, is this right? If so, you will need to make sure the events show up in the âDeveloper Tools > Eventsâ when listening to âzha_eventâ. Then when configuring the controller into apps.yaml, you will need to put the device IEEE into the controller attribute, like this:
example_app:
module: controllerx
class: E1743CoverController
controller: XX:XX:XX:XX:XX:XX
integration: zha
cover: cover.your_cover
Hi, thanks for the quick reply and this indeed what I am trying to do. I am just wondering if you managed to get the controller to generate events in Developer Tools->events via ZHA? As this doesnât work for me and therefore I canât get it to work with ControllerX. I am just wondering if there is a special setting/config/or anything else required?
Hi @Botap again,
I am not sure what you did to pair your controller with ZHA. But these are the steps I followed when I integrated the device: https://www.home-assistant.io/integrations/zha/#configuration---gui
If after doing that it does not work, you can check this GitHub issue from Home assistant: https://github.com/home-assistant/core/issues/31734. You could try to reconfigure the remote again, that is what solved the issue to that person.
@Botap - I see you commented in the github issue as well.
If you have the controller grouped with a bulb using groups, you need to add your controller to that group in order for ZHA events to show.
Go to Config -> ZHA -> Groups. Find the group with your remote in it and select it. Then add your ZHA coordinator to it and try again.
Hiâ Xavi.
Just a quick remark about the transition issues on different platforms.
All proprietary hubs/bridges/gateways (I know off) all supports toggle and on/off with a transition.
In my opinion, it all comes down to bugs in the different implementations made to emulate behaviour of proprietary hubs. Thereâs also transition bugs in HAâs core implementation with at least the Hue Bridge. Iâve still my issue open and unsolvedâŠ
But it CAN be done. Koenkk fixed all known issues with the z2m Ikea TrÄdfri z2m Herdsman converter code.
And the reason why so many transition issues still exist is probably due to the fact that Zigbee protocol itself doesnât support transitions from on/off positions. These have to be emulated by the converter code itself.
+++ Koenkk quote on +++
Some background on why you get these bugs when using transition: Zigbee does not have commands to turn on/off lights with a transition (besides one with a fixed 0.8 transition). Therefore we turning a bulb off with a transition, we set the brightness to 0. When the bulb is turned on again we need to restore this transition.
â Koenkk quote off â
I would suggest that the âDeconz guysâ raised the issue to get the core code fixed!!
I understand your argument for removing default transition, if it gives so much hazzle. Iâm just glad that youâll keep the option to continue using transitions in ControllerX. I would be sad to see them go. Transition is one of the neatest visual feature having smart lights and clearly distinguish smarts lights from lights just switched on and off by a relay or a plain old âdumbâ wall switch ! 
Just my two cents, Xavi ! 
Ciao !
1 Like
I totally agree with you @htvekov with every word you just said. I would even say you made me change my mind. For the moment, I will state this problem in the FAQ and see if deconz and other integrations fix this issue. Then, in the meantime people with this issue can add the add_transition: false.
I also think it would be a pitty to remove such a nice functionality just because different integrations do not support it.
2 Likes
Hi,
I am new to ControllerX and AppDaemon (installed 1 hour ago - ish)âŠ
However I have Conbee2 and using deconz with default integration into HA.
I have managed to set up 2 type of Ikea controllers, an E1810 and an E1744. Both uses the deconz integration.
The E1744 is controlling a Sonos speaker. Everything is working fine, however the volume up/down steps in really, really big steps. Is there any way to change that, so I could get somehow a similar behavior of volume up/down in the app on a smartphone, which is really granular?
The E1810 is controlling an Ikea E27 light bulb. Is there any way to change color of the bulb (white, warm etc)? At least that doesnât work for me. I assume that is because of the deconz integration that doesnât do that correct either?
Here is the code added to apps.yaml
Office_Controller:
module: controllerx
class: E1810Controller
controller: test_rc
integration: deconz
light: light.office_roof_lamp
Bathroom_speaker:
module: controllerx
class: E1744MediaPlayerController
controller: bathroom_sound_controller
integration: deconz
media_player: media_player.bathroom
I can confirm that the left / right buttons on the E1810 does fire events.
Left-click:
{
"event_type": "deconz_event",
"data": {
"id": "test_rc",
"unique_id": "00:0d:6f:ff:fe:4b:56:a4",
"event": 4002
},
"origin": "LOCAL",
"time_fired": "2020-05-06T21:22:22.342690+00:00",
"context": {
"id": "fc5326c782d54c9a97b050cb2387d67e",
"parent_id": null,
"user_id": null
}
}
Right-click:
{
"event_type": "deconz_event",
"data": {
"id": "test_rc",
"unique_id": "00:0d:6f:ff:fe:4b:56:a4",
"event": 5002
},
"origin": "LOCAL",
"time_fired": "2020-05-06T21:22:58.504719+00:00",
"context": {
"id": "22b90ae2b9c04d67b328b2a78cf4f2a1",
"parent_id": null,
"user_id": null
}
}
Is there any way to address the above issues?
Xavi, could we collect data from users of different integration platforms and bulb types, to get a clearer picture of the transition issues ?
If you google this subject, youâll get hundreds of different hits with transition issues. But not all users out there agree on this matter - even with same bulb type and integration 
Just a thought⊠
Hiâ @nano and welcome ! 
Iâm a âz2mâ guy and know actually nothing about deconz (others here do )
But I know about Sonos and ControllerX.
Plese check the examples in documentation Sonos examples with ControllerX
Thereâs a lot of general info on how Sonos can be perfectly integrated with ControllerX.
Iâm using volume_steps:20 to get âsmoothâ volume behavior.
Ciao !
Hi Henning,
Thank. I will have a look at it.
Hi @nano,
Welcome to the ControllerX and AppDaemon world, and also to the community forum
First of all, the integration of E1744 it is by default quite slow and with big steps. However, this is because not everyone has a good Zigbee network. When rotating, ControllerX sends volume changes until rotation stops. You can play with delay which is the time between requests (1000ms) and volume_steps which is the steps needed to go from minimum to maximum value (10 by default). I have tried before and a perfect configuration for me is delay of 100 and volume steps of 20. Here is the configuration:
Bathroom_speaker:
module: controllerx
class: E1744MediaPlayerController
controller: bathroom_sound_controller
integration: deconz
media_player: media_player.bathroom
delay: 100
volume_steps: 20
Note that this will cause to more request to HA and your SONOS, although it will be much smoother if you have good network. You can read more about the parameters in here. You can also check the SONOS example that @htvekov pointed you at, although it does not use the E1744 controller, just the E1810 one.
Regarding the light issue, can you change the color temperature from HA through the light card when you click to the entity? Can you check the value of supported_features from the state attribute of your light in âDeveloper Tools > Stateâ?
OoopsâŠ
Will I ever learn to actually READ what people are writing 
Didnât notice that it was an E1744 controller, my bad.
Hi Xavi,
My supported_features look like this.
min_mireds: 153
max_mireds: 500
brightness: 254
is_deconz_group: false
friendly_name: Office - Roof Lamp
supported_features: 43
From the light card, I can control the light color/color temperature
Any clues?
Hi @nano,
Apparently, this issue comes from deCONZ (https://github.com/dresden-elektronik/deconz-rest-plugin/issues/1861) and it hasnât been fixed yet. The problem is that it does not report color_temp to HA, therefore, ControllerX cannot get the color temperature value. However, the supported_feature (43) indicates it supports: transition, color_temp, flash and brightness. I will try to track closer the issue from them to see if it can get a fix. Iâve seen a PR about it, but it hasnât been merged yet.
Hi Blake, thanks for the reply. My issue is that I am unable to add any Ikea controllers into a group. When creating a group I can add Ikea lights and an Ikea switch into the group. I can also add the Zigbee controller/coordinator to the group, but no Ikea controller. Basically nothing happens, the Ikea controllers remain in the list of member I can add.
I just noticed I get the following message in the log file:
2020-05-09 08:00:22 DEBUG (MainThread) [zigpy.endpoint] [0x73d2:1] Cannot add 0x0001 group, no groups cluster
Not sure if this means anything to you?