Skip to content
  • Deprecation Announcement: 32-bit ARM *docker* images

    Pinned until 8/1/27, 6:56 PM Locked Multi-System Reactor
    1
    0 Votes
    1 Posts
    37 Views
    No one has replied
  • [Solved] build 26150 - engine not starting

    Multi-System Reactor
    8
    0 Votes
    8 Posts
    80 Views
    toggledbitsT
    @gwp1 said in [Solved] build 26150 - engine not starting: @toggledbits I checked, rechecked, RErechecked and couldn't find any issue with that YAML. Upload it to me, I'd like to take a look. @gwp1 said in [Solved] build 26150 - engine not starting: So... my question NOW is: why did it run fine until this build? That logging has been there for several weeks. No idea. But, having once gotten a clean startup, it now has a last known good version of that config file, so whatever it's not happy with won't prevent startup in future.
  • 5 Votes
    141 Posts
    105k Views
    toggledbitsT
    Reactor build 26150 If you are upgrading to this build from 26011 or earlier, please read the cautions for build 26116! A new Router notification method is now available. This method allows a single notification action to send a message to multiple notification targets. Configurable routes allow the selection and filtering of messages for different destinations. See docs In support of the new Router notification method, configured Notifier profiles other than default are considered children of default. If a configuration value is not specified in such a profile, the value will be inherited from the default profile. This allows, for example, the default profile for SMTP to contain the host and authentication information, while additional profiles may contain only different recipient addresses — the additional profiles will use the default profile's host/auth info to connect to the same mail server, without the need to repeat that information in each profile. If an additional profile needs to connect to a different mail server, it may specify its own host and authentication parameters as before. DynamicGroupController: improve response to changes in groups using filter_expression in configuration; Expressions: fix an error in the runReaction() function that may cause it to crash on an attempted dereference through undefined. Make the system more resilient to startup failures caused by hard errors in configuration files. When a (syntactically) valid configuration file is successfully loaded, it is copied to a last-known-good shadow file in the config directory. If the YAML configuration is later edited and contains errors that would prevent it being loaded, Reactor will load the last-known-good configuration, log the error, and display an alert in the Current Alerts widget on the Status page. The alert will clear itself when the file is fixed and later successfully loaded. To be clear, "valid" in this context means parseable (syntactically correct YAML). It does not mean that the keys and values given in the configuration will do what you expect/want or contain values or structures that Reactor can't recognize. Fix a compatibility issue with node version 18. This version of node is only supported in the armv7l docker image (for 32-bit Raspberry Pis). A new backup script backup_reactor_gfs.sh has been added to the tools directory; this script uses the grandfather-father-son backup strategy. If run daily, it will keep 30 daily backups, monthly backups (i.e. the first daily backup of each month), and quarterly backups (i.e. the first monthly backup of each quarter). Command line options suppress the backups of the logs directory and/or the transient/temporary state data for smaller backup size.
  • Farewell, oh good and faithful servant!

    Moved Unsolved General Discussion
    1
    0 Votes
    1 Posts
    62 Views
    No one has replied
  • http request action & digest auth

    Multi-System Reactor
    7
    0 Votes
    7 Posts
    245 Views
    toggledbitsT
    I'll see what can be done later, but this comes from a package I use, not code of my own creation. Despite the bug discovered, if I abandon the external package, I lose years of testing against myriad servers in the wild, so it's a potentially costly trade-off that makes a lot of future work (and frustration, potentially).
  • Cloning actions in reactions does not work

    Multi-System Reactor
    2
    0 Votes
    2 Posts
    111 Views
    toggledbitsT
    Got it. Next build... tomorrow, or Sunday at the latest.
  • Has ping command been removed?

    Multi-System Reactor
    4
    1
    0 Votes
    4 Posts
    163 Views
    toggledbitsT
    OK. I've respun 26140 docker images with some additions to the underlying minimal OS. Grab the updated image for your container and you should have ping back.
  • 0 Votes
    6 Posts
    209 Views
    tunnusT
    @toggledbits got it, thanks!
  • Integrations and 'Loaded'

    Multi-System Reactor
    3
    0 Votes
    3 Posts
    99 Views
    CatmanV2C
    Perfect! Thanks (again) C
  • 0 Votes
    25 Posts
    709 Views
    CatmanV2C
    Thanks, installed and working. Although after the first restart there were some virtual switches in HA that were not being accurately reflected in MSR, but I restarted MSR again, and everything looks fine. Thanks again for your help. Next time I'll upload the logs to start with! C
  • 0 Votes
    19 Posts
    830 Views
    therealdbT
    @gwp1 I never had any doubt about @toggledbits
  • Reactor build 26116: empty group reaction

    Multi-System Reactor
    18
    1 Votes
    18 Posts
    804 Views
    toggledbitsT
    OK. Please turn on log level 5 for that rule only. Run the rule to show the issue, and upload the entire Rule log file as well as reactor.log, the rule storage files (dval and json). Link for upload in your DMs
  • Temperature control with TRVs

    Unsolved General Discussion
    1
    0 Votes
    1 Posts
    260 Views
    No one has replied
  • Upcoming Storage Change -- Got Back-ups?

    Multi-System Reactor
    2
    3 Votes
    2 Posts
    412 Views
    toggledbitsT
    OK, everyone, it's almost time. Sorry for the long pause. Life takes over sometimes. The aforementioned updates will be in the next build, and I am working on wrapping everything up to get that build out later this week. Please make backups of your Reactor data as advised in the head post here. As I said then/there, I've been working with this for months now, with no issues, but my world is not your world or everyone else's world, so there's always the possibility I don't see or have an issue that you do. Prior to releasing this new build in the latest channel, the 26011 build will become the stable channel head. In addition to your backups, that gives you a relatively quick path (especially docker users) to get back onto 26011 if there's a showstopper. This build will also include unified room groups: DynamicGroupController will manage "rooms" (or areas or locations or whatever your hub calls them). If you have two different hubs with devices in the "Living Room," there will be one "Living Room" group with the combined set of devices. The per-controller room groups generated by VeraController and EzloController will be disabled by default, and existing room groups created by these controllers will be marked as dead entities (and eventually purged). If you already use DynamicGroupController to manually create your own room groups via configuration, you can either keep that (and disable DGC's new behavior, if you wish) or switch to DGC's version. An updated version of ZWaveJSController that supports this functionality will be released simultaneously with the core build.
  • Next Release?

    Multi-System Reactor
    6
    0 Votes
    6 Posts
    536 Views
    CatmanV2C
    Just an update. Nothing apparent issue wise since my update yesterday C
  • 0 Votes
    2 Posts
    306 Views
    toggledbitsT
    Grab ZWaveJSController build 26048. It will publish the location in zwave_device.location. It will not create groups automatically (yet), so you'll need to use DynamicGroupController to make your own. Rooms are going to be handled very differently in future. Right now, controllers great groups they own for rooms, and that prevents sharing of rooms between controllers (they can't modify another's groups), so you have to use DGC to manually create unified groups across controllers. That will be more automated in future.
  • Do you Matter?

    General Discussion
    8
    0 Votes
    8 Posts
    1k Views
    CrilleC
    Speaking of Matter and older Shelly (Gen 1 & 2) I found Matterbridge, very similar to Homebridge, paired it to Apple Home and installed matterbridge-shelly and as easy as that all my devices showed up in the Home app. Might be something for you @akbooer . Matterbridge offer other plugins like Zigbee2MQTT, Home Assistant and more, this makes me start thinking of moving away from Homebridge (and some MQTT) to Matterbridge and Matter, especially if a MatterController is eventually in the making. Because I'm Swedish IKEA is very close by and super cheap on "Matter over Thread" devices and my HomePod mini act as a Thread Border Router, I can say Matter starts to grow on me
  • Variables not updating properly

    Multi-System Reactor
    5
    4
    0 Votes
    5 Posts
    506 Views
    tunnusT
    @toggledbits thanks, using an independent reaction works nicely!
  • [Solved] Loading Screen Safari

    Multi-System Reactor
    11
    1
    0 Votes
    11 Posts
    2k Views
    S
    Update: This was not a Reactor issue and Home Assistant was having the problem loading also. It is now working normally in Mac OS 26.4.
  • VEC Virtual Switch Auto Off

    Multi-System Reactor
    2
    1 Votes
    2 Posts
    445 Views
    S
    Is this the proper place to ask for a feature request? I think it would be useful to have VEC Virtual switches to have an option for an Auto Off setting. Thanks

Recent Topics