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. Sunrise/Sunset data
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

Sunrise/Sunset data

Scheduled Pinned Locked Moved Multi-System Reactor
12 Posts 4 Posters 907 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.
  • S Offline
    S Offline
    SweetGenius
    wrote on last edited by
    #1

    I would like to be able to get the current sunrise or sunset times in human readable format from MSR so I can pass the values to Hubitat. I can set a variable on the Hubitat virtual omni sensor but I need some ideas of how to get the data. Is there a variable, expression or how do I convert
    suninfo.sunrise=1629978877000. Is there a better way? Thanks

    Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

    3 1 Reply Last reply
    0
    • S SweetGenius

      I would like to be able to get the current sunrise or sunset times in human readable format from MSR so I can pass the values to Hubitat. I can set a variable on the Hubitat virtual omni sensor but I need some ideas of how to get the data. Is there a variable, expression or how do I convert
      suninfo.sunrise=1629978877000. Is there a better way? Thanks

      3 Offline
      3 Offline
      3rdStng
      wrote on last edited by
      #2

      Hubitat is already aware of the sunrise and sunset time. This is determined by your Location settings. I'm not entirely sure how to pull it out, if you are looking to display it on a dashboard. If you go into System Events, you will see the Sunrise and Sunset times.2021-08-26_223226.jpg

      S 1 Reply Last reply
      0
      • 3 3rdStng

        Hubitat is already aware of the sunrise and sunset time. This is determined by your Location settings. I'm not entirely sure how to pull it out, if you are looking to display it on a dashboard. If you go into System Events, you will see the Sunrise and Sunset times.2021-08-26_223226.jpg

        S Offline
        S Offline
        SweetGenius
        wrote on last edited by
        #3

        @3rdstng Yes, Since I have moved my logic off of Hubitat to MSR, I wanted to have the actual source of my triggers displayed on the Hubitat dashboard as I still use that. The time might be slightly different between the two systems. Thanks

        Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

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

          Try establishing a Global Expression containing this definition:
          getEntity( "weather>default" ).attributes.wx

          The resulting object should include the data you seek.

          EDIT: Except, oops, it does not. Sorry, false start.

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

            I know that Sunset and Sunrise times are included with GET calls to:
            http://api.openweathermap.org/data/2.5/weather

            All you need is an API key and your ZIP code (or other identifier) in the calling URL.

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

              getEntity( "reactor_system>sun" ).attributes.suninfo.sunset (or .sunrise or .civil_dawn or ...) is the attribute you're looking for.

              I still haven't hooked up a strftime() function in the expressions. Let me take care of that today and I'll post a new build at the end of the day.

              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
              2
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #7

                strftime() is now part of new build 21239. docs

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

                S 1 Reply Last reply
                1
                • toggledbitsT toggledbits

                  strftime() is now part of new build 21239. docs

                  S Offline
                  S Offline
                  SweetGenius
                  wrote on last edited by SweetGenius
                  #8

                  The function strftime() works good. So now I have to say that I don't have a clue what I am doing with expressions. I created a global expression and it returns the correct value.
                  Screen Shot 2021-08-28 at 9.20.52 PM.png

                  I need some help on how to get this to Hubitat. I can pass data using a Virtual Omni Sensor in Hubitat and manually entering data in the x_hubitat_extra_commands.setVariable. I thought I could use the perfromAction but I am confused on how the expressions are supposed to work. It looks like it just assigns to a variable so I don't know how to do a performAction.

                  Screen Shot 2021-08-28 at 9.31.33 PM.png

                  Can someone give me some gentle advice so I can learn this?

                  Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

                  toggledbitsT 1 Reply Last reply
                  0
                  • S SweetGenius

                    The function strftime() works good. So now I have to say that I don't have a clue what I am doing with expressions. I created a global expression and it returns the correct value.
                    Screen Shot 2021-08-28 at 9.20.52 PM.png

                    I need some help on how to get this to Hubitat. I can pass data using a Virtual Omni Sensor in Hubitat and manually entering data in the x_hubitat_extra_commands.setVariable. I thought I could use the perfromAction but I am confused on how the expressions are supposed to work. It looks like it just assigns to a variable so I don't know how to do a performAction.

                    Screen Shot 2021-08-28 at 9.31.33 PM.png

                    Can someone give me some gentle advice so I can learn this?

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

                    @sweetgenius @sweetgenius Well, first, you're going to do either of the above actions, not both. And I would recommend against the performAction() expression, because it will execute every time the rule is evaluated, not just when the rule is set, which is guaranteed to be more frequent than that, and maybe annoyingly/incorrectly so.

                    The arguments for the freeform/native Hubitat action are Hubitat dependent/device implementation dependent, and I have no idea what they are... you need to look at the definition of the Omni sensor device, and specifically that action. But since most Hubitat actions only take one value, you might try leaving argument2 blank and using this for argument1: ${{ sunsetE }}

                    This will do a substitution with the value of sunsetE. Substitutions are mentioned in the documentation. Look at the reactor.log file to see what is sent and returned.

                    Since global variables are only updated when used, your sunsetE variable is not going to update automatically every day. This rule you are setting up needs to set daily after midnight at some point. This will both update sunsetE and cause it to be sent to the device.

                    Also, you can avoid the need for ltrim() in your expression by using %-l format for the hour. The - modifier removes padding.

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

                    S 1 Reply Last reply
                    1
                    • toggledbitsT toggledbits

                      @sweetgenius @sweetgenius Well, first, you're going to do either of the above actions, not both. And I would recommend against the performAction() expression, because it will execute every time the rule is evaluated, not just when the rule is set, which is guaranteed to be more frequent than that, and maybe annoyingly/incorrectly so.

                      The arguments for the freeform/native Hubitat action are Hubitat dependent/device implementation dependent, and I have no idea what they are... you need to look at the definition of the Omni sensor device, and specifically that action. But since most Hubitat actions only take one value, you might try leaving argument2 blank and using this for argument1: ${{ sunsetE }}

                      This will do a substitution with the value of sunsetE. Substitutions are mentioned in the documentation. Look at the reactor.log file to see what is sent and returned.

                      Since global variables are only updated when used, your sunsetE variable is not going to update automatically every day. This rule you are setting up needs to set daily after midnight at some point. This will both update sunsetE and cause it to be sent to the device.

                      Also, you can avoid the need for ltrim() in your expression by using %-l format for the hour. The - modifier removes padding.

                      S Offline
                      S Offline
                      SweetGenius
                      wrote on last edited by
                      #10

                      @toggledbits Yes, I was showing both to try to explain what I wanted to do and also the substitution did work in the argument1 box of the Omni sensor. The finished rule would be set to run after midnight.
                      Update, I went away from the Omni sensor and created hub variables on the Hubitat hub and made them visible to MSR. I am setting these variables with local expressions in the rule. Not sure if this is the best or most efficient way but it does work. Any other suggestions are welcomed but thank you for the help.
                      Here are the expressions.

                      Screen Shot 2021-08-29 at 4.56.46 PM.png

                      Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

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

                        Not recommended, as I said before, so use performAction in this way. The Entity Action action in the SET Reaction of your rule is the better choice.

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

                        S 1 Reply Last reply
                        1
                        • toggledbitsT toggledbits

                          Not recommended, as I said before, so use performAction in this way. The Entity Action action in the SET Reaction of your rule is the better choice.

                          S Offline
                          S Offline
                          SweetGenius
                          wrote on last edited by
                          #12

                          @toggledbits Whoops, I totally misread what you posted. I have corrected per you recommendations. Thanks

                          Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

                          1 Reply Last reply
                          0
                          • 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
                            135

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

                          • Error After Upgrade
                            G
                            gwp1
                            0
                            4
                            105

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

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

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

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

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

                          • 🎉 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
                            262
                          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