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
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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 restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor

Adding remotes, scene controllers as entities to MSR

Scheduled Pinned Locked Moved Multi-System Reactor
31 Posts 4 Posters 2.4k 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #15

    But, still, I can't for some reason really understand the code and how different parts relate to each other.

    The event section is a filter to look for a specific event. In your version, you have multiple value keys, which is not allowed. Also, you don't want to filter by value, just accept them all and let the response section deal with them. I recommended against using label because it's changeable in ZWave, whereas the property and property_key values are defined by the device and will not change.

    So again, the event section is the filter that determines what incoming event will match, and what will not.

    Once an event matches, the response section determines what to do with it. Each component of the response section is an attribute of an assigned capability and the instructions to set it. In the case of button.state, my version says grab the value from event.data.value, and then, map that value from the device's string to one of Reactor's accepted capability/attribute value. Setting button.since completes the "contract" of the button capability (i.e. makes it work like similar uses of button in other devices and related to other controllers). I'm not sure I can explain it more simply than that.

    It's really just a "if you find this... do this" configuration. The effect is that if a matching button event is detected by the event section, the response section will interpet the value and map it to a Reactor-compatible value to place on the entity attribute button.state, and also update the button.since timestamp. Thus the since timestamp changes every time a button press event is received, but state may not change, because it's possible to press a button once, wait 15 seconds, and press the same button again, which will result in the value single being persistent on the state attribute and not changing. So to detect an event, you have to check both state and since (and this is consistent with all button behavior in Reactor).

    To test button state in a rule, you test button.state for what you want in that rule (equals single, double, triple), and you AND that test with a button.since changes (from any to any). That will send a very short pulse when a matching button press occurs. While testing, to make sure you can see it, add a "sustained for" delay on the changes condition of a few seconds (keep it short), and you'll more easily see what's going on in the status view. Make sure to remove the delay when you're done playing (keeping it will dampen response to buttons when, for example, a single press is done repeatedly within the delay period).

    Example here: https://smarthome.community/assets/uploads/files/1646184651741-cbff18f3-ce2d-4ecd-ae65-2554f77a4a80-image.png

    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
    0
    • toggledbitsT toggledbits

      But, still, I can't for some reason really understand the code and how different parts relate to each other.

      The event section is a filter to look for a specific event. In your version, you have multiple value keys, which is not allowed. Also, you don't want to filter by value, just accept them all and let the response section deal with them. I recommended against using label because it's changeable in ZWave, whereas the property and property_key values are defined by the device and will not change.

      So again, the event section is the filter that determines what incoming event will match, and what will not.

      Once an event matches, the response section determines what to do with it. Each component of the response section is an attribute of an assigned capability and the instructions to set it. In the case of button.state, my version says grab the value from event.data.value, and then, map that value from the device's string to one of Reactor's accepted capability/attribute value. Setting button.since completes the "contract" of the button capability (i.e. makes it work like similar uses of button in other devices and related to other controllers). I'm not sure I can explain it more simply than that.

      It's really just a "if you find this... do this" configuration. The effect is that if a matching button event is detected by the event section, the response section will interpet the value and map it to a Reactor-compatible value to place on the entity attribute button.state, and also update the button.since timestamp. Thus the since timestamp changes every time a button press event is received, but state may not change, because it's possible to press a button once, wait 15 seconds, and press the same button again, which will result in the value single being persistent on the state attribute and not changing. So to detect an event, you have to check both state and since (and this is consistent with all button behavior in Reactor).

      To test button state in a rule, you test button.state for what you want in that rule (equals single, double, triple), and you AND that test with a button.since changes (from any to any). That will send a very short pulse when a matching button press occurs. While testing, to make sure you can see it, add a "sustained for" delay on the changes condition of a few seconds (keep it short), and you'll more easily see what's going on in the status view. Make sure to remove the delay when you're done playing (keeping it will dampen response to buttons when, for example, a single press is done repeatedly within the delay period).

      Example here: https://smarthome.community/assets/uploads/files/1646184651741-cbff18f3-ce2d-4ecd-ae65-2554f77a4a80-image.png

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

      @toggledbits

      Ok, I understood it at first that I needed to specify more stuff in the event section, like 'value' so it then could be mapped to right command, otherwise it would not be known.

      But nodeid, property and property key is just to filter out right device, all the other data is still there?
      And in that case, I guess that it would work to skip event data and just mapping commands to MSR functions? (Of course nothing else can send 'Keypressed' command because that would be messy)

      toggledbitsT 1 Reply Last reply
      0
      • A Andr

        @toggledbits

        Ok, I understood it at first that I needed to specify more stuff in the event section, like 'value' so it then could be mapped to right command, otherwise it would not be known.

        But nodeid, property and property key is just to filter out right device, all the other data is still there?
        And in that case, I guess that it would work to skip event data and just mapping commands to MSR functions? (Of course nothing else can send 'Keypressed' command because that would be messy)

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

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

        But nodeid, property and property key is just to filter out right device, all the other data is still there?

        That's right. The event section only filters using the data; it does not modify the data or transform it in any way. Whatever is received in the event structure stays as received.

        @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.

        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
        0
        • toggledbitsT toggledbits

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

          But nodeid, property and property key is just to filter out right device, all the other data is still there?

          That's right. The event section only filters using the data; it does not modify the data or transform it in any way. Whatever is received in the event structure stays as received.

          @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.

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

          @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 1 Reply Last reply
          0
          • A Offline
            A Offline
            Andr
            wrote on last edited by toggledbits
            #19

            Anyway, some kinds of sucess the last nights 👍

            All buttons are configured and seems to work so far.

            The final reactor.yaml looks like this (just showing the first two buttons as it is just the entity name and 'property key' that differ )

            event_targets:    # this section starts the event-receiving entities
                    "Keyfob_Fyrkant":      # Assign an ID to your entity; each entity must have a unique ID
                      name: Lukas Keyfob Fyrkant   # 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: 15
                              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: 'single'   # if value is value_in, it is mapped to new_value
                                KeyPressed2x: 'double'
                                KeyPressed3x: 'tripple'
                                KeyHeldDown: 'hold'
                                KeyReleased: 'release'
                            "button.since":  # an attribute that the event modifies.
                              from: "event.context.id"  # dot-reference expression to pull value from event message
                    "Keyfob_Ring":      # Assign an ID to your entity; each entity must have a unique ID
                      name: Lukas Keyfob Ring   # 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: 15
                              property: "scene" # Circle 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: 'single'   # if value is value_in, it is mapped to new_value
                                KeyPressed2x: 'double'
                                KeyPressed3x: 'triple'
                                KeyHeldDown: 'hold'
                                KeyReleased: 'release'
                            "button.since":  # an attribute that the event modifies.
                              from: "event.context.id"  # dot-reference expression to pull value from event message
            

            A thought that crossed my mind recently, to maybe expand the functions of this little remote in the future.
            Fibaro have built in a possibilty for 6 extra scenes that activates after a sequence of button presses I specify. I have not activated this yet as I don't think I really need it, but what I realised is that it probably quite easy to add a lot of differnt button sequences in MSR as long or short that I want?

            Next part is to get some rules and actions set-up that can use the remote.

            1 Reply Last reply
            0
            • A Offline
              A Offline
              Andr
              wrote on last edited by Andr
              #20

              Seems to work like a charm 😁

              Started out with a few rules to let him control a Sonos in his room.
              This one is for starting his favorite playlist, when it not is bedtime and that playlist isn't already playing.

              c9770192-464f-4eb0-854f-9348e4b5b494-image.png

              1 Reply Last reply
              1
              • C Offline
                C Offline
                christian_fabre
                wrote on last edited by
                #21

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

                A A 2 Replies Last reply
                1
                • 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

                                    • Advice reqeusted to migrate MSR from Bare Metal to Container
                                      T
                                      tamorgen
                                      0
                                      5
                                      43

                                    • Reactor (Multi-System/Multi-Hub) Announcements
                                      toggledbitsT
                                      toggledbits
                                      5
                                      122
                                      35.4k

                                    • Z-Wave Future....
                                      CatmanV2C
                                      CatmanV2
                                      0
                                      5
                                      131

                                    • Can´t restart or upgrade/deploy MSR
                                      toggledbitsT
                                      toggledbits
                                      0
                                      4
                                      86

                                    • [Solved] Limit HA Entity in MSR
                                      wmarcolinW
                                      wmarcolin
                                      0
                                      7
                                      191

                                    • Disaster recovery and virtualisation
                                      CatmanV2C
                                      CatmanV2
                                      0
                                      5
                                      662

                                    • Remote access of Zwave stick from Z-wave server
                                      CatmanV2C
                                      CatmanV2
                                      0
                                      3
                                      384

                                    • Organizing/ structuring rule sets and rules
                                      G
                                      gwp1
                                      0
                                      5
                                      374

                                    • Moving MSR from a QNAP container to RP 5 - some issues
                                      G
                                      gwp1
                                      0
                                      5
                                      346

                                    • Widget deletion does not work and landing page (status) is empy
                                      G
                                      gwp1
                                      0
                                      4
                                      338

                                    • Need help reducing false positive notifications
                                      T
                                      tamorgen
                                      0
                                      7
                                      520
                                    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