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
HA and AI
CatmanV2C
Having hours of (actually quite fun) interaction with AI (Chat GPT) making up dashboards and sensors for HA. It's OK (well it's better than I am!) but it makes soooo many mistakes. Gets there in the end though, if you've half a clue (which I do half the time) C
Home Assistant
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Genuinely impressed with Zigbee and HA / Reactor
CatmanV2C
Just for the record, in case anyone is following, I'm really rather impressed. I have installed one of these: https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 That's connected (physically) to the VM running on my Synology, with a 2m USB extension. The same host also runs Openluup, Mosquito, HA Bridge. Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions. Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA. https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so... https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt. And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one). A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....) Commended to the house. Thanks for everyone that got me on the right lines. C
Zigbee
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[HowTo] Using HABridge with Reactor
therealdbT
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO: Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1. Then, configure these endpoints as needed: On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off Dim: For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent} For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent} Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b} Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier. This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa! If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
How-To
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
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