Skip to content

Multi-System Reactor

780 Topics 7.4k Posts
  • Category Topic Guide -- Read Before Posting

    Pinned Locked
    1
    8 Votes
    1 Posts
    810 Views
    No one has replied
  • Reactor (Multi-System/Multi-Hub) Announcements

    Pinned Locked
    120
    5 Votes
    120 Posts
    22k Views
    toggledbitsT
    Reactor build 25097 Expression syntax enhancement: it is now possible to use a variable's value as a key when creating an object on the fly. For example, if the variable cmd contains the word "econo" (presumably derived from configuration or some other dynamic source), it is now possible to create an object { econo: true } by enclosing the key source in square brackets: obj = { [cmd]: true }. For reference, this syntax mimicks JavaScript. Fixed a UI crash when bringing up Reactor initially after using the About page bypass. OWMWeatherController: implement sys_system.restart, which will cause all locations to be refreshed immediately. OWMWeatherController: new config option (boolean) ignore_certs can be set to ignore certificate errors. These seem to pop up occasionally, perhaps because of a misconfiguration in the load balancing at OWM.
  • Organizing/ structuring rule sets and rules

    5
    0 Votes
    5 Posts
    176 Views
    G

    @RHCPNG As @toggledbits notes, I've found myself bouncing around a bit. I've settled on what I call Shared Rules - those that impact all things potentially, at a base level. Wx stuff, HVAC stuff, etc.

    I kinda branch out from there. Interior lighting, Outdoor lighting, Presence, etc. Sorta using "topics" and then rulesets under them.

    I'm also linked to our local community center via site-to-site VPN and am using my home MSR instance to control the Hubitat C7 over there for lighting and outdoor fans 🙂

  • Moving MSR from a QNAP container to RP 5 - some issues

    Solved
    5
    0 Votes
    5 Posts
    162 Views
    G

    @Tom_D please mark issue thread as solved

  • Widget deletion does not work and landing page (status) is empy

    4
    0 Votes
    4 Posts
    145 Views
    G

    @mgvra the landing page issue was addressed here as a side note in another issue thread: https://smarthome.community/post/16764

  • Need help reducing false positive notifications

    7
    0 Votes
    7 Posts
    278 Views
    T

    @toggledbits,

    I tried to go about the way you mentioned, but I don't think it was quite suited for my purpose. The purpose of the rule is to send a notification through Home Assistant to my phone, and I didn't want a delay that I believe your method would have introduced. What I came up with was creating a global variable and a helper rule, that sets the global variable to true when the 300 seconds is exceeded of power being above 3.7.

    b0f50fcc-a06f-49a6-9ccb-38f718d7cc42-image.png

    88547953-dbd8-4646-80a9-48b03a6c09ad-image.png

    Then there is a Variable Value check in the Triggers of the Notification rule:
    8b91b3c4-cc46-44db-a4f1-a76408f7c79b-image.png

    The Reaction resets the Global rule back to false, after the cycle is completed.

    It may not be the most elegant method, but it reduces the false positives on my phone when the cycle selector is bumped. For the same reason, I have the reactor uptime checked, because I would get tons of notifications on my phone when I did an update to MSR, or when my server was rebooted. I know I could completely encapsulate the logic within MSR, but the overly simplistic sensor in HAAS serves it's own purpose in HAAS for my dashboard, and HAAS can't read rule states from MSR, so for my purpose, I already have the simple sensor in place, so why reinvent the wheel?

  • Deleting widgets

    Locked
    4
    0 Votes
    4 Posts
    325 Views
    toggledbitsT

    As of build 24343, widget deletion is accomplished by dragging the widget to the top navigation bar (only). Dragging to the left margin no longer deletes the widget.

  • MQTT configuration question

    Solved
    11
    0 Votes
    11 Posts
    373 Views
    tunnusT

    Hint: for debugging, when you run an action, MQTTController logs the exact topic and full payload being published at INFO level by default.

    I've used MQTTX, which I can highly recommend

  • System Configuration Check - time is offset

    8
    0 Votes
    8 Posts
    350 Views
    G

    @toggledbits I have indeed used the code... and no, this isn't critical. Once I saw MSR was running and working as intended I moved on. Release AYC.

    @Fanan Re time sync: I did a apt-get install systemd-timesyncd on the Proxmox host. I've not seen the warning since.

  • Programmatically capture HTTP Request action status code or error

    3
    0 Votes
    3 Posts
    260 Views
    therealdbT

    So, an empty string is 200ish, otherwise error/timeout is null? That works, thank you!

  • 0 Votes
    9 Posts
    375 Views
    toggledbitsT

    First, always look at the logs. I'm 100% certain that "nothing happens" isn't what's in the logs.

    It looks like the device has separate targetValue values for the white channels, so you may just need to use those. That means for red, green, and blue, you'll use targetValue for the property with a JSON object, but leave the propertyKey blank. For warm white, you use property targetValue with propertyKey zero (0), and for cold white you'll use propertyKey one (1).

    Edit: look at the logs

  • Problem with simultaneous notifications.

    1
    0 Votes
    1 Posts
    124 Views
    No one has replied
  • Problem after upgrading to 25067

    4
    0 Votes
    4 Posts
    233 Views
    R

    I reviewed my Reactor configuration file. Some time ago I had duplicated one of the hubitat device sections in anticipation of making changes to my extended LAN. While one entry was marked as "enabled: false", it seems that MSR did not like the duplicate ID even though the duplicate was disabled. I added and "X" to the "id" and "name" of the duplicated entry and the error messages ceased.
    Thanks for the help

  • Global expressions not always evaluated

    3
    0 Votes
    3 Posts
    180 Views
    tunnusT

    @toggledbits great! Will this fix make it to the next build?

  • [Solved] Local expression evaluation

    13
    0 Votes
    13 Posts
    527 Views
    tunnusT

    @toggledbits the main thing is that now I know that this behaviour is not a bug and there's a clear alternative (not using global variables when rule does not trigger often enough).

    Anyway, MSR is a great software and thanks for your continued support!

  • [Solved] Runtime error when exiting global reaction that contains a group

    7
    0 Votes
    7 Posts
    646 Views
    G

    @toggledbits Confirmed.

  • Cannot delete Global Expressions

    3
    0 Votes
    3 Posts
    256 Views
    SnowmanS

    The new built fixed the issue. Thanks for the fast response. Much appreciated.

  • Local notification methods?

    24
    0 Votes
    24 Posts
    3k Views
    toggledbitsT

    @therealdb said in Local notification methods?:

    @toggledbits time for a custom mqtt template

    LOL! I think for one topic, it might be a bit of overkill, but then, that's kind of how we roll, isn't it?

  • Custom capabilities in MQTT templates

    8
    1 Votes
    8 Posts
    477 Views
    toggledbitsT

    That is cool. I really love stuff that combines simple, available IoT bits with the old greasy bits to solve problems. It appeals to my libertarian steampunk fantasy of how I'd run my home, which unfortunately far exceeds my wife's tolerance for the lower limits of luxury over sustainability. 😆

  • [SOLVED]Hass websocket falsely reporting ready on boot??

    16
    0 Votes
    16 Posts
    644 Views
    toggledbitsT

    The alerts persisting is a sync problem with the alerts data object. I've found and (hopefully) fixed it for the next build. Both it and the Controller Status widget need special handing when the API connection is restarted.

Recent Topics