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. identifying when MSR cannot connect to Home Assistant
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
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
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

identifying when MSR cannot connect to Home Assistant

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

    Hello,

    Likely this is already in MSR, but I am trying to catch when Home Assistant crashes in MSR and power cycle the Pi it is running on. I have something causing instability in my Home Assistant and it becomes unresponsive once or twice a day. In MSR I get a red alert on the title bar and in the current alerts, but not seeing how I can use that as a trigger in MSR. What should I be monitoring?
    Thanks,

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

      Second time today this question was asked, each for a different platform, but the answer is the same.

      I really want you guys to think about this. Two things to consider:

      1. Since you can easily write conditions based on the changes of attributes to entities, is there an entity that maps to your system controller instance, and does it have attributes that might help? (Hint: yes)
      2. Recently, the alerts data were added as attributes of the Reactor System entity, and this discussion ensued. I won't say this is the recommended way to get it done; it's the lesser of the two in my view, but it is a possibility. And that conversation/thread actually began with exactly the same question that started this one.

      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
      • toggledbitsT toggledbits

        Yes, there are at least two ways to do that now. Any thoughts on where you might look?

        Edit: Same question as this thread: https://smarthome.community/topic/832/identifying-when-msr-cannot-connect-to-home-assistant

        And this thread is wandering, so maybe let's leave it alone.

        wmarcolinW Online
        wmarcolinW Online
        wmarcolin
        wrote on last edited by
        #3

        @toggledbits done!

        44a334a7-b0d4-4849-9efb-acfb198cb8b6-image.png

        Thanks!

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

          Well, that's one way. Not the best way IMO, but it works. It has the advantage of capturing a lot of different circumstances, not just the one you asked about.

          By the way, you have installed the recommended here and here Hub Information app, right?

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

          wmarcolinW 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Well, that's one way. Not the best way IMO, but it works. It has the advantage of capturing a lot of different circumstances, not just the one you asked about.

            By the way, you have installed the recommended here and here Hub Information app, right?

            wmarcolinW Online
            wmarcolinW Online
            wmarcolin
            wrote on last edited by
            #5

            @toggledbits yes, all!!

              - id: hubitat
                enabled: true
                implementation: HubitatController
                name: Hubitat Elevation system
                config:
                  # Copy the entire URL from the Maker API app page on your Hubitat UI. A quick, easy way is to
                  # right-click the "Get All Devices" link and choose "Copy link location", the paste it below.
                  source: "http://192.168.33.22/apps/api/131/devices?access_token=fc________________65"
                  #
                  # dump_all_devices - This is for troubleshooting. Do not enable unless asked.
                  dump_all_devices: false
                  # OPCIONAL TEMPORIZADOR ENTRE ACOES - 0,500s entre acoes - ou 2 acoes por segundo
                  action_pace: 100
                  warn_unresponsive: true
                  probe_device: hubitat>132
                  probe_action: x_hubitat_Configuration.configure
            
            

            I limited Hubitat's warning, because there have been no other mistakes, so when it happens, I will understand and take action.

            I also have yet to explore the gain of having monitoring by Hub Information, which can really help me keep up with the platform. I understand that for the connection issue it helps, now what else could it be doing that would be useful? Any suggestions?

            Thanks.

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

              If you have Hub Information installed and have created a device for it, and published that device in Maker API, you do not need to set probe_device or probe_action — HubitatController will know what to do with the device when it sees it.

              Hub Information will , for example, let you make a rule that notifies you when an update is available (assuming you don't regularly log in to your hub's UI to see that). Browse the attributes in the entity. See what you might find, and let your imagination run wild!

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

                OK, what's missing here is that the fastest and simplest way to see if a hub connection is to check the sys_system.state attribute on the hub's system entity (all controllers make two entities by default: the system entity, and a group entity). If it's false, the hub connection is down; if it's true, the hub connection is up. Some hubs have additional capabilities and attributes:

                • VeraController — x_vera_sys.reloads increments/changes every time Luup reloads;
                • HubitatController — x_hubitat_sys.reconnects increments/changes every time Reactor has to reconnect to the hub;
                • EzloController — x_ezlo_sys.reconnects increments/changes every time Reactor has to reconnect to the hub; x_ezlo_sys.restarts increments/changes each time the hub reloads/restarts;

                These can be more specific, and easier, tests than scanning the alerts array on the Reactor System device (which is why I prefer these over that method). You will also get fewer "false positives", as the approach @wmarcolin shows will catch any notification with the word "Hubitat" in it, and those may not all be connection-related.

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

                wmarcolinW 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  OK, what's missing here is that the fastest and simplest way to see if a hub connection is to check the sys_system.state attribute on the hub's system entity (all controllers make two entities by default: the system entity, and a group entity). If it's false, the hub connection is down; if it's true, the hub connection is up. Some hubs have additional capabilities and attributes:

                  • VeraController — x_vera_sys.reloads increments/changes every time Luup reloads;
                  • HubitatController — x_hubitat_sys.reconnects increments/changes every time Reactor has to reconnect to the hub;
                  • EzloController — x_ezlo_sys.reconnects increments/changes every time Reactor has to reconnect to the hub; x_ezlo_sys.restarts increments/changes each time the hub reloads/restarts;

                  These can be more specific, and easier, tests than scanning the alerts array on the Reactor System device (which is why I prefer these over that method). You will also get fewer "false positives", as the approach @wmarcolin shows will catch any notification with the word "Hubitat" in it, and those may not all be connection-related.

                  wmarcolinW Online
                  wmarcolinW Online
                  wmarcolin
                  wrote on last edited by
                  #8

                  @toggledbits hi!

                  I had already created the rule with sys_system.state before, adding this control for the message is a plus that I am putting in case any more Hubitat warnings appear.

                  24fbfcf2-5aa3-4f7f-a8ad-a1a64a9bc171-image.png

                  Regarding the previous message, I will then remove the probe_device from the configuration, because I followed your recommendation and installed the Hub Information > created a device to receive the information > and published it in the Make API. I will put together this update tip, I think it is worth it. Thanks.

                  wmarcolinW 1 Reply Last reply
                  1
                  • wmarcolinW wmarcolin

                    @toggledbits hi!

                    I had already created the rule with sys_system.state before, adding this control for the message is a plus that I am putting in case any more Hubitat warnings appear.

                    24fbfcf2-5aa3-4f7f-a8ad-a1a64a9bc171-image.png

                    Regarding the previous message, I will then remove the probe_device from the configuration, because I followed your recommendation and installed the Hub Information > created a device to receive the information > and published it in the Make API. I will put together this update tip, I think it is worth it. Thanks.

                    wmarcolinW Online
                    wmarcolinW Online
                    wmarcolin
                    wrote on last edited by
                    #9

                    Master @toggledbits 🙂

                    Following the line "I show you the way, I don't give you the transport":), the MSR indicates in Entities the time of the last device status change. Where is this information stored?

                    e9bcef0d-fd5c-4e4a-b2fa-0ade8eeb52e7-image.png

                    Use case: I want to monitor all devices, and the ones that are not communicating for more than 48 hours should know and take action.

                    For sure there are some that can not even, because it would be a problem, then I create an exception list. But initially, I want to see everything that has not been communicated in 48 hours.

                    The principle is almost the same as Hubitat's WatchDog APP, but I want to have my own, and not be dependent on Hubitat's communication or action. I also understand that it has more validity, because it is a way to ensure that the MSR is talking to all devices, and not only to Hubitat.

                    Thanks.

                    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

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

                    • Gradually turn on lights.
                      Tom_DT
                      Tom_D
                      0
                      3
                      52

                    • Error After Upgrade
                      G
                      gwp1
                      0
                      4
                      64

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

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

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

                    • Links to MSR from HA
                      Tom_DT
                      Tom_D
                      0
                      1
                      65

                    • Set Reaction > Script Action
                      wmarcolinW
                      wmarcolin
                      0
                      11
                      395

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

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

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

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