Skip to content

Multi-System Reactor

792 Topics 7.5k Posts
  • Edit group detail

    6
    3
    0 Votes
    6 Posts
    381 Views
    toggledbitsT
    Build 22251 now up.
  • [SOLVED] 'not in' being ignored latest-22240-3b3254d6

    Locked
    27
    5
    0 Votes
    27 Posts
    2k Views
    G
    @toggledbits After I saw this post I tested the daytime version and it behaved as intended. Half the battle down, we'll test the other half this evening. Thanks for the guidance here, it's a different approach but I can def see places where it's useful.
  • [Solved] ZWaveJSController Add-on Install files

    Locked
    8
    0 Votes
    8 Posts
    408 Views
    toggledbitsT
    No, it's a limitation of the Synology container manager, apparently. It doesn't seem to apply updated values from the new image to existing containers. I'll make note of that on the next Reactor build (later today) as well. I've also updated the instructions to just eliminate the install scripts; they don't do anything meaningful (everything ZWaveJSController needs is already in the current Reactor environment). When Reactor 22248 comes out later today, you will not need to upgrade to it unless you feel a need to get the one major new feature (ability to "wait for completion" when a reaction runs another reaction). If you don't need it, don't bother. But if you do decide to upgrade, you will also need to upgrade your ZWaveJSController to its 22248 build as well.
  • Can't upgrade package dependencies [Windows10]

    Locked
    6
    0 Votes
    6 Posts
    323 Views
    A
    @toggledbits said in Can't upgrade package dependencies [Windows10]: I trust the government more than I trust Windows. I'll leave it at that. Hard choice...
  • Hot Water Recirc - Global Date/Time Variable

    Locked
    7
    0 Votes
    7 Posts
    405 Views
    toggledbitsT
    Good approach! Very easy to follow the logic here.
  • Ezlo Plus - Philips Hue devices duplicates in MSR

    Locked
    14
    2
    0 Votes
    14 Posts
    581 Views
    cw-kidC
    @toggledbits Thanks for the additional information, that is certainly good to know about.
  • Can't MSR see my Hass groups /rooms?

    Locked rooms group msr sorting
    4
    0 Votes
    4 Posts
    316 Views
    toggledbitsT
    You can set up groups in Reactor now and they will carry through to the dashboard. Check out the documentation for DynamicGroupController under ControllerConfiguration. If you're just cherry-picking entities for membership, all you need to do is list them in include_entity. No dynamic filter is needed, so you will effectively create a static group.
  • Help with controlling Hue lights through Home Assistant & Reactor

    Locked
    4
    1
    0 Votes
    4 Posts
    223 Views
    S
    @toggledbits thanks that works great (the workaround). One slight typo though, you have script instead of scene in the graphic.
  • "changes from" operator stops to detect change

    Locked
    19
    1
    0 Votes
    19 Posts
    2k Views
    T
    Sigh. So this is weird. I updated to the latest and no change. I then took your advice and just was manually changing the Value8 variable in Vera from alpha to beta. It still didn't help. I finally took the 600 second delay out and noted that the set/reset started working. Put the delay back and all is good (I think). I'll keep an eye on it. Thanks for sticking with me on this one.
  • x_vera_device.failed=true Question

    Locked
    7
    1
    0 Votes
    7 Posts
    335 Views
    toggledbitsT
    The issue isn't that CommFailure was 0 or 1, it was that it wasn't there at all. That suggests it may have existed at some point with value 1, then disappeared, leaving the attribute value on the MSR side stuck (because it had no variable from Vera to use to change it). It's possible the Vera device handler has a bug and instead of setting 0 when the device is configured, it sets it to blank, which as of a couple of firmware versions ago, deletes the variable rather than setting it to an empty value. Having now created it manually, if it later disappears, that would confirm this theory -- something in the firmware is removing for some reason (or worst case, there's user_data corruption). In any case, CommFailure should always exist for Z-Wave devices, so something isn't right there, but of course, no chance that it would be researched or fixed these days. The Vera firmware thread has been long dead, no updates have been published, and questions and requests are left unanswered; I have my doubts that anyone with the knowledge (and will) is still there. Everyone's busy filling the holes in the new firmware (now four years since the acquisition).
  • Removed Devices and Scenes on Ezlo Plus remain in MSR

    Locked
    8
    0 Votes
    8 Posts
    327 Views
    cw-kidC
    @toggledbits Thanks Patrick.
  • Home Assistant Service Call - JSON/Formatting Question

    Locked
    8
    1
    0 Votes
    8 Posts
    1k Views
    PablaP
    @tbully Yeaup I have run into this issue with target as well, for some reason HA doesn't like it.
  • Issue with yellow triangles next to rules

    Locked
    4
    1
    0 Votes
    4 Posts
    259 Views
    S
    Here is the crazy thing. The sensor values were stale, I changed a value in the rule and then saved it. Now there isn't an exclamation point and the sensor value is updating as well. Almost like it was stuck after the upgrade?
  • Feature Request: Disable warnings about HomeAssistant Version

    Locked
    3
    0 Votes
    3 Posts
    210 Views
    R
    ok, fair enough.
  • Expressions in MQTT Payload?

    Locked
    5
    4
    0 Votes
    5 Posts
    365 Views
    therealdbT
    @toggled-bits yes, you’re right regarding JSON. I was referring to the syntax to concatenate variables and constant text. I’m not a blue iris expert and I’ll prefer mqtt anytime, since the retry logic is attached to the qos, whereas you’ll need to write a while block to retry in case of error when using http requests.
  • Rule corruption after sudden power outage

    Locked
    5
    3
    0 Votes
    5 Posts
    327 Views
    CatmanV2C
    @christian_fabre said in Rule corruption after sudden power outage: Thank you for your reply My system is a Raspberry Pi4 4GB with a 120GB SSD from stock. Which is weird, I had the same problem twice following power outages. I'm going to power it through my inverter to prevent this from happening again. Just to be clear: exactly the same issue? Same rules? C
  • Call Service Automation Trigger not Working

    6
    1
    0 Votes
    6 Posts
    500 Views
    PablaP
    So the issue was using data and target all that was needed was the automation's entity ID. Should look something like this now: { "entity_id": [ "automation.bar_alarm_is_not_on_actionable_notifications" ] }
  • Auto evaluation of time based global expressions

    6
    0 Votes
    6 Posts
    293 Views
    CatmanV2C
    As ever, works like a charm. Thanks! C
  • Parsing the output of http request

    7
    0 Votes
    7 Posts
    372 Views
    tunnusT
    Ok, I’m somewhat familiar with regexp, although it was years ago when I used them. It would be a nice extra to my telegram alerts, but have to think twice if it’s worth the effort
  • How Does MSR Handle New/Deleted Entities

    4
    0 Votes
    4 Posts
    321 Views
    toggledbitsT
    Hard refresh the browser, for sure. Reactor does not delete entities for missing devices/entities from the source hub/system immediately because sometimes transient things happen, and you would not want the Reactor entity to disappear and reappear (causes breaks/errors in rules and reactions). So it waits a bit to see if the hub/system brings it back. By default, Reactor entities that are orphaned for 24 hours or more will be purged. You can also delete them manually if you know they are gone and you don't want to wait.

Recent Topics