@tommydog It is in prerelease ordering. I don't have one, had just heard about it.
R
RogerO
@RogerO
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
-
looking for a light switch with presence sensor? -
looking for a light switch with presence sensor? -
Another Vera --> Home Assistant migration questionToday I moved my last device from Vera to HomeAssistant. I do have mixed feelings about it. For all it's flaws and performance issues, it had a very easy interface to get started in and for the average person, could do most of what they needed. Started using PLEG but never got very far with it since I had to spend hours relearning it every time I wanted to add a new automation. Reactor was a breath of fresh air for the Vera and I am eternally grateful for all the assistant I have received from Patrick over the years including some beta code for my Leviton scene controllers and my Venstar thermostat. MSR allowed me to tie my Vera and Home Assistant together while I slowly migrated off Vera and had way more capabilities than I could ever master.
As I get older, my wife keeps telling me that if I die she is selling the house because she cannot run it. That has given me some incentive to simplify my environment so I have gone to only Home Assistant. Would have stayed with MSR if I could have figured out how to get the addon to work in HA, but in the end was easier to move everything to HA and eliminated one more component.
Thanks to all the people that have offered assistance on this community as well as the old Vera forum before EZLO.Roger
Have a nice Vera Plus available if anyone is interested. In the Seattle area but will ship. Make me an offer.
-
Home Assistant add-onHere is a file list from the container, Sorry that it is a screen shot. Don't want to f up my system by typing something stupid and not a docker expert. If there is a specific directory you want me to look at let me know
Still getting 502 bad gateway from nginx
-
Home Assistant add-on@mrw298 Anything I can do to help you troubleshoot or do you have any ideas on how to get this resolved?
-
Home Assistant add-onoh yeah, forgot that part.
-
Home Assistant add-onCurrently running HASSIO on a RPI4
Home Assistant 2023.2.2
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230202.0 - latestUninstalled the addin and deleted the reactor.yaml file. Installed the addin and if choked because it couldn't find yaml file. Using winscp I created one and it will not start. /opt/ is empty.
-
Home Assistant add-onHello,
Trying to install this and getting the following in the logs:2023-02-07 00:26:46,034 INFO exited: reactor (exit status 1; not expected)
2023-02-07 00:26:47,044 INFO spawned: 'reactor' with pid 3569
Using existing set-up
Reactor Token is set, updating config
Reactor latest-23028-ddc3fb14 app 22364 configuration from /config/reactor
NODE_PATH /opt/reactor:/opt/reactor/node_modules
2023-02-07 00:26:48,154 INFO success: reactor entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
node:internal/fs/utils:345
throw err;
^
Error: ENOENT: no such file or directory, open '/config/reactor/logging.yaml'
at Object.openSync (node:fs:585:3)
at Object.readFileSync (node:fs:453:35)
at Function.loadConfig (/opt/reactor/server/lib/Configuration.js:226:68)
at Function.getInstance (/opt/reactor/server/lib/Configuration.js:144:66)
at Object.<anonymous> (/opt/reactor/app.js:105:97)
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 Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
errno: -2,
syscall: 'open',
code: 'ENOENT',
path: '/config/reactor/logging.yaml'Looked in the/opt directory and it was empty. Getting a bad gateway error when I try to load the page.
Thanks,
Roger -
Home Assistant add-on -
Home Assistant add-onExcellent, was hoping it would eventually come to HA. Will you be adding update instructions at some point?
-
Help. Installing Reactor on Home Assistant.@toggledbits Hi Patrick,
Looking at your Portainer doc, found a minor error I think. In second paragraph in first section you have "For most Linux most systems," . Doesn't make sense.Also, should "The stable branch builds have seen action for a while and are more... well... stable." Actually be "The stable branch builds have not seen action for a while and are more... well... stable.
-
OT: Universal RemoteSince I have a bunch of Logitechs as well, I backed this on kickstarter. https://www.kickstarter.com/projects/flirc/the-skip-1s-universal-remote-control-by-flirc/description Should be shipping soon I think. This is their commercial webpage: https://flirc.tv/products/skip1s-remote?variant=43489094729960
-
Light automation thoughts
Home-Assistant/esphome/presence at main · EvisHome/Home-Assistant
My Home Assistant guides, examples and YAMLs for dashboards, projects and reference purposes - EvisHome/Home-Assistant
-
Light automation thoughts@catmanv2 Yeah, it quit working for me as well. Could view it in the wayback machine though.
-
Light automation thoughtsThis one, while geared to HA, uses MQTT over wifi.
https://lab.evishome.com/esphome-mmwave-radar-pir-ble-tracking/ -
Light automation thoughtsYou could build your own. https://community.home-assistant.io/t/mmwave-presence-detection-esphome-style/382778
-
Light automation thoughtshttps://shop.everythingsmart.io/en-us. Had a nice mmwave presence sensor.
-
Have MSR as a shortcut in Home Assistant with duckdns?Check out ZeroTier. It is so easy to set up on all kinds of devices.
-
Version 22305 with ZWaveJS -- Invalid Entity IDs in logThat fixed it. Thanks
-
Version 22305 with ZWaveJS -- Invalid Entity IDs in logHey Patrick,
Just upgraded zwavejs in home assistant and all of the entities in zwavejs are not showing in reactor. Not sure if they broke something in how you read the data or if they broke something with how they read and display the attributes. when I duplicate the screen a few comments back now, it is blank. the zwavejs>controller_all shows all the sys_group.members:sys_group.empty=false
sys_group.members=["zwavejs>system","zwavejs>1-0","zwavejs>35-0","zwavejs>35-0-001","zwavejs>35-0-002","zwavejs>35-0-003","zwavejs>35-0-004","zwavejs>35-0-005","zwavejs>36-0","zwavejs>36-0-001","zwavejs>36-0-002","zwavejs>36-0-003","zwavejs>36-0-004","zwavejs>36-0-005","zwavejs>36-0-009","zwavejs>37-0","zwavejs>37-1","zwavejs>37-2","zwavejs>37-3","zwavejs>37-4","zwavejs>37-5","zwavejs>37-6","zwavejs>37-7","zwavejs>39-0","zwavejs>39-0-001","zwavejs>39-0-002","zwavejs>39-0-010","zwavejs>40-0","zwavejs>40-0-001","zwavejs>40-0-002","zwavejs>40-0-003","zwavejs>40-0-004","zwavejs>40-1","zwavejs>40-2","zwavejs>40-3","zwavejs>40-4","zwavejs>40-5","zwavejs>40-6","zwavejs>40-7","zwavejs>40-8","zwavejs>40-9","zwavejs>45-0","zwavejs>45-0-001","zwavejs>45-0-002","zwavejs>45-0-003","zwavejs>45-0-004","zwavejs>45-0-005","zwavejs>45-0-009","zwavejs>46-0","zwavejs>46-0-001","zwavejs>46-0-002","zwavejs>46-0-003","zwavejs>46-0-004","zwavejs>46-0-005","zwavejs>46-0-009","zwavejs>47-0","zwavejs>48-0","zwavejs>49-0","zwavejs>51-0","zwavejs>54-0","zwavejs>55-0","zwavejs>56-0","zwavejs>57-0","zwavejs>58-0","zwavejs>59-0","zwavejs>60-0","zwavejs>61-0","zwavejs>65-0","zwavejs>66-0","zwavejs>69-0","zwavejs>70-0","zwavejs>70-1","zwavejs>70-2","zwavejs>71-0","zwavejs>73-0","zwavejs>83-0","zwavejs>84-0","zwavejs>85-0","zwavejs>86-0","zwavejs>87-0","zwavejs>88-0","zwavejs>90-0","zwavejs>94-0","zwavejs>94-1","zwavejs>94-2","zwavejs>95-0","zwavejs>98-0"]Currently on MSR 22305 and zwavejs 10.3.0
zwavejs error logs is full of these:
[latest-22305]2022-11-01T14:56:52.344Z <ZWaveJSController:CRIT> Error: Invalid entity ID Error: Invalid entity ID at new Entity (/opt/reactor/server/lib/Entity.js:244:19) at ZWaveJSController.getEntity (/opt/reactor/server/lib/Controller.js:695:28) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1021:31) at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22305]2022-11-01T14:56:52.344Z <ZWaveJSController:ERR> ZWaveJSController#zwavejs node 35 setup failed: [Error]Error: Invalid entity ID [latest-22305]2022-11-01T14:56:52.344Z <ZWaveJSController:CRIT> Error: Invalid entity ID Error: Invalid entity ID at new Entity (/opt/reactor/server/lib/Entity.js:244:19) at ZWaveJSController.getEntity (/opt/reactor/server/lib/Controller.js:695:28) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1021:31) at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22305]2022-11-01T14:56:52.344Z <ZWaveJSController:ERR> ZWaveJSController#zwavejs node 36 setup failed: [Error]Error: Invalid entity ID [latest-22305]2022-11-01T14:56:52.345Z <ZWaveJSController:CRIT> Error: Invalid entity ID Error: Invalid entity ID at new Entity (/opt/reactor/server/lib/Entity.js:244:19) at ZWaveJSController.getEntity (/opt/reactor/server/lib/Controller.js:695:28) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1021:31) at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22305]2022-11-01T14:56:52.345Z <ZWaveJSController:ERR> ZWaveJSController#zwavejs node 37 setup failed: [Error]Error: Invalid entity ID [latest-22305]2022-11-01T14:56:52.345Z <ZWaveJSController:CRIT> Error: Invalid entity ID Error: Invalid entity ID at new Entity (/opt/reactor/server/lib/Entity.js:244:19) at ZWaveJSController.getEntity (/opt/reactor/server/lib/Controller.js:695:28) at ZWaveJSController._register_node (/var/reactor/ext/ZWaveJSController/ZWaveJSController.js:1021:31) at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-22305]2022-11-01T14:56:52.345Z <ZWaveJSController:ERR> ZWaveJSController#zwavejs node 39 setup failed: [Error]Error: Invalid entity ID [latest-22305]2022-11-01T14:56:52.345Z <ZWaveJSController:CRIT> Error: Invalid entity ID Error: Invalid entity IDJust watched the action in the zwavejs debug window and it appears to be capturing the button push.
2022-11-01T23:07:07.393Z CNTRLR « [Node 045] received CentralScene notification {
"nodeId": 45,
"ccId": "Central Scene",
"ccCommand": "0x03",
"payload": "0x008401"
}
Red Series (Z-Wave) - Smart Presence Sensing Dimmer
