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?
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.
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.
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?
Hi!
I get this message when I'm on the status tab:
System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.
I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1
I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...)
/Fanan
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.
While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.
So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.
While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits
Thanks!
Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945
Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.
I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.
This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.
x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}
The "cold white" and "warm white" settings interfer with the rgb color settings.
Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.
So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have
x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33}
14/03/2025, 16:43:57 - value updated
Arg 0:
└─commandClassName: Color Switch
└─commandClass: 51
└─property: targetColor
└─endpoint: 0
└─newValue
└──red: 235
└──green: 33
└──blue: 33
└─prevValue
└──red: 235
└──green: 33
└──blue: 33
└─propertyName: targetColor
14/03/2025, 16:43:57 - value updated
Arg 0:
└─commandClassName: Color Switch
└─commandClass: 51
└─property: currentColor
└─endpoint: 0
└─newValue
└──warmWhite: 204
└──coldWhite: 0
└──red: 235
└──green: 33
└──blue: 33
└─prevValue
└──warmWhite: 204
└──coldWhite: 0
└──red: 235
└──green: 33
└──blue: 33
└─propertyName: currentColor
In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.
x_zwave_values.Color_Switch_currentColor_0=204
x_zwave_values.Color_Switch_currentColor_1=0
x_zwave_values.Color_Switch_currentColor_2=235
x_zwave_values.Color_Switch_currentColor_3=33
x_zwave_values.Color_Switch_currentColor_4=33
Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?
x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}
Thanks in advance.
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.
The Runtime Error is different in the two browsers
Safari v18.3
@http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44
You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.
Google Chrome 133.0.6943.142
TypeError: self.editor.isModified is not a function
at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34)
You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.
Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.
I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.
Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.
I have not created a global expression for some times and just noticed this while doing some clean-up.
I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.
Here's what the log shows.
[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }
[latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay
[latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }
Reactor latest-25067-62e21a2d
Docker on Synology NAS
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.
This was prompted by yesterday's fun and games with my ISP.
I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)
I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?
TIA
C
[Solved] ZWaveJSController Add-on Install files
-
@toggledbits The documentation to install the ZWaveJSController Add-on step 5 says to run the install.sh or install.bat file. I do not see these files in the downloaded archives. Am I overlooking something or doing something wrong?
-
Apologies. That's a build error... this is the first time it's been packaged stand-alone. Please download the release archive again; the package has been updated but keeps the same version number.
-
Apologies. That's a build error... this is the first time it's been packaged stand-alone. Please download the release archive again; the package has been updated but keeps the same version number.
@toggledbits After a fresh download and also since I am using docker, I ran the install.sh from inside the container,(the docs for this Add-on module does not note this) the logs show that it is missing module js-yaml.
[latest-22240]2022-09-05T14:24:58.996Z <GlobalReaction:null> Module GlobalReaction v21333 [latest-22240]2022-09-05T14:24:58.998Z <default:null> Module Engine v22209 [latest-22240]2022-09-05T14:24:58.998Z <default:null> Module httpapi v22141 [latest-22240]2022-09-05T14:24:59.012Z <default:null> Module wsapi v22104 [latest-22240]2022-09-05T14:24:59.015Z <app:NOTICE> Starting Structure... [latest-22240]2022-09-05T14:24:59.020Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [latest-22240]2022-09-05T14:24:59.023Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-22240]2022-09-05T14:24:59.071Z <HassController:null> Module HassController v22238 [latest-22240]2022-09-05T14:24:59.162Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-22240]2022-09-05T14:24:59.182Z <Structure:INFO> Structure#1 loading controller interface hubitat (HubitatController) [latest-22240]2022-09-05T14:24:59.191Z <TaskQueue:null> Module TaskQueue 21351 [latest-22240]2022-09-05T14:24:59.191Z <HubitatController:null> Module HubitatController v22140 [latest-22240]2022-09-05T14:24:59.244Z <Structure:INFO> Structure#1 loading controller interface zwavejs (ZWaveJSController) [latest-22240]2022-09-05T14:24:59.257Z <Controller:CRIT> Controller: failed to load zwavejs implementation /var/reactor/ext/ZWaveJSController/ZWaveJSController.js: [Error]Error: Cannot find module 'js-yaml' Require stack: - /var/reactor/ext/ZWaveJSController/ZWaveJSController.js [latest-22240]2022-09-05T14:24:59.258Z <Controller:CRIT> Error: Cannot find module 'js-yaml' Require stack: - /var/reactor/ext/ZWaveJSController/ZWaveJSController.js Error: Cannot find module 'js-yaml' Require stack: - /var/reactor/ext/ZWaveJSController/ZWaveJSController.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:102:18) at Object.<anonymous> (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:529:88) at Module._compile (node:internal/modules/cjs/loader:1105:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:170:29) [latest-22240]2022-09-05T14:24:59.259Z <Structure:ERR> Structure#1 controller zwavejs ((undefined)) skipped, implementation could not be loaded. [latest-22240]2022-09-05T14:24:59.259Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-22240]2022-09-05T14:24:59.262Z <DynamicGroupController:null> Module DynamicGroupController v22123 [latest-22240]2022-09-05T14:24:59.266Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [latest-22240]2022-09-05T14:24:59.270Z <OWMWeatherController:null> Module OWMWeatherController v22059 [latest-22240]2022-09-05T14:24:59.272Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-22240]2022-09-05T14:24:59.275Z <SystemController:null> Module SystemController v22080 [latest-22240]2022-09-05T14:24:59.278Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [latest-22240]2022-09-05T14:24:59.284Z <MQTTController:null> Module MQTTController v22144 [latest-22240]2022-09-05T14:24:59.329Z <MQTTController:INFO> instance topic ident is mqtt [latest-22240]2022-09-05T14:24:59.332Z <Structure:INFO> Structure#1 loading controller interface nut (NUTController) [latest-22240]2022-09-05T14:24:59.334Z <default:null> Module NUTController v22152 [latest-22240]2022-09-05T14:24:59.337Z <Structure:INFO> Starting controller HassController#hass [latest-22240]2022-09-05T14:24:59.337Z <HassController:NOTICE> HassController#hass starting... [latest-22240]2022-09-05T14:24:59.338Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.21:8123/api/websocket [latest-22240]2022-09-05T14:24:59.345Z <Structure:INFO> Starting controller HubitatController#hubitat [latest-22240]2022-09-05T14:24:59.370Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-22240]2022-09-05T14:24:59.374Z <DynamicGroupController:NOTICE> Controller DynamicGroupController#groups is now online. [latest-22240]2022-09-05T14:24:59.374Z <Structure:INFO> Starting controller OWMWeatherController#weather [latest-22240]2022-09-05T14:24:59.402Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-22240]2022-09-05T14:24:59.404Z <SystemController:NOTICE> Controller SystemController#reactor_system is now online. [latest-22240]2022-09-05T14:24:59.429Z <Structure:INFO> Starting controller MQTTController#mqtt [latest-22240]2022-09-05T14:24:59.430Z <MQTTController:NOTICE> Connecting to broker mqtt://192.168.1.21:1883/ [latest-22240]2022-09-05T14:24:59.476Z <Structure:INFO> Starting controller NUTController#nut [latest-22240]2022-09-05T14:24:59.478Z <NUTController:NOTICE> NUTController#nut connecting to NUT server at "192.168.1.20":3493 [latest-22240]2022-09-05T14:24:59.479Z <NUTController:INFO> NUTController#nut started NUT client connection; waiting for ready [latest-22240]2022-09-05T14:24:59.480Z <app:NOTICE> Starting HTTP server and API...``` Synology Docker MSR v latest-22240-3b3254d6 -
Please reread the install instructions. Nothing gets installed or run inside the docker container.
-
Please reread the install instructions. Nothing gets installed or run inside the docker container.
@toggledbits I did install per the instructions. Only after I got the error is when I tried running the install.sh from inside the container as I remembered from installing the MQTT and NUT add-ons had those instructions for docker. Everything was installed in the ext directory on the synology.
-
Make sure your
NODE_PATHin your container configuration (Environment tab) reads/opt/reactor:/opt/reactor/node_modules. The update mechanism on Synology may not update this value on an existing container (even if reset). -
That was it. It is working now. My NODE_PATH was /opt/reactor, Changed to/opt/reactor:/opt/reactor/node_modules. When did this change and is there something I should of done differently to have this update?
Thanks -
No, it's a limitation of the Synology container manager, apparently. It doesn't seem to apply updated values from the new image to existing containers. I'll make note of that on the next Reactor build (later today) as well. I've also updated the instructions to just eliminate the install scripts; they don't do anything meaningful (everything ZWaveJSController needs is already in the current Reactor environment).
When Reactor 22248 comes out later today, you will not need to upgrade to it unless you feel a need to get the one major new feature (ability to "wait for completion" when a reaction runs another reaction). If you don't need it, don't bother. But if you do decide to upgrade, you will also need to upgrade your ZWaveJSController to its 22248 build as well.
-
T toggledbits locked this topic on