Unable to create automations with Ikea SYMFONISK remote gen2?

Configuration
1

Hey Everyone,

I randomly picked up an Ikea SYMFONISK sound remote gen2 because it has more buttons than the STYRBAR remote. I have successfully added it to my Home Assistant via ZHA and the integration is responding to the device: up, down, next, previous, and play.

Bedroom Ikea Audio Remote Toggle event was fired
8:50:48 PM - 1 second ago
Bedroom Ikea Audio Remote Move With On Off event was fired with parameters: {'move_mode': <MoveMode.Down: 1>, 'rate': 255}
8:50:47 PM - 2 seconds ago
Bedroom Ikea Audio Remote Move With On Off event was fired with parameters: {'move_mode': <MoveMode.Up: 0>, 'rate': 255}
8:50:46 PM - 4 seconds ago
Bedroom Ikea Audio Remote Step event was fired with parameters: {'step_mode': <StepMode.Up: 0>, 'step_size': 1, 'transition_time': 0, 'options_mask': <bitmap8.0: 0>, 'options_override': <bitmap8.0: 0>}
8:50:44 PM - 5 seconds ago
Bedroom Ikea Audio Remote Step event was fired with parameters: {'step_mode': <StepMode.Down: 1>, 'step_size': 1, 'transition_time': 0, 'options_mask': <bitmap8.0: 0>, 'options_override': <bitmap8.0: 0>}
8:50:43 PM - 6 seconds ago

However, automations are not showing up for the recorded inputs:

image

What needs to happen for the button action automation options to appear? Is there a “manual override” method I can use to have Home Assistant respond to button presses within automations?

Thank you for your help!

2 Likes
2

Just wanted to come in and say that I have the same problem. Events show up in the Logbook for the device, but I have no clue how to “catch” them in Automations…

My guess is that this is because the button was released at IKEA in the last couple of weeks, and it wasn’t implemented (mapped) yet. However, I would love to know how to contribute to get this working.

Screenshot_20230318-111739
Screenshot_20230318-1117391644Ă—1251 85.5 KB

3

Okay, so I managed to get a workaround working… :slightly_smiling_face:

  1. Find out what the event data is.
    This can be found when going into Developer Tools > Events > Listen to Events, and enter “zha_event” in “Listening to”. Then go ahead and press the button you want to map in your automation. The result will look something like this:

    20230318_11h30m14s_grim
    20230318_11h30m14s_grim1030Ă—997 68.9 KB

  2. Create a new Automation, and choose “Event” as trigger. Enter “zha_event” as Event Type. Go ahead and paste everything that’s under the “data” part of the first step. In my case, it looks like this:

device_ieee: 94:de:b8:ff:fe:9b:6c:ba
unique_id: 94:de:b8:ff:fe:9b:6c:ba:1:0x0008
device_id: d566165ce40ded1411fd1fad6c1c2316
endpoint_id: 1
cluster_id: 8
command: move_with_on_off
args:
  - 1
  - 255
params:
  move_mode: 1
  rate: 255

  1. Redo for all buttons you want to map.

  2. Profit!?

Hope it works for you as well as it did for me!

I guess the question of creating a proper “mapping” (like the one you requested) remains, but this might work in the meantime.

2 Likes
4

So, another update. Seems like these two buttons are not being picked up by ZHA…

20230318_115834~3
20230318_115834~31920Ă—2560 112 KB

5

Hey @Rydberg95 !

Welcome to the community!!

Ya, the “dot” and “dot dot” buttons aren’t yet supported by ZHA for some reason. I guess they are working on it (hopefully). I want to use those to toggle which device I am controlling!

Your suggestion for “manually” creating button listeners looks excellent! I will give it a go and see what I can make of them. If I find out anything noteworthy, I’ll report back here so everyone can be up to date.

Thank you for your help!!