Multi-System Reactor

729 Topics 7.0k Posts
  • 8 Votes
    1 Posts
    669 Views
    No one has replied
  • 5 Votes
    108 Posts
    14k Views
    Reactor build 22243

    POTENTIAL BREAKING CHANGE: The conditions in a Reaction's repeat...while group are meant to be Constraints, not Triggers -- they are stateless, meaning that they are evaluated each time they are run, not when an underlying condition triggers them (such as a timer expiring on a sustained for option). This was always meant to be the case, but an error in the UI implementation permitted certain condition options applicable only to trigger conditions. This is now fixed, and any constraints containing condition options will have those options removed during later editing, and the options will not function (they haven't been working correctly anyway) until that time.

    Shell Command action now supports expression substitution. This makes an already dangerous (security-wise) action even moreso, so it must be enabled explicitly by setting allow_shell_action_substitution: true in the engine configuration section of reactor.yaml. It is highly recommended that Shell Command actions only be used on systems that have HTTPS access and Access Control (user authentication) enabled, to reduce the possibility that the action could be a vector for attacking the host system and your network. PR 0000378: VirtualEntityController: fix configuration collision between virtual entities affecting time-series aggregations. PR 0000369: Add error attribute for ev_charger system capability documentation. PR 0000349: Support custom sounds for Pushover notification. PR 0000290: Display rule ID in rule editor (convenience). HassController: Bless Hass to 2024.8.3 ZWaveJSController 22242

    BREAKING CHANGE WARNING: The entity IDs of certain child entities may change to reflect a more deterministic naming style. Entities principally effected would be those created in 2022 and earlier for scene activation. Rules that use these entities will need to be updated.

    Handle notification special events (in Notification CC 113 type 6) for locks for better performance of keypad capability attributes (where the device and Z-Wave JS support it). Update Fibaro FGR222/FGRM222 handling for manufacturer proprietary venetian blind position and tilt Creation of child entities is expanded to include all command classes that result in capability/attribute collisions on an entity. That is, if two or more values (from Z-Wave JS) on an endpoint resolve to the same Reactor capability, a new child entity is created.
  • 0 Votes
    3 Posts
    31 Views

    I'll keep this instruction for the future. I got frustrated, reset the device and paired it again and it's now reporting good when changed. I tried everything before the inevitable dance. Who knows what was corrupted. Guess "it's just Zwave"™️ Thanks.

  • Rule Execution Sequence

    6
    0 Votes
    6 Posts
    76 Views

    @wmarcolin what if you do this like below:

    Rule 1: commands/reactions up to (and including) shutdown
    Rule 2: triggers when rule 1 is true with a long delay reset value (or maybe latching), and commands/reactions start with 900 s delay and the rest of the reactions

  • 0 Votes
    6 Posts
    102 Views

    0 closed, 99 open (so, horizontal). 50 is 50% open. But maybe my device is specific, I've never been able to open more than flat/horizontal.

  • 0 Votes
    37 Posts
    559 Views

    Try activating the central scene on the device. Since these values are events, they aren't created until the first event is received. You may also need to refresh the browser, or at least "stimulate" the redraw of the entity list (by modifying the filters, etc.).

  • 0 Votes
    6 Posts
    83 Views

    I've seen this before on some battery devices. A couple I have will also go to uninitialized after replacing batteries. Kind of a pain, but I think years of Z-Waving has conditioned us all to a few "quirks".

  • 0 Votes
    9 Posts
    92 Views

    ok, easier. Go to your homeassistant installation directory, look for an hidden .storage folder, and then core.config_entries. entry_id is the key you'll need.

  • 0 Votes
    2 Posts
    55 Views

    A lot more specifics about the device and attribute are needed to answer this question. Please review the posting guidelines and update your head post (post your additional information by editing the head post, not posting a reply here).

  • 0 Votes
    4 Posts
    79 Views

    @toggledbits It never crossed my mind to use HTTP. I'll give it a try.

  • 0 Votes
    3 Posts
    48 Views

    Since you're fixing shutters, don't forget the tilt position 😉 Thanks!

  • 0 Votes
    8 Posts
    68 Views

    Yeah, that's related to recent changes Z-Wave JS made for similar devices. They are now supporting a command class they didn't before. Start a new thread for it, and I'll run it down.

  • Issue with Zooz Zen14 outlet and Zwavejs

    7
    0 Votes
    7 Posts
    125 Views

    @toggledbits said in Issue with Zooz Zen14 outlet and Zwavejs:

    Try build 24232 of ZWaveJSController just posted. This is an interim build.

    That appears to have fixed the issue. Thanks!

  • This topic is deleted!

    1
    0 Votes
    1 Posts
    1 Views
    No one has replied
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    1 Views
    No one has replied
  • 0 Votes
    12 Posts
    324 Views

    For me a "for/foreach" could be useful as well, when dealing with multiple devices and the same actions. Now this part is all code.

  • MSR, Repeat While not evaluated?

    5
    0 Votes
    5 Posts
    82 Views

    Redesign in progress. Thanks again for this great multi platform tool.

  • 0 Votes
    2 Posts
    104 Views

    @Andr said in Need some advice how to fix a rule that throttles sometimes.:

    I had understand it that if Constraints isn't true, then the triggers isn't evaluated.

    Nope. The triggers are evaluated first. If they are satisfied, then the constraints are examined. So that 180 updates per minute from the Shelly is what's causing the throttling.

    You need to reduce the frequency of updates from the source device to the rule. Since you seem to only care about the power over a period of 10 seconds, you could use the time series features of VirtualEntityController and produce, for example, a 10-second moving average. The VEC will gobble update the individual updates from the Shelly and drive virtual sensors that advertise the moving average, per phase. Your rule can then check the average from the virtual sensors (you probably don't need sustained for at that point, because the moving average contains the time component). Depending on how "bouncy" the source power readings are, it may still update a lot, but you can tune/dampen that by playing with the precision (e.g. set precision: -1 to round to nearest 10 watts).

  • Delete many entities more efficient?

    Solved
    5
    0 Votes
    5 Posts
    114 Views

    @toggledbits Thanks! This is the solution I was looking for, since I'm not that patient... 🙂

  • 1 Votes
    43 Posts
    2k Views

    I got a tons of new Gen3 devices, so expect lots of new templates! 🎉

    In the meanwhile, v 24210 is online https://github.com/dbochicchio/reactor-mqtt-contrib/releases/tag/24210

    New shelly_relay_power_gen3 to get power meters via Gen3 devices and a couple of fixes here and there.

Recent Topics