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

akbooer

@akbooer
This trigger no longer working - complaining about the operator needing changing
cw-kidC
Topic thumbnail image
Multi-System Reactor
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
Can you run MSR on Home Assistant OS ?
cw-kidC
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC. Sounds like Home Assistant OS is linux based using Docker for HA etc. Would I also be able to install things like MSR as well on their OS ? On the same box? Thanks.
Multi-System Reactor
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
Self test
CatmanV2C
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something? Cheers C
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
About
Posts
1.5k
Topics
23
Shares
0
Groups
1
Followers
3
Following
0

Posts

Recent Best Controversial

  • HDMI oddness
    akbooerA akbooer

    @CatmanV2 said in HDMI oddness:

    It does however have a SCART socket. Maybe I should use that 😉

    😲

    General Discussion

  • Single protocol?
    akbooerA akbooer

    @Pabla said in Single protocol?:

    Not sure if anyone could possibly use one protocol for everything however, in my case for my switches, plugs, door locks and some door/motion sensors they all are using z wave.

    No specific reason why, it's mainly because I started with vera which had built in z wave so It was familiar to me when I switched over from HA.

    The opposite effect for me… when I finally gave up on Vera, I ditched all my Z-wave devices and switched to Shelly using WiFi for all wallbox switching devices. So, I’m at a loss to understand this comment…

    IMO you can't go wrong between Zigbee or Z wave. I would stay away from any wifi devices though since you limited to what local control they offer, and definitely avoid, at all cost any cloud reliant devices for obvious reasons.

    Wi-Fi seems to give all the control I need, integrates easily with Apple Home, which I use as my main control, now. For some individual lights I use Zigbee, in the form of Philips Hue, which also has a native bridge to Apple Home, which also offers a secure cloud connection for off-site access. I’m slowly upgrading to Shelly Gen 4 devices which offer Matter protocol which will enable me to abandon the Homebridge software running on my NAS for further simplification.

    General Discussion

  • There is an alternative to homebridge-mqttthing
    akbooerA akbooer

    This is great timing! I’ve just been re-jigging my Homebridge config, finally removing the Hue bridge plug-in in favour of a native connection through my Home Hub mini.

    But there’s more to do, and this might help. Thanks.

    Software

  • Shelly Wall Display XL
    akbooerA akbooer

    Support for RGBW LED strips is excellent!

    IMG_4556.jpeg

    Hardware

  • Shelly Wall Display XL
    akbooerA akbooer

    You inspired me to give the original wall display a go…

    …I like it! (More configuration to do). This is unmodified Shelly firmware.

    IMG_4591.jpeg

    Hardware

  • Do you Matter?
    akbooerA akbooer

    I got a bad impression of Zwave from Vera, quite incorrectly. Should have stuck with it but actually dumped it. Mostly Shelly now, and its Gen 4 modules are Matter capable.

    General Discussion

  • Do you Matter?
    akbooerA akbooer

    Well, that seems remarkably easy configuration…

    Just added a Shelly 2PM Gen4 (dual switch) to Apple Home. It just required me to scan the QR code from the Home app and wait a short while.

    No other configuration required initially. In particular, no need to set up IP addresses or anything.

    Subsequently, I did enable MQTT and openLuup picked up on it immediately (although as a generic Shelly device, because I haven’t included that as a recognised device, yet.)

    Control seems to work instantly from Apple Home app. Now need to link it to automation and other switches.

    So far, so good.

    General Discussion

  • Do you Matter?
    akbooerA akbooer

    Is anyone using the Matter protocol to connect devices?

    General Discussion

  • Shelly Wall Display XL
    akbooerA akbooer

    Ooohhh. Nice!

    Hardware

  • Shelly Wall Display XL
    akbooerA akbooer

    Yes indeed, let’s hear/see more!

    Hardware

  • Little Bobby tables...
    akbooerA akbooer

    …had to happen.

    General Discussion

  • Home Assistant Voice
    akbooerA akbooer

    @CatmanV2 said in Home Assistant Voice:

    Cheers! I shall try and make some time 🙂
    (Is it just me that hates having to watch videos? Can't we just have instructions written down? 🙂 )

    Not just you! Such a lot of very poor narration and not so easy to refer back to! A modern disease.

    Home Assistant

  • Home Assistant Voice
    akbooerA akbooer

    I didn’t go the HA route, but have voice control through Apple HomeKit and Siri. Works OK, but don’t use it much.

    Home Assistant

  • Wiring Samotech SM308-S into light fitting
    akbooerA akbooer

    What’s the difficulty? Does your switch wiring have a neutral? What country are you in?

    Hardware wifi switches smart home

  • Disaster recovery and virtualisation
    akbooerA akbooer

    Impressive.. great when it all works too!

    I’ve been very happy since I moved everything I could to Synology.

    A
    K

    General Discussion

  • AltUI sans internet connection
    akbooerA akbooer

    Yes, if it’s openLuup, then I was going to suggest that… rather depends on what you were trying to do.

    Software

  • 'Random' lights turning on
    akbooerA akbooer

    Bizarre! … but good catch.

    I’m a Siri user, myself. How do you link Alexa to openLuup? My link to Siri is via HomeKit (of course) for Hue and Shelly devices.

    General Discussion

  • openLuup email server
    akbooerA akbooer

    @a-lurker said in openLuup email server:

    To keep things so they are more likely to work, it's suggested the email address should be totally case insensitive regardless.

    Yes. I see from the ource code comments tht eraly-on I removed address wrapping to lower case. It's an easy change, but I'm going to find out why I did that in the first place, before reverting.

    @a-lurker said in openLuup email server:

    Is it your preference to leave the saved files in the raw mode or would you consider translating the base64 text in the openLuup code base?

    Don't see why not. Again, I need to dig in to see why that isn't working out of the box. There's plenty Base64 decoding going on within the server anyway.

    @a-lurker said in openLuup email server:

    On a side note, does the reception of an email by openLuup generate some sort of trigger that can be watched.

    Your best bet would surely be to register a callback handler to listen for messages on a specific address?

    I have another big project ongoing with some sort of a deadline at the start of December, so I'll need to leave things until then before I can get back to this code.

    Thanks again for your documentation efforts. I did say I would provide a link from the openLuup app... perhaps in the footer, like there is for the forum?

    openLuup

  • openLuup email server
    akbooerA akbooer

    You have been doing your homework!

    I need to remind myself of what I did way back when before being able to reply sensibly.

    But thanks for the excellent analysis.

    openLuup

  • Looking for Remote Switch boxes that can also be used with a wireless Decora Style Switch.
    akbooerA akbooer

    Not sure if your controller handles WiFi controlled devices?

    General Discussion
  • Login

  • Don't have an account? Register

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