#Phillips Hue RDM001?

1 messages · Page 1 of 1 (latest)

tired nacelle
#

I've been switching everything over from Hue to Home Assistant Zigbee. Everything has been going great, except for when I got to my RDM001 - which turns a regular wall switch into a Hue on/off switch. It added just fine, but when I go to make an automation and add it as a trigger there isn't an "On" of "Off" option like everthing else. I just have:

Device offline
Battery level changes
Firmware update availability changed
Firmware became up to date
Firmware got an update available
Identify has been pressed

If I look at the logbook when pressing the switch on or off I get these entries:

Switch On event was fired
or
Switch Off with Effect event was fired with parameters: {'effect_id': 0, 'effect_variant': 0}

Does anyone know what I'm doing wrong or how I can get an On/Off with this device in my triggers? Thanks!!

image.png
static thorn
#

As far as I know, when you select a "device" trigger, it will only show you the options for which HA knows the history. It is better to react on a entity state, not on a device id. This explains it well: https://community.home-assistant.io/t/why-and-how-to-avoid-device-ids-in-automations-and-scripts/605517

Go to the device, find the entity that you are interested with, go back to automation, select the "state" trigger, and select your state.

Home Assistant Community
Why and how to avoid device_ids in automations and scripts

Background When you start writing automations, a device trigger seems the obvious choice. Everybody knows what a device is and it comes at the top of the UI dropdown list. It works… but it is certainly not a “great way to start” because it is storing up problems for the future. Far better to use an entity, with state or numeric_state....

tired nacelle
#

Huh, thank you! Yeah when you start an automation from the device it's especially confusing then since these are the options you get before you get to the automation screen (not shown in that article). I'll give this a shot using the bottom option "Create new automation", I've done all my others (and I've done a lot of them already - so that sucks I've been doing it wrong, lol.

Screenshot_2025-05-16_095652.png
#

Hmm... while that is good information to know, it doesn't seem to be getting me anywhere. When I search for the entity in the Numeric State (or the other option), I'm still only getting these as options - and I don't think any of these have the states I'm looking for?

image.png
static thorn
#

don't start the automation from the device. Go to autoamtions, start empty new one, as a trigger select "State". Numeric state is for entities that have a number, while if I understand you want switch, which I guess is a "on/off" state.

#

can you also show the device page with list of all entities?

tired nacelle
#

Thanks again! It looks like it only has two entities - Battery and Identify, with two disabled entities - LQI and RSSI (no idea what that means or what those are)

image.png
static thorn
#

and if you actually press the button, you say it does show something in the log?

#

you are clearly missing the "button" entity, I agree

#

what happens if you try to "reconfigure" button?

#

https://community.home-assistant.io/t/how-to-configure-the-philips-hue-wall-module-to-use-push-button-momentary-type-wall-switches-zha/451125 this may help you

Home Assistant Community
How to configure the Philips Hue wall module to use push button (mo...

OK, here’s the meat of the meat and potatoes: Hue wall modules ship by default prepared to handle a single rocker. Momentary switches, when connected to the Hue module, generate two “left button pressed” events instead of one. This is obviously bad because now you need to add debouncing to your automations. What you must configure is t...

#

Looks very complex to me

tired nacelle
#

I'm attempting a reconfigure now, I'm not at home - so not sure if I'll need to be home for it be successful or not. I did see those posts previously, but didn't look too much at them since I'm using a regular rocker wall switch and not a push button switch - but I'll look through them and see if maybe I can use the info in there to figure out how to configure mine. Thanks again! This is what I get in the log when using the switch:

image.png
#

The reconfigure failed, trying it again now. Interestingly it shows an onoff in the table, but it did not add the entity for it (maybe because it failed?). I'll keep reading through those articles to see if I can figure out how to work around this.

reconfigure_failed_1.png reconfigure_failed_2.png
tired nacelle
#

Unfortunately nothing useful in there, seems to be all about setting the device to work in push button mode. Mine is already set to single-rocker mode from being part of my Hue zigbee network. I'm thinking that my best bet at this point is to try removing it and re-adding it to try to get the On/Off entities to show up. I'll try that this weekend. 🤞

I'm also seeing mentions of z2mqtt, which I've never heard of. I already have mqtt running from a Frigate install - so maybe I should look into that. I saw someone say they are running both z2mqtt and zha in hopes of z2mqtt exposing more entities - so maybe I should look into setting that up and seeing if it exposes the OnOff entity on the RDM001?

tired nacelle
#

Another update: Looking at my RWL022 Hue Switches, those don't seem to have entities other than Battery and Identify listed under Diagnostic either 🤔 - they all have On and Off events though.

static thorn
#

Zigbee2MQTT is definitely better