search

xaviml / controllerx

Create controller-based automations with ease to control your home devices and scenes.
https://xaviml.github.io/controllerx/
MIT License
335 stars 69 forks source link

[BUG] HueDimmerController #572

Closed bilbon0bud closed 2 years ago

bilbon0bud commented 2 years ago

Bug report

All my hue dimmer stop working since release 4.22, everything works fine with 4.21.

Description

i do not edit my configuration, only update to 4.22, restart AppDaemon. All my configuration stop working.

i saw my bouton press in the app deamon, but nothing change on my lights.

i rollback to 4.21 restart app daemon and everything work fine.

Additional information

AppDaemon app configuration

remote_dimmer_porte_emma: module: controllerx class: HueDimmerController controller: sensor.emma_dimmer_porte_action integration: z2m light: name: light.emma_suspension actions:

parents_dimmer_lit_paul: module: controllerx class: HueDimmerController controller: sensor.parents_dimmer_lit_paul_action integration: z2m light: name: light.parents_suspension actions:

parents_dimmer_lit_angelique: module: controllerx class: HueDimmerController controller: sensor.parents_dimmer_lit_angelique_action integration: z2m light: name: light.parents_suspension actions:

remote_dimmer_porte_suspension: module: controllerx class: HueDimmerController controller: sensor.parent_dimmer_porte_action integration: z2m light: name: light.parents_suspension actions:

louis_dimmer_porte: module: controllerx class: HueDimmerController controller: sensor.louis_dimmer_porte_action integration: z2m light: name: light.louis_principale actions:

louis_dimmer_lit: module: controllerx class: E1810Controller controller: sensor.louis_dimmer_lit_action integration: z2m light: name: light.skate_bas actions:

remote_bureau_dimmer_1: module: controllerx class: HueDimmerController controller: sensor.bureau_dimmer_1_action integration: z2m light: name: light.bureau

remote_bureau_dimmer_2: module: controllerx class: HueDimmerController controller: sensor.bureau_dimmer_2_action integration: z2m light: name: light.bureau

Logs

with 4.21 i can see Good logs

022-09-13 17:27:13.764446 INFO media_lights_sync_louis: Using libimagequant quantization method 2022-09-13 17:27:13.766728 INFO media_lights_sync_louis: Listening for picture changes on 'media_player.reveil_louis' 2022-09-13 17:27:13.776897 INFO media_lights_sync_salon: Using FastOctree quantization method 2022-09-13 17:27:13.779589 INFO media_lights_sync_salon: Listening for picture changes on 'media_player.nesthubmax5cda' 2022-09-13 17:27:13.794733 INFO remote_dimmer_porte_emma: 🎮 ControllerX v4.22.0 2022-09-13 17:27:13.890065 INFO parents_dimmer_lit_paul: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.035108 INFO parents_dimmer_lit_angelique: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.113016 INFO remote_dimmer_porte_suspension: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.191226 INFO louis_dimmer_porte: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.268646 INFO louis_dimmer_lit: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.355431 INFO remote_bureau_dimmer_1: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.433046 INFO remote_bureau_dimmer_2: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.516833 INFO AppDaemon: App initialization complete 2022-09-13 17:27:19.433501 INFO AppDaemon: New client Admin Client connected 2022-09-13 17:27:21.979779 INFO remote_bureau_dimmer_2: 🎮 Button event triggered: on_press_release 2022-09-13 17:27:21.991413 INFO remote_bureau_dimmer_2: 🏃 Running Predefined (on) now 2022-09-13 17:27:22.009327 INFO remote_bureau_dimmer_2: 🤖 Service: light.turn_on

With 4.22

only show 022-09-13 17:27:13.764446 INFO media_lights_sync_louis: Using libimagequant quantization method 2022-09-13 17:27:13.766728 INFO media_lights_sync_louis: Listening for picture changes on 'media_player.reveil_louis' 2022-09-13 17:27:13.776897 INFO media_lights_sync_salon: Using FastOctree quantization method 2022-09-13 17:27:13.779589 INFO media_lights_sync_salon: Listening for picture changes on 'media_player.nesthubmax5cda' 2022-09-13 17:27:13.794733 INFO remote_dimmer_porte_emma: 🎮 ControllerX v4.22.0 2022-09-13 17:27:13.890065 INFO parents_dimmer_lit_paul: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.035108 INFO parents_dimmer_lit_angelique: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.113016 INFO remote_dimmer_porte_suspension: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.191226 INFO louis_dimmer_porte: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.268646 INFO louis_dimmer_lit: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.355431 INFO remote_bureau_dimmer_1: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.433046 INFO remote_bureau_dimmer_2: 🎮 ControllerX v4.22.0 2022-09-13 17:27:14.516833 INFO AppDaemon: App initialization complete 2022-09-13 17:27:19.433501 INFO AppDaemon: New client Admin Client connected

Additional Context

xaviml commented 2 years ago

Hi @bilbon0bud ,

I see from both logs that they are using v4.22.0 (even the ones you say it was v4.21.0. You can see the version when apps are initialized.

In any case, you are experiencing this problem because since v4.21.0, the default mapping for Hue Dimmer controller has changed to support the non-legacy mapping from this controller on Zigbee2MQTT. You can read about it in the release notes. You can also see that the mapping has changed in the device documentation and it does not match what you get in the logs.

You have 2 options:

Screenshot from 2022-09-17 10-15-26

You can read further on why was this done for this controller here.

Let me know if you struggle with either option.

Regards, Xavi M.

bilbon0bud commented 2 years ago

Hello

Everything works now

Thanks for your help Le 17 sept. 2022 à 10:22 +0200, Xavi Moreno @.***>, a écrit :

Hi @bilbon0bud , I see from both logs that they are using v4.22.0 (even the ones you say it was v4.21.0. You can see the version when apps are initialized. In any case, you are experiencing this problem because since v4.21.0, the default mapping for Hue Dimmer controller has changed to support the non-legacy mapping from this controller on Zigbee2MQTT. You can read about it in the release notes. You can also see that the mapping has changed in the device documentation and it does not match what you get in the logs. You have 2 options:

• Downgrade to v4.20.0 so the old mapping is supported. • Use ControllerX >= v4.21.0 and flagged the device as legacy: false in Zigbee2MQTT. You can do it on the device.yaml file found in /config/zigbee2mqtt/device.yaml and add legacy: false next to friendly_name attribute. Or you can do it through UI, going to device "Settings (specific)" and mark legacy as False as shown in the picture below.

You can read further on why was this done for this controller here. Let me know if you struggle with either option. Regards, Xavi M. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>