Multi-System Reactor

705 Topics 7.0k Posts
  • 8 Votes
    1 Posts
    633 Views
    No one has replied
  • 5 Votes
    104 Posts
    13k Views
    Reactor STABLE Update

    The stable branch of Reactor is now updated to build 24057. For changes, please scroll back and see the changes and advisory listed since the previous stable branch build (which was 23344).

    IMPORTANT: Bare-metal users will need to update installed packages (see note here) and be aware of the breaking change notification (same link).

    NOTE: This will be the last stable branch release that supports versions of nodejs < 18. If you haven't yet upgraded nodejs on your system, you will need to do so before the next stable update (an even-numbered LTS version is recommended). This applies to bare-metal users only; docker users have compatible versions of nodejs built into the Reactor distribution image.

  • 0 Votes
    3 Posts
    104 Views

    That did it. Thanks for your help.

  • 0 Votes
    9 Posts
    359 Views

    It's the same for dimming.set and power_switch.set all .set, an entity rebuild solves those too with 24162.

    (@toggledbits Mantis ID 372)

  • [Dev] Inheritance in MQTT templates?

    39
    1 Votes
    39 Posts
    581 Views

    Yep, all warnings gone! Thank you for all your work!

  • Need Testers

    Locked
    78
    1 Votes
    78 Posts
    2k Views

    The userauth branch has now been merged into the main line release path (latest), and released in build 24152. This topic is now closed. Open new topics for any new issues.

    Thanks to all of you for your work in testing these changes.

  • 0 Votes
    6 Posts
    108 Views

    Understood! Reverted to 24120. All good.
    Thanks for the heads up on the localization file.

  • 1 Votes
    42 Posts
    2k Views

    v 24146 is out.
    Mainly refactoring, with the addition of the first Shelly Gen 3 device (a relay).

    GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor

    Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

  • VirtualEntityController & time series

    6
    0 Votes
    6 Posts
    217 Views

    Yup, I'd expect that, based on my testing. All aggregates are working except weighted average.

    Two issues, first, a doc error, it should be wa for the aggregate name, not wma.

    Second issue, computation is botched, so it will give a value, but it's incorrect. But the brain-fade on my part was simple, and you can easily work around it until I get the next build out: add expr: "value*X" where X is the depth you've requested (e.g. 4).

    Next build will fix it, but remember to remove the expression workaround when you install it.

    (I know there are five samples, but "depth" should handle that?)

    Correct!

  • 0 Votes
    9 Posts
    120 Views

    @toggledbits,
    Thank you Patrick. It's not throwing an alert now. Very elegant solution.

    I'll verify that it works once I get in the car after work and marked the thread as solved.

  • 0 Votes
    2 Posts
    93 Views

    Solved: Figured it out myself. I needed to add - include_group: "zwavejs" into the yaml file. This took out most of the extraneous entries that are battery powered.

    I still had a couple of ghost zwavejs nodes that I needed to manually remove. I may have to try and reset the zwavejs db somehow and get a clean reading of all the devices.

  • MQTT action & expressions

    6
    0 Votes
    6 Posts
    160 Views

    @therealdb & @toggledbits it wasn't that easy... I finally got this working, but it took a couple of iterations. Correct version below:

    pool_set_temp: capabilities: [ hvac_heating_unit ] primary_attribute: hvac_heating_unit.setpoint actions: hvac_heating_unit: set_setpoint: topic: "pool/set" payload: type: json expr: '{ "command": 4, "value": min( 30, max( 20, int( parameters.setpoint ) ) ), "time": 0, "interval": 0 }'

    Devil is in the details I guess.

  • InfluxFeed plugin & throttling export

    4
    0 Votes
    4 Posts
    156 Views

    I'm prototyping something that may make a good general solution for this.

  • 0 Votes
    1 Posts
    198 Views
    No one has replied
  • How to HTTPS

    6
    0 Votes
    6 Posts
    440 Views

    @gwp1 Your certificate won't work then

    C

  • 0 Votes
    7 Posts
    283 Views

    This code is now obsolete because the latest versions of both MSR and MQTTController have this behavior natively. I'll leave it just in case someone wants to look at some code enumerating/saving attributes.

  • 0 Votes
    16 Posts
    812 Views

    Awesome, that did the trick!

    Screenshot 2024-04-25 at 9.31.15 AM.png

  • Can't Restart Reactor - Corrupted SD Card?

    7
    0 Votes
    7 Posts
    402 Views

    To close this thread out, it wasn't a Reactor issue. My Rpi 3B+ was simply overheating and throttling processes. Moved to an Odroid N2+ with a heatsync running Ubuntu and everything is running smoothly!

  • Post-DST and MSR not reflecting local time

    18
    0 Votes
    18 Posts
    2k Views

    @toggledbits yeah, I just got new hardware and am considering moving to the containerized version. But that's going to take some time as it's tech I've not played with before and my day job + new puppy haven't left much dev hours these months. 🙂

    MSR is now very integral to the operation of this house so I need to tread carefully when poking the proverbial bear.

  • 0 Votes
    3 Posts
    231 Views

    Rene,

    You don't need all that, this should be sufficient:

    select_capabilities: power_sensor: attributes: value: true

    or the equivalent, using an array of attribute names (my favorite):

    select_capabilities: power_sensor: attributes: [ 'value' ]

    or using the other YAML array syntax:

    select_capabilities: power_sensor: attributes: - value

    You can also use a negative to suppress an attribute:

    select_capabilities: power_sensor: attributes: [ '-units' ]

    Also, can I ask that you go back and fix the formatting of the code sections of your posts, for the benefit of future readers looking at your question and example solution?

Recent Topics