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. Preview of 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
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

Preview of Multi-System Reactor

Scheduled Pinned Locked Moved Multi-System Reactor
58 Posts 11 Posters 5.5k Views 11 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #9

    Unfortunately I haven't run any UI5 in years, so I don't have anything around to play with. Technically, however, there's no reason it could not be made to work.

    For any interface, the only requirement is some kind of API where device information can be gathered. I can't imagine HomeSeer not having one, but it's not a system I've ever had contact with.

    For the moment, if there's no objection from the owner, I'd rather communicate in this forum rather than the Vera Community forums, and maybe a category can be set up just for that, to help thread the discussions a bit better. I've also got Discord, but I don't know how many people really use that or would be interested in trying; but I like the more immediate flow of messaging for some things. As I said in the video, there's an entire ecosystem that has nothing to do with building the project that needs to come together, so I'm sure it will evolve.

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

    akbooerA 1 Reply Last reply
    0
    • Black CatB Offline
      Black CatB Offline
      Black Cat
      wrote on last edited by
      #10

      @toggledbits
      I'm surprised that you never looked at Homeseer as a Vera replacement, it appears to have a huge US (local to you) user base, may I ask why?
      Do you have a timeline for release, perhaps a Beta; I know that there will be many chopping at the bit for a test drive.

      aka Zedrally

      1 Reply Last reply
      0
      • toggledbitsT toggledbits

        Unfortunately I haven't run any UI5 in years, so I don't have anything around to play with. Technically, however, there's no reason it could not be made to work.

        For any interface, the only requirement is some kind of API where device information can be gathered. I can't imagine HomeSeer not having one, but it's not a system I've ever had contact with.

        For the moment, if there's no objection from the owner, I'd rather communicate in this forum rather than the Vera Community forums, and maybe a category can be set up just for that, to help thread the discussions a bit better. I've also got Discord, but I don't know how many people really use that or would be interested in trying; but I like the more immediate flow of messaging for some things. As I said in the video, there's an entire ecosystem that has nothing to do with building the project that needs to come together, so I'm sure it will evolve.

        akbooerA Offline
        akbooerA Offline
        akbooer
        wrote on last edited by
        #11

        @toggledbits said in Preview of Multi-System Reactor:

        I'd rather communicate in this forum rather than the Vera Community forums, and maybe a category can be set up just for that, to help thread the discussions a bit better.

        Sounds like a good idea to me. This forum has always been platform independent, so what better place?

        1 Reply Last reply
        1
        • PerHP Offline
          PerHP Offline
          PerH
          wrote on last edited by
          #12

          If the idea is to create a top automation layer - what about including some of your other automation luup plugins? I think i.e. Delaylight, SiteSensor and AutoVirtualThermostat would fit nicely as Automation templates that can be quickly configured?

          Automation templates is something i've been missing in Reactor, what i mean by that is simply a good way to copy the structure of a good automation i have running in one room to another room (Today I have a Reactor sensor in each room, and one for "House" automation).
          Example: I have two guest rooms set up with identical sensor and actuator layouts, so the automation i want would be identical for those rooms.

          Another side note, i think some sort of room organization would be nice in the entities list?

          I'm not entirely sure about how to implement either of these, or the scope of the work it entails, just throwing out some ideas. 🙂

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

            [Possibly split the following feedback into its own thread if seeking input on MSR Dashboard UI]

            As a Dashboard n00b, I'd benefit from knowing exactly where on a particular Dashboard tile to tap for "Dim+", "Dim-", "On/100%" and "Off/0%". So I created two examples, linked below, despite knowing full well that others have created much better examples than this on other platforms. I also fully acknowledge that this kind of feedback is premature, as the official roll-out of MSR's Dashboard feature has not yet happened.

            ON: https://drive.google.com/file/d/1kWPtPa2HQ5GExBIi45QNJGyEvsz5QVZu/view?usp=sharing
            OFF: https://drive.google.com/file/d/1EIZK1BggsDtNWm8mfBT605N7-cnkeSQ_/view?usp=sharing

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

              SUGGESTION

              In the text fields used under "Rulesets", instead of having "Add your rule's triggers here" guidance text pre-populate the object (which requires users to click-drag-delete before typing), could you instead use the object's .placeholder attribute?

              I know this is a controversial stylistic choice among CSS designers, but the Placeholder approach carries with it some immediate benefits:

              • Help text disappears upon clicking into field;
              • Help text reappears if user empties the field;
              • Can appear in different font style (e.g. greyed, italic) from input text;
              • Not apt to be misinterpreted as filled text, nor read by a screen reader app;

              Minutiae, yes, but still worth my mentioning IMHO.
              COUNTERARGUMENT: https://www.smashingmagazine.com/2018/06/placeholder-attribute/

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

                SUGGEST (I'll happily move these suggestions elsewhere, such as the Mantis, if instructed to do so)

                Assuming that "==0" and "is FALSE" will both match the condition of a device being turned OFF (the MSR UI seems to prefer "false" to "0" when referring to POWER_SWITCH.STATE, for instance), could you also add "is ON" and "is OFF" to the drop-down list of comparators?

                However redundant, this seems a natural language-y thing to have in place for novice users, who may not think in binary 0/1.

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

                  There are a bunch of hints in the capabilities data that I'm not making use of yet. This is exactly that kind of thing.

                      "power_switch": {
                          "attributes": {
                              "state": {
                                  "type": "bool",
                                  "values": {
                                      "true": "on",
                                      "false": "off"
                                  }
                              }
                          },
                  

                  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
                  1
                  • LibraSunL Offline
                    LibraSunL Offline
                    LibraSun
                    wrote on last edited by
                    #17

                    By now, you understand I'm reluctant to add an "Issue" to the Mantis when I'm merely thinking aloud, so here goes with another set of MSR thoughts:

                    (1) Should each Ruleset have its own top-level DISABLE flag/button/status? (i.e. above even 'Triggers' and 'Constraints')
                    (2) Would it be useful to be able to "enable/disable" a Ruleset from another Ruleset? (this may already be possible, I haven't checked deeply)
                    (3) Does MSR possess the same "Throttling" feature as Luup Reactor, to stem circular references and flapping? I'll be interested to learn whether the reset mechanism is also similarly employed.
                    (4) Since lexpjs is normally evaluated at compile-time, would it be possible to (i) perform syntax checking during Expression entry, (ii) provide a drop-down 'helper' (APK-esque pick-list) from which users can select from a menu of possible functions, and/or (iii) generate daily alert summaries advising user of non-working Expressions (or other error conditions within MSR)?

                    I included (4)(iii) because I'm always uncovering old Reactor recipes that have "issues" resulting from obsolete references. And I love the way, for instance, Synology NAS units email their owners to notify them of system status, security concerns, updates needed, etc.

                    toggledbitsT 1 Reply Last reply
                    0
                    • LibraSunL LibraSun

                      By now, you understand I'm reluctant to add an "Issue" to the Mantis when I'm merely thinking aloud, so here goes with another set of MSR thoughts:

                      (1) Should each Ruleset have its own top-level DISABLE flag/button/status? (i.e. above even 'Triggers' and 'Constraints')
                      (2) Would it be useful to be able to "enable/disable" a Ruleset from another Ruleset? (this may already be possible, I haven't checked deeply)
                      (3) Does MSR possess the same "Throttling" feature as Luup Reactor, to stem circular references and flapping? I'll be interested to learn whether the reset mechanism is also similarly employed.
                      (4) Since lexpjs is normally evaluated at compile-time, would it be possible to (i) perform syntax checking during Expression entry, (ii) provide a drop-down 'helper' (APK-esque pick-list) from which users can select from a menu of possible functions, and/or (iii) generate daily alert summaries advising user of non-working Expressions (or other error conditions within MSR)?

                      I included (4)(iii) because I'm always uncovering old Reactor recipes that have "issues" resulting from obsolete references. And I love the way, for instance, Synology NAS units email their owners to notify them of system status, security concerns, updates needed, etc.

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

                      @librasun said in Preview of Multi-System Reactor:

                      (1) Should each Ruleset have its own top-level DISABLE flag/button/status? (i.e. above even 'Triggers' and 'Constraints')

                      I could probably add this is a macro-instruction in the UI, but Rule Sets are only an organizational structure for the benefit of the user and have no inherent relationship to the Rule for purposes of logic. Such a feature would simply loop over the list of rules in the set and enable or disable them. The Rule Set itself would not have an enabled or disabled state.

                      (2) Would it be useful to be able to "enable/disable" a Ruleset from another Ruleset? (this may already be possible, I haven't checked deeply)

                      This will definitely not be happening, for the same reason I don't allow enabling/disabling a Rule from another rule: this could quickly create a situation in which a user's logic is completely unsupportable, because at any given time you don't know what is enabled or disabled, or who enabled or disabled, or when or why. IMO, the less users understand about how to structure their logic (e.g. elusive boolean algebra), the more likely a kludge like this would be used, as well; it would become the crutch from he**. I'm all for choices and giving users a little rope that they might hang themselves with, but this seems like a guaranteed highway to pain.

                      My evidence of this, by the way, is how quickly people went to various modes of the "Reset Latched" action, rather than structuring their logic so that latched conditions would reset naturally. MSR has only natural unlatching.

                      (3) Does MSR possess the same "Throttling" feature as Luup Reactor, to stem circular references and flapping? I'll be interested to learn whether the reset mechanism is also similarly employed.

                      It does indeed, although MSRs version is a little software. In MSR, when the threshold is breached, it simply delays further performance on that rule. It literally throttles it back, rather than cutting the gas off entirely.

                      (4) Since lexpjs is normally evaluated at compile-time, would it be possible to (i) perform syntax checking during Expression entry, (ii) provide a drop-down 'helper' (APK-esque pick-list) from which users can select from a menu of possible functions, and/or (iii) generate daily alert summaries advising user of non-working Expressions (or other error conditions within MSR)?

                      lexpjs is fully portable between the different versions of JavaScript that run within a browser and that which runs in nodejs. So it's very possible to have "test compiles", and it's a pretty light-weight thing to do. Of course, this won't catch runtime errors, like referring to an entity that doesn't exist, or an attribute on an entity that doesn't exist, but I agree it would make editing smoother. Little UI tweaks like this are fine for bug reports. I like them as reminders. I think this (as in, what is happening right here, right now) is a good workflow: discuss, and when we find the consensus on what needs to be done, open a PR to memorialize it.

                      Now, getting really fancy and having a bunch of drop-down pickers/assistants, should probably be a separate second PR. I think the first level problem is to get more dynamic syntax checking, and then we start thinking about assistants.

                      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
                      1
                      • LibraSunL Offline
                        LibraSunL Offline
                        LibraSun
                        wrote on last edited by LibraSun
                        #19

                        Dang, I just jetted back here to declare my idea #1 as "dumb" but thankfully you beat me to it. Individual Rules already have their own (manual) enable/disable anyway. Dunno what I was talking about. 🙂

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

                          USER NOTE: Whereas in MFL I followed your prescribed paradigm of naming Reactors after individual Rooms (e.g. "DINING ROOM", "PORCH", etc.), with MSR I'm leaning toward naming Rulesets after their meta-function (e.g. "LIGHTING", "SECURITY", "ENVIRONMENT", etc.) instead.

                          Dunno if you've made a conscious decision to promote one naming schema over another, but wanted to toss this idea in the ring.

                          1 Reply Last reply
                          0
                          • LibraSunL LibraSun

                            Dang, I just jetted back here to declare my idea #1 as "dumb" but thankfully you beat me to it. Individual Rules already have their own (manual) enable/disable anyway. Dunno what I was talking about. 🙂

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

                            @librasun said in Preview of Multi-System Reactor:

                            Dang, I just jetted back here to declare my idea #1 as "dumb" but thankfully you beat me to it.

                            I don't think that's at all dumb, and it makes a lot of sense, depending upon, as you said in your follow-on post, what schema you choose for your rules. So far, I've gone with one rule set per room, just leaving the mapping established by the importer. Particularly when getting the rules moved from RFL to MSR, I often had to disable an entire room's (rule set's) rules until I got something fixed.

                            It's not a bad idea at all.

                            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
                            1
                            • LibraSunL Offline
                              LibraSunL Offline
                              LibraSun
                              wrote on last edited by
                              #22

                              May I also just add that I appreciate how a Reaction can "Stop" itself? Could be a powerful debugging tool when needed.

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

                                LEARNED SOMETHING TODAY

                                1. You can click-and-drag Rules to reorganize them in Rulesets. Who knew?
                                2. You cannot, however, click-to-highlight the Rule ID of an expanded rule, in order to copy that text.
                                3. Setting an Expression := away is entirely different from := "away". The first evaluates to (null) if no such named Global exists; the second evaluates to the string "away".

                                #2 would be hugely helpful for times when you need to troubleshoot the Reactor.log. (I understand CSS and HTML, but don't know the correct term for "object not swipable" -- is this a side-effect of, say, a very high z-index on that block element?).

                                As for #3, I foolishly thought MSR's expression parser, lexpjs, was meant to typecast unknown objects (away ► "away") but that was a n00b miscalculation.

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

                                  Looks like #2 is a limitation of "sortable" objects in jQuery UI. The sortable takes over all clicks and drags. I'll keep poking for workarounds, but don't get your hopes up.

                                  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
                                  1
                                  • LibraSunL Offline
                                    LibraSunL Offline
                                    LibraSun
                                    wrote on last edited by
                                    #25

                                    re: #2 it might then be helpful to replicate the Rule ID within the Edit view of each Rule?

                                    toggledbitsT 1 Reply Last reply
                                    0
                                    • LibraSunL LibraSun

                                      LEARNED SOMETHING TODAY

                                      1. You can click-and-drag Rules to reorganize them in Rulesets. Who knew?
                                      2. You cannot, however, click-to-highlight the Rule ID of an expanded rule, in order to copy that text.
                                      3. Setting an Expression := away is entirely different from := "away". The first evaluates to (null) if no such named Global exists; the second evaluates to the string "away".

                                      #2 would be hugely helpful for times when you need to troubleshoot the Reactor.log. (I understand CSS and HTML, but don't know the correct term for "object not swipable" -- is this a side-effect of, say, a very high z-index on that block element?).

                                      As for #3, I foolishly thought MSR's expression parser, lexpjs, was meant to typecast unknown objects (away ► "away") but that was a n00b miscalculation.

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

                                      @librasun said in Preview of Multi-System Reactor:

                                      You can click-and-drag Rules to reorganize them in Rulesets. Who knew?

                                      You can do the same with Rule Sets... organize them in any order you wish.

                                      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
                                      • LibraSunL LibraSun

                                        re: #2 it might then be helpful to replicate the Rule ID within the Edit view of each Rule?

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

                                        @librasun said in Preview of Multi-System Reactor:

                                        re: #2 it might then be helpful to replicate the Rule ID within the Edit view of each Rule?

                                        Why do you need the rule ID?

                                        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
                                        • LibraSunL Offline
                                          LibraSunL Offline
                                          LibraSun
                                          wrote on last edited by
                                          #28

                                          Armed with the unique Rule ID, one can (somewhat more) quickly do a "FIND" in Notepad while looking at REACTOR.LOG

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

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

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            75

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

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

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

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            69

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            400

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

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

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

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            239
                                          Powered by NodeBB | Contributors
                                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Unsolved