Zigbee Remote ZGRC-KEY-013 doesn't show possible actions in Home Assistant GUI

Configuration Zigbee
1

Hi there,

recently, I’ve bought the Sunricher ZGRC-KEY-013 remote control (looks like this one: Sunricher Single Color 4 Groups ZigBee Key Remote Controller SR-ZG9001K12-DIM-Z4 Zigbee compatibility). I managed to add it to my Home Assistant using ZHA and a Sonoff Dongle after a couple of attempts. So far so good.

However, when I want to make an automation in the GUI the only possible trigger is “Device offline”. I expected the different buttons of the remote control to show up in that list.

In my investigation I came across this blueprint:

Which works great for all buttons except for the “all on” and “all off” at the top of the remote as they are not defined in the blueprint. So to me that is a sign that the buttons do work, but are not correctly configured and thus don’t show up in the GUI.

Either way, how can I add them to the blueprint? Currently, in the blueprint the buttons are called g1_on_press and scene1_press for example. How do I find out the name of the all on and all off buttons of the remote?

Alternatively, how can i make the individual buttons show up as part of a normal automation dialog in the GUI without a blueprint?

2

“Looks like” is not good enough. :smile:

On top of that, the page you linked to shows the device as not confirmed working with ZHA…

Edit: There are three Sunricher remotes in the Z2M devices list, none of them with the same model number as yours. You need to do your research before you buy stuff.

1 Like
3

It has the Zigbee Logo on it (https://www.ledisons.de/smart-home/zigbee-led-treiber/zigbee-4-zonen-fernbedienung/). What does that mean then if not that it should work as a Zigbee device?

The buttons that are defined in the blueprint do work. So to me it seems I need to try to find out what the two non-working buttons are called so I can add them to the blueprint. Do you have a suggestion on how to do that?

4

It sounds like this device works with events (meaning there is no entity it’s just a bunch of triggers firing i the background…) you SHOULD be able to see events in developer tools

That said, Jack is absolutely right. Looks like is not good enough. It may look like x and act like x kinda but it is NOT X.

Just having the ‘zigbee logo’ is not enough to guarantee 100% operation. Because a thing called vendor specific clusters exist (a thing invented to allow vendors to have ‘custom’ functions means not all systems understand the vendor specific clusters and therefore don’t work.— unless someone writes something to make your chosen zigbee integration use it

So Yes probably event driven you may be able to find the event in dev tools. But if the event isn’t firing then you need to go see if the device is setup to send the event (and that would be the vendor specific config mentioned above)

For ZHA, you can read about adding custom device support here: Zigbee Guide: How-to add/setup local custom ZHA Device Handlers (also known as ”quirks”) in the ZHA integration

5

Thanks Nathan, that clarified it and helped me understand.

When I looked further I found out that the all on button (and all off button respectively) doesn’t send an individual event, but rather all other 4 events together. So that’s why one cannot add an individual action for it.

I’ll have to live without those two buttons then I guess.

Thanks for the quick help either way

1 Like