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. Entities - where used and what triggered it
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

Entities - where used and what triggered it

Scheduled Pinned Locked Moved Multi-System Reactor
5 Posts 3 Posters 401 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.
  • PerHP Offline
    PerHP Offline
    PerH
    wrote on last edited by PerH
    #1

    Haven't payed attention to the development for a while (and it seems to be progressing fast), is there a way to see where an entity is used, and what action used it recently?

    If not, it would be nice to have when things happen when they shouldn't, wether its because of bugs or bad logic. 🙂

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

      At the moment, if you turn the logging level for the "Rule" class (see more below) to 5 or higher (but 5 is enough), rules will log dependency notifications (entities or other data changing that cause them to re-evaluate). Looks like this (scroll to see the first line, in particular):

      2021-03-29T12:04:39.753Z <Rule:5:Rule.js:448> Rule#rule-grpy8wi802 requesting eval; entity-changed Entity#house>device_376
      2021-03-29T12:04:39.753Z <Rule:5:Rule.js:768> Rule#rule-grpy8wi802 (Dehumidifier Off) evaluate() acquiring mutex
      2021-03-29T12:04:39.753Z <Rule:5:Rule.js:774> Rule#rule-grpy8wi802._evaluate() mutex acquired, evaluating
      2021-03-29T12:04:39.753Z <Rule:5:Rule.js:782> Rule#rule-grpy8wi802 update rate is 3/min limit 60/min
      2021-03-29T12:04:39.753Z <Rule:5:Rule.js:627> Rule#rule-grpy8wi802 evaluateExpressions() with 0 expressions
      2021-03-29T12:04:39.753Z <Rule:5:Rule.js:810> Rule#rule-grpy8wi802._evaluate() trigger state now false (was false)
      

      In all likelihood, the logging of a changing entity starting a rule evaluation is going to get promoted to "info" level (4) and be a visible message in a default configuration (without changing log levels). But, as I'm working in the background on status tab info and trouble alerts, I'm experimenting with a more comprehensive way of reporting this on the UI. But this is what it is for now.

      For reactions, at the moment all actions against entities are logged unconditionally. That looks like this (notice the Engine:null entry and the line from VeraController that follows):

      2021-03-30T12:01:18.245Z <Engine:INFO> Enqueueing "Pump Run Conditions<RESET>" (rule-grpjx0sdf8:R)
      2021-03-30T12:01:18.245Z <Engine:NOTICE> Starting reaction Pump Run Conditions<RESET> [RuleReaction#rule-grpjx0sdf8:R]
      2021-03-30T12:01:18.245Z <Engine:null> _resume_reaction() entity house>device_373 (Recirc Pump Switch) perform power_switch.off({  }
      )
      2021-03-30T12:01:18.246Z <VeraController:null> VeraController#house enqueue task for Entity#house>device_373 action power_switch.off
      : task { "newTargetValue": "0", "DeviceNum": 373, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "Set
      Target" }
      2021-03-30T12:01:18.426Z <Engine:NOTICE> Resuming reaction Pump Run Conditions<RESET> from step 1
      2021-03-30T12:01:18.426Z <Engine:INFO> Pump Run Conditions<RESET> all actions completed.
      

      This does not require a change in the logging level for the Engine class (that runs reactions) right now. In future, it will also get a level 5 requirement, but, there already exists a monitored_entities in which you can place an array of (canonical) entity IDs for which the system will log all actions performed regardless of source (so by rule reaction, global reaction, or user action from the UI).

      reactor:
        baseurl: ... your other top-level configuration stuff
        engine:    # this line indented two spaces
          monitored_entities:
            - hass>light_test_dimmer_73
            - vera>device_10
            - hubitat>1
            - vera>device_254
      

      Changing Log Levels

      Logging is controlled by configuration in logging.yaml. Every object in the system can be logged either through its parent class or by individual object, so you can set a logging level for all rules, or for just one particular rule you are interested in. The structure of the file should be clear from the example in dist-config/logging.yaml.

      1. Rule #1: do not under any circumstances change the "default" logging level at the top of logging.yaml.
      2. Class- or object-based logging level can be changed by either modifying the level below the listed class or object, if it's already in the file. If it's not, add a class by indenting the class name with two space and following with a colon, and then on the following line add level: indented four spaces and your level (see example below). To add a specific object, such as a single rule, use the ID found in the UI status display and add it. And example of each is shown below:
        Rule:                     # this line is indented TWO spaces
          level: 5               # this line is indented FOUR spaces
        Rule#rule-kvjw8634:
          level: 6
      

      You can later return the log level to the default (4) or remove the entry entirely. If you set log levels high, remember to set them back down after troubleshooting or you'll be logging a lot of unnecessary data.

      More info on Logging here: https://reactor.toggledbits.com/docs/Logging/

      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
      • PerHP Offline
        PerHP Offline
        PerH
        wrote on last edited by PerH
        #3

        Ok, that will work. Thanks.

        Would be good to have a "quick look" somewhere in the UI though, specifically where reactor performs an action, not for all evaluations or change notifications.
        The usual scenario is that some light is turned off when it shouldn't, and i need to know what turned it off. (may not have been reactor at all)
        I.e a list of the 5 latest actions done on the entity at the bottom of the entity status list? with date/time and rule/reaction name?

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

          Yup, coming. For now, check the logs.

          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
          • 3 Offline
            3 Offline
            3rdStng
            wrote on last edited by
            #5

            I could use this "Where Used" feature as well. I have 3 Global Expressions that I don't think I have using, but want to make sure before I nuke them. I did not change my logging levels, but did search through all the reactor.log files and do not see anything. Is there a different way to see if they are in use, other than killing them and seeing what breaks?

            1 Reply Last reply
            1
            • toggledbitsT toggledbits locked this topic on
            • T tbully referenced 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
              77

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

            • Error After Upgrade
              G
              gwp1
              0
              4
              78

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

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

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

            • Links to MSR from HA
              Tom_DT
              Tom_D
              0
              1
              72

            • Set Reaction > Script Action
              wmarcolinW
              wmarcolin
              0
              11
              401

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

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

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

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