Thanks for your answer, that's basically the same way I use the rule sets.
R
RHCPNG
@RHCPNG
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.
Following on from my last thread, some progress has been made over the weekend.
With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system.
Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic.
Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work.
Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic.
Once that hurdle is sorted I'm torn between:
Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or
Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.)
Decisions, decisions.
C
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.
Posts
-
Organizing/ structuring rule sets and rules -
Organizing/ structuring rule sets and rulesHi 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.
-
Feature Request: Sublevel in RulesetsHi @toggledbits
Would you please consider adding an extra sublevel in the rulesets?
I have grouped my rules in rooms/ areas. This works great for me, but I would also like to group rules for the same functionality (in a room). This would make the rules easier to find and name.
Please let me know if this is an option. Thanks!
-
Switching between z-wave software controllersHi all,
Is it easy to switch between z-wave software controllers? I have a UZB and I want to update the firmware through Z-Way, but in the end I would like to use Z-Wave JS UI.
Can I just turn the controller off and switch to another one?
-
Docker container for Z-Way@PerH said in Docker container for Z-Way:
Its been a while since i've used this now, I've moved to Z-WaveJS..
Socat - so you have a remote connection to your z-stick? Should work fine with this contatiner, just set it up in the docker-compose file.
That said, I would ask on the z-way forum, you may find a more current z-way version in a newer container..All settings should be persistent if volumes are set up correctly.
I don't have a remote connection yet, I'm preparing for the migration from Vera to Z-way. I wanted to nuke the Vera and use it as a central hub for my Z-way stick.
From what I've read, Socat will not work in combination with docker. The Ser2net/ Socat solution is giving me a headache with the preparation alone. It is difficult with docker, so it seems, unless you create a docker specifically with Socat in it. But creating docker images is not a skill I possess (yet).
Unlike others in this thread, I'm a fan of docker containers. (Easier to maintain, troubleshoot and keep up-to-date). But Socat is a show stopper for now.
I think I'll ditch the Vera Edge and Z-way docker. I'm looking at using a Raspberry Pi with USB/IP (can't easily install this on the Vera) now instead of Ser2net/Socat and running the Z-way addon for HA.
-
Docker container for Z-Way@PerH Does your docker image support Socat? And, if so, is the configuration persistent after a container update?
-
Expressions page showing old dataThe only lead I have is the disk space, I don't know what else it could be, although I cleared some space as soon as I got the notification.
I don't know what to do to further analyze this. I will monitor this and see if it happens again.
It would be helpful if Reactor could save the expressions to the json more often.
-
Expressions page showing old dataThe exit procedure seems fine.
[latest-23114]2023-06-21T17:47:59.159Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) starting evaluation; because expression-state-changed GlobalExpression#gTempOutside [latest-23114]2023-06-21T17:47:59.159Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) starting evaluation; because expression-state-changed GlobalExpression#gTempOutside [latest-23114]2023-06-21T17:47:59.160Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) trigger evaluation result is true (previously true) [latest-23114]2023-06-21T17:47:59.160Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) evaluated; trigger state unchanged (true); rule state remains SET [latest-23114]2023-06-21T17:47:59.161Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) trigger evaluation result is false (previously false) [latest-23114]2023-06-21T17:47:59.162Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23114]2023-06-21T17:47:59.162Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) evaluation complete [latest-23114]2023-06-21T17:47:59.162Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) evaluation complete [latest-23114]2023-06-21T17:48:07.032Z <app:NOTICE> Shutdown signal (SIGTERM) received. Stopping Reaction Engine... [latest-23114]2023-06-21T17:48:07.034Z <app:NOTICE> Closing APIs... [latest-23114]2023-06-21T17:48:07.035Z <wsapi:NOTICE> wsapi: closing... [latest-23114]2023-06-21T17:48:07.036Z <httpapi:NOTICE> HTTP API closing... [latest-23114]2023-06-21T17:48:07.036Z <app:NOTICE> Stopping Engine... [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Motor op lader (rule-liot7yyg in Garage) stopping [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Zonnescherm auto IN (rule-lipp4379 in Tuin) stopping [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Zonnescherm auto UIT (rule-lhdixs68 in Tuin) stopping [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Disk space low (rule-lgyxocj5 in System) stopping [latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Niels at home (rule-lg7vjm7n in Proximity) stopping [latest-23114]2023-06-21T17:48:07.042Z <Rule:NOTICE> Tessa at home (rule-lg7v960f in Proximity) stopping [latest-23114]2023-06-21T17:48:07.043Z <Rule:NOTICE> Tessa driving (rule-lg7v6f3w in Proximity) stopping [latest-23114]2023-06-21T17:48:07.043Z <Rule:NOTICE> Tessa at work (rule-lg7v3cm6 in Proximity) stopping [latest-23114]2023-06-21T17:48:07.043Z <Rule:NOTICE> Tessa at S&K (rule-lg7uxvzo in Proximity) stopping [latest-23114]2023-06-21T17:48:07.088Z <Rule:NOTICE> Windows open (rule-grp1myo029o in Weer) stopping [latest-23114]2023-06-21T17:48:07.088Z <Rule:NOTICE> Windows closed (rule-grp1mznck5b in Weer) stopping [latest-23114]2023-06-21T17:48:07.088Z <wsapi:NOTICE> wsapi: server closed [latest-23114]2023-06-21T17:48:07.089Z <httpapi:INFO> HTTP server closed. [latest-23114]2023-06-21T17:48:07.090Z <Rule:NOTICE> Motor op lader (rule-liot7yyg in Garage) stopped [latest-23114]2023-06-21T17:48:07.091Z <Rule:NOTICE> Zonnescherm auto IN (rule-lipp4379 in Tuin) stopped [latest-23114]2023-06-21T17:48:07.094Z <Rule:NOTICE> Zonnescherm auto UIT (rule-lhdixs68 in Tuin) stopped [latest-23114]2023-06-21T17:48:07.095Z <Rule:NOTICE> Disk space low (rule-lgyxocj5 in System) stopped [latest-23114]2023-06-21T17:48:07.096Z <Rule:NOTICE> Niels at home (rule-lg7vjm7n in Proximity) stopped [latest-23114]2023-06-21T17:48:07.097Z <Rule:NOTICE> Tessa at home (rule-lg7v960f in Proximity) stopped [latest-23114]2023-06-21T17:48:07.098Z <Rule:NOTICE> Tessa driving (rule-lg7v6f3w in Proximity) stopped [latest-23114]2023-06-21T17:48:07.099Z <Rule:NOTICE> Tessa at work (rule-lg7v3cm6 in Proximity) stopped [latest-23114]2023-06-21T17:48:07.100Z <Rule:NOTICE> Tessa at S&K (rule-lg7uxvzo in Proximity) stopped [latest-23114]2023-06-21T17:48:07.101Z <Rule:NOTICE> Windows open (rule-grp1myo029o in Weer) stopped [latest-23114]2023-06-21T17:48:07.102Z <Rule:NOTICE> Windows closed (rule-grp1mznck5b in Weer) stopped [latest-23114]2023-06-21T17:48:07.111Z <Engine:NOTICE> [Engine]Engine#1 has shut down. [latest-23114]2023-06-21T17:48:07.112Z <app:NOTICE> Closing Structure... [latest-23114]2023-06-21T17:48:07.112Z <Structure:NOTICE> Structure#1 Stopping controllers... [latest-23114]2023-06-21T17:48:07.112Z <Structure:INFO> Structure#1 stopping VeraController#openluup [latest-23114]2023-06-21T17:48:07.113Z <Controller:NOTICE> VeraController#openluup stopping [latest-23114]2023-06-21T17:48:07.117Z <Controller:ERR> Controller VeraController#openluup is off-line! [latest-23114]2023-06-21T17:48:07.952Z <Structure:INFO> Structure#1 stopping HassController#hass [latest-23114]2023-06-21T17:48:07.952Z <HassController:NOTICE> HassController#hass stopping [latest-23114]2023-06-21T17:48:07.965Z <wsapi:WARN> client close from unknown connection? "192.168.1.174#25" [latest-23114]2023-06-21T17:48:07.966Z <wsapi:WARN> client close from unknown connection? "192.168.1.174#24" [latest-23114]2023-06-21T17:48:07.983Z <HassController:NOTICE> HassController#hass websocket closing, 1000 [latest-23114]2023-06-21T17:48:07.985Z <Controller:NOTICE> HassController#hass stopping [latest-23114]2023-06-21T17:48:07.988Z <Controller:ERR> Controller HassController#hass is off-line! [latest-23114]2023-06-21T17:48:09.266Z <Structure:INFO> Structure#1 stopping DynamicGroupController#groups [latest-23114]2023-06-21T17:48:09.266Z <DynamicGroupController:null> DynamicGroupController#groups stopping [latest-23114]2023-06-21T17:48:09.267Z <Controller:NOTICE> DynamicGroupController#groups stopping [latest-23114]2023-06-21T17:48:09.268Z <Controller:ERR> Controller DynamicGroupController#groups is off-line! [latest-23114]2023-06-21T17:48:09.279Z <Structure:INFO> Structure#1 stopping SystemController#reactor_system [latest-23114]2023-06-21T17:48:09.279Z <Controller:NOTICE> SystemController#reactor_system stopping [latest-23114]2023-06-21T17:48:09.281Z <Controller:ERR> Controller SystemController#reactor_system is off-line! [latest-23114]2023-06-21T17:48:09.288Z <Structure:INFO> Structure#1 Final data sync... [latest-23114]2023-06-21T17:48:09.288Z <default:INFO> Closing container Container#rulesets [latest-23114]2023-06-21T17:48:09.289Z <default:INFO> Closing container Container#rules [latest-23114]2023-06-21T17:48:09.289Z <default:INFO> Closing container Container#reactions [latest-23114]2023-06-21T17:48:09.289Z <default:INFO> Closing container Container#states [latest-23114]2023-06-21T17:48:09.316Z <default:INFO> Closing container Container#default [latest-23114]2023-06-21T17:48:09.316Z <default:INFO> Closing container Container#expressions [latest-23114]2023-06-21T17:48:09.318Z <Structure:NOTICE> Structure Structure#1 stopped [latest-23114]2023-06-21T17:48:09.319Z <app:NOTICE> Stopping timers... [latest-23114]2023-06-21T17:48:09.319Z <app:NOTICE> Shutdown complete, process ID 1I did get a disk space notification, so my first thought was that that was the problem. But I believe there always was enough space, more than 1 gb at least.
Does Reactor do something more then only give a signal that disk space is low? Maybe save the cache or something in that line.
-
Expressions page showing old dataIs it possible to save it more often? I have to figure out what's causing the loss of the expressions, but for now my backup is "worthless". Now, the only way to get the expressions back would be a restore of a full backup of the docker files, but then I will potentially lose other changes.
Any idea why I only lose the expressions and not other changes that are done later?
-
Expressions page showing old dataSorry for posting in the other thread, but the problem didn't seem to only be applicable to the add-on.
You don't understand the problem fully. The browser was not the problem. The changes were gone in the expressions.json.
After doing the changes again in the browser, the changes were still not visible in the json. Only after a restart, they were visible in the json.
-
Expressions page showing old dataHi @toggledbits,
I seem to be having the same issue. Is it possible that the expressions are only saved to the json when a restart of Reactor is done?
Today I looked in Reactor and saw an old version of all my expressions. My latest changes were gone (done a few days ago). Reactor didn't have a restart in the meantime.
When I recreated all new expressions and looked in expression.json, the new expressions weren't there (yet). After I did a restart of Reactor, the changes were visible.
Which moments are the expressions saved to the file?
I'm not running the add-on, but the docker. I do not have the latest update yet (latest-23114-e4060aae)
This doesn't explain why my changes were gone, but I'm still tinkering about that. Maybe my backup messes something up.
-
Can't post screen shots here now?Same here.
-
Testing reaction set global expressionOk, that makes sense. Thanks for clearing this up! Maybe make a note in the documentation? Most kind of expect all the actions to run when you click the "Run action now" button on the Reaction, I think. And it's even more confusing if it's also dependent on the rule being active or not.
-
Testing reaction set global expression@toggledbits But why do other actions DO run, when I hit "Run action now", even though my rule is deactivated.
I have an "entity action" next to the "set variable" in the same reaction and this action does fire.
-
Testing reaction set global expressionSorry, can't upload a screenshot. The website gives me a connection error when I try to add it.
-
Testing reaction set global expressionHi @toggledbits
Just a quick question. I noticed that I can't test a "set variable" action when the rule is not active. I wanted to set a global expression in a reaction and wanted to test it by pushing the "Run action now" button in the border of the reaction, but it didn't do anything. Only when I activated the rule, the button worked.
Is this a bug or is this by design?
I'm running the latest docker build:
latest-23114-e4060aae -
Home assistant addon: Import Vera/Openluup backupPff, solved. It was a copy/paste issue of some sorts. I removed the space and typed it again and now it works. Thanks for the help!
-
Home assistant addon: Import Vera/Openluup backup@toggledbits said in Home assistant addon: Import Vera/Openluup backup:
You never posted the original command (the one the instructions gave you), and the error message you got from it. You've only posted an experiment that you tried after, which isn't really relevant. Post the original
lncommand that's not working, and the output/error it generated.That's because it is the same error, namely:
/opt/reactor # ln -sf /var/reactor/storage .
/bin/sh: ln -sf: not found -
Home assistant addon: Import Vera/Openluup backupCan someone please check if the symbolic link command (ln) still works in the latest docker? I want to know if it's a problem with my container or in the image.
-
Home assistant addon: Import Vera/Openluup backupYes, I know. Tried that first, of course. This was to check if it was a PATH issue.