Zigbee2MQTT - RGBGenie Remote Control - ZB-5001/5004 4/5 Zone Dimmer ZB-5008/ZB-5028 RGBW 4 Zone Color Wheel and controls blueprint - all actions + should support other multi-zone Remote Controls and Wall Panels (Iluminize/Namron/Sunricher/Muller)

Finally figured out why… now the next question. They are X/Y values… how does one convert to RGB? Is it using CIE or ?

Have a look at the Zigbee2MQTT IKEA 5 Button Remote blueprints. From memory, the author covered all different color spaces, but I can’t remember the details.

I’ll take a look and see if I can find it. Thanks

Hello,
Do you think your bluescript could work with this remote Control ?

And could it be adapted for a conbee stick (I don’t use zigbee2mqtt)
Thank you

It “looks” the same as the ZB-5001/4 remote, so would probably be a reasonable bet. Re Conbee, my understanding (might be wrong) is that it also uses the Zigbee protocol, so it would be a matter of a. device support within Conbee, and the messaging protocol back to HomeAssistant. I’d be confident that it could be adapted, but I don’t know enough to advise.

I love the blueprint and really want to get my RGBGenie ZB-5028 working with my light group. But it’s trhowing the following error, and I am unable to diagnose the problem. Any suggestions? Thanks in advance!

Source: helpers/template.py:540 
First occurred: January 28, 2023, 2:22:15 PM (78 occurrences) 
Last logged: 12:22:13 AM

Template variable error: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'action' when rendering '{% if remote_type_zb_5004 %} {{ trigger.to_state.attributes.action in ('off', 'on', 'brightness_move_down', 'brightness_move_up', 'brightness_stop', 'recall_1', 'recall_2' ) }} {% else %} {{ trigger.to_state.attributes.action.find('_') != -1 }} {% endif %}'

Here is the corresponding code from automations.yaml

  alias: Z2M - RGBGenie ZB-5008/5028 or ZB-5004 4 Zone Remote 1.1
  description: ''
  use_blueprint:
    path: bayview252/rgbgenie-zb-5004-and-zb-5028-combined.yaml
    input:
      remote: sensor.rgbgeniezb5028_action
      zb_5004: false
      helper_stop_button: input_boolean.rgbgenie_automation_helper
      scene_1_1:
        entity_id: scene.daytime_bright_orange_light
      scene_1_2:
        entity_id: scene.early_morning_dim_red_light
      light_group_1:
        entity_id: light.rgb_lights

So, quick glance at the above.

Could you confirm what device is registering when paired. Also confirm if you are using zigbee2mqtt?

Device type will allow you to look inside the zigbee2mqtt device converters to see how the button press is being interpreted before being passed to MQTT broker in HA.

I would use something like MQTT Explorer to have a look at the messages your button press(es) is/are generating and see where that takes you.

2nd thing would be to monitor the topics in the Developer Tool section within Home Assistant, and make sure they match.

Full description on the how to’s is beyond me as I set these up a while back, and don’t have a lot of spare time nowdays.

Thanks, Gerry! I understand time pressures, so any of your time is very much appreciated.

The MQTT Integration in HA shows:

RGB remote with 4 endpoints and 3 scene recalls (ZB-5028)
by RGB Genie
Firmware: 2.2.3_r12

It’s paired with Zigbee2MQTT and here’s what Z2M reports:

