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.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. How to upgrade from an old version of MSR?
Variables not updating properly
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Loading Screen Safari
S
Topic thumbnail image
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
Changes operator does not always detect change
tunnusT
I've had similar problems before, but now this issue has resurfaced. Using build 26011 on Docker. As I copied one old rule as a "template" for a similar new rule, where I have multiple conditions using changes operator (from any to any, and with delay reset of 900), these conditions do not detect change in attributes. Even if I manually reset the rule, reset delay timers do not restart. If I do a new rule from scratch, and do not copy/import anything old, the same conditions work properly. Also, if I modify copied rule's conditions (put a random number to "from" & "to" fields), then save, and after that remove those modifications, rule begins to function normally. Just editing e.g. delay reset value does not do any good in this context. @toggledbits, I can DM logs & related rule files to you, if you just send me instructions.
Multi-System Reactor
Dynamic MQTT topics and parameters
M
Topic thumbnail image
Multi-System Reactor
Condition for trend
T
Topic thumbnail image
Multi-System Reactor
Struggling to setup my first Tasmota device and MQTT
cw-kidC
Topic thumbnail image
Multi-System Reactor
Existing Rule stopped working HTTP command fetching IP address from website
cw-kidC
Topic thumbnail image
Multi-System Reactor
Set reaction triggering wrong z-wave device
T
Topic thumbnail image
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
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
This trigger no longer working - complaining about the operator needing changing
cw-kidC
Topic thumbnail image
Multi-System Reactor
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
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

How to upgrade from an old version of MSR?

