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

Edwin1972

@Edwin1972
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
71
Topics
15
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • When turning off the dimmer, set the LoadLevelLast to 100%
    E Edwin1972

    I have the following issue: In my Vera, I have created a dimmer using the Switchboard plugin. I want this light always turn on at 100% brightness when turn the light on. By default, the dimmer remembers its last used setting. I have created the following scene: when the light is turned off, the LoadLevelLast should be 100.

    9937e326-2453-43bd-bd32-917803b38e90-image.png

    Manually, this works through the test Luup code (Lua), but not through the scene's action by execute the following Luup code.

    I also tried in MSR, but no result

    Does anyone know the solution to this?

    Vera/openLuup plugins

  • [Solved] MSR actions aren't running anymore-- can't find what's broken
    E Edwin1972

    I updated my pi4 with commande sudo apt upgrade and then updated MSR to 23010 and everything works fine.
    Thanks you all for your response.

    Multi-System Reactor

  • [Solved] MSR actions aren't running anymore-- can't find what's broken
    E Edwin1972

    Thanks for quick response. I'm not handy with log files yet. I'll try in the weekend. first I will upgrade to the latest version.

    Multi-System Reactor

  • [Solved] MSR actions aren't running anymore-- can't find what's broken
    E Edwin1972

    Suddenly my MSR actions aren't running anymore. I've had this before, but with an update to a new version it was fixed. see also

    https://smarthome.community/topic/987/msr-actions-aren-t-running-anymore-can-t-find-what-s-broken/3?_=1674661492589

    But an update from version 22240 to 22256 gave this time no result.

    The reactions aren't running correctly. Most of my MSR automations are use turn lights on/off, and time based automations nothing worked where MSR does his magic.

    I've also tested a bunch of things to see what's broken, here's what I've observed:
    -I can successfully flip lights on/off manually within Vera
    -I can successfully flip lights on/off manually within MSR's Entities section
    -the sensors are correctly reporting to Vera and MSR (I can see when they're switch on/off)
    -the rules within MSR are working correctly, I can see when they flip to 'true' of 'false' '
    '
    But I cannot successfully run the "Set Reaction" and "Reset Reaction" within MSR (by hitting the 'play' button)
    But the play buttons on the entitiy action in the "Set Reaction" and in "Reset Reaction" they work well.

    Can someone help me to get MSR working again

    MSR is running bare metal on Rpi4

    Multi-System Reactor

  • use an expression for “condition must sustained for”
    E Edwin1972

    Reactor 22240-3b3254d6; Raspian bare-metal (RPi4)

    Is it possible to use an expression for “condition must sustained for”? I tried and no error but no result either. When collapsing condition options, the button remains yellow, but the content is no longer displayed when expanded.
    Is this a bug or not possible to use an expression for this?

    9fceec61-d200-4319-a28b-5e409a74883a-image.png

    Multi-System Reactor

  • Reactor 3.9develop-21009.1600 ALTUI Error
    E Edwin1972

    After upgrade everything works fine. @toggledbits Thanks again for the quick response.
    @amg0 When there is a new version of altui I always get an automatic notification. Can't I turn that off?

    Vera/openLuup plugins

  • Reactor 3.9develop-21009.1600 ALTUI Error
    E Edwin1972

    To day I also have the same problem. I've read the post, but can't trace the solution. I am using reactor (version 3.9develop-21009.1600) in openluup and AltUI v2.54.2553. Maybe someone can help me which steps I need to take to use reactor in openluup again.

    Vera/openLuup plugins

  • MSR actions aren't running anymore-- can't find what's broken
    E Edwin1972

    I had the same problem. After upgrade to new version the problem is solved

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    E Edwin1972

    I haven't found the time yet to fix MSR. I think there is something wrong with NPM. Node Red can't update some plugins either.

    Is it also possible to use the function in a reactor (openluup)?

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    E Edwin1972

    @toggledbits I have updated MSR to latest-21258-6fb388e but still get the same error

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    E Edwin1972

    Thanks for the quick response. I'm playing with it but I get an error when input expression.
    @toggledbits Is this due to the prerelease MSR? I am using version (pre-release) 0.1-21096. I haven't upgraded to new version yet

    61b5ee2b-bdb4-41a2-affb-c5048c3bc0cb-image.png

    Multi-System Reactor

  • Using Hikvision HTTP API request with MSR
    E Edwin1972

    I have a Hikvision camera for a month and have been playing with it. Now I read a post of cw-kid (post : System integration roadmap) that you can control the camera by HTTP API request. That's cool if that also will work for me. Can someone explain what to enter in MSR for HTTPS request command to do so. (Marked red arrows)

    93ca9c9a-9ab1-443c-9201-5efcff3a45e2-image.png

    I want to turn the smart supplement light on and off at a specific time. Now I do that with scheduled switch, but it is better to control that with sunrise and sunset function with MSR. I'm curious how it works.

    Multi-System Reactor

  • MSR http PUT error
    E Edwin1972

    @whyfseeguy I also have a Hikvision camera since a month and I'm playing with it. Now I read your post that you can set a variable remotely through ISAPI. That would be cool. Could you explain how you can do that with MSR. I want to turn the smart supplement light on and off at a certain hour. Now I do that with scheduled switch but it's better with sun rise and sun set with logic MSR

    Multi-System Reactor

  • Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge
    E Edwin1972

    @rafale77
    I overwritten the L_ZWay2.lua file. De Z-way bridge does its job. The devices gives reaction (ON/OFF) but bridge gives no update of Remote_2-0-0-14-S, Remote_2-0-0-24-S or Remote_2-0-0-25-S

    Z-Wave.me

  • Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge
    E Edwin1972

    @rafale77
    I overwritten the L_ZWay2.lua file (keep the old one) on my PI4. The z-way bridge does not give an error, but the switches no longer respond in openluup. After the old file has been restored, they will work again.

    Z-Wave.me

  • calculate with MSR variables in LuaXP
    E Edwin1972

    @toggledbits
    Yes, it works! Excellent.
    Thank you for your time! Now I can continue my project. The new variable is also useful.

    Multi-System Reactor

  • calculate with MSR variables in LuaXP
    E Edwin1972

    Thanks! I have installed version 21098 on my vera and I entered 2.5 but it returns the same as 2. With stopwatch about 50 sec.

    Multi-System Reactor

  • calculate with MSR variables in LuaXP
    E Edwin1972

    @toggledbits My explanation of my project

    I use somfy motors (rfx) to open and close my roman blinds electrically. I can control this via RFXtrx433E USB Transceiver connect to my Vera. RFX gives no feedback so I can only open and close them and not moving them to a position based on the percentage of the slider. The RFX plugin (Tinmann) works with a slider related on MaxMoveTime (time to go from completely open to completely close)., but it doesn’t work with somfy. So I started my own project.

    I have installed the switchboard plugin on my Vera. I have created a virtual switch (virtual window coverings) and use it in MSR to close my blinds with the slider based on MaxMoveTime (time to go from completely open to completely close). It works with Vera and also with voice control by google home.

    MRS setting:
    Expression : LoadLevel_Last_Oost, MaxMoveTime_Oost

    c54f6eef-6c95-4e79-b5af-ade45904c297-image.png

    What I haven't solved yet is the following:
    I can operate Romand blinds by MSR with time schedule but would like to operate Roman blinds manually with the fibaro roller shutter 2, double click down / up and triple click stop function. For example, with a double click function I can start the following action:

    a6473fa6-4705-4fe0-b364-8bfd00f567bf-image.png

    I am using the virtual window covering (Switchboard) and switching up (double click Up), down (double click down) and stop (Triple click down). Switchboard can simulate motor movement of the covering by ramping LoadLevelStatus at a rate of XX% per second to the target value. This is the problem.
    MaxMoveTime (time to go from completely open to completely close) = 40 sec. Switchboard simulate motor movement = 34 sec (RampRatePerSecond =2).

    To set simulate motor movement =40 seconds, RamRatePerSeconde should be = 2.35. This does not work because they must be integer number. Is there a possibility to set the MaxMoveTime to simulate motor movement instead of movement % per sec?

    Multi-System Reactor

  • Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge
    E Edwin1972

    Check, Implementation file in the plugin device is I_ZWay2.xml.

    95f94047-2516-477e-9b30-76ab971efbad-image.png

    Z-Wave.me
  • Login

  • Don't have an account? Register

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