MSR Not Recognizing Old HASS on New VM
-
And that's also with
ignore_cert: true
, correct?@toggledbits correct
-
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.
-
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.
@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?
-
Just use a different ID for the new HassController instance... so if you had
id: hass
in the first config, usehass2
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.
-
Just use a different ID for the new HassController instance... so if you had
id: hass
in the first config, usehass2
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.
@toggledbits Just quickly set up a new Hass VM and am seeing the same errors. Tried with both
ignore_cert: true
andfalse
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. -
To be specific, you need to try
ws://
(ignore_cert
does not matter for this case), andwss://
withignore_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...
-
To be specific, you need to try
ws://
(ignore_cert
does not matter for this case), andwss://
withignore_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...
@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
-
@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
@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?
-
@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?
-
T toggledbits locked this topic on