Multi-System Reactor

691 Topics 6.8k Posts
  • [Solved] VirtualEntityController setup

    Locked
    3
    0 Votes
    3 Posts
    144 Views

    @toggledbits my bad on the logs. I didn't necessarily think of this as "error" as much as "what did I miss??"

    Adjustment made and all looks happy.

    f56ae334-807b-42d1-91df-9a14fe1b620a-image.png

    4daa6b73-7325-458c-b845-b48451042826-image.png

  • Approach to Rulesets, a philosophic question

    Locked
    14
    0 Votes
    14 Posts
    533 Views

    @toggledbits I’ll try them soon. I’m quite busy at work, but I hope to remove a couple of virtual devices from my Vera and move ha bridge and my dashboard to native MSR http commands. Thanks for the addition!

  • Entity action & controllers

    Locked
    2
    0 Votes
    2 Posts
    75 Views

    Experience has taught me that it is usually more mystifying to users why a device isn't listed at all when they think they want to use it, than listing a device and having it display no attributes or actions for it.

  • 0 Votes
    4 Posts
    110 Views

    @toggledbits no errors in the log (sorry, I had a long day yesterday and was too late at home to check), but the new version is working good again. Thanks!

  • 0 Votes
    9 Posts
    186 Views

    Just to close the loop, per the release notes for 22257, a device exception was created for IBlinds 2.0, and @tamorgen confirmed via PM that it's working as expected.

  • OpenWeatherMap not providing any data

    Locked
    4
    0 Votes
    4 Posts
    108 Views

    @tamorgen I can assure you that OWM does work very well with MSR. I am not using the reactor.yaml config, however. I call to OWM with a ruleset that populates multiple variables. I do this for OWN, Apple Sky, and Ambient (from my own wx station's API.)

  • How to close these new metadata windows?

    Locked
    2
    0 Votes
    2 Posts
    80 Views

    Just tested this out on Chrome and the window disappears once the mouse moves away from the entity, have you tried a different browser perhaps?

  • 0 Votes
    14 Posts
    239 Views

    Upgraded successfully and the limit for Pulse is back!

  • 0 Votes
    11 Posts
    206 Views

    @cw-kid had the same situation, only after I totally removed "accept: ..." and didn't add it back, those alerts stopped

  • ZWaveJS new device alerts

    Locked
    2
    0 Votes
    2 Posts
    99 Views

    Sure. Can do.

  • Where do the icons come from?

    Locked
    4
    0 Votes
    4 Posts
    111 Views

    Yeah, I usually pay attention to the green text when looking for true conditions. The red x's look too much like a web error icon so didn't even think about looking at a true condition to see what it looked like.

  • 0 Votes
    5 Posts
    133 Views

    This warning can be ignored for HTTP Request actions only. It should be heeded for all other types. I will silence the notice on the next build.

  • Reactor not showing full vera device parameters

    Locked
    13
    0 Votes
    13 Posts
    374 Views

    So, I have found my missing parameters! They appeared following a reactor update. Perhaps next time I add new vera devices, I should stop reactor and re-start it after I have added the new devices and things have settled down. Anyhow, thanks again for your assitance Patrick.

  • Last Modifed Information

    Locked
    18
    0 Votes
    18 Posts
    434 Views

    Hi @toggledbits !!

    After your class in January, I started using Dynamic Group Controller to manage devices that have no changes after a period to alert me of an eventual problem (48 hours for one group and 7 days for another).

    "dgc_lastupdate_48h": name: DGC Last Update Up 48 hours select: - include_controller: - hubitat - exclude_entity: - "hubitat>54" - "hubitat>257" - "hubitat>56" filter_expression: > entity.lastupdate < (time()-172800000) "dgc_lastupdate_7d": name: DGC Last Update Up 7 days select: - include_entity: - "hubitat>107" - "hubitat>1569" - "hubitat>483" filter_expression: > entity.lastupdate < (time()-604800000)

    It works and helped a lot, but as you already said, it can fail because a simple name update or reset of the HE/MSR can update everything and not indicate failures. Even updating the battery does not mean that the device is working. It can send a signal, but having no action does not help to identify the failure.

    So I don't know if I could include in the Thanksgiving wishlist maybe something like Last Action, where it would store the date and time of when the device performs an action, i.e., the primary attribute that triggers a Trigger, for example.

    Sorry to bother you with this subject again, but with a very large number of devices that I already have, it is becoming increasingly difficult to identify failures, a device that stops working, and then impacts the entire automation.

    Thanks.

  • sunset/sunrise question in 22251

    Locked
    11
    0 Votes
    11 Posts
    170 Views

    @toggledbits I wasn't sure at the time of the OP post that it was a legit bug and not just... me.

    🙂

  • First post

    Locked
    8
    1 Votes
    8 Posts
    189 Views

    @toggledbits said in First post:

    Haven't used Fedora in a good while (although I'm a Berkeley guy), but most *nix has the which command you can use to find the path that a command lives in: which node

    That did it. I always forget that command!

  • 0 Votes
    18 Posts
    297 Views

    @toggledbits said in Create Expression to call out Entity ID of Tripped Binary Sensor:

    You can't do it in x_hass_system.call_service (specifically and uniquely) because the data is an object field in that action, and the substitution doesn't work in object types, only in strings.

    This restriction has been lifted in build 22251. The data will now be stored as a string rather than an object, so that substitution can occur. This requires that any use of call_service be edited, so that the stored data is updated to the new form. You'll get alerts for actions that need to be edited. See the announcement for build 22251 for more info.

  • Input Text Support for Home Assistant

    4
    0 Votes
    4 Posts
    121 Views

    @pabla said in Input Text Support for Home Assistant:

    Hey Patrick, now that I know I cannot use expressions in the data section of service calls

    This restriction has been lifted in build 22251.

  • Edit group detail

    6
    0 Votes
    6 Posts
    131 Views

    Build 22251 now up.

  • 0 Votes
    27 Posts
    686 Views

    @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.

Recent Topics