Skip to content
  • 0 Votes
    41 Posts
    2k Views
    3
    I don't know if my issue is related or not here. It seems like it should, but I also understand that local expression handling has changed within the last couple of builds. I don't know exactly when my issue started, nor what build I was on. My guess would be Sept 7th as my rule was last "SET" on that date. I am running latest-25254-f6a45e41 in a docker on unRAID. The following rule has been in place for years and has been working pretty reliably, until recently. [image: 1758138895825-e28ec3c2-6787-450e-82b3-1576b3b9b5b1-image.png] The Set Reaction is just to turn on the shower exhaust fan. I collapsed it for screenshot space. If I change the Local Expressions to: (and in this order) MBath_HumityRise = "CurrentHumidity - MBath_prevHumidity" MBath_prevHumidity = "CurrentHumidity" CurrentHumidity = (some # value like 48) And then manually change the CurrentHumidity value to 54 (something >=3), the rule triggers. The MBath_HumidityRise value changes to 6 too. Setting the CurrentHumidity to 50, changes the HumidityRise value to -4. When I set these expressions back to pull from the device, I see the prevHumidity value change, but the HumidityRise value always stays 0. I set up global expression under different names and watched the values too. In the same order with the Rise expression above the Prev expression, I never see the Rise value change. I will see if I have 25260 available for my docker update and test that, but for the life of me I cannot figure out why this rule stopped working.
  • [Reactor] Copy&Paste of Rules

    Multi-System Reactor
    1
    0 Votes
    1 Posts
    152 Views
    No one has replied
  • 1 Votes
    45 Posts
    7k Views
    therealdbT
    Version 25244: https://github.com/dbochicchio/reactor-mqtt-contrib/releases/tag/25244 Add new Shelly Gen3 templates for dimmer and energy meter, modify version in manifest.yaml to 25244, enhance sensor expressions for accuracy, and improve event handling and actions. General refactoring and cleanup across YAML files for consistency and quality.
  • 0 Votes
    5 Posts
    275 Views
    toggledbitsT
    This looks like a job for a finite state machine. An alternate way to tackle this may be to have a state local variable that's just a number/counter that increments when the scene controller button is pushed... Set Variable state = ${{ ( ( state ?#0 } + 1 ) % 3 }}. This will make state cycle through the values 0, 1, 2, 0, 1, 2... Then the reaction has these groups: When state == 0: turn both fans off When state == 1: turn 1 on, 2 off When state == 2: turn 1 off, 2 on [image: 1756482827376-2b5121d9-527f-4151-a719-7859c19bcd89-image.png] It's easy to add a fourth state if you want the option of having both fans on at the same time. I'll leave the changes as an exercise for readers. DM if you need a hint.
  • Stop the MSR by an external switch on Hubitat.

    Multi-System Reactor
    6
    0 Votes
    6 Posts
    489 Views
    Tom_DT
    I would never rely on automation to keep equipment you are working on off. Turn it off at the breaker or disconnect.
  • Expose MSR entities

    Multi-System Reactor
    11
    0 Votes
    11 Posts
    447 Views
    CatmanV2C
    You are both gents! C
  • Comment in Globa Expressions

    Multi-System Reactor
    2
    1 Votes
    2 Posts
    445 Views
    CrilleC
    Maybe not the prettiest way to do it but why not let the rule set the comment followed by the value? Like ”This is set by rule Test”, value
  • Little Bobby tables...

    Unsolved General Discussion
    3
    0 Votes
    3 Posts
    334 Views
    CatmanV2C
    @akbooer indeed so C
  • Home Assistant Voice TTS is Easy

    Home Assistant
    3
    2
    0 Votes
    3 Posts
    458 Views
    CatmanV2C
    I take it back. Worked immediately! C
  • Play Audio through Home Assistant Voice Unit

    Home Assistant
    1
    2
    1 Votes
    1 Posts
    291 Views
    No one has replied
  • Home Assistant Voice

    Home Assistant
    21
    0 Votes
    21 Posts
    1k Views
    CatmanV2C
    Watching with great interest! C
  • Unofficial thread for compatibility

    Multi-System Reactor
    1
    2 Votes
    1 Posts
    261 Views
    No one has replied
  • Gradually turn on lights.

    Solved Multi-System Reactor
    21
    0 Votes
    21 Posts
    1k Views
    toggledbitsT
    @tbully said in Gradually turn on lights.: I'm having this same issue with a bare metal install. I assume this fix will be included in a future release? (No hurry. This is just a nice-to-have thing...) The 25208 build released yesterday includes the fixes in the temporary containers built for @vezinpi and others on this thread.
  • 5 Votes
    123 Posts
    60k Views
    toggledbitsT
    Reactor build 25208 Status page: fix an issue placing the widget adder tool the first time (i.e. on a new browser or after flushing cache/cookies). HTTP Request action now offers storage of the query response in "advanced form." This is a structure (object) that includes the response body as well as the response status, messages, and response headers. The simple form (store body or null) is the default and all existing HTTP Request actions will use the simple form response unless/until modified. Telegram notifications now support photo and video messages. To send a photo or video message, select the appropriate Message Format and place the URL or filename in the Message field. Telegram's limits for file type and size must be observed (refer to Telegram's documentation). HassController: Configuration for filter_entity now accepts regular expressions to match to entity IDs (i.e. it can now do pattern matching, not just match exact strings). Specify regular expressions in /regexp/flags form (e.g. /^update./i to match IDs that begin with update., case insensitive; flags are optional, and the only flag supported right now is i for case-insensitive matching). HassController will requery for service data if the lookup of service data from the startup query does not have the needed info. This can occur when an integration is not fully up and running when HA restarts -- HA will only report on services for fully running integrations at the time. The requery updates the service data for integrations that start later. HassController remove old entity mapping configuration that was preventing a mutable attribute (dimming.step) from being changed by the user permanently. Expressions: new geodist() extension function to compute Great Circle Distance between two points (presumably on Earth). See docs for details. Example: kilometers = geodist( lat1, lon1, lat2, lon2 ) HassController: Bless Hass to 2025.7.3
  • Can't customize home page

    Multi-System Reactor
    15
    0 Votes
    15 Posts
    554 Views
    G
    @toggledbits appreciate the quick turnaround on this. It def caught me off-guard.
  • Error After Upgrade

    Multi-System Reactor
    4
    1
    0 Votes
    4 Posts
    509 Views
    G
    @tbully thanks for putting a smile on my face today. Much needed. Much appreciated.
  • 0 Votes
    5 Posts
    810 Views
    R
    Seems to be working perfectly. Thanks! Should have thought of that myself.
  • 0 Votes
    22 Posts
    3k Views
    G
    @therealdb I use those as well. As you see in my AWAY rule there's a catch there using a virtual switch for my calendar integration. If a calendar entry has a specific keyword it turns the switch on. If the switch is on, AWAY knows not to fire.... VACA has it covered. @toggledbits beat me to it: comments, comments, comments. I've lost too many years off my life trying to remember why this rule does what it does and how.
  • 0 Votes
    3 Posts
    296 Views
    T
    That's fair. Thanks for answering with a workaround at least
  • Links to MSR from HA

    Multi-System Reactor
    1
    0 Votes
    1 Posts
    272 Views
    No one has replied

Recent Topics