Use case:
When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.
To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.
Then another situation: the water pump system and garden irrigation, another switch.
In short, I had to create several virtual switches in Hubitat to disable rules in MSR.
Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.
If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.
Would it be possible to do something like this? Any recommendations from the experts?
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of.
Thanks.
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI:
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status
Last 11:20:37
My MQTT configuration (local_mqtt_devices.yaml) for the related entity is:
layzspa_message:
type: ValueSensor
capabilities: ["temperature_sensor", "value_sensor", "power_sensor"]
primary_attribute: power_sensor.value
events:
"layzspa/message":
"power_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.PWR )'
expr: "float(payload.PWR)"
"value_sensor.air":
json_payload: true
if_expr: '! isnull( payload?.AIR )'
expr: "float(payload.AIR)"
"value_sensor.pump":
json_payload: true
if_expr: '! isnull( payload?.FLT )'
expr: "float(payload.FLT)"
"value_sensor.god":
json_payload: true
if_expr: '! isnull( payload?.GOD )'
expr: "float(payload.GOD)"
"value_sensor.lock":
json_payload: true
if_expr: '! isnull( payload?.LCK )'
expr: "float(payload.LCK)"
"value_sensor.unit":
json_payload: true
if_expr: '! isnull( payload?.UNT )'
expr: "float(payload.UNT)"
"value_sensor.error":
json_payload: true
if_expr: '! isnull( payload?.ERR )'
expr: "float(payload.ERR)"
"temperature_sensor.green":
json_payload: true
if_expr: '! isnull( payload?.GRN )'
expr: "float(payload.GRN)"
"temperature_sensor.red":
json_payload: true
if_expr: '! isnull( payload?.RED )'
expr: "float(payload.RED)"
"temperature_sensor.target":
json_payload: true
if_expr: '! isnull( payload?.TGT )'
expr: "float(payload.TGT)"
"temperature_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.TMP )'
expr: "float(payload.TMP)"
"temperature_sensor.virtual":
json_payload: true
if_expr: '! isnull( payload?.VTM )'
expr: "round(float(payload.VTM), 1)"
"temperature_sensor.ambient":
json_payload: true
if_expr: '! isnull( payload?.AMB )'
expr: "float(payload.AMB)"
"layzspa/Status":
"value_sensor.status":
if_expr: '! isnull( payload )'
expr: "payload"
"layzspa/button":
"value_sensor.button":
if_expr: '! isnull( payload )'
expr: "payload"
and in reactor.yaml I have:
"layzspa_states":
name: "Lay-Z-Spa States"
friendly_name: 'Lay-Z-Spa States'
include: layzspa_message
I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded).
Get it at (install is similar to MQTTController and such):
https://github.com/dbochicchio/reactor-opensprinkler
Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty.
Since I've learnt a lot from this controller, I'll explore new controllers soon.
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?
[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
