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. MSR Not Recognizing Old HASS on New VM
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
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
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
[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

MSR Not Recognizing Old HASS on New VM

Scheduled Pinned Locked Moved Multi-System Reactor
20 Posts 2 Posters 1.8k Views 2 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.
  • toggledbitsT toggledbits

    The log snippet shows the ws:// result but no wss:// result. I'd like to see that, because it's probably a different message and maybe more useful. The messages you are showing clearly indicate it wants you to use wss://.

    PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #8

    @toggledbits logs attached using wss://

    [latest-22258]2022-09-21T02:38:34.723Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:38:34.723Z <HassController:NOTICE> HassController#hass websocket to wss://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-21T02:38:34.723Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:38:39.737Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:38:54.745Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:38:54.745Z <HassController:NOTICE> HassController#hass websocket to wss://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-21T02:38:54.746Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:38:59.748Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:39:14.751Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:39:14.752Z <HassController:NOTICE> HassController#hass websocket to wss://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-21T02:39:14.752Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:39:19.759Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:39:28.763Z <VeraController:INFO> VeraController#vera 0 dead entities older than 86400000s purged
[latest-22258]2022-09-21T02:39:34.765Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:39:34.765Z <HassController:NOTICE> HassController#hass websocket to wss://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-21T02:39:34.765Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:39:39.771Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:39:54.776Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:39:54.777Z <HassController:NOTICE> HassController#hass websocket to wss://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-21T02:39:54.777Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:40:04.779Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:40:19.786Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:40:19.787Z <HassController:NOTICE> HassController#hass websocket to wss://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-21T02:40:19.788Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:40:34.791Z <HassController:NOTICE> HassController#hass connecting to wss://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:40:49.796Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:40:49.797Z <HassController:NOTICE> HassController#hass websocket to wss://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-21T02:40:49.798Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-21T02:41:00.728Z <Rule:INFO> Inside Light Polling (Rule#rule-grpqlebtkk) starting evaluation; because timer-trigger Timer#rule-grpqlebtkk
    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #9

      And that's also with ignore_cert: true, correct?

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      PablaP 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        And that's also with ignore_cert: true, correct?

        PablaP Offline
        PablaP Offline
        Pabla
        wrote on last edited by
        #10

        @toggledbits correct

        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by toggledbits
          #11

          OK. All I can suggest at this point is that maybe you have the old IP address of the previous system in Hass' configuration somewhere and it's messing things up. Beyond that, I'm out of ideas. Maybe shut down that VM, create a new one, install Hass fresh and clean without restoring the prior configuration, just use a default configuration, and see if you can connect to it. If you can, it's definitely something in the old config/restored install. If you can't, maybe something in the VM configuration... I don't know. This usually isn't much of a challenge, and HassController isn't doing anything tricky, it uses a standard Websocket library in wide use for its connections, so I'm doubtful there's suddenly some bug or incompatibility there.

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          PablaP 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            OK. All I can suggest at this point is that maybe you have the old IP address of the previous system in Hass' configuration somewhere and it's messing things up. Beyond that, I'm out of ideas. Maybe shut down that VM, create a new one, install Hass fresh and clean without restoring the prior configuration, just use a default configuration, and see if you can connect to it. If you can, it's definitely something in the old config/restored install. If you can't, maybe something in the VM configuration... I don't know. This usually isn't much of a challenge, and HassController isn't doing anything tricky, it uses a standard Websocket library in wide use for its connections, so I'm doubtful there's suddenly some bug or incompatibility there.

            PablaP Offline
            PablaP Offline
            Pabla
            wrote on last edited by
            #12

            @toggledbits Will try creating a new Hass install and see if I can get MSR to work. In terms of the existing config, none of the entities will get auto deleted since the controller is offline right? Also if I clear out he Hass config completely from MSR, restart MSR then reconfigure as if its the first time entering a Hass config in will this overwrite all my existing Hass entities?

            1 Reply Last reply
            0
            • toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #13

              Just use a different ID for the new HassController instance... so if you had id: hass in the first config, use hass2 in the second.

              It probably won't matter anyway, as the IDs should be stable... the new entities would have the same IDs as the old, be of the same type, etc.

              Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

              PablaP 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                Just use a different ID for the new HassController instance... so if you had id: hass in the first config, use hass2 in the second.

                It probably won't matter anyway, as the IDs should be stable... the new entities would have the same IDs as the old, be of the same type, etc.

                PablaP Offline
                PablaP Offline
                Pabla
                wrote on last edited by
                #14

                @toggledbits Just quickly set up a new Hass VM and am seeing the same errors. Tried with both ignore_cert: true and false no luck. This seems to be a VMware issue, I did do look through settings but couldn't really see anything that would stop MSR from connecting.

                1 Reply Last reply
                0
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #15

                  To be specific, you need to try ws:// (ignore_cert does not matter for this case), and wss:// with ignore_cert: true. Both cases.

                  Beyond that, I'm at a loss. Are you running Hass in docker? Are you running Reactor in docker? I'd look at all of that, too...

                  Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                  PablaP 1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    To be specific, you need to try ws:// (ignore_cert does not matter for this case), and wss:// with ignore_cert: true. Both cases.

                    Beyond that, I'm at a loss. Are you running Hass in docker? Are you running Reactor in docker? I'd look at all of that, too...

                    PablaP Offline
                    PablaP Offline
                    Pabla
                    wrote on last edited by
                    #16

                    @toggledbits Neither are running in docker, both run on their own VM on the same host. Just the difference now is Reactor is running on a VirutalBox VM and MSR is on a VMware VM

                    toggledbitsT 1 Reply Last reply
                    0
                    • PablaP Pabla

                      @toggledbits Neither are running in docker, both run on their own VM on the same host. Just the difference now is Reactor is running on a VirutalBox VM and MSR is on a VMware VM

                      toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by
                      #17

                      @pabla said in MSR Not Recognizing Old HASS on New VM:

                      Just the difference now is Reactor is running on a VirutalBox VM and MSR is on a VMware VM

                      Huh?

                      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                      PablaP 1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        @pabla said in MSR Not Recognizing Old HASS on New VM:

                        Just the difference now is Reactor is running on a VirutalBox VM and MSR is on a VMware VM

                        Huh?

                        PablaP Offline
                        PablaP Offline
                        Pabla
                        wrote on last edited by
                        #18

                        @toggledbit Lol whoops meant to say MSR is running on a VirtualBox VM and Hass is running on a WMware VM

                        1 Reply Last reply
                        0
                        • PablaP Offline
                          PablaP Offline
                          Pabla
                          wrote on last edited by
                          #19

                          So did a little research and it looks like Websocket is not supported in VMware workstation 16.. I just bought an ODROID cause I am tired of tinkering with all these issues I have had with VMs

                          1 Reply Last reply
                          0
                          • PablaP Offline
                            PablaP Offline
                            Pabla
                            wrote on last edited by
                            #20

                            Just to close this thread up, it was a VMware issue as stated above. Moved over to an ODROID and MSR connected no problem.

                            1 Reply Last reply
                            1
                            • toggledbitsT toggledbits locked this topic on
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes

                            Recent Topics

                            • Set reaction triggering wrong z-wave device
                              T
                              tamorgen
                              0
                              17
                              99
                            • Can you run MSR on Home Assistant OS ?
                              CatmanV2C
                              CatmanV2
                              0
                              12
                              150
                            • RPi Alternative: Orange Pi 4 LTS (3GB RAM/16GB eMMC)
                              toggledbitsT
                              toggledbits
                              0
                              2
                              1.7k
                            • RPi Alternative: Orange Pi Zero 2 (1GB)
                              toggledbitsT
                              toggledbits
                              2
                              3
                              3.5k
                            • RPi Alternative: Libre Computer AML-S905X-CC "Le Potato" (2GB RAM)
                              toggledbitsT
                              toggledbits
                              5
                              6
                              3.1k
                            • HA and AI
                              therealdbT
                              therealdb
                              0
                              4
                              144
                            • How to upgrade from an old version of MSR?
                              CatmanV2C
                              CatmanV2
                              0
                              26
                              419
                            • This trigger no longer working - complaining about the operator needing changing
                              toggledbitsT
                              toggledbits
                              0
                              18
                              168
                            • Self test
                              CatmanV2C
                              CatmanV2
                              0
                              3
                              116
                            • Access control - allowing anonymous user to dashboard
                              toggledbitsT
                              toggledbits
                              0
                              2
                              129
                            • VEC Virtual Switch Auto Off
                              S
                              SweetGenius
                              1
                              1
                              92
                            • Upcoming Storage Change -- Got Back-ups?
                              toggledbitsT
                              toggledbits
                              3
                              1
                              84
                            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