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. Intervals ? "Self Retriggering Timer" ?
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

Intervals ? "Self Retriggering Timer" ?

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 3 Posters 618 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.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #1

    Hi

    I am looking to create a rule that will run its actions every x minutes whilst I have a particular light turned on.

    As a test I created a rule with:

    Trigger - Light is turned ON

    Condition (Constraints) - Interval 1 minute

    adc31057-02e0-4e7f-a29a-633ca23e42d4-image.png

    Action - Send a TTS that says "One Minute"

    When I first turn on this light the rule then becomes true.

    On the rules summary card it says its waiting for the next minute and I can see it flashing green every minute, so the interval timer appears to be working OK

    d465ef8a-8db1-4f38-ba03-403d0a1165e5-image.png

    However the action "Set Reaction" is never run every minute as I wanted. In fact the action never ran at all and I never heard a TTS announcement.

    I have either set this up completely wrong which is more than likely or its a bug ?

    My end goal is to have a rule that runs some LUA code every 15 minutes when I turn on a particular light.

    Thanks

    toggledbitsT 1 Reply Last reply
    0
    • cw-kidC cw-kid

      Hi

      I am looking to create a rule that will run its actions every x minutes whilst I have a particular light turned on.

      As a test I created a rule with:

      Trigger - Light is turned ON

      Condition (Constraints) - Interval 1 minute

      adc31057-02e0-4e7f-a29a-633ca23e42d4-image.png

      Action - Send a TTS that says "One Minute"

      When I first turn on this light the rule then becomes true.

      On the rules summary card it says its waiting for the next minute and I can see it flashing green every minute, so the interval timer appears to be working OK

      d465ef8a-8db1-4f38-ba03-403d0a1165e5-image.png

      However the action "Set Reaction" is never run every minute as I wanted. In fact the action never ran at all and I never heard a TTS announcement.

      I have either set this up completely wrong which is more than likely or its a bug ?

      My end goal is to have a rule that runs some LUA code every 15 minutes when I turn on a particular light.

      Thanks

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

      @cw-kid @cw-kid The Interval condition is an "old" way of doing what the "Pulse" output mode of condition options does better. For your purpose, you can have a single condition that checks if the light is on, and put it into pulse output mode under options, with repeats. The condition will produce true pulses while the light is on, and stay false when the light is off. The Reaction will run accordingly.

      An interval cannot be used as a Constraint, at least, not like you've done it, because it naturally produces very short pulses (10 millisecond, in fact), so in order for your condition to work, the light would have to turn on during the 10ms pulse. Remember, constraints are only evaluated at the instant the trigger conditions attempt to set. If the constraints allowed the rule to run after the triggers became true previously, then they would not act like constraints and just act like more conditions in an AND group with the triggers.

      FYI, the pulse mode output also produces 10ms pulses naturally, so they are very hard to see in the UI. You can stretch them out by wrapping the condition in a group with a "delay reset" option of 1-2 seconds (or however long you want to watch).

      Ref: https://reactor.toggledbits.com/docs/Condition-Options/#output-control-options

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

      cw-kidC 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        @cw-kid @cw-kid The Interval condition is an "old" way of doing what the "Pulse" output mode of condition options does better. For your purpose, you can have a single condition that checks if the light is on, and put it into pulse output mode under options, with repeats. The condition will produce true pulses while the light is on, and stay false when the light is off. The Reaction will run accordingly.

        An interval cannot be used as a Constraint, at least, not like you've done it, because it naturally produces very short pulses (10 millisecond, in fact), so in order for your condition to work, the light would have to turn on during the 10ms pulse. Remember, constraints are only evaluated at the instant the trigger conditions attempt to set. If the constraints allowed the rule to run after the triggers became true previously, then they would not act like constraints and just act like more conditions in an AND group with the triggers.

        FYI, the pulse mode output also produces 10ms pulses naturally, so they are very hard to see in the UI. You can stretch them out by wrapping the condition in a group with a "delay reset" option of 1-2 seconds (or however long you want to watch).

        Ref: https://reactor.toggledbits.com/docs/Condition-Options/#output-control-options

        cw-kidC Offline
        cw-kidC Offline
        cw-kid
        wrote on last edited by
        #3

        @toggledbits said in Intervals ? "Self Retriggering Timer" ?:

        For your purpose, you can have a single condition that checks if the light is on, and put it into pulse output mode under options, with repeats. The condition will produce true pulses while the light is on, and stay false when the light is off. The Reaction will run

        Done that:

        55604903-ad3b-4dcb-bc24-275d33b0a1c5-image.png

        I can see it pulsing on the rules summary card.

        37017dbc-a124-4e37-ace6-2ded9615156a-image.png

        So the action should be run every time it pulses right ?

        I've only heard the TTS once. So the action has only run once.

        1 Reply Last reply
        0
        • cw-kidC Offline
          cw-kidC Offline
          cw-kid
          wrote on last edited by cw-kid
          #4

          You also have a small bug? In the Pulse if you actually enter 0 in the box that says "seconds,
          up to - times (0/blank=no limit)" and save the rule.

          When you go back in to that area later the 0 has gone and its blank.

          I know blank and 0 is the same thing, but as I'd manually entered a 0 in there I kind of expected it to still be there.

          Not a big issue at all just thought I'd mention it.

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

            No, you can't put the pulse in the Constraints either. You've got it backwards, and since the two conditions are the same, you don't need the Constraint at all, because pulse mode output has the built-in constraint you want: it only pulses when the condition test is true.

            You should have a single trigger condition for your light entity is TRUE with pulse output configured. Constraints should be empty.

            The removal of the zero on the option is intentional.

            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
            • cw-kidC Offline
              cw-kidC Offline
              cw-kid
              wrote on last edited by
              #6

              Sorry my bad, I've changed it to one trigger and deleted the constraint, its working now and the TTS is happening every X Minutes.

              Thank you.

              1 Reply Last reply
              0
              • cw-kidC Offline
                cw-kidC Offline
                cw-kid
                wrote on last edited by
                #7

                @toggledbits

                Seems to be working great at a 60 second repeat time. My LUA code placed directly in to the rules action is running every 60 seconds. I will try a repeat at every 15 minutes next which is what I actually wanted.

                Only other thing that might be nice to see, is a count down timer shown on the rules summary card for the repeat time. It does show a count down timer currently for the pulse time only which I have set to 10 seconds.

                Many thanks.

                1 Reply Last reply
                0
                • LibraSunL Offline
                  LibraSunL Offline
                  LibraSun
                  wrote on last edited by
                  #8

                  Funny, I just submitted a "Feature Request" on the bug tracker for a timestamp next to each Global Reaction so you can know when it last ran. I hadn't thought of the utility of a countdown timer for its next programmed run. Seems helpful!

                  1 Reply Last reply
                  0
                  • cw-kidC Offline
                    cw-kidC Offline
                    cw-kid
                    wrote on last edited by
                    #9

                    Well on this particular rule, If I glance at its summary card, I'd just like to see how long till the next repeat happens / the next time the LUA code in the action will be run.

                    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
                      141

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

                    • Error After Upgrade
                      G
                      gwp1
                      0
                      4
                      105

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

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

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

                    • Links to MSR from HA
                      Tom_DT
                      Tom_D
                      0
                      1
                      91

                    • Set Reaction > Script Action
                      wmarcolinW
                      wmarcolin
                      0
                      11
                      437

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

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

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

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