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
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

MSR Not Recognizing Old HASS on New VM

Scheduled Pinned Locked Moved Multi-System Reactor
20 Posts 2 Posters 681 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.
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by Pabla
    #1

    Hey Patrick, had to switch over my HA VM from VirtualBox to VMware since VirtualBox stopped playing well. Anyways I updated the IP address to the new VM IP and deleted the Long Lived Access Token and created a new one just in case (copy pasted the new token into the config file). Tried rebooting both the HA machine and the MSR one too and MSR is still not connecting. The only thing I have not tried yet is creating another controller entry, but I am worried it may create all new entities for everything forcing me to redo all my logic. Here are some logs:

    [latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-20T21:17:24.749Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-20T21:18:09.753Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-20T21:18:24.761Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-20T21:19:01.083Z <VeraController:INFO> VeraController#vera 0 dead entities older than 86400000s purged
[latest-22258]2022-09-20T21:19:14.780Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-20T21:19:29.785Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-20T21:20:24.791Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-20T21:20:39.813Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out
[latest-22258]2022-09-20T21:20:39.820Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation
[latest-22258]2022-09-20T21:20:39.820Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out
    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #2

      Check the (Home Assistant) settings for the http component and make sure those make sense for the new IP you are on. Also make sure the websocket_api component is configured. Did you make any other configuration changes? Enable SSL/TLS? If you were using SSL/TLS on the old VM, did you issue a new certificate for new one?

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

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

        I am not sure what to check for the http component in HA, however I confirmed that web socket is still in my configuration file. I have not made any other config changes, basically restored from my backup from the old VM. I wasn't using SSL/TLS on the old VM so I don't think I need to mess with it.

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

          Doing a bit of research on the HA forums and looks like someone has had almost the exact same issue and came to the solution of disabling https. Haven't tried that yet since I am unsure if that would be safe.

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

            Try adding ignore_cert: true in the config section for HassController (after source and same indent level). You may additionally need to change the ws:// in the source to wss://. If that works, SSL/TLS is enabled in Hass and you are on a self-signed or invalid certificate (but no changes to Hass needed).

            Also, if your Hass http component configuration has ssl_certificate then SSL/TLS is enabled. That's another way to tell.

            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

              Try adding ignore_cert: true in the config section for HassController (after source and same indent level). You may additionally need to change the ws:// in the source to wss://. If that works, SSL/TLS is enabled in Hass and you are on a self-signed or invalid certificate (but no changes to Hass needed).

              Also, if your Hass http component configuration has ssl_certificate then SSL/TLS is enabled. That's another way to tell.

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

              @toggledbits tried setting ignore_cert: true and this is what came up in the logs tried both ws:// and wss//. I do not have the http component in my HA config file

              [latest-22258]2022-09-21T02:52:29.492Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:52:29.493Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [TypeError]TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
[latest-22258]2022-09-21T02:53:29.501Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:53:29.502Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [TypeError]TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
[latest-22258]2022-09-21T02:54:29.507Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:54:29.509Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [TypeError]TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
[latest-22258]2022-09-21T02:55:29.519Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:55:29.519Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [TypeError]TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
[latest-22258]2022-09-21T02:56:21.052Z <VeraController:INFO> VeraController#vera 0 dead entities older than 86400000s purged
[latest-22258]2022-09-21T02:56:29.528Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:56:29.529Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [TypeError]TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
[latest-22258]2022-09-21T02:57:29.530Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket
[latest-22258]2022-09-21T02:57:29.531Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [TypeError]TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
[latest-22258]2022-09-21T02:58:20.106Z <Rule:INFO> "10 Min Light Polling" (Rule#rule-grpqldnna5) starting evaluation; because timer-trigger Timer#rule-grpqldnna5
[latest-22258]2022-09-21T02:58:20.107Z <Rule:INFO> "10 Min Light Polling" (Rule#rule-grpqldnna5) evaluated; rule state transition from RESET to SET!
[latest-22258]2022-09-21T02:58:20.124Z <Rule:INFO> "45 Min Light Polling" (Rule#rule-l6whyfqd) starting evaluation; because data-changed Data#states:cs-rule-grpqldnna5
[latest-22258]2022-09-21T02:58:20.124Z <Rule:INFO> "10 Min Light Polling" (Rule#rule-grpqldnna5) evaluation complete
[latest-22258]2022-09-21T02:58:20.125Z <Rule:INFO> "45 Min Light Polling" (Rule#rule-l6whyfqd) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-22258]2022-09-21T02:58:20.126Z <Rule:INFO> "45 Min Light Polling" (Rule#rule-l6whyfqd) evaluation complete
[latest-22258]2022-09-21T02:58:20.126Z <Engine:INFO> Enqueueing ""10 Min Light Polling<SET>"" (rule-grpqldnna5:S)
[latest-22258]2022-09-21T02:58:20.139Z <Engine:NOTICE> Starting reaction "10 Min Light Polling<SET>" (rule-grpqldnna5:S)
[latest-22258]2022-09-21T02:58:20.140Z <HassController:null> HassController#hass: sending payload for x_hass_system.call_service on System#hass>system action: [Object]{ "type": "call_service", "service_data": { "entity_id": "light.island_lights" }, "domain": "zwave_js", "service": "refresh_value" }
[latest-22258]2022-09-21T02:58:20.141Z <HassController:ERR> HassController#hass request 1663729100140<2022-09-20, 7:58:20 p.m.> (call_service) failed: [Error]Error: WebSocket not connected
[latest-22258]2022-09-21T02:58:20.143Z <Engine:INFO> Resuming reaction "10 Min Light Polling<SET>" (rule-grpqldnna5:S) from step 1"

              Not sure if this is useful but here are some logs pertaining to web socket from HA Supervisor

              22-09-20 19:39:48 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
22-09-20 19:58:33 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
22-09-20 19:58:33 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
22-09-20 19:58:33 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
22-09-20 19:58:38 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #7

                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://.

                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

                  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

                                          • Gradually turn on lights.
                                            G
                                            gwp1
                                            0
                                            4
                                            145
                                          • Stop the MSR by an external switch on Hubitat.
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            1
                                            38
                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            106
                                          • Reset attribute value of entity in event handler
                                            R
                                            RHCPNG
                                            0
                                            5
                                            209
                                          • Need help figuring out how to delay a reset on reaction
                                            G
                                            gwp1
                                            0
                                            22
                                            931
                                          • Way to search for rules (rule state) in other rules
                                            T
                                            tamorgen
                                            0
                                            3
                                            104
                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            93
                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            440
                                          • Wiring Samotech SM308-S into light fitting
                                            akbooerA
                                            akbooer
                                            0
                                            2
                                            152
                                          • Errors after updating to MQTTController build 25139
                                            toggledbitsT
                                            toggledbits
                                            0
                                            6
                                            242
                                          • 🎉 My very first MSR controller: OpenSprinkler
                                            therealdbT
                                            therealdb
                                            5
                                            13
                                            920
                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            264
                                          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