Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Adding remotes, scene controllers as entities to MSR
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can't customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor

Adding remotes, scene controllers as entities to MSR

Scheduled Pinned Locked Moved Multi-System Reactor
31 Posts 4 Posters 4.6k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C christian_fabre

    Thanks ...
    I followed this post and managed to successfully use my HANK SCN04 remote with Reactor and Home Assistant.

    A Offline
    A Offline
    Andr
    wrote on last edited by
    #22

    @christian_fabre
    Happy to hear that it come to use (and that myself learned a few things on the way)
    😁

    1 Reply Last reply
    0
    • A Andr

      @toggledbits said in Adding remotes, scene controllers as entities to MSR:

      ||@andr said in Adding remotes, scene controllers as entities to MSR:

      And in that case, I guess that it would work to skip event data and just mapping commands to MSR functions?||

      I'm not sure what you mean by this. I don't think you want to skip anything. You should filter the incoming events, to make sure that you are handling the right events from the right device. So you need to be specific in the event filter to both the event type and the sending device.

      That was just me trying to understand how stuff is related, not something I would try out.
      For example, in my system there is only one device that are sending "Keypressed3x" and that can not be mixed up with anything else. In that case if I had such uniq string to map to MSR command 'triple' I could skip the filtering in event section?

      Again, this is just for my own curiosa trying to learn something new.

      toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #23

      @andr said in Adding remotes, scene controllers as entities to MSR:

      In that case if I had such uniq string to map to MSR command 'triple' I could skip the filtering in event section?

      No. You must filter. If you don't, every incoming event then causes the response section to act and will likely cause spurious changes of the entity data.

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      1 Reply Last reply
      0
      • C christian_fabre

        Thanks ...
        I followed this post and managed to successfully use my HANK SCN04 remote with Reactor and Home Assistant.

        A Offline
        A Offline
        apocalypsehobby
        wrote on last edited by
        #24

        @christian_fabre said in Adding remotes, scene controllers as entities to MSR:

        Thanks ...
        I followed this post and managed to successfully use my HANK SCN04 remote with Reactor and Home Assistant.

        @christian_fabre Do you mind sharing the code you used? I have two of the HANK SCN04 as well, and am trying to do the same thing

        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by toggledbits
          #25

          I believe that the following is a cleaned-up version of the final code (that which @Andr posted above is not indented properly as shown in these forums and won't work directly, so please use this instead):

          controllers:
            - id: hass
              implementation: HassController
              enabled: true
              name: Home Assistant
              config:
                source: 'ws://192.168.0.nnn:8123'
                # The lines above are a guide for indenting only, DO NOT COPY.
                # --- Start copy/paste from below this line ---
                event_targets: 
                  "hank_XXX_btn_1": 
                    name: "Hank XXX Button 1"
                    capabilities: 
                      - button
                    events: 
                      - event: 
                          event_type: zwave_js_value_notification
                          data: 
                            node_id: XXX  # Put your ZWaveJS node ID here
                            property: scene
                            property_key: "001"  #  001=button 1, 002=button 2, etc.
                        response: 
                          button.since: 
                            from: event.context.id
                          button.state: 
                            from: event.data.value
                            map: 
                              KeyHeldDown: hold
                              KeyPressed: single
                              KeyPressed2x: double
                              KeyPressed3x: triple
                              KeyReleased: release
                  "hank_XXX_btn_2": 
                    name: "Hank XXX Button 2"
                    capabilities: 
                      - button
                    events: 
                      - event: 
                          event_type: zwave_js_value_notification
                          data: 
                            node_id: XXX  # Put your ZWaveJS node ID here
                            property: scene
                            property_key: "002"  #  001=button 1, 002=button 2, etc.
                        response: 
                          button.since: 
                            from: event.context.id
                          button.state: 
                            from: event.data.value
                            map: 
                              KeyHeldDown: hold
                              KeyPressed: single
                              KeyPressed2x: double
                              KeyPressed3x: triple
                              KeyReleased: release
          

          You need to copy the lines beginning with event_targets: to the end, and paste them into the config section of the controllers entry for your HassController instance. You should change all instances of XXX to the ZWave node ID of your Hank controller. This will give you buttons 1 and 2. To add buttons 3 and 4, just copy-paste either button 1 or button 2 and modify the button number (property_key), entity name, and entity ID. One Reactor entity is created for each button you configure.

          If you are not well-versed in editing YAML, I suggest you make a backup copy of your config directory before making any changes.

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          A 1 Reply Last reply
          1
          • C Offline
            C Offline
            christian_fabre
            wrote on last edited by
            #26
            # If you have more than one of any type of controller, just copy the section for controller type
            # and give it new (unique) "id". There is no limit on the number of controllers.
            controllers:
            
              - id: hass
                enabled: true
                implementation: HassController
                name: A Home Assistant system
                config:
                  source: 'wss://XX.XX.XX.XX:8123'
                  access_token: "YYYYYYYYY"
                  #
                  event_targets:    # this section starts the event-receiving entities
                          "Hank_SCN04_bp1":      # Assign an ID to your entity; each entity must have a unique ID
                           name: Hank_bp1   # This is optional but recommended, so you have a friendly name
                           capabilities: ['button']  # define an array of capabilities to be modified by the event 
                           events:  # define an array of events that modify capability attributes on the entity
                             - event:  # start of an event; each element of the events array begins this way
                                 event_type: zwave_js_value_notification
                                 data:  # optional section, if further matching to the event data is required
                                   node_id: 12
                                   property: "scene" # Square button
                                   property_key: "001"
                               response:  # begin the (required) response section for handling the event
                                 "button.state":  # an attribute that the event modifies.
                                   from: "event.data.value"  # dot-reference expression to pull value from event message
                                   map:                    # optional, map to modify value
                                     KeyPressed: 'appui_court'   # if value is value_in, it is mapped to new_value
                                     KeyReleased: 'appui_relache'
                                     KeyHeldDown: 'appui_maintenu'
                                 "button.since":  # an attribute that the event modifies.
                                   from: "event.context.id"  # dot-reference expression to pull value from event message		
                          "Hank_SCN04_bp2":      # Assign an ID to your entity; each entity must have a unique ID
                           name: Hank_bp2   # This is optional but recommended, so you have a friendly name
                           capabilities: ['button']  # define an array of capabilities to be modified by the event 
                           events:  # define an array of events that modify capability attributes on the entity
                             - event:  # start of an event; each element of the events array begins this way
                                 event_type: zwave_js_value_notification
                                 data:  # optional section, if further matching to the event data is required
                                   node_id: 12
                                   property: "scene" # Square button
                                   property_key: "002"
                               response:  # begin the (required) response section for handling the event
                                 "button.state":  # an attribute that the event modifies.
                                   from: "event.data.value"  # dot-reference expression to pull value from event message
                                   map:                    # optional, map to modify value
                                     KeyPressed: 'appui_court'   # if value is value_in, it is mapped to new_value
                                     KeyReleased: 'appui_relache'
                                     KeyHeldDown: 'appui_maintenu'
                                 "button.since":  # an attribute that the event modifies.
                                   from: "event.context.id"  # dot-reference expression to pull value from event message
                          "Hank_SCN04_bp3":      # Assign an ID to your entity; each entity must have a unique ID
                           name: Hank_bp3   # This is optional but recommended, so you have a friendly name
                           capabilities: ['button']  # define an array of capabilities to be modified by the event 
                           events:  # define an array of events that modify capability attributes on the entity
                             - event:  # start of an event; each element of the events array begins this way
                                 event_type: zwave_js_value_notification
                                 data:  # optional section, if further matching to the event data is required
                                   node_id: 12
                                   property: "scene" # Square button
                                   property_key: "003"
                               response:  # begin the (required) response section for handling the event
                                 "button.state":  # an attribute that the event modifies.
                                   from: "event.data.value"  # dot-reference expression to pull value from event message
                                   map:                    # optional, map to modify value
                                     KeyPressed: 'appui_court'   # if value is value_in, it is mapped to new_value
                                     KeyReleased: 'appui_relache'
                                     KeyHeldDown: 'appui_maintenu'
                                 "button.since":  # an attribute that the event modifies.
                                   from: "event.context.id"  # dot-reference expression to pull value from event message
                          "Hank_SCN04_bp4":      # Assign an ID to your entity; each entity must have a unique ID
                           name: Hank_bp4   # This is optional but recommended, so you have a friendly name
                           capabilities: ['button']  # define an array of capabilities to be modified by the event 
                           events:  # define an array of events that modify capability attributes on the entity
                             - event:  # start of an event; each element of the events array begins this way
                                 event_type: zwave_js_value_notification
                                 data:  # optional section, if further matching to the event data is required
                                   node_id: 12
                                   property: "scene" # Square button
                                   property_key: "004"
                               response:  # begin the (required) response section for handling the event
                                 "button.state":  # an attribute that the event modifies.
                                   from: "event.data.value"  # dot-reference expression to pull value from event message
                                   map:                    # optional, map to modify value
                                     KeyPressed: 'appui_court'   # if value is value_in, it is mapped to new_value
                                     KeyReleased: 'appui_relache'
                                     KeyHeldDown: 'appui_maintenu'
                                 "button.since":  # an attribute that the event modifies.
                                   from: "event.context.id"  # dot-reference expression to pull value from event message
                  #
                  #
            

            I abruptly attach a copy of my file.
            I was inspired by the code given in the posts above
            It works correctly for me.

            1 Reply Last reply
            0
            • toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #27

              A couple of things:

              1. The indenting is incorrect. The parser may accept it, for now, but a future upgrade to the parser library may be more strict (I do not write the library, I just include it as a dependency). Use a tool like yamllint to fix it.
              2. You should not change the values in the map section. The values there are meant to map Hass' values into Reactor's values, and the Reactor-side values you have modified are not valid Reactor values for the button.state attribute. Valid values are defined by Reactor's button capability and include: single, double, triple, 4, 5, hold, release, and long. You should return these to the values originally given, and adjust your condition tests accordingly.

              Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

              1 Reply Last reply
              0
              • toggledbitsT toggledbits

                I believe that the following is a cleaned-up version of the final code (that which @Andr posted above is not indented properly as shown in these forums and won't work directly, so please use this instead):

                controllers:
                  - id: hass
                    implementation: HassController
                    enabled: true
                    name: Home Assistant
                    config:
                      source: 'ws://192.168.0.nnn:8123'
                      # The lines above are a guide for indenting only, DO NOT COPY.
                      # --- Start copy/paste from below this line ---
                      event_targets: 
                        "hank_XXX_btn_1": 
                          name: "Hank XXX Button 1"
                          capabilities: 
                            - button
                          events: 
                            - event: 
                                event_type: zwave_js_value_notification
                                data: 
                                  node_id: XXX  # Put your ZWaveJS node ID here
                                  property: scene
                                  property_key: "001"  #  001=button 1, 002=button 2, etc.
                              response: 
                                button.since: 
                                  from: event.context.id
                                button.state: 
                                  from: event.data.value
                                  map: 
                                    KeyHeldDown: hold
                                    KeyPressed: single
                                    KeyPressed2x: double
                                    KeyPressed3x: triple
                                    KeyReleased: release
                        "hank_XXX_btn_2": 
                          name: "Hank XXX Button 2"
                          capabilities: 
                            - button
                          events: 
                            - event: 
                                event_type: zwave_js_value_notification
                                data: 
                                  node_id: XXX  # Put your ZWaveJS node ID here
                                  property: scene
                                  property_key: "002"  #  001=button 1, 002=button 2, etc.
                              response: 
                                button.since: 
                                  from: event.context.id
                                button.state: 
                                  from: event.data.value
                                  map: 
                                    KeyHeldDown: hold
                                    KeyPressed: single
                                    KeyPressed2x: double
                                    KeyPressed3x: triple
                                    KeyReleased: release
                

                You need to copy the lines beginning with event_targets: to the end, and paste them into the config section of the controllers entry for your HassController instance. You should change all instances of XXX to the ZWave node ID of your Hank controller. This will give you buttons 1 and 2. To add buttons 3 and 4, just copy-paste either button 1 or button 2 and modify the button number (property_key), entity name, and entity ID. One Reactor entity is created for each button you configure.

                If you are not well-versed in editing YAML, I suggest you make a backup copy of your config directory before making any changes.

                A Offline
                A Offline
                apocalypsehobby
                wrote on last edited by
                #28

                @toggledbits wow, thank you.

                I've successfully added the Hank devices to the reactor.yaml file, along with a couple other remotes. Here are my notes for anyone else on this endeavor.

                • Hank HKZW-SCN04 has 4 buttons, and from my tests they do not support 2x or 3x clicks/presses.

                • Minoston MR40Z V1.0 has 4 buttons, and supports all of the presses that you mapped.

                • Zooz ZEN34 Ver. 1.0 has 2 buttons and supports all the presses that you mapped PLUS it has 4x and 5x presses as well.

                1 Reply Last reply
                1
                • A Offline
                  A Offline
                  apocalypsehobby
                  wrote on last edited by
                  #29

                  Hey friends - I'm trying this again with another remote, this time the ZB-5001 from RGB Genie.

                  It's not working yet, but I feel like I'm close. The device is successfully populating into MSR as an Entity, but when I press a button on the remote it does not report any changes to MSR.

                  Could you help me check my work?


                  DATA FROM HASSIO_EVENTS.LOG

                  • "endpoint_id" tells which button has been pressed (1-5)
                  • "cluster_id" seems to always stay at 6
                  • "command" shows whether you've pressed the "on" or "off" side of buttons 1-5
                  zha_event {
                  	"id": 1676585189844,
                  	"type": "event",
                  	"event": {
                  		"event_type": "zha_event",
                  		"data": {
                  			"device_ieee": "60:a4:23:ff:fe:65:a3:fb",
                  			"unique_id": "60:a4:23:ff:fe:65:a3:fb:2:0x0006",
                  			"device_id": "516aaf4459a4f4f319a178de36a28dfd",
                  			"endpoint_id": 1,
                  			"cluster_id": 6,
                  			"command": "on",
                  			"args": [],
                  			"params": {}
                  		},
                  		"origin": "LOCAL",
                  		"time_fired": "2023-02-16T22:07:24.518489+00:00",
                  		"context": {
                  			"id": "01GSE495V6J686X0RGXYZ046CG",
                  			"parent_id": null,
                  			"user_id": null
                  		}
                  	}
                  

                  MY BEST ATTEMPT AT THE CODE FOR REACTOR.YAML

                        event_targets: 
                          "RGBG-Remote-Button-1": 
                            name: "RGBG Remote Button 1"
                            capabilities: 
                              - button
                            events: 
                              - event: 
                                  event_type: zha_event
                                  data: 
                                    device_id: "516aaf4459a4f4f319a178de36a28dfd"
                                    endpoint_id: "1"
                                response: 
                                  button.since: 
                                    from: event.data.time_fired
                                  button.state: 
                                    from: event.data.command
                                    map: 
                                      on: on
                                      off: off
                  
                  A 1 Reply Last reply
                  0
                  • toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by
                    #30

                    "It's not working yet" isn't an adequate description of expectation vs observation, but I can tell right off your map is probably wrong.

                    map:
                      "on": true
                      "off": false
                    

                    The words on and off have special meaning in YAML and must be quoted here. The explicit words true and false for boolean values should be used.

                    Also, your since value should be put through the time() function, because that attribute is a timestamp, not a string.

                    If there are other problems, we'd need more narrative description to help lead us in the right direction.

                    And of course, you've checked the logs for helpful messages, right?

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    1 Reply Last reply
                    0
                    • A apocalypsehobby

                      Hey friends - I'm trying this again with another remote, this time the ZB-5001 from RGB Genie.

                      It's not working yet, but I feel like I'm close. The device is successfully populating into MSR as an Entity, but when I press a button on the remote it does not report any changes to MSR.

                      Could you help me check my work?


                      DATA FROM HASSIO_EVENTS.LOG

                      • "endpoint_id" tells which button has been pressed (1-5)
                      • "cluster_id" seems to always stay at 6
                      • "command" shows whether you've pressed the "on" or "off" side of buttons 1-5
                      zha_event {
                      	"id": 1676585189844,
                      	"type": "event",
                      	"event": {
                      		"event_type": "zha_event",
                      		"data": {
                      			"device_ieee": "60:a4:23:ff:fe:65:a3:fb",
                      			"unique_id": "60:a4:23:ff:fe:65:a3:fb:2:0x0006",
                      			"device_id": "516aaf4459a4f4f319a178de36a28dfd",
                      			"endpoint_id": 1,
                      			"cluster_id": 6,
                      			"command": "on",
                      			"args": [],
                      			"params": {}
                      		},
                      		"origin": "LOCAL",
                      		"time_fired": "2023-02-16T22:07:24.518489+00:00",
                      		"context": {
                      			"id": "01GSE495V6J686X0RGXYZ046CG",
                      			"parent_id": null,
                      			"user_id": null
                      		}
                      	}
                      

                      MY BEST ATTEMPT AT THE CODE FOR REACTOR.YAML

                            event_targets: 
                              "RGBG-Remote-Button-1": 
                                name: "RGBG Remote Button 1"
                                capabilities: 
                                  - button
                                events: 
                                  - event: 
                                      event_type: zha_event
                                      data: 
                                        device_id: "516aaf4459a4f4f319a178de36a28dfd"
                                        endpoint_id: "1"
                                    response: 
                                      button.since: 
                                        from: event.data.time_fired
                                      button.state: 
                                        from: event.data.command
                                        map: 
                                          on: on
                                          off: off
                      
                      A Offline
                      A Offline
                      apocalypsehobby
                      wrote on last edited by
                      #31

                      @toggledbits Thank you for helping, and that's more than fair.

                      I was pressing a button on the remote while viewing the Entity section of MSR, and the virtual device showed no change (the values stayed at "null"). I was expecting them to report on/off and to report the time change.


                      For others' reference, it is now working with the following code:

                            event_targets: 
                              "RGBG-Remote-Button-1": 
                                name: "RGBG Remote Button 1"
                                capabilities: 
                                  - button
                                events: 
                                  - event: 
                                      event_type: zha_event
                                      data: 
                                        unique_id: "60:a4:23:ff:fe:65:a3:fb:1:0x0006"
                                    response: 
                                      button.since: 
                                        expr: time()
                                      button.state: 
                                        from: event.data.command
                                        map: 
                                          "on": true
                                          "off": false
                      

                      Same goes for buttons 2-5, just tweak the value of "unique_id". Button 1 it ends with "1:0x0006" and button 2 would end with "2:0x0006", etc.

                      A caveat to this device is the on/off buttons at the very top send the same signal to HA as the "device 1 on/off" buttons (1:0x0006).

                      Here's a link to the device: https://rgbgenie.com/?product=rgbgenie-5-zone-remote-and-dimmer-zigbee

                      1 Reply Last reply
                      0
                      • toggledbitsT toggledbits locked this topic on
                      • A Andr referenced this topic on
                      • C cd12172 referenced this topic on
                      • PablaP Pabla referenced this topic on
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      Recent Topics

                      • Caution: zwave-js-ui docker 11.4.0 is broken
                        toggledbitsT
                        toggledbits
                        0
                        2
                        18

                      • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                        toggledbitsT
                        toggledbits
                        0
                        68
                        4.8k

                      • Shelly Wall Display XL
                        therealdbT
                        therealdb
                        2
                        6
                        85

                      • Handling Dead Entities and Renamed Entities
                        PablaP
                        Pabla
                        0
                        5
                        74

                      • Strange behavior for MQTT templates using payload and attributes
                        toggledbitsT
                        toggledbits
                        0
                        6
                        129

                      • [MSR] reactor-mqtt-contrib package for additional MQTT templates
                        therealdbT
                        therealdb
                        1
                        46
                        8.2k

                      • HA 2025.9.4 Supported Yet?
                        toggledbitsT
                        toggledbits
                        0
                        2
                        85

                      • The reaction stopped working (Google Nest max playing a video)
                        toggledbitsT
                        toggledbits
                        0
                        7
                        352

                      • Rule Set UI bug - RESOLVED
                        toggledbitsT
                        toggledbits
                        1
                        2
                        232

                      • [Reactor] Copy&Paste of Rules
                        therealdbT
                        therealdb
                        0
                        1
                        299

                      • [Reactor] Help with screne controller cycling logic
                        toggledbitsT
                        toggledbits
                        0
                        5
                        402

                      • Stop the MSR by an external switch on Hubitat.
                        Tom_DT
                        Tom_D
                        0
                        6
                        735
                      Powered by NodeBB | Contributors
                      Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Unsolved