Multi-System Reactor

705 Topics 7.0k Posts
  • MSR and Switchboard TRI state switches

    Locked
    3
    0 Votes
    3 Posts
    112 Views

    Got it. Thanks.

  • Time triggers not firing

    Locked
    2
    0 Votes
    2 Posts
    123 Views

    Just a note that log timestamps (the ones starting each log line) are always in Z/UTC, but many timestamps reported in the log line text are displayed in configured local time. As can be seen in the final image above, the Engine's master tick also periodically logs what it believes local time to be. The time displayed in the header of the UI is the local time of the browser, not the host system or Reactor, and so may still be different (i.e. you're sitting on a browser in California at UTC-8 working on your Pi in New York at UTC-5).

    I will bind /etc/localtime to future docker containers. Not possible since it's a security risk, which makes sense (you don't want containers being able to arbitrarily mount things anywhere in the filesystem). So, looks like a TZ environment variable is where we'll be. I'll add it to the docs.

  • 0 Votes
    15 Posts
    336 Views

    Roger that. While sage advice, bear in mind that I do these exercises as much to keep my brain active as to hone my MSR chops. I literally have nothing else to keep me occupied, lol. So I'll go put the finishing touches on the intermediate workflow, check that it works (which I know it will), and then look forward to stringing it all back together more efficiently next week.

  • Reactor logic talk

    Locked
    14
    0 Votes
    14 Posts
    309 Views

    It works well now with separate rules for on and off, where "OFF" has the same constraints as "ON", and "OFF" has "ON"-rule changes to false as trigger.

    Now, the autolight (which turns on a very low dimming level) turn on, and if someone manually turns the light on at this point, the light goes to the dimming level chosen.
    (In this case its not the switch connected to one light that is pressed, its a virtual switch that turns on multiple lights.)

  • I'm no longer a PLEG user !

    Locked
    8
    4 Votes
    8 Posts
    231 Views

    Yes PLEG wasn't the easiest thing to learn but it did save Vera. Powerful but not so user friendly. The conditions were the hardest part as you wrote them all out like expressions. Bulletproof though, I rarely had any issues with it. I skipped the whole Reactor for Vera thing, converted now so better late than never I guess.

  • Intervals ? "Self Retriggering Timer" ?

    Locked
    9
    0 Votes
    9 Posts
    212 Views

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

  • Master Dimmer using expression?

    Locked
    8
    0 Votes
    8 Posts
    214 Views

    Yes I agree.

  • How do I "else"

    Locked
    10
    1 Votes
    10 Posts
    308 Views

    Working on to get the values into, InfluxDB, not there yet. Will continue tomorrow.

  • Insert Entity tool for expressions

    Locked
    2
    0 Votes
    2 Posts
    86 Views

    Not yet.

  • Scene Controllers

    Locked
    3
    0 Votes
    3 Posts
    137 Views

    Sorry I didn't see this thread before I created the other new one. Please merge them.

    Thanks

  • 0000075: Timeout Overflow Warning

    Locked
    2
    0 Votes
    2 Posts
    94 Views

    Thank you!

  • Contact Sensor Opened > 1 minute ago how ?

    Locked
    10
    0 Votes
    10 Posts
    275 Views

    Another thing that's been annoying, is when my garden lights via a schedule turn on or off in the back garden, the Hikvision IP camera triggers motion being detected as a result.

    I could maybe use this method to stop that happening and stop MSR running the actions "Set Reaction", by checking that the state of the lights hasn't changed within the last X seconds.

    Seems to be working, checking if the patio door has changed state in the last 60 seconds OR if the Festoon Lights in the garden have changed state in the last 10 seconds.

    89079f2a-927a-48cc-9078-dc2b5553a109-image.png

  • Rule stopped working

    Locked
    3
    0 Votes
    3 Posts
    126 Views

    OK, I update and report back if it happens again.

  • 0 Votes
    4 Posts
    120 Views

    @toggledbits said in Newly created rules with 21060, null of null no data:

    Will be in today's build

    Presume that is version 0.1.21061.

    I just saw its available now on Mantis and updated.

    This problem has gone away now.

    When I first hit the toggle button to enable the newly created rule, data is now populated in the Triggers in the rules summary card.

    Thanks

  • Feature request: Automation templates

    Locked
    1
    1 Votes
    1 Posts
    87 Views
    No one has replied
  • No time and date?

    Locked
    4
    0 Votes
    4 Posts
    158 Views

    Guess it was reactor, its gone with 21060. 🙂

  • 0 Votes
    26 Posts
    751 Views

    If it's not working, don't recreate it yet. Save the JSON file with its ID from inside storage/rules and send that to me (you can just post it on a PR--should be small/short). After you've capture it, then you can go ahead and recreate. If there's anything broken in the rule itself, I should be able to see it.

  • Timers in my log

    Locked
    26
    0 Votes
    26 Posts
    699 Views

    Not yet, but it's on its way. Definitely showing promise. Thanks for your help is making it work!

  • This topic is deleted!

    Locked
    2
    0 Votes
    2 Posts
    10 Views
  • Delays not working as expected

    Locked
    12
    0 Votes
    12 Posts
    309 Views

    Thanks for the fixes Patrick.

    I've now tried them on my test rules and both (PR#64 and 65) work fine. 👍

    I've also updated all my imported rules to use the "delay reset" on the "Follow" output mode. These are all working now with the added bonus of being able to monitor the delays counting down.

    Thanks again for the brilliant MSR.

Recent Topics