Multi-System Reactor

684 Topics 6.7k Posts
  • 8 Votes
    1 Posts
    564 Views
    No one has replied
  • 5 Votes
    95 Posts
    11k Views
    Reactor Build 24052

    BARE-METAL USERS: It is recommended that you update package dependencies when installing all Reactor updates. After unpacking the Reactor archive, remove any existing package-lock.json file from your Reactor install directory, and then run npm i --no-save --no-package-lock --omit dev to update package dependencies.

    BREAKING CHANGE: The valve capability's state attribute value is now boolean, to match similar system capabilities (was previously/erroneously string). If you are using an entity with the valve capability in conditions or actions, make sure the type for the current or target state is boolean now.

    Update support for many packages. Please remember to do npm i --no-save --no-package-lock (bare-metal installs only; docker containers are always up-to-date). Add ability to override the state of a rule from the UI, for logic debugging purposes. A disabled rule will have its state forced, but will not run its reactions. An enabled rule will also have its state forced, but the corresponding rule reaction will run on the state transition. When overridden, the trigger and constraint conditions have no effect on the overall rule state, but (if rule enabled) are still evaluated and their status is still accurately displayed on the status card for the rule in the UI. PR 0000357: Implement getRule() extension function to get rule metadata; refer to the docs for more. Fix an error in the handling of the entity action cache in the UI (occurred when running actions from the entity detail in the Entities list). Docs: improvements to description of custom event handlers for HassController (still a work in progress, but isn't everything?). Docs: add a section in VeraController doc for the firmware's UnsafeLua flag, required to be on for the x_vera_sys.runlua action to be available. The value is now also published as an attribute on the system entity. HassController: Implement new HA valve domain with our valve capability. HassController: Bless Hass to 2024.2.2 MQTTController Build 24050

    NOTE: Either 24049 or 24050 of MQTTController is required for Reactor 24052.

    Rebuild entity when configuration change detected (supports version field in user templates). PR 0000365: Fix broken config for tasmota_generic_relay template's toggle.toggle action. New templates for genmon (generator monitoring; see https://github.com/jgyates/genmon) Support for new js-yaml Support map in event handling configuration.
  • ZWaveJSController - open/close reversal

    2
    0 Votes
    2 Posts
    6 Views

    What capability?

  • 0 Votes
    10 Posts
    47 Views
  • 0 Votes
    3 Posts
    40 Views

    That setting is in Users & Account Info - Security - Enable potentially unsafe lua code, like wget and RunLua.

    It was unchecked. I checked it again and Reloaded the engine and it started working again. I am not sure how that setting got turned OFF as I didn't do it.

    But thanks anyway for pointing me in the right direction !

  • Expression for Seconds Left in Day

    Solved
    3
    0 Votes
    3 Posts
    42 Views

    Exactly what I needed thanks Patrick!!

  • Widgets and filtering

    10
    0 Votes
    10 Posts
    200 Views

    @toggledbits I was thinking of the list of running tasks as "Set Rules", a simple way of having this query.

  • Feature Request: Disable Individual Actions

    2
    1 Votes
    2 Posts
    71 Views

    If you use groups in your reactions, you can disable those individual groups, might help a little

  • Actionable notification question

    7
    0 Votes
    7 Posts
    93 Views

    I realize the documentation on configuring event handlers isn't great. I've made some updates and will post them later today, but I still feel it needs work. Feel free to ask questions and make suggestions; then I'll know what holes to fill.

  • Reaction using Shell Command SSH

    2
    0 Votes
    2 Posts
    93 Views

    Update ot anyone trying to SSH from Multihub Reactor...

    I went to a linux bare metal install. Installing through the Add On store reset the docker image with every HASS restart. This means openSSH and the shared keys would disappear.

    Also - at time of writting the AddOn store version is out of date with no appearant activty. Likely to change, but I moved on to give more flexability to MSR.

    I look forward to the unintended consequences 🙂

  • 0 Votes
    3 Posts
    102 Views

    I did not write the Reactor Add-on installation method/package for Home Assistant and I do not support it. I have no idea how it works, and I don't have a setup to debug/troubleshoot with. Perhaps another user of the Reactor Add-on can chime in.

    There was a related question/post in late December, here, and other recent posts. Check those out. They may provide some insight.

    The user who originally provided that add-on is no longer providing updates, apparently. Perhaps someone else who uses this configuration would want to pick it up?

  • 0 Votes
    4 Posts
    185 Views

    Yes, I would be interested.

  • 0 Votes
    2 Posts
    81 Views

    I love it when solutions come to you in your dreams. It dawned on me that my Hub Security on the hub was reset but I still had it enabled on MSR. As soon as I enabled it on my hub and restarted MSR, and literally had a kid walk through the entire house, every motion sensor was tripping back and forth from inactive to active back to inactive.

  • Alarm from Home Assistant MQTT format into MSR

    3
    0 Votes
    3 Posts
    124 Views

    I don't have a Zwave/Zigbee Alarm, so I really don't know. I tried to search for something, but these alarms are not common. Right now, I'm just setting the same value coming from the payload.

    I had a virtual AlarmPartition under Vera and it was not mapped to security_mode, but that's fair, because I'm quite sure this capability was used in plugins and not by real devices.

    EDIT: since we're at this, is it safe to assume that the values reported in the docs (http://msr.bochicchio.it/docs/Standard-Capabilities/#other) are lower case instead of the case reported in the doc page? Thanks @toggledbits

  • 0 Votes
    16 Posts
    313 Views

    @toggledbits thanks.
    I've modified the build.sh from the other add-on and set up docker hub. Despite not fully being able to understand what and where Linux read/write errors actually arise from, I've got the files built and pushed. Had to use a pi to build the arm and aarch, then Ubuntu in Windows to build the amd64 due to errors and warnings about architecture. Unsure if that has to be that way, or they should be buildable from one platform or not.
    This was the better idea as when I tried to update the other add-on container, msr warned about node.js being out of date by doing it that way.
    I've got my version loading from a local plug in and pulled/running from GitHub now on my test install. Only thing to work out
    Only thing left to work out is why the alerts/entities aren't updating, but I'm thinking that's because the default in msr points to a dns name for HA. Which is likely resolving to my prod HA Yellow (incorrect login alerts on there also point to that). Was a rush before I needed to head away. I'll backup/remove and pull the new add-on to my prod. hardware once at a computer I can work properly from, then copy the rulesets etc into a backup for that and re-export it.
    Appreciate the tips from you and @Pabla
    It's a bit more work to build the files and pull into my own add-on but it's better I have the control and still run a supported HA install 🙂

    Update: That was it, installed/updated Reactor on my HA Yellow, entities updating as expected 🙂

  • 0 Votes
    3 Posts
    89 Views

    @toggledbits Got it. Will show all attributes next time. Thanks

  • [RESOLVED] PSA for Hubitat 2.3.7.x upgrade

    8
    0 Votes
    8 Posts
    208 Views

    🤔

  • 0 Votes
    4 Posts
    113 Views

    You don't need to configure any custom events. The ZWaveJSController mapping for the ZEN32 produces five entities, usually named xxx Scene001 through ...005 (where xxx is your base device name). These all publish the button capability.

    See also: https://smarthome.community/post/15176

    1614dbc8-0619-498c-a504-af9223f5a336-image.png

  • 0 Votes
    5 Posts
    103 Views

    Nice- very flexible.

  • 0 Votes
    7 Posts
    163 Views

    Happy to hear it worked out!! Just a tip if you chose to control your Envisalink through HA-Envisalink and not HA-Vera-Enivsalink take a look at this integration. It has a few more features than the native Envisalink integration.

Recent Topics