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. Variables for fun and profit
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

Variables for fun and profit

Scheduled Pinned Locked Moved Multi-System Reactor
19 Posts 3 Posters 749 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.
  • CatmanV2C Offline
    CatmanV2C Offline
    CatmanV2
    wrote on last edited by
    #1

    Well the use of expressions in my Idiot Question over there has opened many new and exciting doors which I am itching to run through. This one has slammed in myu face 😞

    So in reactor we have an expression:
    getstate( 46, "urn:upnp-org:serviceId:VClock1", "AlarmTime" )
    which returns
    Last result: "05:15:00"
    Then we convert this to time one hour earlier:
    time(AlarmTime) - 3600
    which returns
    Last result: 1658373300

    Cool!

    In MSR:
    getstate is not supported
    getEntity("vera>AlarmClock").attributes.x_vera_svc_upnp_org_VClock1.AlarmTime
    Returns:
    Last value: (string) "05:15:00"
    Marvellous!
    time (AlarmTime)
    Returns
    Last value: (null) null

    Boo! Hiss!

    OK seriously, is there a reference I've missed or somewhere I can look at this stuff. time() in Lua returns the epoch time which is fab, but what's my equivalent to the time usage in Reactor?

    TIA
    C

    The Ex-Vera abuser know as CatmanV2.....

    1 Reply Last reply
    0
    • CatmanV2C Offline
      CatmanV2C Offline
      CatmanV2
      wrote on last edited by CatmanV2
      #2

      Quick update, from reading the manual (doh)
      time ([AlarmTime])
      Returns an epoch time (yay) (or at least I think it does. See below
      Unfortunately where in Reactor
      time(AlarmTime) returns the correct epoch time for my alarm clock
      time ([AlarmTime]) in MSR returns epoch time that is equivalent to:

      Saturday, 1 January 2022 00:00:00

      Which makes not a huge load of sense to me no matter which way I squint as it appears to be 7 months, 4 hours and 15 minutes out.

      I throw myself on your mercy

      C

      The Ex-Vera abuser know as CatmanV2.....

      CrilleC 1 Reply Last reply
      0
      • CatmanV2C CatmanV2

        Quick update, from reading the manual (doh)
        time ([AlarmTime])
        Returns an epoch time (yay) (or at least I think it does. See below
        Unfortunately where in Reactor
        time(AlarmTime) returns the correct epoch time for my alarm clock
        time ([AlarmTime]) in MSR returns epoch time that is equivalent to:

        Saturday, 1 January 2022 00:00:00

        Which makes not a huge load of sense to me no matter which way I squint as it appears to be 7 months, 4 hours and 15 minutes out.

        I throw myself on your mercy

        C

        CrilleC Offline
        CrilleC Offline
        Crille
        wrote on last edited by
        #3

        @catmanv2 There might be better ways of doing it but this would result in an epoch time of current date and the time for AlarmTime.

        do
        hms = split(getEntity("vera>AlarmClock").attributes.x_vera_svc_upnp_org_VClock1.AlarmTime, ':'),
        t = dateparts(time()),
        t.hour = hms[0],
        t.minute = hms[1],
        t.second = hms[2],
        time(t)
        done
        
        1 Reply Last reply
        1
        • CatmanV2C Offline
          CatmanV2C Offline
          CatmanV2
          wrote on last edited by
          #4

          Thanks for that. Very much appreciated, but it won't work in an expression window I think?

          I really confused as to why time returns this odd epoch time

          C

          The Ex-Vera abuser know as CatmanV2.....

          CrilleC 1 Reply Last reply
          0
          • CatmanV2C CatmanV2

            Thanks for that. Very much appreciated, but it won't work in an expression window I think?

            I really confused as to why time returns this odd epoch time

            C

            CrilleC Offline
            CrilleC Offline
            Crille
            wrote on last edited by
            #5

            I'm no expert but maybe the string doesn't comply with MSR iso-date-string.
            What error do you get in the expression?

            1 Reply Last reply
            1
            • CatmanV2C Offline
              CatmanV2C Offline
              CatmanV2
              wrote on last edited by CatmanV2
              #6

              No error at all, it just returns the 'wrong' epoch time. Behaving differently between Reactor and MSR (I would assume by design)
              <edit> It appears part of this might be caused but Reactor time() conversion returning epoch time in seconds. MSR time() is (or appears to be) returning epoch time in milli seconds.

              The use case is as follow:
              Set the alarm time (which varies, of course depending on weekends, holidays etc)
              The alarm is triggered and turns on the Volumio player in the bedroom, gently increases the volume and wakes us up (ha!)

              Subtract one hour from the alarm time, and that's when we want the heating to come on from its overnight low.

              Of course I could set the alarm one hour earlier, use that to turn on the heating then wait an hour to trigger the Volumio, but that feels inelegant as well as prone to bad choices of alarm time.

              If anyone has a suggestion of how the first case might be accomplished, it would be lovely.

              Cheers

              C

              The Ex-Vera abuser know as CatmanV2.....

              CrilleC 1 Reply Last reply
              0
              • CatmanV2C CatmanV2

                No error at all, it just returns the 'wrong' epoch time. Behaving differently between Reactor and MSR (I would assume by design)
                <edit> It appears part of this might be caused but Reactor time() conversion returning epoch time in seconds. MSR time() is (or appears to be) returning epoch time in milli seconds.

                The use case is as follow:
                Set the alarm time (which varies, of course depending on weekends, holidays etc)
                The alarm is triggered and turns on the Volumio player in the bedroom, gently increases the volume and wakes us up (ha!)

                Subtract one hour from the alarm time, and that's when we want the heating to come on from its overnight low.

                Of course I could set the alarm one hour earlier, use that to turn on the heating then wait an hour to trigger the Volumio, but that feels inelegant as well as prone to bad choices of alarm time.

                If anyone has a suggestion of how the first case might be accomplished, it would be lovely.

                Cheers

                C

                CrilleC Offline
                CrilleC Offline
                Crille
                wrote on last edited by Crille
                #7

                Do you need to set the heating in epoch time?
                If so and Reactor for Vera is in seconds you could just convert from milliseconds with

                substr(time(t), 0, 10)
                

                and substract 1 hour by changing to this line instead

                t.hour = hms[0] - 1,
                

                in the above example.

                CatmanV2C 1 Reply Last reply
                1
                • CrilleC Crille

                  Do you need to set the heating in epoch time?
                  If so and Reactor for Vera is in seconds you could just convert from milliseconds with

                  substr(time(t), 0, 10)
                  

                  and substract 1 hour by changing to this line instead

                  t.hour = hms[0] - 1,
                  

                  in the above example.

                  CatmanV2C Offline
                  CatmanV2C Offline
                  CatmanV2
                  wrote on last edited by CatmanV2
                  #8

                  @crille Really appreciated

                  No I don't need to set the heating time, there's a rule that compares current time to the calculated time for heating on. Given that
                  time(0) returns epoch, that seemed a sensible way of doing it

                  Unfortunately truncating the epoch in ms simply knocks the milliseconds off so instead of getting Saturday, 1 January 2022 00:00:00.000 you get Saturday, 1 January 2022 00:00:00

                  It should be
                  Thursday, 21 July 2022 03:15:00
                  or
                  Thursday, 21 July 2022 03:15:00.000

                  Even using strftime returns Jan 1

                  Very very odd. Really appreciate your continued efforts though!

                  C

                  The Ex-Vera abuser know as CatmanV2.....

                  CrilleC 1 Reply Last reply
                  0
                  • CatmanV2C CatmanV2

                    @crille Really appreciated

                    No I don't need to set the heating time, there's a rule that compares current time to the calculated time for heating on. Given that
                    time(0) returns epoch, that seemed a sensible way of doing it

                    Unfortunately truncating the epoch in ms simply knocks the milliseconds off so instead of getting Saturday, 1 January 2022 00:00:00.000 you get Saturday, 1 January 2022 00:00:00

                    It should be
                    Thursday, 21 July 2022 03:15:00
                    or
                    Thursday, 21 July 2022 03:15:00.000

                    Even using strftime returns Jan 1

                    Very very odd. Really appreciate your continued efforts though!

                    C

                    CrilleC Offline
                    CrilleC Offline
                    Crille
                    wrote on last edited by
                    #9

                    I'm a little lost and don't know what you actually want to achieve and what arguments you are giving time().
                    We might get different results as time() operates in the timezone set for the runtime.
                    I'll leave you with my tests and take a fresh look in the morning as it's getting late here. (sorry for Swedish in the screenshot as strftime() is locale-aware.)

                    AlarmTime.PNG

                    1 Reply Last reply
                    1
                    • CatmanV2C Offline
                      CatmanV2C Offline
                      CatmanV2
                      wrote on last edited by CatmanV2
                      #10

                      Ahh this appears to work, thanks so much!

                      I need to do some more testing, specifically around the testing of AlarmTimeSub1 vs current time but I very much appreciate your patience guiding this muppet!

                      <edit> So yes AlarmTimeSub1 evaluates perfectly. Now I need to compare that to actual time (if the actual time is later than AlarmTimeSub1, then I want the evaluation to be 'true')
                      time() >= AlarmSubTime1

                      Returns false.

                      C

                      The Ex-Vera abuser know as CatmanV2.....

                      1 Reply Last reply
                      0
                      • CatmanV2C Offline
                        CatmanV2C Offline
                        CatmanV2
                        wrote on last edited by CatmanV2
                        #11

                        OK fixed it. Thanks, too early to be trying this stuff 🙂

                        strftime("%T", time()) >= AlarmSubTime1

                        Evaluates as true so that's great 🙂

                        C

                        The Ex-Vera abuser know as CatmanV2.....

                        1 Reply Last reply
                        1
                        • toggledbitsT Away
                          toggledbitsT Away
                          toggledbits
                          wrote on last edited by
                          #12

                          FYI, @Crille has provided a correct example for computing an offset time to get an epoch (numeric) time to use for comparisons. The string comparison performed by strftime("%T", time()) >= AlarmSubTime1 is really poor programming style and should not be used; numeric comparisons are better here. Unfortunately, the responses don't give adequate detail as to what "wrong" answer is produced by @Crille 's solution, so I can't comment other than the critique.

                          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
                          • CatmanV2C Offline
                            CatmanV2C Offline
                            CatmanV2
                            wrote on last edited by CatmanV2
                            #13

                            Thanks. I have no programming style so happy to be educated 🙂

                            <types long reply to explain the 'issue'>
                            <while typing resolves the issue>
                            <deletes explanation>

                            is time() >= HeatTime better style?

                            <edit>
                            I guess I'm still curious as to why
                            time([AlarmTime]) in MSR and time(AlarmTime) in reactor return a different stamp (apart from the ms vs s part that is)

                            Thanks again for all you do

                            C

                            The Ex-Vera abuser know as CatmanV2.....

                            toggledbitsT 1 Reply Last reply
                            0
                            • CatmanV2C CatmanV2

                              Thanks. I have no programming style so happy to be educated 🙂

                              <types long reply to explain the 'issue'>
                              <while typing resolves the issue>
                              <deletes explanation>

                              is time() >= HeatTime better style?

                              <edit>
                              I guess I'm still curious as to why
                              time([AlarmTime]) in MSR and time(AlarmTime) in reactor return a different stamp (apart from the ms vs s part that is)

                              Thanks again for all you do

                              C

                              toggledbitsT Away
                              toggledbitsT Away
                              toggledbits
                              wrote on last edited by toggledbits
                              #14

                              @catmanv2 said in Variables for fun and profit:

                              is time() >= HeatTime better style?

                              Yes.

                              I guess I'm still curious as to why
                              time([AlarmTime]) in MSR and time(AlarmTime) in reactor return a different stamp (apart from the ms vs s part that is)

                              You haven't given any examples of this. I don't believe it to be true (except, as noted, for millisecond precision in Multi-Hub Reactor). My guess is you are not actually asking about the return values, but about why the functions take different arguments. The reason is that the expression language in Multi-Hub Reactor is entirely new, and while there is some overlap between them, I would argue that the newer form is vastly superior and corrects many errors (read: decisions I made that I later regretted) in the Lua-based form. Another reason is that Multi-Hub Reactor is not Lua-based, so I did not feel the need to be Lua-compatible, whereas Reactor for Vera, being a Lua plugin for a Lua system, is meant to capitalize on existing user experience with Lua on that now-defunct (Vera) platform.

                              Also, if AlarmTime contains the string 12:34:56, the using time([AlarmTime]) in either Multi-Hub or Vera Reactor would be passing incorrect arguments to the function. If you want to pass a string, you do so without [] surrounding. If you include the [], you are creating an array containing a string, which is nonsensical (to the function -- it sees an error). The documentation (for Multi-Hub) states that the function takes an optional single string argument, or up to six optional numeric arguments (representing in order given (year, month, day, hour, minute, second), or an optional dateparts-form object. The [] you see in the documentation is from an old-but-still-widely-used BNF form to indicate an optional argument, it is not meant to be literally included in your expression. So the following would be valid calls to time:

                              1. time() with no arguments (because all arguments are optional)
                              2. time( "2022-07-22T08:53:23+02:00" ) -- an ISO 8601 date string with TZ
                              3. time( 2022, 7, 22 ) -- produces midnight on 2022-Jul-22 in the host time zone (three optional arguments not given -- hour, minute, second)
                              4. time( 2022, 7, 22, 8, 10, 0 ) -- produces 8:10am on 22-Jul-2022 in the host time zone
                              5. and the dateparts() form has already been given in examples above by @Crille

                              Note that the string passed must be in ISO 8601 form, so a simple "12:34:56" time alone would not be parsable and produce an invalid result.

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

                              CatmanV2C 1 Reply Last reply
                              0
                              • toggledbitsT toggledbits

                                @catmanv2 said in Variables for fun and profit:

                                is time() >= HeatTime better style?

                                Yes.

                                I guess I'm still curious as to why
                                time([AlarmTime]) in MSR and time(AlarmTime) in reactor return a different stamp (apart from the ms vs s part that is)

                                You haven't given any examples of this. I don't believe it to be true (except, as noted, for millisecond precision in Multi-Hub Reactor). My guess is you are not actually asking about the return values, but about why the functions take different arguments. The reason is that the expression language in Multi-Hub Reactor is entirely new, and while there is some overlap between them, I would argue that the newer form is vastly superior and corrects many errors (read: decisions I made that I later regretted) in the Lua-based form. Another reason is that Multi-Hub Reactor is not Lua-based, so I did not feel the need to be Lua-compatible, whereas Reactor for Vera, being a Lua plugin for a Lua system, is meant to capitalize on existing user experience with Lua on that now-defunct (Vera) platform.

                                Also, if AlarmTime contains the string 12:34:56, the using time([AlarmTime]) in either Multi-Hub or Vera Reactor would be passing incorrect arguments to the function. If you want to pass a string, you do so without [] surrounding. If you include the [], you are creating an array containing a string, which is nonsensical (to the function -- it sees an error). The documentation (for Multi-Hub) states that the function takes an optional single string argument, or up to six optional numeric arguments (representing in order given (year, month, day, hour, minute, second), or an optional dateparts-form object. The [] you see in the documentation is from an old-but-still-widely-used BNF form to indicate an optional argument, it is not meant to be literally included in your expression. So the following would be valid calls to time:

                                1. time() with no arguments (because all arguments are optional)
                                2. time( "2022-07-22T08:53:23+02:00" ) -- an ISO 8601 date string with TZ
                                3. time( 2022, 7, 22 ) -- produces midnight on 2022-Jul-22 in the host time zone (three optional arguments not given -- hour, minute, second)
                                4. time( 2022, 7, 22, 8, 10, 0 ) -- produces 8:10am on 22-Jul-2022 in the host time zone
                                5. and the dateparts() form has already been given in examples above by @Crille

                                Note that the string passed must be in ISO 8601 form, so a simple "12:34:56" time alone would not be parsable and produce an invalid result.

                                CatmanV2C Offline
                                CatmanV2C Offline
                                CatmanV2
                                wrote on last edited by
                                #15

                                @toggledbits OK I'll try to give an example (I'm sure / hopeful you can explain)

                                In my Reactor (and I'm pretty sure you set this up for me a couple of years back!) I have:
                                getstate( 46, "urn:upnp-org:serviceId:VClock1", "AlarmTime" )
                                Underneath is stated: Last result: "06:00:00"

                                Then we have
                                time(AlarmTime) - 3600
                                Underneath: Last result: 1658462400

                                Screenshot 2022-07-22 at 11.42.38.png

                                In MSR we have:
                                getEntity( "vera>Alarm Clock" ).attributes.x_vera_svc_upnp_org_VClock1.AlarmTime
                                Underneath: Last value: (string) "06:00:00"

                                If we then do
                                time(AlarmTime) - 3600000 the result printed is
                                Last value: (null) null

                                Screenshot 2022-07-22 at 11.43.35.png

                                time([AlarmTime]) - 3600000
                                Returns: Last value: (number) 1640995200000

                                Screenshot 2022-07-22 at 11.44.11.png

                                Please note I changed the HeatTime in reactor to HeatTimeMSR in MSR just to demonstrate the 'difference' in output.

                                Clearly I'm missing something fundamental and obvious!

                                Cheers

                                C

                                The Ex-Vera abuser know as CatmanV2.....

                                toggledbitsT 1 Reply Last reply
                                0
                                • CatmanV2C CatmanV2

                                  @toggledbits OK I'll try to give an example (I'm sure / hopeful you can explain)

                                  In my Reactor (and I'm pretty sure you set this up for me a couple of years back!) I have:
                                  getstate( 46, "urn:upnp-org:serviceId:VClock1", "AlarmTime" )
                                  Underneath is stated: Last result: "06:00:00"

                                  Then we have
                                  time(AlarmTime) - 3600
                                  Underneath: Last result: 1658462400

                                  Screenshot 2022-07-22 at 11.42.38.png

                                  In MSR we have:
                                  getEntity( "vera>Alarm Clock" ).attributes.x_vera_svc_upnp_org_VClock1.AlarmTime
                                  Underneath: Last value: (string) "06:00:00"

                                  If we then do
                                  time(AlarmTime) - 3600000 the result printed is
                                  Last value: (null) null

                                  Screenshot 2022-07-22 at 11.43.35.png

                                  time([AlarmTime]) - 3600000
                                  Returns: Last value: (number) 1640995200000

                                  Screenshot 2022-07-22 at 11.44.11.png

                                  Please note I changed the HeatTime in reactor to HeatTimeMSR in MSR just to demonstrate the 'difference' in output.

                                  Clearly I'm missing something fundamental and obvious!

                                  Cheers

                                  C

                                  toggledbitsT Away
                                  toggledbitsT Away
                                  toggledbits
                                  wrote on last edited by toggledbits
                                  #16

                                  @catmanv2 said in Variables for fun and profit:

                                  If we then do
                                  time(AlarmTime) - 3600000 the result printed is
                                  Last value: (null) null

                                  This is expected because AlarmTime contains only 06:00:00, which is not an ISO 8601-compatible string.

                                  time([AlarmTime]) - 3600000
                                  Returns: Last value: (number) 1640995200000

                                  Also expected, as I said above, because the [] surrounding AlarmTime convert it to an array, which is a form of object, so time() is thinking its a dateparts()-compatible object and using what's available from it (which in fact is nothing at all, i.e. the "it's nonsensical" reference in that comment) to compute the time.

                                  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
                                  • CatmanV2C Offline
                                    CatmanV2C Offline
                                    CatmanV2
                                    wrote on last edited by CatmanV2
                                    #17

                                    So fundamentally Reactor's time and MSR's time are just different and behave differently?

                                    <edit>
                                    Or getstate and getEntity are returning something different from each other, I guess.

                                    Thanks for the clarity there, and the patience 🙂

                                    C

                                    The Ex-Vera abuser know as CatmanV2.....

                                    1 Reply Last reply
                                    0
                                    • toggledbitsT Away
                                      toggledbitsT Away
                                      toggledbits
                                      wrote on last edited by
                                      #18

                                      Many of the functions behave differently, and this is intentional. The functions of Multi-Hub Reactor are (in my view) an improved evolution of any same-named functions in Reactor for Vera. Reading the documentation is key to success.

                                      I'm working right now (back at my desk, yay!) at expanding the parsing capabilities of time() to make your particular use case a bit easier.

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

                                      CatmanV2C 1 Reply Last reply
                                      1
                                      • toggledbitsT toggledbits

                                        Many of the functions behave differently, and this is intentional. The functions of Multi-Hub Reactor are (in my view) an improved evolution of any same-named functions in Reactor for Vera. Reading the documentation is key to success.

                                        I'm working right now (back at my desk, yay!) at expanding the parsing capabilities of time() to make your particular use case a bit easier.

                                        CatmanV2C Offline
                                        CatmanV2C Offline
                                        CatmanV2
                                        wrote on last edited by CatmanV2
                                        #19

                                        @toggledbits that's super. Thanks again for all your help!

                                        C

                                        The Ex-Vera abuser know as CatmanV2.....

                                        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
                                          132

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

                                        • Error After Upgrade
                                          G
                                          gwp1
                                          0
                                          4
                                          103

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

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

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

                                        • Links to MSR from HA
                                          Tom_DT
                                          Tom_D
                                          0
                                          1
                                          90

                                        • Set Reaction > Script Action
                                          wmarcolinW
                                          wmarcolin
                                          0
                                          11
                                          433

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

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

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

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

                                        • Don't have an account? Register

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