Description Product ID: ZB-5028 www.RGBgenie.com (520)-338-8849
Last seen N/A
Availability [Disabled](https://www.zigbee2mqtt.io/guide/configuration/device-availability.html#availability-advanced-configuration)
Device type EndDevice
Zigbee Model RGBgenie ZB-5028
Zigbee Manufacturer RGBgenie
Description RGB remote with 4 endpoints and 3 scene recalls
Support status Supported
IEEE Address 0x000d6f001668b688
Network address 0x2884
Firmware build date NULL
Firmware version 2.2.3_r12
Manufacturer [RGB Genie](https://www.zigbee2mqtt.io/supported-devices/#v=RGB%20Genie)
Model [ZB-5028](https://www.zigbee2mqtt.io/devices/ZB-5028.html#rgb%2520genie-zb-5028)
Power Battery 100%
Interview completed True

The device was paired with Z2M with all defaults and I’ve confirmed that there are no Z2M filters set.

FYI, in case this is helpful, Z2M reports the state as

    "battery": 100,
    "brightness_2": 159,
    "linkquality": 100,
    "voltage": 3800,
    "action": "",
    "action_color": {
        "x": 0.201,
        "y": 0.243
    },
    "action_group": 33795,
    "action_transition_time": 0,
    "action_color_temperature": 230
}

Under the MQTT integration settings “Listen to a Topic,” and pressing the power button once:

zigbee2mqtt/RGBGenieZB5028
 
Message 1 received on zigbee2mqtt/RGBGenieZB5028 at 8:30 AM:
{
    "action": "",
    "battery": 100,
    "brightness_2": 159,
    "linkquality": 112,
    "voltage": 3800
}
QoS: 0 - Retain: false

Message 0 received on zigbee2mqtt/RGBGenieZB5028 at 8:30 AM:
{
    "action": "on_1",
    "battery": 100,
    "brightness_2": 159,
    "linkquality": 112,
    "voltage": 3800
}
QoS: 0 - Retain: false

Here’s one thing that I am wondering about:

[sensor.rgbgeniezb5028_action] doesn’t appear to have any other attributes besides icon and friendly_name, according to the States page in HA. But the code seems to be expecting that it has an action attribute.

Well, thanks for taking a look!

Michael

Ok, MQTT is seeing the action attribute, so that’s good. Looks like when you paired the device, for some reason, Home Assistant decided either not to register the “action” attribute OR zigbee2mqtt did not expose the attribute. I don’t think it is “case 3”: that the attribute is disabled within HA, but you could check that in Settings>Device page for the remote, and look in Diagnostics. Link Quality is disabled in my example.


You could delete the device from Z2M, and re-pair. Sometimes that is all that is required, but check Z2M Debug logs, see what’s in there when re-pairing.
Check for other debugging info on how to debug the setup of Home Assistant Device/Entities with Z2M. Good luck!

I am in the market for remote control that can control up to 4 lights through Home Assistant. I’m being a little cautious as I had bought another device but it turned out to want to act as a secondary controller which does not appear to be compatible with Home Assistant. Can you confirm the ZB-5001 or 5004 work as an Zigbee endpoint device? The company web site describes the direct control of light bulbs and doesn’t highlight their use with a system such as Home Assistant.

Also reading through the above posts, I don’t see where anyone has actually used this with a ZB-5001, but it looks as if you have it working with a ZB-5004, so if this is working in someone’s setup, I might take a chance on it.

Just looking for more information in hopes of avoiding past mistakes. Any input you can provide is appreciated. Thanks.

I won’t guarantee the ZB-5001, as I don’t have one myself, but it works perfectly with the 5004. I would be incredibly surprised if it doesn’t work. If you have issues, post here, and I’ll be happy to help out with diagnostics, etc.

Thanks for the confirmation. I’ll go ahead and order a 5004 and give it a shot. I’ll try and post back with the results.

Ordered a 5004 and after 3 weeks I cancelled the order as it hasn’t shipped and there was no communication from the vendor.
I have now placed an order for a Vesternet 8 button remote that per the web site is compatible with Home Assistant. Guess I’ll find out.

edit: wrong link above. There is a Zigbee version which is the one I ordered.

That should work fine. It’’s a white labelled Sunricher according to the Herdsman converter js. Good luck

Received the Vesternet (Sunricher) remote and was able to create an automation using your blueprint. Thanks for the blueprint and the assistance!

1 Like

Hello Rich, how did you manage to integrate the Zigbee remote control into Home Assistant using the blueprint? Unfortunately, my remote control doesn’t provide an “action_group” or any other five-digit number. I think we’re using the same remote control, but it doesn’t work for me even if I leave the blueprint as it is (Vesternet Zigbee Remote Control - 12 Button).

To answer your question, yes, I have the Vesternet 12 button remote working with this blueprint. I’m trying to remember what I did to get it to work, but not getting too far, so here is my working config. Note that I creatively called my remote control - “Remote 1”.

Hey, thanks for your response. I have obviously set up the same as you, but unfortunately, I’m getting an error saying that the remote control doesn’t have an “action.”

Hi Fabian, that means that the template logic is not able to extract the string correctly. That could be due to a number of reasons such as the incorrect zigged converter being used when you first paired the device, or a different firmware / update from the manufacturer that has changed the messaging.

Have a look at the messages above starting from Zigbee2MQTT - RGBGenie Remote Control - ZB-5001/5004 4/5 Zone Dimmer ZB-5008/ZB-5028 RGBW 4 Zone Color Wheel and controls blueprint - all actions + should support other multi-zone Remote Controls and Wall Panels (Iluminize/Namron/Sunricher/Muller) - #17 by Blasphemes

This gave some basic steps to determine some initial information. Also, if you can provide some logs, and command history from MQTTExplorer, that would be helpful also.

debug 2023-11-05 17:34:48: Received Zigbee message from 'Dimmer_remote_2', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 2 with groupID 2
info  2023-11-05 17:34:48: MQTT publish: topic 'zigbee2mqtt/Dimmer_remote_2', payload '{"action":"on","action_group":2,"battery":18.5,"linkquality":72}'

I monitor this topic occasionally, so if I don’t answer immediately, you’ll know why.

Cheers.

Of course, I understand that your time is valuable, just as mine is. That’s why I appreciate any additional help or information. It’s not always guaranteed to receive assistance these days.

The MQTT Integration in HA shows:

Zigbee remote control - 12 button (VES-ZB-REM-013)
von Vesternet
Firmware: 2.5.3_r20

The Zigbee2MQTT Log:

Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"on_1","battery":50,"linkquality":184}'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":184}'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'on_1'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"on_2","battery":50,"linkquality":184}'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"on_3","battery":50,"linkquality":184}'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":184}'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":184}'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'on_2'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'on_3'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"on_4","battery":50,"linkquality":184}'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":184}'
Info 2023-11-05 09:28:21MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'on_4'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"off_1","battery":50,"linkquality":188}'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":188}'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'off_1'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"off_2","battery":50,"linkquality":188}'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"off_3","battery":50,"linkquality":188}'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":188}'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":188}'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'off_2'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'off_3'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"off_4","battery":50,"linkquality":188}'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":188}'
Info 2023-11-05 09:28:24MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'off_4'
Info 2023-11-05 09:28:27MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"on_1","battery":50,"linkquality":164}'
Info 2023-11-05 09:28:27MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":164}'
Info 2023-11-05 09:28:27MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'on_1'
Info 2023-11-05 09:28:28MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"off_1","battery":50,"linkquality":180}'
Info 2023-11-05 09:28:28MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung', payload '{"action":"","battery":50,"linkquality":180}'
Info 2023-11-05 09:28:28MQTT publish: topic 'zigbee2mqtt/Versternet Fernbedienung/action', payload 'off_1'

