Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
S

sidmsmith

@sidmsmith
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Little Bobby tables...
CatmanV2C
...is back.... https://arstechnica.com/google/2025/08/researchers-use-calendar-events-to-hack-gemini-control-smart-home-gadgets/?utm_source=facebook&utm_medium=social&utm_campaign=dhfacebook&utm_content=null&fbclid=IwY2xjawMBq-pleHRuA2FlbQIxMQABHlSqIalzbz1IxcJFzlw8GBE6nC3FwvxcHgR370nJhogU6JjqbmRxG-lysqgh_aem_lx9XboYFKw9tpHnedGQKUA C
General Discussion
Home Assistant Voice TTS is Easy
toggledbitsT
Topic thumbnail image
Home Assistant
Play Audio through Home Assistant Voice Unit
toggledbitsT
Topic thumbnail image
Home Assistant
Home Assistant Voice
CatmanV2C
Has anyone had a play with the local voice control for HA? I've got one on order because... https://www.home-assistant.io/voice-pe/ C
Home Assistant
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can't customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
About
Posts
6
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Expression Evaluation - Last Seen Date/Time
    S sidmsmith

    I think I solved this with a completely different approach. Instead of using variables based on Last Seen, I am just checking the current state of the sensor and used the Restriction that the sensor must be FALSE (ie door closed) for 120 seconds. Not sure why I did not try this the first time.

    Screenshot 2024-09-03 181724.png

    Since my Reaction is now working, I should probably close this out as Solved. However, I am still interested in how to use a variable as described in the original post in case I need to use a similar approach in the future. Hopefully someone can provide some guidance (thanks realdb!) on how to use the variables. If I don't hear back within a few days, I will go ahead and update this as Solved.

    General Discussion

  • Expression Evaluation - Last Seen Date/Time
    S sidmsmith

    @therealdb Thanks for your feedback!

    I have not used a metadata statement like this before so have a follow up. I think I have the proper data elements. But is this statement supposed to be part of the Expression definition or the Reaction Trigger? The screenshot below shows what I tried creating the expression.

    Screenshot 2024-09-03 161415.png

    Sorry for the lack of understanding on my part! Is the goal to have the variable itself be true/false? Or is the goal to have the variable still provide a numeric result that is used in the reaction? I may just need a little more direction.

    Thanks again!

    General Discussion

  • Expression Evaluation - Last Seen Date/Time
    S sidmsmith

    I am trying to run a reaction that turns on lights if a sensor has not been tripped for 2 minutes. Basically, when a garage door is open, turn on inside lights if nothing has been sensed for 2 minutes. My question has to do with the expression/variable for "Last Seen". The variable never gets updated over time since the last seen event never changes.

    Screenshot 2024-09-02 191632.png

    In the screenshot above, the reaction checks for any garage door as well as the variable called "GarageLastEntry". The expression for this variable is displayed below:

    Screenshot 2024-09-02 191651.png

    The problem that I am experiencing is that the variable never changes over time. I understand that this is because the "last seen" variable does not change over time when there is no activity. In this screenshot, the value shows 0.029... This can also be seen as the current value in the original reaction screenshot above. After 10 minutes, this value should be 10. However, when a garage door is opened, the variable does not get updated and thus the rule does not become true since .029 is less than 2.

    When I go to the variable and click on the > icon, the variable then gets updated as expected as seen below:
    Screenshot 2024-09-02 191711.png

    So the ultimate question is, how do I use a rule that can use a variable such as "last seen"? Do I need to create another variable or reaction that multiplies this by 1 every minute? From what I read in the manual, a variable is evaluated every time it is included in a reaction. But this is not what I am seeing.

    I also want to ask another question related to this variable. It seems like Reactor continuously deletes this variable and I have to keep recreating it? I have never experienced this with MSR so wanted to ask if this is a common problem or if my definition is causing this.

    Any info is appreciated!!!

    General Discussion

  • MSR Not Actioning
    S sidmsmith

    I updated to the latest build and this solved all of my issues. Thanks for the suggestions! I will try to stay up to date on the latest stable builds from here on.

    Multi-System Reactor

  • MSR Not Actioning
    S sidmsmith

    I am running MSR on a small windows machine. Earlier this week, the machine restarted and Reactor restarted as well. I am now experiencing an issue in which Reactor doesn't seem to be making any updates or calling any scenes. Reactor is communicating with Vera and all entities seem to be accurate (ie lights on or off) and manually clicking on Actions seems to work just fine. The Status page also seems accurate and displays rules automatically being SET and RESET. But when the Reaction changes from SET to RESET or vice versa, none of the actions are actually invoked.

    For example, I manually ran a SET action at 11:29 and my lights turned on. At 11:30, the Status Dashboard shows the rule updating to RESET, but the lights did not turn off.

    I have included a screenshot of the rule history below as well as the log for these times as well.

    Any ideas on what can be going on? I have tried restarting the Windows machine as well as Reactor multiple times to see if this fixes this behavior but have not had any success. Any information is appreciated.

    78f9f75f-d24c-4ff4-a23a-fda0c98cbcbc-image.png

    [stable-22274]2023-04-14T03:29:39.161Z VeraController:null VeraController#vera enqueued task for Entity#vera>scene_3 action script.run: task [Object]{ "SceneNum": "3", "DeviceNum": 0, "id": "action", "serviceId": "urn:micasaverde-com:serviceId:HomeAutomationGateway1", "action": "RunScene" }
    [stable-22274]2023-04-14T03:29:39.587Z VeraController:INFO VeraController#vera 0 dead entities older than 86400000s purged
    [stable-22274]2023-04-14T03:29:45.763Z Rule:NOTICE Evening Lights Rule (Rule#rule-la4gnzmt) configuration changed; reloading
    [stable-22274]2023-04-14T03:29:45.766Z Rule:NOTICE Evening Lights Rule (Rule#rule-la4gnzmt) stopping
    [stable-22274]2023-04-14T03:29:45.772Z Rule:NOTICE Evening Lights Rule (Rule#rule-la4gnzmt) stopped
    [stable-22274]2023-04-14T03:29:45.773Z Rule:NOTICE Rule#rule-la4gnzmt (Evening Lights Rule) starting
    [stable-22274]2023-04-14T03:29:45.777Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) starting evaluation; because startup
    [stable-22274]2023-04-14T03:29:45.779Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) evaluated; rule state transition from RESET to SET!
    [stable-22274]2023-04-14T03:29:45.802Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) evaluation complete
    [stable-22274]2023-04-14T03:29:45.809Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) started
    [stable-22274]2023-04-14T03:29:45.811Z Engine:INFO Enqueueing "Evening Lights Rule<SET>" (rule-la4gnzmt:S)
    [stable-22274]2023-04-14T03:29:45.840Z Engine:NOTICE Starting reaction Evening Lights Rule<SET> (rule-la4gnzmt:S)
    [stable-22274]2023-04-14T03:29:45.842Z Engine:INFO Evening Lights Rule<SET> all actions completed.
    [stable-22274]2023-04-14T03:30:00.008Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) starting evaluation; because timer-trigger Timer#rule-la4gnzmt
    [stable-22274]2023-04-14T03:30:00.024Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) evaluated; rule state transition from SET to RESET!
    [stable-22274]2023-04-14T03:30:00.055Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) evaluation complete
    [stable-22274]2023-04-14T03:30:00.062Z Engine:INFO Enqueueing "Evening Lights Rule<RESET>" (rule-la4gnzmt:R)
    [stable-22274]2023-04-14T03:30:00.079Z Engine:NOTICE Starting reaction Evening Lights Rule<RESET> (rule-la4gnzmt:R)
    [stable-22274]2023-04-14T03:30:00.080Z Engine:INFO Evening Lights Rule<RESET> all actions completed.
    [stable-22274]2023-04-14T03:30:01.099Z VeraController:INFO VeraController#vera 0 dead entities older than 86400000s purged

    Multi-System Reactor

  • HTTP Request Max Response Limit
    S sidmsmith

    MSR has a parameter called "http_request_action_maxresponse" that can be updated within the properties. There is a good section describing this in the manual. However, the installation config file doesn't include the parameter out of the box. I was able to add the parameter (see below) and eventually got it to work after searching for a while.

    Suggestions:

    1. Include the parameter in the initial config file (or)
    2. Update the manual to state that the parameter should be added to the file

    Additional suggestion:
    I understand that it is potentially unsafe to have a large limit overall. However, some API calls unfortunately return large sizes which aren't necessarily problematic. The additional suggestion is to include a configurable max size within each HTTP Reaction in the UI. If it isn't populated then MSR could default to the config file like it does today. This way, we could have a reasonable default limit while allowing larger limit for certain HTTP calls.

      engine:
        #
        # enabled - Whether or not the rules engine runs. Change only when directed.
        enabled: true
        http_request_action_maxresponse: 10000
    
    Multi-System Reactor
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved