18481340-4d9c-4d0c-8027-49adfa28f32a-image.png
e0e1c895-a830-48d5-8346-cbae551b441d-image.png
This has been working flawlessly each year incl this year until... Tonight... nada.
Is this due to the holiday being late this year ie because today is the 22nd, not after the 22nd?
I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
Hi @toggledbits,
I have lots of logs with this:
<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignmentAny hints to where look at to avoid this? Thanks.
Hi @toggledbits
I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.
Could you please elaborate more? Thanks.
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi!
In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
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.A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0
Hi!
Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?
And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?
And being more ambitious, does Windget have an icon to open these TXT files in the navigated?
Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂
Hi @toggledbits
I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.
I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.
Thanks.
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0
Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=nullTilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nullMSR Not Recognizing Old HASS on New VM
-
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 -
Check the (Home Assistant) settings for the
httpcomponent and make sure those make sense for the new IP you are on. Also make sure thewebsocket_apicomponent 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? -
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.
-
Try adding
ignore_cert: truein theconfigsection for HassController (aftersourceand same indent level). You may additionally need to change thews://in the source towss://. 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
httpcomponent configuration hasssl_certificatethen SSL/TLS is enabled. That's another way to tell. -
@toggledbits tried setting
ignore_cert: trueand this is what came up in the logs tried bothws://andwss//. I do not have thehttpcomponent 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 -
The log snippet shows the
ws://result but nowss://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 usewss://. -
@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 -
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.
-
@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: hassin the first config, usehass2in 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: trueandfalseno 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_certdoes 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
-
@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?
-
@toggledbit Lol whoops meant to say MSR is running on a VirtualBox VM and Hass is running on a WMware VM
-
T toggledbits locked this topic on
