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. Flapping device
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

Flapping device

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 2 Posters 786 Views 2 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.
  • tunnusT Offline
    tunnusT Offline
    tunnus
    wrote on last edited by tunnus
    #1

    Got a warning that "Rule is being throttled because its update rate exceeds 60 updates per minute. Check for logic errors that may be causing an evaluation loop, or devices that are "flapping".

    Device in question here is Aeotec Smart Switch 6 connected to Vera Plus, and its configuration is below:

    Screenshot 2021-08-31 at 13.13.22.png

    Shouldn't be an evaluation loop as the rule is very simple (two AND'ed conditions where the first checks whether alarm state is "disarmed" and the second if smart switch power switch state is false).

    Noticed though at the time of warning that wattage measured/reported was changing quite rapidly, so even though wattage was not used in the rule, could that be the reason for throttling? If so, is there anything else that could be done other than raising minimum change values in device configuration? Would like to retain sensitivity for other purposes.

    Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

      We'd need to see the rule (and any rules/reactions that affect the device), not just the device, to make a determination about why it's flapping.

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

      tunnusT 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        We'd need to see the rule (and any rules/reactions that affect the device), not just the device, to make a determination about why it's flapping.

        tunnusT Offline
        tunnusT Offline
        tunnus
        wrote on last edited by
        #3

        @toggledbits here's the rule:

        Screenshot 2021-09-02 at 0.05.53.png

        Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

          Pretty straightforward. I'm guessing it's the percentage change that's the issue. With the threshold set at 10%, a change of just 1W when the total wattage is 10W or less will send an update, for example. Some deeper examination of the range in which the excess reports occur may lead you to better values for the configuration. A device that is generating that much traffic (more than one transaction per second) is probably going to lead to other problems in the mesh on Vera, since neither getting busy nor narrow timing are strong points of the Vera ZWave stack. You may be able to address momentary drops in power demand (such as when the motors pause) by using "delay reset" or "sustained for" options to dampen spikes and drops in the device's behavior. This would also then reduce the demand on the device for high accuracy and frequent updates, and let you configure these values to let it be less chatty. I mean, if you're using this to signal you when the wash is done, do you need to know to the second?

          If you really don't want to reconfigure the device, you can set the update rate higher in the engine section of reactor.yaml by setting update_rate_limit to some value higher than 60 (the default). That's a system-wide setting, so it applies to everything.

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

          tunnusT 1 Reply Last reply
          1
          • toggledbitsT toggledbits

            Pretty straightforward. I'm guessing it's the percentage change that's the issue. With the threshold set at 10%, a change of just 1W when the total wattage is 10W or less will send an update, for example. Some deeper examination of the range in which the excess reports occur may lead you to better values for the configuration. A device that is generating that much traffic (more than one transaction per second) is probably going to lead to other problems in the mesh on Vera, since neither getting busy nor narrow timing are strong points of the Vera ZWave stack. You may be able to address momentary drops in power demand (such as when the motors pause) by using "delay reset" or "sustained for" options to dampen spikes and drops in the device's behavior. This would also then reduce the demand on the device for high accuracy and frequent updates, and let you configure these values to let it be less chatty. I mean, if you're using this to signal you when the wash is done, do you need to know to the second?

            If you really don't want to reconfigure the device, you can set the update rate higher in the engine section of reactor.yaml by setting update_rate_limit to some value higher than 60 (the default). That's a system-wide setting, so it applies to everything.

            tunnusT Offline
            tunnusT Offline
            tunnus
            wrote on last edited by
            #5

            @toggledbits thanks for the analysis & advice! I'm actually using this rule for a simple task that it enables power back to washing machine when in disarmed state. There's a similar rule to cut the power when in "armed away" state.

            Not relating to MSR, but cannot seem to trigger configuration update for this smart switch:

            Screenshot 2021-09-02 at 11.37.59.png

            Did both "save changes" and "apply changes", but both only trigger luup reload and configuration stays the same...

            Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

              Hard refresh your browser after reloading Luup. It's a UI bug in UI7.

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

              tunnusT 2 Replies Last reply
              0
              • toggledbitsT toggledbits

                Hard refresh your browser after reloading Luup. It's a UI bug in UI7.

                tunnusT Offline
                tunnusT Offline
                tunnus
                wrote on last edited by
                #7

                @toggledbits did that, and also "configure node right now", nothing seems to change the actual configuration 😞

                Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

                1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  Hard refresh your browser after reloading Luup. It's a UI bug in UI7.

                  tunnusT Offline
                  tunnusT Offline
                  tunnus
                  wrote on last edited by
                  #8

                  @toggledbits Coming back to this, eventually I was able to change the configuration (below), but still, whenever the washing machine is running, I keep getting the same alerts.

                  Screenshot 2021-10-14 at 16.00.53.png

                  These two rules that are mentioned in the alerts do not even trigger at the time of alerts, because not all conditions are true (see previous posts, where washing machine power switch state should be false for the rule to be triggered).

                  Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

                  1 Reply Last reply
                  0
                  • toggledbitsT toggledbits locked this topic on
                  • wmarcolinW wmarcolin 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
                    132

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

                  • Error After Upgrade
                    G
                    gwp1
                    0
                    4
                    104

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

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

                  • 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
                    90

                  • Set Reaction > Script Action
                    wmarcolinW
                    wmarcolin
                    0
                    11
                    433

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

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

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

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