Re-configure IKEA rotary remote E1744

Configuration
,
1

Hello,
I used to have it configured with AppDeamon / controllerX / zigbee2mqtt, triple press to power on a sonos speaker via a smart plug and the rotary for the volume, a few years later, not using it much (as the volume setting was always a little clumsy) the volume isn’t changing anymore, probably a breaking change somewhere…
In between I’ve seen that blueprints are another way to configure it.
Has someone any idea if I should switch or try to find the problem ? I must confess that I’m not remembering a lot about my configuration of AppDeamon / controllerX / zigbee2mqtt.
Thanks

2

Har do answer, i don’t use any of that setup except the rotary knob.
It works fine for me in ZHA even the volume, but I have a rate limit on the messages it sends so that is probably why it works fine.
I remember it sending a lot of messages sometimes.

3

Hi @tbozo ,

I am happy to help you out to fix your issues. I have a E1744 device that controls a Google Home mini and has been working smoothly for ages with ControllerX.

I can help you out if you provide the following:

  • ControllerX configuration.
  • Zigbee2MQTT logs proving that the controller is sending actions.
  • AppDaemon logs to show ControllerX registers the device properly.

With this, I will know where the problem might be coming from.

Regards,
Xavi M.

4

This is interesting. Could you help elaborate a bit on the setup, or maybe point me the direction?

5

That is in node red.
But it’s the delay node, and you configure it to rate limit and I believe mine is set to 150 ms.
That means all the real events are passed as it should but the fake ones are stopped.

I think you could do it in HA also by having mode single and end the automation with a delay of 150 ms.

6

Hi,

Thanks, here are the logs :

Zigbee2MQTT:info  2022-09-15 12:02:52: MQTT publish: topic 'zigbee2mqtt/SymfoniskRotary1', payload '{"action":"brightness_move_up","action_rate":195,"battery":34,"brightness":186,"linkquality":68,"rate":195,"update":{"state":"available"},"update_available":true}'
Zigbee2MQTT:info  2022-09-15 12:02:52: MQTT publish: topic 'zigbee2mqtt/SymfoniskRotary1', payload '{"action":"","battery":34,"brightness":186,"linkquality":68,"rate":195,"update":{"state":"available"},"update_available":true}'
Zigbee2MQTT:info  2022-09-15 12:02:52: MQTT publish: topic 'zigbee2mqtt/SymfoniskRotary1/action', payload 'brightness_move_up'
Zigbee2MQTT:info  2022-09-15 12:02:52: MQTT publish: topic 'zigbee2mqtt/SymfoniskRotary1', payload '{"action":"brightness_stop","battery":34,"brightness":186,"linkquality":68,"rate":195,"update":{"state":"available"},"update_available":true}'
Zigbee2MQTT:info  2022-09-15 12:02:52: MQTT publish: topic 'zigbee2mqtt/SymfoniskRotary1', payload '{"action":"","battery":34,"brightness":186,"linkquality":68,"rate":195,"update":{"state":"available"},"update_available":true}'
Zigbee2MQTT:info  2022-09-15 12:02:52: MQTT publish: topic 'zigbee2mqtt/SymfoniskRotary1/action', payload 'brightness_stop'
Zigbee2MQTT:info  2022-09-15 12:02:53: MQTT publish: topic 'zigbee2mqtt/SymfoniskRotary1', payload '{"action":"brightness_move_up","action_rate":195,"battery":34,"brightness":186,"linkquality":70,"rate":195,"update":{"state":"available"},"update_available":true}'
Zigbee2MQTT:info  2022-09-15 12:02:53: MQTT publish: topic 'zigbee2mqtt/SymfoniskRotary1', payload '{"action":"","battery":34,"brightness":186,"linkquality":70,"rate":195,"update":{"state":"available"},"update_available":true}'

2022-09-15 11:07:53.452343 INFO cuisine_speaker: 🎮 Button event triggered: `brightness_move_down`
2022-09-15 11:07:53.585038 INFO cuisine_speaker: 🎮 Button event triggered: `brightness_move_up`
2022-09-15 11:07:53.622952 INFO cuisine_speaker: 🏃 Running `Predefined (hold_volume_down)` now
2022-09-15 11:07:53.791930 INFO cuisine_speaker: 🏃 Running `Predefined (hold_volume_up)` now
2022-09-15 11:07:53.886429 INFO cuisine_speaker: 🎮 Button event triggered: `brightness_stop`
2022-09-15 11:07:53.973909 INFO cuisine_speaker: 🏃 Running `Predefined (release)` now
2022-09-15 11:07:54.107713 INFO cuisine_speaker: 
🤖 Service: media_player.volume_set
  - entity_id: media_player.bureau
  - volume_level: 0.97
2022-09-15 11:07:54.162802 INFO cuisine_speaker: 
🤖 Service: media_player.volume_set
  - entity_id: media_player.bureau
  - volume_level: 1.00
2022-09-15 11:07:54.284987 INFO cuisine_speaker: 
🤖 Service: media_player.volume_set
  - entity_id: media_player.bureau
  - volume_level: 0.97
2022-09-15 12:02:52.246390 INFO cuisine_speaker: 🎮 Button event triggered: `brightness_move_up`
2022-09-15 12:02:52.312485 INFO cuisine_speaker: 🏃 Running `Predefined (hold_volume_up)` now
2022-09-15 12:02:52.431995 INFO cuisine_speaker: 
🤖 Service: media_player.volume_set
  - entity_id: media_player.bureau
  - volume_level: 1.00

And the config

cuisine_speaker:
module: controllerx
class: E1744MediaPlayerController
controller: SymfoniskRotary1
integration:
  name: z2m
  listen_to: mqtt
  action_key: action # By default is `action` already
media_player: media_player.bureau
volume_steps: 30
delay: 50
mapping:
  brightness_move_down: hold_volume_down
  brightness_move_up: hold_volume_up
  brightness_stop: release
  toggle: play_pause
  brightness_step_up: next_track
  brightness_step_down:
    service: homeassistant.toggle
    data:
      entity_id: switch.0x842e14fffe3daeef
#delay: 150
7

I don’t know why it’s back, at the time I took the logs it wasn’t but from the log it looked as if it was OK AFAIK.
Anyway after a couple new updates and reboot it’s back, but still really hard to use, as it jumps easilly to full volume and/or have some buffering of the orders. I guess I sould play with debounce in device and delay and steps in config. But If you have a working set of options I’ll try your setup.

BTW this is what I have for the remote in the devices.yaml of zigbee2mqtt folder

  legacy:false
  debounce: 0
  debounce_ignore: []
8

Hi @tbozo ,

I only have the legacy: false setting for this device. Not sure if debounce helps or not, probably try both 0 and 1.

Regarding volume_steps and delay, they are both variables to tweak around as well to get the best result depending on your network throughput. I personally do not recommend a delay of less than 100, but you can try it out. I have delay: 100 and volume_steps: 20 for example.

If after tweaking this parameters you still experience some lag, it could be that problem might come from media player device, so in that case you might want to increase the delay and decrease volume_steps.

I hope this tips will help you find the right setup for you.

This is a video I posted in Twitter on how my E1744 works controlling a chromecast volume: https://twitter.com/xaviml93/status/1278000379444240390 it was with deCONZ, but I experience the same with Zigbee2mqtt.

Regards,
Xavi M.