Beginning with the next Reactor release, there will be some dependency changes and new deprecations.
These apply to users on bare-metal installs only. If you are running Reactor in a docker container, the following does not apply to you — the container supplies its own dependencies and will be up-to-date.
All versions of nodejs prior to 18 are now end-of-life (no maintenance), so starting with the next Reactor build, they are deprecated for use with Reactor; they will continue to work until March 1 2024 (about 3 months from now), so you need to upgrade before that date. The recommended version of nodejs is 20, which is the current long-term support (LTS) version (EOL in mid-2026). Version 18 is the prior LTS version and still supported (by OpenJS Foundation and Reactor) until mid-2025, so it's a good fallback if you have issues getting version 20 running. As of this writing, the current 20 is 20.10.0, and the current 18 is 18.18.2. Both have been tested with Reactor 23302.
Now, nodejs version 20.9.0 seems to have dependencies that are not easily resolved on Raspberry Pi OS (formerly Raspbian) Buster (Debian 10). If you are using an RPi running Buster, you should select nodejs 18. That gives you until mid-2025 to upgrade both nodejs and the RPi OS to a more modern version (the current RPi OS is bookworm, Debian 12, 64-bit). The tools/rpi-install.sh script will be enhanced for the next build to try to discern what is reasonable for your system and make the appropriate upgrades; it is safe to run even on a current Reactor install.
If you are running an OS other than Raspberry Pi OS, try for nodejs 20, but use 18 as a fallback if you can't get it installed and running.
@togglebits I have another one for you.
HASS controller shows hvac_control.state="heating, cooling or idle".
ZWaveJSController controller shows hvac_control.state="heat, cool, or idle"
I believe hvac_control.state="heating, cooling or idle" should be what the ZWaveJSController should show.
"heat", "cool" or "off" are values assigned to the hvac_control.mode attribute.
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 thermostat 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
Certain MSR updates are irrelevant for some users (e.g. only Hass related changes when you are not using one), so I was wondering if there could be a dismiss (firmware) feature similar to Hubitat?
Then when you'll use "dismiss", a blue checkmark would disappear until there's a new firmware.
Noticed that if I try to use a case statement, I'll have to have multiple when clauses, otherwise I'll get syntax error.
(I tried to include a screenshot, but got parse error from the forum...)
The following works:
case when condition == true: "This is true" when condition == false: "Now it is false" else "Something else" endBut this will end up with syntax error:
case when condition == true: "This is true" else "Something else" endUsing build 23242 on Docker
When doing something like curl -o - 'http://localhost:8111/api/v1/entity/ezlo>device_61baf509129e0725bd9f80e1/attribute/dimming.level' I get a response with current dimming level for example "0.6"
but curl -o - 'http://localhost:8111/api/v1/entity/ezlo>device_61baf509129e0725bd9f80e1/perform/dimming.set?level=0.8' sets the dimming level to 0.8 but gives no response which causes the connection to eventually timeout.
Doing it in a browser performs the action but leaves the tab with a spinning wheel of a loading page.
Is this expected behavior?
Edit: Solved in build 22142
Hi @toggledbits
Apparently, there have been some changes to the CallMeBot interface, as the service recently stopped working for me. I've tried several configurations, and none of the ones below are working.
# CallMeBot CallMeBot: profiles: default: # description - A friendly description of this profile (for menus) description: Default Profile New # # api_url - Access URL for CallMeBot API being used api_url: http://api.callmebot.com/start.php # # api_key - (if needed) API key (use for Facebook API, WhatsApp API, etc.). # If the API you are using does not require it, leave it # commented out or blank. api_key: "177xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxTGk" # # source - (if needed) Source field for some APIs. If yours does not require # it, leave it commented out or blank. #source: "source-value" # # phone - (if needed) Phone field for some APIs. If yours does not require # it, leave it commented out or blank. phone: "+5xxxxxxxx33" # # user - (if needed) User field for some APIs. If yours does not require # it, leave it commented out or blank. #user: "@xxxxxxxxxxxxx" # # lang - (optional) Language/voice; default "en-US-Standard-C". # See CallMeBot docs for possible values. lang: "en-US-Standard-C" # # rpt - (optional) Number of times to repeat message; default: 1. rpt: 2I have already tested using the phone or the user.
Looking at the action log, I see that it starts, runs and finishes without any problems.
[latest-23302]2023-11-05T14:35:54.106Z <Engine:INFO> Enqueueing "teste<SET>" (rule-lolk0nlj:S) [latest-23302]2023-11-05T14:35:54.108Z <Engine:NOTICE> Starting reaction teste<SET> (rule-lolk0nlj:S) [latest-23302]2023-11-05T14:35:54.111Z <Engine:INFO> teste<SET> all actions completed.When testing directly on the site, I see that it no longer uses API, and I haven't even found where to generate the API KEY.
http://api.callmebot.com/start.php?source=web&user=+5xxxxxxxx33&text=Teste callmebot pelo numero novo&lang=en-US-Standard-CPlease, can you advise me on what I should do to solve the problem?
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
I have just noticed that two of my z-wave switches, Inovelli LZW31 and Aeotec ZWA037, although responding correctly to commands such as (turning on the switch, changing LED color, etc.), are not displaying the right power_switch.state when turned ON. All other attributes are showing proper values.
Example when I turn on either switches,
In Home Assistant (hass), the power_switch.state = true while in ZWaveJSController (zwavejs), the power_switch.state = false.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
Here's what the log shows.
[latest-23302]2023-11-01T21:14:00.303Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.304Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.304Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.304Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:00.308Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.309Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.309Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.309Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:00.311Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.312Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.312Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.313Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:00.315Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.317Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.317Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.317Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:03.258Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) starting evaluation; because entity-changed Light#hass>light_office_light [latest-23302]2023-11-01T21:14:03.259Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) trigger evaluation result is true (previously false) [latest-23302]2023-11-01T21:14:03.260Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluated; rule state transition from RESET to SET! [latest-23302]2023-11-01T21:14:03.271Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluation complete [latest-23302]2023-11-01T21:14:03.273Z <Engine:INFO> Enqueueing "Toggle office light LED color state between green/blue Copy<SET>" (rule-lof5hpwe:S) [latest-23302]2023-11-01T21:14:03.285Z <Engine:NOTICE> Starting reaction Toggle office light LED color state between green/blue Copy<SET> (rule-lof5hpwe:S) [latest-23302]2023-11-01T21:14:03.287Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Light#zwavejs>138-0 with [Object]{ "parameter": "84", "size": 1, "value": 3, "bitmask": 0 } [latest-23302]2023-11-01T21:14:03.345Z <Engine:INFO> Resuming reaction Toggle office light LED color state between green/blue Copy<SET> (rule-lof5hpwe:S) from step 2 [latest-23302]2023-11-01T21:14:03.346Z <Engine:INFO> Toggle office light LED color state between green/blue Copy<SET> all actions completed. [latest-23302]2023-11-01T21:14:05.191Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs node 138-0 no value +currentValue: found for power_switch.state [latest-23302]2023-11-01T21:14:05.205Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) starting evaluation; because entity-changed Light#hass>light_office_light [latest-23302]2023-11-01T21:14:05.205Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) trigger evaluation result is true (previously true) [latest-23302]2023-11-01T21:14:05.206Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluated; trigger state unchanged (true); rule state remains SET [latest-23302]2023-11-01T21:14:05.206Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluation complete [latest-23302]2023-11-01T21:14:10.503Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs node 138-0 no value +currentValue: found for power_switch.state [latest-23302]2023-11-01T21:14:10.518Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) starting evaluation; because entity-changed Light#hass>light_office_light [latest-23302]2023-11-01T21:14:10.519Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) trigger evaluation result is false (previously true) [latest-23302]2023-11-01T21:14:10.520Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluated; rule state transition from SET to RESET! [latest-23302]2023-11-01T21:14:10.529Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluation complete [latest-23302]2023-11-01T21:14:10.530Z <Engine:INFO> Enqueueing "Toggle office light LED color state between green/blue Copy<RESET>" (rule-lof5hpwe:R) [latest-23302]2023-11-01T21:14:10.542Z <Engine:NOTICE> Starting reaction Toggle office light LED color state between green/blue Copy<RESET> (rule-lof5hpwe:R) [latest-23302]2023-11-01T21:14:10.543Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Light#zwavejs>138-0 with [Object]{ "parameter": "84", "size": 1, "value": 2, "bitmask": 0 } [latest-23302]2023-11-01T21:14:10.596Z <Engine:INFO> Resuming reaction Toggle office light LED color state between green/blue Copy<RESET> (rule-lof5hpwe:R) from step 2 [latest-23302]2023-11-01T21:14:10.597Z <Engine:INFO> Toggle office light LED color state between green/blue Copy<RESET> all actions completed. [latest-23302]2023-11-01T21:14:12.441Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs node 138-0 no value +currentValue: found for power_switch.statePS I am trying to attach an image but getting "Something went wrong while parsing server response". Also, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version.
Hopefully I have provided the necessary information.
Thanks in advance.
Some background
I have two simple rules that will toggle my carport's down lights depending on outdoor brightness when I open the motorized sliding gate. I.e. if the brightness is 1500 lux or less and the gate is opened, the down lights will be switched on, and when the gate is closed, the lights will switch off after 3 minutes. Pretty simple 'coming home' functionality so to speak.
Here's the switch off rule showing the 'hard coded' thresholds
Screenshot from 2023-10-31 18-44-46.png
The problem
I would like to parameterize the lux and switch off delay using entities. I bet the lux threshold can be done with local expressions the same way I do my WC background music scheduling:
But the since I'm using the Condition must be sustained for functionality for the switch off rule, I have no idea how to parameterize that with some entity value.
So my question is that is it even possible to do this using entities or could there some other way to accomplish the same functionality? In this example it's the sustain -value but I might need same kind of parameterization for the delay reset also.
I have to go with entities, since my own HA system will provide the threshold values for the MSR through the MQTTController.
Help would be appreciated @toggledbits
br,
mgvra
MSR latest-23302-b7def56a and MQTTController [0.1.23254]
So I have a strange one here and I don't know if there is a way to do this or not. I have blue iris triggering a vera virtual switch when AI detects motion on my front porch. Reactor then triggers the light, this works perfect. I want to shut the light off when there is no motion, this also works perfect. What I am having am issue with is when someone turns on the light manually I don't want it to turn off after motion is detected. Example: we are expecting a pizza so we turn on the porch light. 5 min later amazon delivers a package, trips motion. 10 min later Reactor is going to turn off the light. If I manually turn on the light before motion is detected I do not want reactor to turn it off. For the life of me I cannot figure the logic out. Does anyone have any ideas?
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 @toggledbits
Is there any way that in the trigger the Varable Value could select the desired part of the array?
For example, I could have a global variable VarTEST$[Part1, Part2, Part3] like this: ${{ [TestText, 5, 3] }}. Use the Variable Value to validate a VarTEST[Part2] == 5 trigger.
What am I doing today? I've defined 3 global variables:
3ae76d20-ffce-4f66-9002-1b4d6cc7c3c3-image.png
And I validate each variable.
3bcc1d62-2ce1-41ca-9f00-f98578c0d597-image.png
In short, I would like to have a global variable of the array type, and be able to select which element of the array I would use for validation in a trigger.
Thanks
Hello all I am trying to run the service call browser_mod.popup from MSR to HA. If I enter the service data in YAML like this:
dismissable: true autoclose: false timeout: 120000 content: type: custom:mushroom-alarm-control-panel-card entity: alarm_control_panel.home_partition states: - armed_home - armed_away layout: vertical show_keypad: true target: device_id: e684ad00b76e330e57a8c915dc367bc4For some reason the target portion of the data isn't sent and therefor the popup shows up on all my browser mod devices not the only one I had specified in the device_id. Here is a snippet of the reactor log, no errors that I see just looks like the target info isn't being passed on.
[latest-23242]2023-10-12T23:51:50.795Z <Engine:INFO> Enqueueing "Main Floor Tablet Alarm Arming Popup<SET>" (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:51:50.800Z <Engine:NOTICE> Starting reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:51:50.813Z <HassController:INFO> HassController#hass action x_hass_system.call_service([Object]{ "service": "browser_mod.popup", "data": "data:\n dismissable: true\n autoclose: false\n timeout: 120000\n content:\n type: custom:mushroom-alarm-control-panel-card\n entity: alarm_control_panel.home_partition\n states:\n - armed_home\n - armed_away\n layout: vertical\n show_keypad: true\ntarget:\n device_id: e684ad00b76e330e57a8c915dc367bc4" }) on System#hass>system succeeded [latest-23242]2023-10-12T23:51:50.816Z <Engine:INFO> Resuming reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) from step 1 [latest-23242]2023-10-12T23:51:50.817Z <Engine:INFO> Main Floor Tablet Alarm Arming Popup<SET> all actions completed.So I used an online YAML to JSON converter since I am not the good with JSON and it converted the YAML to this:
{ "data": { "dismissable": true, "autoclose": false, "timeout": 120000, "content": { "type": "custom:mushroom-alarm-control-panel-card", "entity": "alarm_control_panel.bar_partition", "states": [ "armed_home", "armed_away" ], "layout": "vertical", "show_keypad": true } }, "target": { "device_id": "34ae76561192c4bb0b64fb07ad0f01c1" } }When I use this in my reaction the popup doesn't show up properly. Something pops up but it's just a grey bar. Interestingly the JSON version actually does target only the device_id I had specified. Here is the reactor log output:
[latest-23242]2023-10-12T23:52:39.875Z <Engine:INFO> Enqueueing "Main Floor Tablet Alarm Arming Popup<SET>" (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:52:39.880Z <Engine:NOTICE> Starting reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:52:40.291Z <HassController:INFO> HassController#hass action x_hass_system.call_service([Object]{ "service": "browser_mod.popup", "data": "{\n \"data\": {\n \"dismissable\": true,\n \"autoclose\": false,\n \"timeout\": 120000,\n \"content\": {\n \"type\": \"custom:mushroom-alarm-control-panel-card\",\n \"entity\": \"alarm_control_panel.home_partition\",\n \"states\": [\n \"armed_home\",\n \"armed_away\"\n ],\n \"layout\": \"vertical\",\n \"show_keypad\": true\n }\n },\n \"target\": {\n \"device_id\": \"e684ad00b76e330e57a8c915dc367bc4\"\n }\n}" }) on System#hass>system succeeded [latest-23242]2023-10-12T23:52:40.293Z <Engine:INFO> Resuming reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) from step 1 [latest-23242]2023-10-12T23:52:40.294Z <Engine:INFO> Main Floor Tablet Alarm Arming Popup<SET> all actions completed.My limited skill with JSON has kind of backed me into a corner here, so if anyone could help me format it correctly that would be great!
MSR latest 23242
HA 2023.10.1
Here's my second attempt at a Reactor Controller, this time to integrate LG TVs:

Reactor controller for LG TV (webos). Contribute to dbochicchio/reactor-lgtv development by creating an account on GitHub.
Standard capabilities are provided and TV volume, mute and switch status are controllable.
There's also an action to send toast notifications on your TV.
webos 5+ is required.
I installed a new iblind this evening and it is appearing in ZWaveJS. It is operational thru Home Assistant just fine. It is operational thru the HA ZwaveJS plugin just fine.
Where it is non-responsive is in MSR for some reason. The entities are there. Adding the node to a Reaction and then attempting to run said Reaction nets me this:
[latest-23242]2023-09-08T05:33:08.454Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value motion_sensor.state=false [latest-23242]2023-09-08T05:33:08.455Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Binary Sensor#zwavejs>11-0.x_zwave_values.Binary_Sensor_Motion to false [latest-23242]2023-09-08T05:33:08.692Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Binary Sensor#zwavejs>11-0 [latest-23242]2023-09-08T05:40:23.960Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>20-0 with [Object]{ } [latest-23242]2023-09-08T05:40:23.962Z <ZWaveJSController:5:ZWaveJSController.js:1843> ZWaveJSController#zwavejs no implementation mapped; attempting default [latest-23242]2023-09-08T05:40:25.062Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.refresh on Cover#zwavejs>20-0 with [Object]{ } **[latest-23242]2023-09-08T05:40:25.063Z <ZWaveJSController:5:ZWaveJSController.js:1843> ZWaveJSController#zwavejs no implementation mapped; attempting default** [latest-23242]2023-09-08T05:40:25.065Z <ZWaveJSController:5:ZWaveJSController.js:294> ZWaveJSController#zwavejs sending #1694151625064<9/8/2023, 1:40:25 AM>: [Object]{ "command": "node.refresh_values", "nodeId": 20, "messageId": 1694151625064 } [latest-23242]2023-09-08T05:40:26.307Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>20-0 [latest-23242]2023-09-08T05:40:26.317Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>20-0 [latest-23242]2023-09-08T05:40:26.318Z <ZWaveJSController:5:ZWaveJSController.js:667> ZWaveJSController#zwavejs update node 20 value "0:128:level:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 20, "args": { "commandClassName": "Battery", "commandClass": 128, "property": "level", "endpoint": 0, "newValue": 100, "prevValue": 100, "propertyName": "level" } } [latest-23242]2023-09-08T05:40:26.319Z <ZWaveJSController:5:ZWaveJSController.js:684> ZWaveJSController#zwavejs updating attributes for node 20 value "0:128:level:"=100: [Array][ "battery_power.level", "battery_power.since" ] [latest-23242]2023-09-08T05:40:26.320Z <ZWaveJSController:5:ZWaveJSController.js:698> ZWaveJSController#zwavejs updating attribute battery_power.level with [Object]{ "entity": "20-0", "impl": { "expr": "float( value ) / 100", "valueId": "128:level:" } } [latest-23242]2023-09-08T05:40:26.321Z <ZWaveJSController:5:ZWaveJSController.js:591> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>20-0 battery_power.level [latest-23242]2023-09-08T05:40:26.322Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value battery_power.level=1 [latest-23242]2023-09-08T05:40:26.323Z <ZWaveJSController:5:ZWaveJSController.js:698> ZWaveJSController#zwavejs updating attribute battery_power.since with [Object]{ "entity": "20-0", "impl": { "expr": "time()", "valueId": "128:level:" } } [latest-23242]2023-09-08T05:40:26.323Z <ZWaveJSController:5:ZWaveJSController.js:591> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>20-0 battery_power.since [latest-23242]2023-09-08T05:40:26.324Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value battery_power.since=1694151626324<9/8/2023, 1:40:26 AM> [latest-23242]2023-09-08T05:40:26.325Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Cover#zwavejs>20-0.x_zwave_values.Battery_level to 100 [latest-23242]2023-09-08T05:40:26.333Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>20-0 [latest-23242]2023-09-08T05:40:26.334Z <ZWaveJSController:5:ZWaveJSController.js:667> ZWaveJSController#zwavejs update node 20 value "0:128:isLow:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 20, "args": { "commandClassName": "Battery", "commandClass": 128, "property": "isLow", "endpoint": 0, "newValue": false, "prevValue": false, "propertyName": "isLow" } } [latest-23242]2023-09-08T05:40:26.336Z <ZWaveJSController:5:ZWaveJSController.js:324> ZWaveJSController#zwavejs request 1694151625064<9/8/2023, 1:40:25 AM> (node.refresh_values) success notification [latest-23242]2023-09-08T05:40:26.337Z <ZWaveJSController:5:ZWaveJSController.js:684> ZWaveJSController#zwavejs updating attributes for node 20 value "0:128:isLow:"=false: [Array][ ] [latest-23242]2023-09-08T05:40:26.338Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Cover#zwavejs>20-0.x_zwave_values.Battery_isLow to false [latest-23242]2023-09-08T05:40:26.558Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>20-0Please note the highlighted logpart - no other iblind has this. In addition, in MSR>Entities several show as null rather than having a value as the others do.
69631fbc-db4e-4e8d-aa98-10565811cd93-image.png
I tried deleting all Entities associated with this device from MSR and then refreshing ZWaveJS in Home Assistant and restarting MSR - the Entities return but in the same state/s.
Admittedly, it's been a very long three weeks at work - I could have missed something obvious during setup but I sure can't figure what it is.
Hi @toggledbits
I'm trying to use OWM, apparently, I receive the correct information, but after a while, the MSR disconnects.
My configuration is as follows.
- id: weather enabled: true implementation: OWMWeatherController name: OWM Weather config: # Place your OWM API key here (remember to enable the controller after adding your appid) appid: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" # How often weather is allowed to be refreshed. This helps limit OWN API use, # to keep you in their good graces (and on their free tier). This value is # in minutes. interval: 30 locations: - id: home name: Home Weather # Set the location by specifying ONE OF: latitude+longitude, OWN city # ID, or location (as postal,country). If none is set, the system # location will be used. latitude: 8.9936 longitude: -79.5197 city_id: 3703443 #location: "30269,us" # Enable "save_full_response" to save the full response (you may have # need to use parts of the response that are not part of the wx # capability in your dashboard widgets). #save_full_response: falseWhen I request a systemctl status reactor I get this message:
root@main:/home/wilson/reactor/logs# systemctl status reactor ● reactor.service - Multi System Reactor Loaded: loaded (/etc/systemd/system/reactor.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-09-08 21:03:13 EST; 5s ago Main PID: 194711 (node) Tasks: 11 (limit: 9390) Memory: 82.5M CPU: 2.508s CGroup: /system.slice/reactor.service └─194711 /usr/bin/node app -p Sep 08 21:03:13 main node[194711]: Error: Incompatible serialization data; can't unserialize Sep 08 21:03:13 main node[194711]: at System.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) Sep 08 21:03:13 main node[194711]: at /home/wilson/reactor/server/lib/Controller.js:458:70 Sep 08 21:03:13 main node[194711]: at Array.forEach (<anonymous>) Sep 08 21:03:13 main node[194711]: at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) Sep 08 21:03:13 main node[194711]: at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) Sep 08 21:03:13 main node[194711]: at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) Sep 08 21:03:13 main node[194711]: at /home/wilson/reactor/server/lib/Controller.js:93:37 Sep 08 21:03:13 main node[194711]: [latest-23242]2023-09-09T02:03:13.855Z <NUTController:null> Module NUTController v22305 Sep 08 21:03:13 main node[194711]: [latest-23242]2023-09-09T02:03:13.859Z <SystemController:null> Module SystemController v23214 root@main:/home/wilson/reactor/logs# root@main:/home/wilson/reactor# systemctl status reactor ● reactor.service - Multi System Reactor Loaded: loaded (/etc/systemd/system/reactor.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2023-09-08 20:48:36 EST; 2min 58s ago Main PID: 194353 (node) Tasks: 11 (limit: 9390) Memory: 66.0M CPU: 9.493s CGroup: /system.slice/reactor.service └─194353 /usr/bin/node app -p Sep 08 20:48:37 main node[194353]: at System.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) Sep 08 20:48:37 main node[194353]: at /home/wilson/reactor/server/lib/Controller.js:458:70 Sep 08 20:48:37 main node[194353]: at Array.forEach (<anonymous>) Sep 08 20:48:37 main node[194353]: at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) Sep 08 20:48:37 main node[194353]: at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) Sep 08 20:48:37 main node[194353]: at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) Sep 08 20:48:37 main node[194353]: at /home/wilson/reactor/server/lib/Controller.js:93:37 Sep 08 20:48:37 main node[194353]: [latest-23242]2023-09-09T01:48:37.017Z <NUTController:null> Module NUTController v22305 Sep 08 20:48:37 main node[194353]: [latest-23242]2023-09-09T01:48:37.024Z <SystemController:null> Module SystemController v23214 Sep 08 20:48:37 main node[194353]: [latest-23242]2023-09-09T01:48:37.475Z <Timer:null> Timer#rule-l7ujwva5 just a note: I'm setting a delay of > lines 1-20/20 (END)I can see this information in the log, but I don't understand what I should do to fix it.
[latest-23242]2023-09-09T02:03:13.838Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-23242]2023-09-09T02:03:13.845Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [latest-23242]2023-09-09T02:03:13.847Z <OWMWeatherController:null> Module OWMWeatherController v22294 [latest-23242]2023-09-09T02:03:13.850Z <Controller:WARN> OWMWeatherController#weather failed (1) to restore entity controller_all: [Error] Inco> [latest-23242]2023-09-09T02:03:13.850Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Group.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) at /home/wilson/reactor/server/lib/Controller.js:458:70 at Array.forEach (<anonymous>) at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) at /home/wilson/reactor/server/lib/Controller.js:93:37 [latest-23242]2023-09-09T02:03:13.851Z <Controller:WARN> OWMWeatherController#weather failed (1) to restore entity default: [Error] Incompatibl> [latest-23242]2023-09-09T02:03:13.851Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at Entity.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) at /home/wilson/reactor/server/lib/Controller.js:458:70 at Array.forEach (<anonymous>) at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) at /home/wilson/reactor/server/lib/Controller.js:93:37 [latest-23242]2023-09-09T02:03:13.852Z <Controller:WARN> OWMWeatherController#weather failed (1) to restore entity system: [Error] Incompatible> [latest-23242]2023-09-09T02:03:13.852Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-] Error: Incompatible serialization data; can't unserialize at System.unserialize (/home/wilson/reactor/server/lib/Entity.js:624:19) at /home/wilson/reactor/server/lib/Controller.js:458:70 at Array.forEach (<anonymous>) at OWMWeatherController._restoreEntities (/home/wilson/reactor/server/lib/Controller.js:446:36) at new Controller (/home/wilson/reactor/server/lib/Controller.js:37:45) at new OWMWeatherController (/home/wilson/reactor/server/lib/OWMWeatherController.js:327:9) at /home/wilson/reactor/server/lib/Controller.js:93:37 [latest-23242]2023-09-09T02:03:13.853Z <Structure:INFO> Structure#1 loading controller interface nut (NUTController) [latest-23242]2023-09-09T02:03:13.855Z <NUTController:null> Module NUTController v22305 [latest-23242]2023-09-09T02:03:13.855Z <Controller:INFO> Loaded NUTController version "0.1.22305"; Patrick Rigney/Kedron Holdings LLC <patrick@> [latest-23242]2023-09-09T02:03:13.857Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [And finally, I have a second house, with the same OWM configuration I made today, and it doesn't show any errors.
Please, your traditional help.
Thanks.
After a prolonged power cut, the UPS was unable to cope with the weather and shut down the entire system.
When I returned, I had the problem that the host time displayed in the browser and automatically used in the rules was not correct.
I searched for a topic here on this forum that talked about it, but it referred to a container installation. There was a recommendation to go into the storage/states directory and delete the files and restart MSR, I did it and it didn't solve the problem.
There was also a recommendation to go directly to the browser to check the time, and I did so and I see that the time is correct.
8ad429c8-ea5f-45b4-8670-7d0353a50a0e-image.png
As you can see on the screen above:
MSR browser shows the correct browser time 21:23, but host time 13:02; In the browser below the direct query and the host time is correct 9:22:54 PM; Setting the VM date command on the third screen, the time is 9:23:00 PM.I've opened the entire reactor.log file and searched for any errors, and there aren't any.
^L [latest-23242]2023-09-15T02:11:12.928Z <app:null> Reactor build latest-23242-5ee8e1d4 starting on v18.12.0 [latest-23242]2023-09-15T02:11:12.929Z <app:null> Process ID 1807 user/group 1000/1000; bare-metal; platform linux/x64 #179-Ubuntu SMP Mo> [latest-23242]2023-09-15T02:11:12.929Z <app:null> Basedir /home/leonardo/reactor; data in /home/leonardo/reactor/storage [latest-23242]2023-09-15T02:11:12.929Z <app:null> NODE_PATH=/home/leonardo/reactor [latest-23242]2023-09-15T02:11:12.933Z <app:INFO> Configured locale (undefined); selected locale(s) en_US.UTF-8 [latest-23242]2023-09-15T02:11:12.955Z <app:INFO> Loaded locale en-US for en-US [latest-23242]2023-09-15T02:11:12.958Z <Structure:null> Module Structure v23172 [latest-23242]2023-09-15T02:11:12.959Z <Capabilities:null> Module Capabilities v22356 [latest-23242]2023-09-15T02:11:12.969Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 23914 revisi> [latest-23242]2023-09-15T02:11:12.978Z <Plugin:null> Module Plugin v22300 [latest-23242]2023-09-15T02:11:12.981Z <TimerBroker:null> Module TimerBroker v22283 [latest-23242]2023-09-15T02:11:12.983Z <Entity:null> Module Entity v22353 [latest-23242]2023-09-15T02:11:12.986Z <Controller:null> Module Controller v23069 [latest-23242]2023-09-15T02:11:12.992Z <default:null> Module Ruleset v22293 [latest-23242]2023-09-15T02:11:12.992Z <default:null> Module Rulesets v22146 [latest-23242]2023-09-15T02:11:12.996Z <GlobalExpression:null> Module GlobalExpression v23211 [latest-23242]2023-09-15T02:11:13.003Z <Predicate:null> Module Predicate v23093 [latest-23242]2023-09-15T02:11:13.005Z <AlertManager:null> Module AlertManager v22283 [latest-23242]2023-09-15T02:11:13.007Z <Rule:null> Module Rule v23107 [latest-23242]2023-09-15T02:11:13.009Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-23242]2023-09-15T02:11:13.010Z <Engine:null> Module Engine v23231 [latest-23242]2023-09-15T02:11:13.012Z <httpapi:null> Module httpapi v23058 [latest-23242]2023-09-15T02:11:13.019Z <wsapi:null> Module wsapi v23172 [latest-23242]2023-09-15T02:11:13.019Z <app:NOTICE> Starting Structure...As you can see, the time in the log is 02:11, which is correct, because I'm in time zone -5, which means it's 09:11PM for me.
I've restarted the VM, the computer hosting the VM, and the MSR a few times and the same difference remains. What do you recommend for the next step in understanding and solving the problem?
Thanks.
Good afternoon,
I'm running my MSR instance on an old NAS server running Fedora 37 Server. This is an older Core i5-4690K server that has served me well overall, but it's showing it's age, and will often reboot into maint mode if it applies updates overnight. I've been trying to troubleshoot, but it's also in my office (makes my office hot), and I'm looking at getting either a QNAP or Syslogy rack mount NAS to replace it.
What I'm wondering is what the process would be to migrate my current MSR config and move it to a different platform. I have quite a large ruleset that I don't want to have to recreate. I know I can run it in a container on either platform, but I'm not sure how I would migrate all my rules over. Is there one config file that has all of the rules, or could I simply copy my /reactor directory over to a enw platform?
I am also considering moving the MSR instance to a stand alone RPI 4 with a SSD. This way, while I'm migrating all of my files off of my NAS, I'm not loosing Reactor's functionality until I have whichever rack mount NAS I go with up and running, with all of the data migrated.
Thoughts?
zwaveJS controller question/s
-
The authorization key was from the preview/development cycle, to limit access to just a handful of people that were working closely with me to get the first version going. You can omit it. I'll update the docs.
-
Where are you seeing this, by the way? Specific link/page please.
-
@toggledbits /docs/ZWaveJSController/
-
@toggledbits Unfortunately, this means I have something else afoot. Let the log-diving commence!
-
Did you get it going?
-
@toggledbits I did not yet (silly day job, getting all in the way of the REAL work...)
I did get as far as log-diving:
[latest-22308]2022-11-08T22:06:50.268Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs connecting to ws://192.168.1.198:3000 [latest-22308]2022-11-08T22:06:50.272Z <ZWaveJSController:WARN> ZWaveJSController#zwavejs websocket error during open/negotation: [Error]Error: connect ECONNREFUSED 192.168.1.198:3000 [latest-22308]2022-11-08T22:06:50.273Z <ZWaveJSController:WARN> ZWaveJSController#zwavejs ws error code ECONNREFUSED [latest-22308]2022-11-08T22:06:50.274Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs websocket to ws://192.168.1.198:3000 closed during open/negotiation [latest-22308]2022-11-08T22:06:50.275Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs connection to ws://192.168.1.198:3000 failed; will retry [latest-22308]2022-11-08T22:06:50.276Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs retry 912 delay 120000
My initial thought is something is competing for that port - but, again, that's with little to no research beyond pulling the logs.
-
How are you running ZWave JS UI? (how is it installed, started, etc.?)
-
@toggledbits Using the Home Assistant add-on.
-
@toggledbits It is.
EDIT: I even cleared the 0.0.0.0 from the
Server Host
field just in case it was causing something wonky. -
0.0.0.0 is another way of saying "any address", so that's OK. Looks like HassOS, then?
-
@toggledbits Yessir on both points.
-
It's the devil.
Try this: https://github.com/home-assistant/core/issues/63670#issuecomment-1008624418
-
@toggledbits So this is interesting (to me)...
This isn't running. Should it be? In my initial install of Z-Wave JS UI it seemed to point toward that NOT running, it was handling everything and that just needed to be installed (which it prompted for IIRC.) I do have three devices on and running.
EDIT: started Z-Wave JS, third tab
Configuration
and added this:Z-Wave JS keeps stopping after I access Z-Wave JS UI which further supports my recollection that they don't both RUN, but both need to COEXIST.
-
I have no idea... you can try it. HassOS is, to me, the devil incarnate, and I don't use it. Others here do, I suspect, and maybe they have some experience to offer. I would take the auto-updates, at least, because HA itself often requires new/latest versions of Z-Wave JS, and everything goes away on that integration when it doesn't get it.
-
Quick question @toggledbits : in looking at my iblinds, I see the ability to call for recalibration. The Hubitat community driver has surfaced this. HASS has not (not a surprise, they're quite conservative in what they surface), MSR's zwaveJS controller does not. Is there a way to do so manually (editing a config, for instance)? These blinds wander over time and a scheduled recalibration is very helpful.
-
I would have to look at the device data for the iBlinds devices you have, but I believe that you can access any feature of any device via ZWaveJSController, it just may not be a declared action on a native Reactor capability (in the same way you can call any service in HassController, even if it's not a declared service on the Reactor entity). We just need to figure out what that mechanism is for the iBlinds devices, and either use it as offered, or decide to bring it forward as a simplified action.
Can you point me to online docs for iBlinds that describe how to start (via Z-Wave) the calibration process?