The MQTT Explorer History:

05.11.2023 09:28:28 
{"action":"","battery":50,"linkquality":180}
05.11.2023 09:28:28(-0 seconds) 
{"action":"off_1","battery":50,"linkquality":180}
05.11.2023 09:28:27(-1.27 seconds) 
{"action":"","battery":50,"linkquality":164}
05.11.2023 09:28:27(-0 seconds) 
{"action":"on_1","battery":50,"linkquality":164}
05.11.2023 09:28:24(-2.73 seconds) 
{"action":"","battery":50,"linkquality":188}
05.11.2023 09:28:24(-0 seconds) 
{"action":"off_4","battery":50,"linkquality":188}
05.11.2023 09:28:24(-0.01 seconds) 
{"action":"","battery":50,"linkquality":188}
05.11.2023 09:28:24(-0 seconds) 
{"action":"","battery":50,"linkquality":188}
05.11.2023 09:28:24(-0 seconds) 
{"action":"off_3","battery":50,"linkquality":188}
05.11.2023 09:28:24(-0 seconds) 
{"action":"off_2","battery":50,"linkquality":188}
05.11.2023 09:28:24(-0.02 seconds) 
{"action":"","battery":50,"linkquality":188}
05.11.2023 09:28:24(-0 seconds) 
{"action":"off_1","battery":50,"linkquality":188}
05.11.2023 09:28:21(-2.73 seconds) 
{"action":"","battery":50,"linkquality":184}
05.11.2023 09:28:21(-0 seconds) 
{"action":"on_4","battery":50,"linkquality":184}
05.11.2023 09:28:21(-0.02 seconds) 
{"action":"","battery":50,"linkquality":184}
05.11.2023 09:28:21(-0 seconds) 
{"action":"","battery":50,"linkquality":184}
05.11.2023 09:28:21(-0 seconds) 
{"action":"on_3","battery":50,"linkquality":184}
05.11.2023 09:28:21(-0 seconds) 
{"action":"on_2","battery":50,"linkquality":184}
05.11.2023 09:28:21(-0.02 seconds) 
{"action":"","battery":50,"linkquality":184}
05.11.2023 09:28:21(-0.01 seconds) 
{"action":"on_1","battery":50,"linkquality":184}

It’s paired with Zigbee2MQTT and here’s what Z2M reports:

Device Name
Vesternet Remote Control
Description
Last Seen
N/A
Availability
Online
Device Type
End Device
Zigbee Model
ZGRC-KEY-013
Zigbee Manufacturer
Sunricher
Description
Zigbee remote control - 12 button
Support Status
Supported

IEEE Address
0x842e14fffe900159
Network Address
0x2241
Firmware Date
NULL
Firmware Version
2.5.3_r20
Manufacturer
Vesternet
Model
VES-ZB-REM-013
Power Supply
Battery 50%
Interview Successful
True

Edit: I removed the remote control from Z2M twice and reset it to factory settings, then reconnected it. The logs show neither more nor less than before.