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. Device information in string or array
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
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
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
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
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

Device information in string or array

Scheduled Pinned Locked Moved Multi-System Reactor
18 Posts 4 Posters 1.2k Views 4 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
    #9

    Yes, that's what I am referring to as planned but not yet implemented in my earlier reply.

    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
    1
    • wmarcolinW Offline
      wmarcolinW Offline
      wmarcolin
      wrote on last edited by
      #10

      Ah, ok, thanks!

      1 Reply Last reply
      0
      • H Offline
        H Offline
        HansW
        wrote on last edited by toggledbits
        #11

        Well, I have been trying to use the above example to get a message reporting LAN connectivity failure of devices in my network.

        So I have set up an array with devices the Global expressions named DeviceTrackerList:

        ['hass>device_tracker_airport_time_capsule_van_hw','hass>device_tracker_airport_time_capsule_van_hw','hass>device_tracker_akita','hass>device_tracker_altherma_lan_adapter','hass>device_tracker_ap_bijkeuken' etc] 
        

        Then I run into problems defining the loop into a variable DeviceTrackerNotHome:

        each id in DeviceTrackerList:getEntity( id).state == not_home ? id: null
        

        Which returns the entire list. I have tried a few dozen of other options but either the entire list or an empty list is returned. Obviously my .state does not do the trick but what is the correct syntax to use here? (And where could I have found that myself?...)

        Then the next step is to use the names of the failing devices in a message.

        My last global variable is named DeviceTrackerMessage and holds

        join(each id in DeviceTrackerNotHome:getEntity(id).name, ', ')
        

        which returns a nice list of friendly names but I have no idea how to use that in my message.

        I expected { "message": {DeviceTrackerMessage} } to work but it did not and all other attempts to construct something failed as well.

        So I do hope someone can help here to point out to me what is probably obvious but difficult for a novice user to see. 🙂

        toggledbitsT 1 Reply Last reply
        0
        • H HansW

          Well, I have been trying to use the above example to get a message reporting LAN connectivity failure of devices in my network.

          So I have set up an array with devices the Global expressions named DeviceTrackerList:

          ['hass>device_tracker_airport_time_capsule_van_hw','hass>device_tracker_airport_time_capsule_van_hw','hass>device_tracker_akita','hass>device_tracker_altherma_lan_adapter','hass>device_tracker_ap_bijkeuken' etc] 
          

          Then I run into problems defining the loop into a variable DeviceTrackerNotHome:

          each id in DeviceTrackerList:getEntity( id).state == not_home ? id: null
          

          Which returns the entire list. I have tried a few dozen of other options but either the entire list or an empty list is returned. Obviously my .state does not do the trick but what is the correct syntax to use here? (And where could I have found that myself?...)

          Then the next step is to use the names of the failing devices in a message.

          My last global variable is named DeviceTrackerMessage and holds

          join(each id in DeviceTrackerNotHome:getEntity(id).name, ', ')
          

          which returns a nice list of friendly names but I have no idea how to use that in my message.

          I expected { "message": {DeviceTrackerMessage} } to work but it did not and all other attempts to construct something failed as well.

          So I do hope someone can help here to point out to me what is probably obvious but difficult for a novice user to see. 🙂

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

          @hansw said in Device information in string or array:

          each id in DeviceTrackerList:getEntity( id).state == not_home ? id: null

          The state part isn't right... everything from getEntity() to the question mark, in fact. Go to the Entities list, find one of the entities you have listed in DeviceTrackerList, and click on it to open its detail pane. You'll see the correct names of all the attributes listed there. Two things need to be fixed: (a) where you have getEntity( id ).state in the above example, you need to replace it with getEntity( id ).attributes.capabilityname.attributename (e.g. .attributes.x_hass.state or .attributes.x_hass_device_tracker.location_name); and (2) where you have not_home, there is probably no variable by that name, and I'm betting you actually meant to compare to a string here, so that needs to be surrounded in quotes: ... == "not_home"

          @hansw said in Device information in string or array:

          which returns a nice list of friendly names but I have no idea how to use that in my message.
          I expected { "message": {DeviceTrackerMessage} } to work

          The message would be something like:

          ${{ "Trackers not home: " + DeviceTrackerMessage }}
          

          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
          • H Offline
            H Offline
            HansW
            wrote on last edited by HansW
            #13

            Thanks again for your help @toggledbits. I had been looking at the wrong place (in HASS) for the entities but your pointer was a great help also for other uses of reactor. The expressions are working like a charm now.

            Still having trouble getting the JSON correct using the Variable though. I am using the x_hass_system.call_service and whatever I try it fails.

            The string looks like:
            { "title": "The following devices fail: ", "message": XXXX } Where at the location of the XXXX I probably need a trick to insert the DeviceTrackerMessage with surrounding double quotes but I don't have a clue.

            I even tried building the JSON into a global variable but it looks like the escape characters do not work or maybe I overlook something obvious.

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

              Show me all of the variables involved, and your rule and it's reactions. We'll work from the point you've arrived at.

              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
              • H Offline
                H Offline
                HansW
                wrote on last edited by
                #15

                Thanks @toggledbits , the variables I showed you in my earlier post and I corrected them zo they evaluate properly now into a string DeviceTrackerMessage which holds the friendly name of the devices offline, separated with comma's. As a string it does not have "" around it.

                My rule has a lot of Entity Attribute checks of all devices checked on x_hass.state <> home and combined into an OR.

                Then as a constraint I check the Variable Value DeviceTrackerMessage <> ""

                And then the Set Reaction holds:

                Entity Action hass>system x_hass_system.call_service with service: notify.my_device and the data: holding
                { "title": "Some devices failed: ", "message": XXXXX }

                Where on the position of XXXX I tried all I could think of.

                I know the rule might not be perfect yet but just testing the Set Reaction should generate a message. When replacing the XXXX with "test" I get a message.

                Also I tried adding a variable called JSONString and populating that using to JSON but I cannot get the result to look like a JSON string nor to work.

                Hope this helps.....

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

                  The data field requires either a string that can be parsed as JSON data, or (works but not documented), you can pass an object from an expression. Both of these will require that you use a substitution to get the object or string into the field.

                  My suggestion is that you minimize the need to understand quoting, etc. by creating another variable to house the data object, and pass that variable in the Entity action. Two steps:

                  1. Create an expression (could be local or global) called notify_data defined as follows:

                     { "title": "Some devices failed", "message": DeviceTrackerMessage }
                    
                  2. To insert that into your Entity Action, set the data field to ${{ notify_data }}

                  That's what I would consider to be the "easy" way, which is a little longer than the most direct route, but easier (I think) to understand (and support/remember in future). The first step creates an object with two keys and sets their values: the title is a string, and the message is the value of DeviceTrackerMessage (no quotes around that name means it's a variable reference). The second step passes the object to the data field.

                  The other way would simply be to set the data field in your action to the JSON string directly in one step. There are several ways to do this, and one of them is to use a similar approach to what we've done above, and just have the stringify() function convert it to JSON for us (that's what it does). Set the data field in your Entity Action to:

                  ${{ stringify( { "title": "Some devices failed", "message": DeviceTrackerMessage } ) }}
                  

                  You should be able to see the similarity here. The interior object definition creates an object with two keys, title and message, and their particular values. That is passed to stringify(), which converts it to JSON, and that result string becomes the value of the field passed to Hass on the service call.

                  You can also do this without stringify(), but it's more complicated. We have to build the JSON string ourselves and insert the data from DeviceTrackerMessage into it using string concatenation, with careful use of different quotes for different purposes (the tricky part):

                  ${{ '{ "title": "Some devices failed", "message": "' + DeviceTrackerMessage + '" }' }}
                  

                  Notice that before and after + DeviceTrackerMessage + we have double quotes inside single quotes (hard to see, especially at the end). But this would also work, provided DeviceTrackerMessage does not contain any double quotes itself. Quoting can be hard to get right, especially for new players, so I generally try to find solutions that avoid it, which is why I put the other two solutions first on my list.

                  Edit: heh... actually, an even shorter version of my first alternative is to not use stringify() at all and just create and pass the object on the fly... set data field to this:

                  ${{ { "title": "Some devices failed", "message": DeviceTrackerMessage } }}
                  

                  That's about as direct as it gets -- you're creating and passing the data object in one step, there is no need to convert it to a JSON string because you can pass the object directly. For clarity, no additional variable needs to be created, either. I think I like this best.

                  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
                  • H Offline
                    H Offline
                    HansW
                    wrote on last edited by
                    #17

                    Thanks a lot for your elaborate answer and explanation @toggledbits! I do appreciate this and it helps me further, also with other issues, to make better use of your wonderful tool! I was not aware of this ${{ }} construction and I have no idea from which language this syntax is but I guess it forces the bit in between to be evaluated.

                    Anyway, it solved the problem! Thanks a lot!!

                    toggledbitsT 1 Reply Last reply
                    1
                    • H HansW

                      Thanks a lot for your elaborate answer and explanation @toggledbits! I do appreciate this and it helps me further, also with other issues, to make better use of your wonderful tool! I was not aware of this ${{ }} construction and I have no idea from which language this syntax is but I guess it forces the bit in between to be evaluated.

                      Anyway, it solved the problem! Thanks a lot!!

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

                      @hansw said in Device information in string or array:

                      I was not aware of this ${{ }} construction and I have no idea from which language this syntax is but I guess it forces the bit in between to be evaluated.

                      That is exactly what it does, and the value that results become the value of that field for the action. Similar syntax is used in many applications (it's not really a language feature as much as it is an application feature), among them Home Assistant. Reactor for Vera used plain { } but this was problematic because the more robust expression language of MSR uses those characters.

                      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
                      1
                      • toggledbitsT toggledbits locked this topic on
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      Recent Topics

                      • Gradually turn on lights.
                        G
                        gwp1
                        0
                        4
                        127

                      • Stop the MSR by an external switch on Hubitat.
                        wmarcolinW
                        wmarcolin
                        0
                        1
                        27

                      • Error After Upgrade
                        G
                        gwp1
                        0
                        4
                        101

                      • Reset attribute value of entity in event handler
                        R
                        RHCPNG
                        0
                        5
                        197

                      • Need help figuring out how to delay a reset on reaction
                        G
                        gwp1
                        0
                        22
                        923

                      • Way to search for rules (rule state) in other rules
                        T
                        tamorgen
                        0
                        3
                        99

                      • Links to MSR from HA
                        Tom_DT
                        Tom_D
                        0
                        1
                        88

                      • Set Reaction > Script Action
                        wmarcolinW
                        wmarcolin
                        0
                        11
                        431

                      • Wiring Samotech SM308-S into light fitting
                        akbooerA
                        akbooer
                        0
                        2
                        142

                      • Errors after updating to MQTTController build 25139
                        toggledbitsT
                        toggledbits
                        0
                        6
                        236

                      • 🎉 My very first MSR controller: OpenSprinkler
                        therealdbT
                        therealdb
                        5
                        13
                        915

                      • Advice reqeusted to migrate MSR from Bare Metal to Container
                        T
                        tamorgen
                        0
                        5
                        257
                      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