Hi,
I have a SYMFONISK sound remote that I’ve paired with ZHA, but the events are not appearing when I listen for “zha_event” in developer tools. Events from other types of remotes show (such as the TRADFRI remote), and the sound remote works fine when paired to a TRADFRI gateway (i.e. it can control the volume fine on a Sonos speaker, and can play/pause).
Any suggestions on how I can troubleshoot this?
Thanks!
Have no experience with zha, but there might be a difference between other remotes (likely button based) and symfonisk.
Don’t know if it will help you, but when using it through zigbee2mqtt, there is only one state output which changes repeatably between particular state and empty one. For example when turning it right, the state changes in sequence:
rotate_right, “”, rotate_roght, “”, rotate_right, “”, rotate_stop, “”
Persistence of states other than empty string is very short
But you don’t automate from the state, go to configuration, devices and choose the symfonisk device. Click the plus next to Automations and follow your nose.
I’ve set up an automation that should fire when pressing the button, but it doesn’t fire.
It seems others are having trouble with this controller and zigbee2mqtt too:
@maxym are you using this controller with zigbee2mqtt successfully?
yes, I added 2 symfonisks without problems.
I glanced the mentioned github issue. People mention brightness. I didn’t use simulated brightness, so it reports following states: rotate_right, rotate_left, play_pause, totate_stop, skip_forward, skip_backward and empty string
I’m not using HA automation. I’m using NR instead. Also I’m still I’m on HA 2021.1.5 (but recent zigbee2mqtt).
I presented my automation here: IKEA Symfonisk & ABB Tango
So do you have legacy set to true or false?
In z2m GUI Settings/Advanced: Legacy API: checked
In add on configuration:
experimental:
new_api: false
This latter setting is not used any more anyway (Koenkk said).
Edit Koenkk also said:
legacy_api: true → legacy api enabled, false = disabled. It doesn’t matter for Home Assistant, this was left in to prevent a breaking change. For new installations it is disabled by default.
I have no custom behaviour set for single devices.
Im facing the same issue with zha and symfonisk controller. It used to work but has stopped working after an update … do not ask me which one, had not used it since December and wanted to use it just recently, realizing it was not working.
I can pair the controller, but no events are fired when using the controller. well at least not if i listen to zha_event or * in developer tools.
help would be much appreciated.
thanks
edit:
when i say i can pair, i have tried resetting the controller and pair it against zha several times, but it does not fix the issue 
edit:
hmmm… it seems to have something to do with the zigbee receiver … i have a sonoff BASICZBR3 attached and i tried adding the controller through this unit, and now it works. 
The Zigbee interface I’m using (HUSBZB-1) doesn’t appear to be compatible with zigbee2mqtt.
I’d also appreciate any suggestions on how to get this working with ZHA - is this a bug?
@cool_bombom I also have tried resetting and re-pairing it with ZHA a few times to no avail. Isn’t the BASICZBR3 a Zigbee-controlled switch that connects to a hub? What do you mean you connected the SYMFONISK controller through the BASICZBR3?
@jayce20 It is possible to use the BASICZBR3 with zha, and since it is on main power it acts as a router/host in the zigbee network (read more about zigbee mesh network). So when you navigate to the BASICZBR3 unit in the zha interface it is possible to pair new units via that unit… by the way i also use HUSBZB-1
I’m running into exactly the same issue as you are I believe. I have the Nortek controller (HUSBZB-1) - I have my devices paired but nothing shows on zha_event
Happily following this thread
When. you look at your devices in - do they show a last update time? Mine is usually once a day → and if I move the devices around and re-view the network it will re-form correctly … but I’m struggling to figure out how to debug the ZHA stream and figure out what is or isn’t going on.
So if I pull info on the two remotes I get this:
But that means they do report a status update - but not getting ZHA events… I’ll go press the buttons and see if the status (last seen) thing updates…
(and the last seen times are still the same… - also at one point one was reporting a battery value but no longer)
And more interesting they are actually now offline in my zigbee visualization …
Any chance you are seeing similar things?
My “last seen” reads 2021-08-27T18:27:46
In the visualization, it doesn’t show as offline right now; I’ll keep an eye on it, and see if it goes offline
Thanks @cool_bombom - I tried pairing the remote via a Zigbee wall outlet, but still has the same problem.
After doing some research looks like there is a bug with zha that drains the battery in a day for some Ikea stuff. There is an open GitHub issue. Not sure if it’s related but it’s related to my issue cause I tested the batteries and they were dead
That would stop it working 
Have you been seeing battery drain?
Hello.
I got the problem too with two E1744.
I’ll go get some battery, but no events is published after being paired with ZHA.
I was having a similar issue (Sound remote paired with ZHA but couldn’t see anything in zha_event). My best guess to the cause is that something goes wrong during the pairing process.
I finally got it working after re-pairing the remote for like the 5th time. Here’s the steps I followed just in case it matters:
-Take remote to be right beside hub
-Open up new window with developer tools in HA and subscribe to ‘zha_event’ (to see if you are able to sense remote inputs)
-Delete remote from ZHA
-Take battery out of remote
-Put battery back in
-Start pairing in ZHA
-Hold down paring button on remote
-Once remote pairs, rotate and click button to see if you see any activity from zha_event
If that doesn’t work, I’d recommend you continue to repeat that process until the remote works for you.
Also, when I finally got the remote to pair again the battery was drained to 14%. You might need new batteries if you aren’t able to get the remote to pair.