Scheduled Pinned Locked Moved Multi-System Reactor
26 Posts 6 Posters 1.2k Views 6 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by
    #21

    A.I. is pretty good! I don't normally use it tbh. Scared of the future robots gonna rule the world.

    I asked:

    Yes please tell me more about the general concepts of Proxmox. I do know what virtual machines are however I have used them in the past. But I have never heard of Proxmox before. I am familiar with Debian however I already have a thin client here running Debian and Multi System Reactor aka MSR. MSR is a 3rd party logic rules engine which can be used with your devices in Home Assistant. I need a new setup that allows me to run home assistant and msr on the same pc etc.

    It replied but it recommends to run MSR in an LXC rather than a full VM. The whole setup sounds it would be brilliant, but for me to do it, is probably lot of time, learning and head straching lol. So it's gonna be a commitment.

    Here is what it said:

    Since you are already comfortable with Debian and Virtual Machines, Proxmox is going to feel like a superpower for your home lab.
    ​What is Proxmox?
    ​Proxmox Virtual Environment (PVE) is a Type-1 Hypervisor.
    ​Type-2 (What you've used): Like VirtualBox on Windows. You have an OS, then an app, then the VM.
    ​Type-1 (Proxmox): It is the OS. It sits directly on the "bare metal" hardware.
    ​Crucially for you, Proxmox is built on top of Debian. When you install it, you are essentially installing a highly customized version of Debian with a world-class Web GUI to manage VMs and Containers.
    ​The Strategy: Running HAOS and MSR Together
    ​Since you want to run both Home Assistant and Multi-System Reactor (MSR) on one machine, Proxmox is the perfect "manager" to keep them isolated but interconnected.
    ​1. Home Assistant (The VM)
    ​You will create a Virtual Machine (VM) and install HAOS directly into it.
    ​Why a VM? HAOS wants to "own" the hardware. In a VM, Proxmox gives it a virtualized hard drive and CPU, keeping it stable and allowing for the "Add-on Store" to work perfectly.
    ​Ease of use: There are famous "Helper Scripts" (by tteck) that allow you to install HAOS on Proxmox with a single command.
    ​2. Multi-System Reactor (The LXC Container)
    ​Since MSR is a Node.js application that runs great on Linux, you don't need a full VM for it. You should use a Linux Container (LXC).
    ​What is an LXC? It’s lighter than a VM. It shares the Proxmox (Debian) kernel but has its own file system.
    ​The Benefit: An LXC for MSR will use almost zero idle RAM (around 100-200MB) compared to a full VM which might grab 2GB just to boot.
    ​Why this is better than your current setup:
    ​Snapshots: Before you update Home Assistant or change a massive rule in MSR, you click "Snapshot." If it breaks, you hit "Rollback" and you're back in 10 seconds.
    ​Backups: Proxmox can automatically back up your entire HA setup and MSR setup to an external drive or NAS every night while you sleep.
    ​Hardware Pass-through: If you have a Zigbee or Z-Wave USB stick, Proxmox makes it easy to "pass" that physical USB port into the Home Assistant VM.
    ​The "Debian" Safety Net: Since the base is Debian, you can still SSH into the host and use familiar commands if you ever need to troubleshoot the hardware level.
    ​Recommended "UK eBay PC" Allocation:
    ​If you buy an 8th Gen i5 with 16GB RAM (as discussed):
    ​Proxmox Host: Uses ~1GB RAM.
    ​HAOS VM: Assign 4GB RAM (it will use ~2GB).
    ​MSR LXC: Assign 1GB RAM (it will use ~200MB).
    ​Leftover: You still have 10GB of RAM free to experiment with other things like Pi-Hole, Plex, or a local MQTT broker.
    ​Would you like me to find those "Helper Scripts" for you so you can see how easy the one-command installation is?

    1 Reply Last reply
    0
    • cw-kidC Offline
      cw-kidC Offline
      cw-kid
      wrote on last edited by
      #22

      This video is wild and super scary, if real and why I very rarely use A.I.

      I'd love to hear you guys opinions as being the expert technical guys you are.

      Woman Claims "Something Sinister" Is Taking Over The Internet, And It's Crazier Than We Think
      1 Reply Last reply
      0
      • cw-kidC Offline
        cw-kidC Offline
        cw-kid
        wrote on last edited by cw-kid
        #23

        Wow Gemini A.i. has it all totally covered lol. I had like an hour long conversation with it. It says it can tell me exactly how to setup such a new HA system step by step and has even come up with a migration plan for my MSR rules!

        We are currently talking about building dashboards in HA.

        I told it I was currently using Home Remote with Vera and I described my current dashboard menu structure and sub menu structure and how I have a menu item for each room etc.

        A.I. is telling me how to do the same in Home Assistant talking about different card options. Its even shown me some HA dashboard demos from YouTube and it says it can "watch" and understand these videos. So if I pick one I like it can then advise me how to build it in Home Assistant.

        Witch craft it's just like talking too a human expert.

        So think I won't need to ask to many questions on the forum now.

        My mind is blown about the A.I. conversation I just had. I've never spoken to them in depth before and not about technical stuff.

        I will still be avoiding A.I. in general however.

        Humans are totally cooked, we will all be replaced by the robots.

        1 Reply Last reply
        0
        • therealdbT Offline
          therealdbT Offline
          therealdb
          wrote on last edited by
          #24

          Yes to Zwave js ui. Zwa2 range is impressive. You’ll thank me later 🤣

          There’s zigbee2mqtt that’s basically the same route as Zwave js and home assistant has a zigbee usb key as well.
          Everything is then exposed and orchestrated via reactor.

          Regrading AI, I’m more and more offloading dev tasks to GitHub Copilot Agent inside VS Code and I love it. I have a special chat with custom instructions for reactor where I ask about logic guidance and checks. This is the sort of tasks that generative AI excels at.

          --
          On a mission to automate everything.

          My MS Reactor contrib
          My Luup Plug-ins

          1 Reply Last reply
          0
          • CrilleC Offline
            CrilleC Offline
            Crille
            wrote on last edited by
            #25

            For Zigbee I have an older Sonoff 3.0 USB Dongle Plus and Zigbee2MQTT running rock solid but if I were to replace it I would go for the Sonoff Dongle Max, looks pretty impressive and can be placed wherever there’s an ethernet port (or WiFi).

            1 Reply Last reply
            0
            • CatmanV2C Offline
              CatmanV2C Offline
              CatmanV2
              wrote on last edited by
              #26

              Couple of observations:

              1. You don't need to start from ground up HA plays really nicely with MSR and Vera. You can slide over as slowly as you like (I think I was running for nearly 2 years before I got the time to move it all
              2. I've been playing with AI as well (saves me bugging the brains trust here) Chat GPT and Claude. Although Claude is better they are both wrong FAR MORE often than they are right. I've been through 20+ iterations of code, every time being told 'This will absolutely work' and it doesn't

              That's not a massive issue as I sort of know what I'm doing, but I absolutely would not expect any AI at this point to be able to set you up a complete HA set up from scratch.

              As for Proxmox it does seem to be very popular. I'm not sure why as it's kind of complex (or looks that way to me after very limited study) I'm running my VMs on my Synology NASs. They are protected on a UPS, and take a snapshot every night. Roll back to a working instance takes minutes if not seconds.

              $0.02

              C

              The Ex-Vera abuser know as CatmanV2.....

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              Recent Topics

              • Variables not updating properly
                tunnusT
                tunnus
                0
                5
                124

              • [Solved] Loading Screen Safari
                S
                SweetGenius
                0
                11
                858

              • VEC Virtual Switch Auto Off
                S
                SweetGenius
                1
                2
                247

              • Changes operator does not always detect change
                toggledbitsT
                toggledbits
                0
                4
                252

              • Dynamic MQTT topics and parameters
                M
                mgvra
                0
                6
                324

              • Condition for trend
                T
                tamorgen
                0
                12
                518

              • Struggling to setup my first Tasmota device and MQTT
                cw-kidC
                cw-kid
                0
                23
                1.4k

              • Raspberry Pi 4 dual RAM variant introduced to mitigate RAM price increases
                A
                a-lurker
                0
                2
                479

              • Existing Rule stopped working HTTP command fetching IP address from website
                toggledbitsT
                toggledbits
                0
                12
                627

              • Set reaction triggering wrong z-wave device
                T
                tamorgen
                0
                19
                865

              • Can you run MSR on Home Assistant OS ?
                CatmanV2C
                CatmanV2
                0
                12
                577

              • RPi Alternative: Orange Pi 4 LTS (3GB RAM/16GB eMMC)
                toggledbitsT
                toggledbits
                0
                2
                2.1k
              Powered by NodeBB | Contributors
              Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
              • Login

              • Don't have an account? Register

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