controllerx: [BUG] Zigbee2MQTT breaking changes
Bug report
As Zigbee2MQTT 1.42. or 2.0 come with breaking changes (https://github.com/Koenkk/zigbee2mqtt/discussions/24198), it also breaks some controllers, such as E1743
Description
The controller does not work anymore.
Additional information
- Devices involved:
- Model: eg. IKEA E1743
- …
- Integration: z2m
- AppDaemon version: v4.4.2
- HACS version (if installed from there): 2.0.1
- Home Assistant Core version: 2024.11.3
AppDaemon app configuration
nachttisch_links:
module: controllerx
class: E1743Controller
integration: z2m
controller: sensor.dim_nachttisch_links_action
light: light.hue_color_lamp_1
nachttisch_rechts:
module: controllerx
class: E1743Controller
integration: z2m
controller: sensor.dim_nachttisch_rechts_action
light: light.schlafzimmer_nachttisch_rechts
wohnzimmer_dim:
module: controllerx
class: E1743Controller
integration: z2m
controller: sensor.dim_wohnzimmer_action
light: light.wohnzimmer_decke
flur_dim:
module: controllerx
class: E1743Controller
integration: z2m
controller: sensor.dim_flur3_action
light: light.flur_deckenlampe
kueche_dim:
module: controllerx
class: E1743Controller
integration: z2m
controller: sensor.dim_kueche_action
light: light.unterschranke_kuche
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 20 (8 by maintainers)
Commits related to this issue
- feat(z2m): add event entity listener related to #1090 — committed to xaviml/controllerx by xaviml 2 years ago
- feat(z2m): add event entity listener related to #1090 — committed to xaviml/controllerx by xaviml 2 years ago
- feat(z2m): add event entity listener related to #1090 — committed to xaviml/controllerx by xaviml 2 years ago
v2.0.0 of Z2M has been released.
Here’s what I had to do:
Appdaemon config
Apps configuration
Before
After
Suggestions
I suggest updating the second code sample here, it wasn’t immediately clear that the
controllerkey had changed, nor that the device’s friendly name was expected. Maybe also setup a Z2M 2.0 migration page in the docs?MQTT error
I got the following errors in the logs. Looks like it ended up successful (Plugin initialization complete) but still, a bit scary.The warning disappeared when listening only to z2m messages (
client_topicsconfig key).Logs
Edited on 2025-01-04: add appdaemon config example + update on MQTT warning
I ran into trouble with node-red, and found out that there is a setting in Z2M that should be activated:
According to KennethLavrsen it is no longer experimental.
It’s a rather cool addition, it will create an entity for the event.
So instead of a sensor, it’s doable with an event entity.
The value of the button in Node Red is in: data.new_state.attributes.event_type
A cool benefit is that if you go to Developer Tools -> States and look up the device, it shows the possible values provided by the button.
Maybe ControllerX could use this as well @xaviml ?
ControllerX v4.29.0 has been now released.
Hi @Crocmagnon ,
I had similar issue in my setup, but I did not have time to debug where the problem was coming from. However, it seemed a problem from Zigbee2MQTT since when I restarted it, it got fixed.
The following issue was released on Zigbee2MQTT 2.1.2, so maybe that was causing it: https://github.com/Koenkk/zigbee2mqtt/issues/26281
Since I have this version, it has not happened to me again.