Innr RC250 remote control - Missing triggers in automation

emiel.molenaar · February 2, 2022, 7:50pm

I have bought an Innr RC250 (Remote Control - Dim je slimme verlichting draadloos - Innr Lighting) and added it into HA via my ConBee II.

I am trying to create some automations with it, but the only triggers available for this device are:

As this is a fairly new device, I can not find any related info about it. Does this mean HA does not support this remote (yet)? Is there any way to fix this? Thanks for pointing me in the right direction.

leandroqm · February 25, 2022, 10:17pm

I have a similar issue.
I tried adding it via Zigbee2MQTT, but it says that it is not supported, unfortunately.

Solo_Cola · July 10, 2022, 1:34am

Hey there,

I am facing the same issue. Do you know any solution for this? I am using ZHA with a Sonoff Zigbee 3.0 USB Dongle Plus.

svanzon · October 1, 2022, 7:51pm

I have this one also and can’t connect it with Conbee 2 stick (Phoscon / deConz). Hope someone can help?

I have not found any source on the internet about this switch. Except how to connect it with Hue, you can connect it to the Zigbee network and then to separate lights. This is working with my test. But i’m not able to integrate it with Home Assistant (not with Conbee 2 and not with Hue bridge).

stadros83 · October 11, 2022, 12:56pm

Is there any news on this ?
I just got one hoping it will work directly but it seems not …

Arran · September 5, 2023, 1:55pm

Just received one, the attached image shows the exposed events (AFAIK)

Although I was able to pair it directly with a Zigbee Lightlink Group and it works great.

peterdew · December 29, 2023, 10:49am

The problem still exists I suppose. I got the same problem with the inner RC 210.

I got it working by using the log in development tools.

It appears that the event is send as a zha_event in my case.
Using that data in a manual trigger configuration:

description: “…”
trigger:

platform: event
event_type: zha_event
event_data:
device_ieee: ‘00:3c:84:ff:fe:1d:2d:eb’
command: “on”
condition:
action:
service: scene.turn_on
target:
entity_id: scene.verlichting_woonkamer
mode: single

Utopiah · January 4, 2024, 10:02am

Indeed Peter, it’s still a problem. I just tried to add both the RC 210 and RC 250 from innr. They both connect but the configuration step does not make all the capabilities of the devices available. I’m not familiar yes with the development tools but I’m a developer.

Any pointer on what’s the right process to make an unsupported devices properly supported?
Where are the logs where one can inspect events (assuming button press generate events)?
One it has been discovered properly where should one share back the results so that others can use them too?
How come the configuration fails in the first place? I thought the point of Zigbee was precisely to have a protocol insuring compatibility.

Thanks already for sharing your findings.

Utopiah · January 4, 2024, 10:11am

Here is what I get from (failed) reconfiguration of the 250 :

Utopiah · January 4, 2024, 10:15am

For the RC 210 I get which I supposed I could use in YAML but probably not via the UI :

innr RC 210 Off event was fired
11:13:53 AM - Now
innr RC 210 On event was fired
11:02:52 AM - 11 minutes ago

How can I know from Logbook what YAML code to write though? Is it an event named “Off”?

Edit: using /developer-tools/event and listening to * (which I assume is all events) I managed to get something on button press

allard77 · January 18, 2024, 1:26am

I just got an RC250 and am finding the same problem. I can trigger on ZHA events though, so not all is lost, it’s just a bit harder in the GUI. If I finish an automation I can maybe adapt a blueprint to make it easier for people.
There’s an issue on Github, but it doesn’t look like anyone is working on it actively.

Utopiah · January 22, 2024, 9:08am

Yes, please share back if you get something. Somehow I manage to only get an event once then nothing more. So I toggle another light on once, nothing since.

allard77 · January 22, 2024, 9:16am

I had some test automation that worked to switch a light on and off, but I’m not actively using it in my home yet, so it’s not complete yet, only the on-off button is mapped. I’ll post here when I have something more useful.

allard77 · January 23, 2024, 3:04am

gist.github.com

https://gist.github.com/AllardKatan/1f358fe587c1fe2315b2ea22478e600c

innr_RC250_test.yaml

alias: test innr
description: "An automation that takes the ZHA_events fired by the INNR RC 250 remote and triggers on this to attach actions to each button. Because of the circular way the left and right buttons send their commands, you need a numeric input helper to parse those correctly as left and right. Replace <insert> tags at the device id, unique id, ieee and of course the light entity with your own values. It works for me, use at your own risk"
trigger:
  - platform: event
    event_type: zha_event
    event_data:
      unique_id: <insert>
      command: "on"
    id: "on"
  - platform: event

This file has been truncated. show original

Here’s my automation with all the buttons. It’s not a blueprint, you’ll have to edit it to insert the right id’s for remote and light. The commands are a bit stupid so you need a helper to de-cycle the left and right buttons. Your problem with not seeing events at all anymore probably means you lost contact with the device and need to re-pair it??

I might go ahead and make this into a full blueprint but I first want to figure out the templating because I had to make the code very ugly to make it work, since I couldn’t figure out how to use the trigger variable to decide what the command was…

allard77 · January 24, 2024, 1:23am

FYI: I updated the automation with MUCH cleaner code, and it can switch scenes now as well. Working on a blueprint but still bugfixing that

gist.github.com

https://gist.github.com/AllardKatan/1f358fe587c1fe2315b2ea22478e600c

innr_RC250_test.yaml

alias: test innr
description: "An automation that takes the ZHA_events fired by the INNR RC 250 remote and triggers on this to attach actions to each button. Because of the circular way the left and right buttons send their commands, you need a numeric input helper to parse those correctly as left and right. Replace <insert> tags at the device id, unique id, ieee and of course the light entity with your own values. It works for me, use at your own risk"
trigger:
  - platform: event
    event_type: zha_event
    event_data:
      unique_id: <insert>
      command: "on"
    id: "on"
  - platform: event

This file has been truncated. show original

Utopiah · February 3, 2024, 9:53pm

FWIW I took my own advice into account (sigh) so after pairing/unpairing and reconfiguring, absolutely 0 thinking, I do indeed manage to get all events properly. It’s a bit of a mess but I can get the on/off main button, increase/decrease brightness and the side buttons too (even though they somehow keep track of a value, not very convenient).

It’s been a bit tricky but seems to work reliably now!