• Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.

SmartHome Community

[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
G

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-0

Please 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.

Multi-System Reactor
[Solved] OWM error
wmarcolinW

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: false

When 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.

Multi-System Reactor
Host time is wrong
wmarcolinW

@toggledbits

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.

Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT

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.
Multi-System Reactor
Migration question
T

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?

Multi-System Reactor
docker synology import
M

Hello,

I've installed MSR in a Docker container on my Synology NAS. I'm able to access my Vera, but I'm having trouble using the Reactor import within the Docker environment. I'm using the Docker terminal, and I've navigated to "/opt/reactor". However, when I try to run the command, it's telling me I'm not in the installation directory, even though I can see the "tools" directory and the "apps.js" file there. I've also tried changing the file permissions, but nothing seems to work. How do you manage this in a Synology Docker container? Do you use the terminal inside Docker, or SSH into the Synology itself? I'm not finding the "/opt/reactor" path, but I see a "/var/reactor" directory, which I placed in my storage folder.

ERROR: This script must only be run from the Reactor app directory.

Multi-System Reactor
MSR - Bug report
T

@toggledbits

Maybe I'm missing something, but this appears to be a bug.

I'm troubleshooting a rule to see if one of the system participants is arriving (presence changes from not home to home). I want this arriving state to be less than 5 minutes (300 seconds), to differentiate between being home for a longer period of time, and just getting home.

In the restrictions sections of the Trigger, I set "Condition must be sustained for less than 300 seconds", and I save the trigger.

After I save and exit, I'm looking at the rule, and it's changed itself to x_hass.state == home; for at least 300 secs. I go back into edit the rule, and it in fact shows "at least" from the drop down.

This logic is of course failing and I can't seem to get it to work.

Changed to less than, and saved:

10a57ff9-4d8c-46b3-b594-399ef2a6d320-image.png

Exited:

a81587d6-f0fa-4518-ad00-a9f601f14509-image.png

Back in rule:

b8e27dd2-e6e7-4f93-844e-83e2b11e976d-image.png

I'm running latest-23218-ebab7a1b.

Multi-System Reactor
MSR Detecting HA Proximity Entity State as a String
PablaP

I added the Proximity integration to HA to create automations based on if a person is on vacation or not. The integration creates an entity and its x_hass.state is the distance to the zone you have setup in HA. For some reason MSR sees that value as a string so I am not able to use the<, >, etc operators as a trigger. Is there anyway this could be fixed without needing to convert the string in a local expression?

MSR 23218
HA 2023.8.3

Entity Attributes if needed

x_hass.domain="proximity" x_hass.entity_id="proximity.arman_proximity" x_hass.services=["proximity"] x_hass.state="0" x_hass_attr.dir_of_travel="unknown" x_hass_attr.friendly_name="arman_proximity" x_hass_attr.nearest="Arman’s iPhone" x_hass_attr.unit_of_measurement="km"
Multi-System Reactor
MSR SMTP Notifications fail - <wsapi:CRIT> Error: Engine has not been started
B

MSR Version: latest-23218
Running as Docker Container : Docker version 24.0.5, build ced0996
OS: Linux 15BPMSR1 6.1.26-05272-g26c406245a2c #1 SMP PREEMPT_DYNAMIC Thu Apr 27 10:15:40 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

SMTP notifications had been working fine and I am unsure exactly what action(s) stopped it from working.

I have verified that the SMTP server configured in notifications.yml is working properly.

To duplicate the problem I am forcing an SMTP email notification using the set reaction play button, the reactor.log shows the following errors:

[latest-23218]2023-08-21T14:23:22.462Z <wsapi:ERR> [WSAPI]wsapi#1 can't queue reaction rule-lgxmrba4:S: [Error] Engine has not been started [-] [latest-23218]2023-08-21T14:23:22.463Z <wsapi:CRIT> Error: Engine has not been started [-] Error: Engine has not been started at Engine.queueReaction (/opt/reactor/server/lib/Engine.js:1494:46) at WSAPI.clientMessage (/opt/reactor/server/wsapi/wsapi.js:782:64) at WebSocket.<anonymous> (/opt/reactor/server/wsapi/wsapi.js:301:157) at WebSocket.emit (node:events:527:28) at WebSocket.emit (node:domain:475:12) at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1068:20) at Receiver.emit (node:events:527:28) at Receiver.emit (node:domain:475:12) at Receiver.dataMessage (/opt/reactor/node_modules/ws/lib/receiver.js:517:14) at Receiver.getData (/opt/reactor/node_modules/ws/lib/receiver.js:435:17)

I have tried:

OS level: apt udate and apt upgrade and reboot

docker pull toggledbits/reactor:latest-aarch64 latest-aarch64: Pulling from toggledbits/reactor Digest: sha256:d8a019d457c9fef61f7c3e6908db1f1d0a2d14b6f7c5e9d4fc536c791503d152 Status: Image is up to date for toggledbits/reactor:latest-aarch64 docker.io/toggledbits/reactor:latest-aarch64

docker stop reactor
docker start reactor

docker compose down
docker compose up -d

To no avail.

I feel like I'm missing something obvious but can't put my finger on it.

Thank you in advance for any guidance.
-bh

Multi-System Reactor
Long-running task in MSR
therealdbT

I have a rule that's driving my pool heater to match the solar excess. In the previous iteration, I checked for the status every minute, but I wanted something different and smarter. The logic is basically:

run continuously from 9:15 to 18:15 check for conditions, and if there's solar excess, use the power to turn on the heater, then wait 1 minute to check again turn off the heater, then wait 5 minutes to prevent frequent on/off cycles

I thought that this could be very similar to Reactor-Ex machina's logic, so I crafted a rule that's basically doing the same: an infinite loop from 9:15 to 18:15 that's checking for status and has a delay based on the heater's condition.

All went well, but after a couple of hours, I got this:

Reaction task "49683" failed due to an exception. Please see the log. rule-liy7z3gf:S (Pool-Heater-Solar) step 0: Error: Task has run too much! Runaway?

and the rule was reset (and the heater was left on). Is that by design and I should adopt another strategy? What are others doing when they have a state machine?

With the EV charger I did two groups of condition, each triggering every x minutes based on the charger status, but this seems less smarter and very rudimental. Any suggestion is appreciated. Thanks.

Multi-System Reactor
Integrate UPS with MSR
wmarcolinW

I have a Tripp-Lite UPS (https://www.tripplite.com/smartpro-lcd-120v-1500va-900w-line-interactive-ups-avr-tower-lcd-usb-10-outlets~smart1500lcdt) that connected by a USB cable to my computer, reports various power supply and failure information, as shown in the panel below.

b9f0ea34-d654-4b26-b968-4f8cf0a4e0c1-image.png

afa73913-5318-42c6-af9a-02d36e2e6ea1-image.png

The application I installed runs Java and opens the console to send the information.

Has anyone tried to bring the information into the MSR? Or even a VeraPlus?

Thanks.

Multi-System Reactor
pattern match or find expression? I am stuck again
cw-kidC

Hi

I am stuck trying to extract the "SignalLevel" value which is the WIFI Signal Strength off my Foscam via a http request. The request returns this, which isn't Json formatted data I don't think.

<CGI_Result> <result>0</result> <SignalLevel>52</SignalLevel> </CGI_Result>

I created a rule that saves the http response into a Global Expression

872f534e-5899-43e4-ade5-f2b8ab54a412-image.png

But I am struggling to work out what is the correct expression code to extract the value?

Can anyone more knowledgeable please help?

Thank you.

Multi-System Reactor
MSR thinks all my Ezlo Controller devices no longer exist, they do !
cw-kidC

Hi

Today in MSR alerts I see 100 alerts saying that the devices on my Ezlo controllers no longer exist.

They do still exist. I checked some of these devices in the Ezlo Online API Tool doing a hub.devices.list query.

I then checked that the ID numbers were the same for the devices and they are the same device ID's still.

So my devices do still exist with the same device ID's it seems.

So not sure why MSR has over 100 alerts saying otherwise.

9d7c4732-40f3-4551-b8d4-e24e0e8dda10-image.png

I then looked in Entities selected my Ezlo Plus controller and it listed all my devices OK I think and nothing looked out of place.

Thanks

Multi-System Reactor
Is this possible? Store data from Asus Router ajax .asp page for Temperature data.
cw-kidC

I just discovered there is a secret webpage I didn't know about for my Asus Merlin router that when I run it in a browser gives me all the routers current temperatures.

http://192.168.0.1/ajax_coretmp.asp

249c6e47-38ae-4812-b149-da1fd22072cb-image.png

I have to be logged into the router to access it however.

I tried to create an MSR rule with a HTTP request to store all this data in to a local expression.

But it looks like its not passing or accepting the username and password for my router, I tried Basic and Digest.

I just get this back in the local expression in the rule.

(string) "<HTML><HEAD><script>window.top.location.href='/Main_Login.asp';</script>\n</HEAD></HTML>\n"

The data returned in the browser looked like this:

curr_coreTmp_wl0_raw = "43°C"; curr_coreTmp_wl0 = (curr_coreTmp_wl0_raw.indexOf("disabled") > 0 ? 0 : curr_coreTmp_wl0_raw.replace("°C", "")); curr_coreTmp_wl1_raw = "49°C"; curr_coreTmp_wl1 = (curr_coreTmp_wl1_raw.indexOf("disabled") > 0 ? 0 : curr_coreTmp_wl1_raw.replace("°C", "")); curr_coreTmp_wl2_raw = "disabled"; curr_coreTmp_wl2 = (curr_coreTmp_wl2_raw.indexOf("disabled") > 0 ? 0 : curr_coreTmp_wl2_raw.replace("°C", "")); curr_coreTmp_wl3_raw = "disabled"; curr_coreTmp_wl3 = (curr_coreTmp_wl3_raw.indexOf("disabled") > 0 ? 0 : curr_coreTmp_wl3_raw.replace("°C", "")); curr_cpuTemp = "66.495"; fanctrl_info = "";

I know how to do this for webpages and sites that give back JSON data, however this data I am not sure what format it is, Javascript ? The page is a .asp ajax page.

So not sure if this is possible ?

I really wanted to monitor the CPU temps on my router as its been getting very hot, even with extra USB fans now on the back of it. Think its a firmware bug maybe in the Asus firmware as others have been talking about it online.

Thanks.

Multi-System Reactor
Virtual Devices for lamellas in Vera
therealdbT

So, I've just installed two venetian blinds and I want to control their lamellas with Fibaro FGRM222.
According to the old place, this could be accomplished with some Zwave raw messages and I'm OK with it.
Since I've moved (mostly) everything virtual in MSR, I'm now ready to add a virtual device with actions.

Looking at the docs, it seems possible, but it's not documented. @toggledbits any hints? I want to define a cover and send Zwave commands to the existing x_vera_svc_micasaverde_com_ZWaveNetwork1.SendData action. Thanks.

Multi-System Reactor
Feature request: user authentication
T

@toggledbits,
I'm not sure if this is something you've looked into (or something I'm completely missing in the installation documentation), but would it be possible to add user authentication to the MSR frontend? On my Home Assistant instance, I have external access set up using Cloudflare, and I can add other instances within my network to that Cloudflare configuration, but without any sort of authentication to access MSR, I obviously can't open it to the internet, unless I want random people screwing around with my home automation.

Multi-System Reactor
TypeError: Cannot set properties of undefined (setting '__suppress_dependencies') when setting variables
therealdbT

I've just updated to 23218 and now I'm getting this:

27a959bd-486b-41ae-8137-c5f456044a82-image.png

There seems to be related to global variables. The first and last ones are global reactions, while the second is a normal one. All are setting global variables.

Multi-System Reactor
Feature Request: Latest Reactor Version Number Attribute
PablaP

Hey @toggledbits was wondering if we could have the latest reactor version number as an attribute for the Reactor System entity. It would be useful for me so I can use it for my wget command to automatically download the latest .tar.gz file. Ideally the complete version number like this 23171-85463e02.

Multi-System Reactor
Odd behavior in Weekday checkmarks (MSR)
T

@toggledbits ,
I was just taking a look at some of my scheduling to adjust for a new work schedule, and I noticed that the checkboxes for days of the week appear to be off.

75e1b936-1693-4db1-8ed5-ecfae57d3abf-image.png

if you'll notice in the screenshot, Sun - Tuesday are good, but then Sat comes next, then Wed, then Sat again, then Wed again. No TGIF in this week.

I know this isn't how I set up the rules (which would explain the behavior I was investigating).

Edit: BTW, I checked all my Week Day entries, and they are all like this.

I'm running latest-23196-40ef07f4 on Fedora 37 Server w/o Docker.

Multi-System Reactor

Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

Latest version is installed, we are still working on some visual changes.

[SOLVED] Rethinking HVAC moving from Reactor (Vera) to MSR

Scheduled Pinned Locked Moved Multi-System Reactor
18 Posts 2 Posters 305 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #1

    In my Vera config I have two SiteSensors (one for Ambient Wx, one for OpenWxMap) that point to two unique Reactor devices for controlling HVAC in my home. This is done for redundancy - if the Ambient API drops it returns zero data which then triggers a standalone Master API Reactor device to flip on the OWM SiteSensor and corresponding HVAC Reactor device to continue controlling the house conditions.

    Once the Ambient API returns to available the Master API Reactor device flips back to the Ambient SiteSensor and corresponding HVAC Reactor device, turning OFF the SiteSensor for OWM to save on API calls.

    I've been able to duplicate one half of this, including the Master API role, in MSR. But... here's the tricky part... I can't turn "off" the MSR Rule Sets for the OWM version. As such, HVAC is sent conflicting data and doesn't know what to do.

    Before I go alls deep into explaining how all of this currently works, am I missing something somewhere that would allow me to trigger the on/off of MSR Rule Sets?

    Solved here: https://smarthome.community/post/10329

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    0
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by
    #2

    The simplest possible suggestion I can come up with involves creating a go/no-go variable within each Rule you'd like to control in that fashion. By creating an empty expression (let's call it "Go") in Rule A, for example, you could add a Constraint in Rule A:

    [Expression Value] [ Go ] == 1
    

    You could then, in Rule B, use a [Set Variable] [ Go ] = 1 (yes, MSR rules can now see each other's settable variables!) when you want Rule A active, and = 0 when you want Rule A deactivated.

    Did I come close to answering your question?

    1 Reply Last reply
    0
  • G Offline
    G Offline
    gwp1
    wrote on last edited by
    #3

    I'm... not sure lol I'm not savvy in proper use of expressions so there needs to be more meat added to this bone for me to fully grasp it, I'm afraid.

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    0
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by LibraSun
    #4

    Give it time, as there is a shallow-but-nonzero learning curve moving from Reactor over to MSR. Let's keep this conversation going until you have things working according to plan. Don't hesitate to post screenshots of your work for us to review.

    My suggestion is to start with "Test Rules" that you build for no particular purpose (certainly not for daily driving of Vera devices!), just to kick the tires with. This is a good way to get a grasp of how Expressions work in particular. I probably create and destroy 3-4 throwaway Test Rules every day, just workshopping different approaches to problems similar to yours.

    G 1 Reply Last reply
    0
  • G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #5

    Oh I have made very liberal use of Test rules, believe me lol It's been very helpful. I'll try to pull together some screenshots here shortly. As to Reactor>MSR, yes, there's a slight curve. I've been able to pare down my Reactor device designs considerably using MSR.

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    1
  • G Offline
    G Offline
    gwp1
    replied to LibraSun on last edited by
    #6

    @librasun b0331912-b953-4db5-a38d-7b09c5d49736-image.png

    This is the high-level architecture. Three arming rules, then the appropriate on/off rules that trigger when the arming criteria are met.

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    1
  • G Offline
    G Offline
    gwp1
    wrote on last edited by
    #7

    Continuing, there were two SiteSensors in Vera - I've moved the Ambient API one to MSR as noted above with the high-level.

    In Vera, it's easy to turn on and off the SiteSensor for OpenWxMap to reduce API calls based on query results from the Ambient API SiteSensor. There's a ruleset moved into MSR that drives the failover/back.

    642f8c3b-3d19-4bd1-8527-a25ea452cc8f-image.png

    74a35033-5029-4046-bba4-9cb1cc99231d-image.png

    In MSR, however, I cannot turn off the OWM ruleset when Ambient API is driving. The result becomes two sets of data being sent to the t-stats which annoys them.

    Currently, I'm using the SiteSensor for OWM in Vera and the ruleset in MSR for Master failover/back and driving Ambient data to the t-stats.

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    0
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by LibraSun
    #8

    Remember, it's entirely plausible to introduce an expressionless (empty) "Go" variable within any Rule, such that the Rule A "runs" (acts Enabled) with "Go" set to "1", and is barred from running (acting Disabled) with it set to "0".

    To make this setup work, simply have your other Rule B's Set Reaction do a [ Set Expression ] [ = ] [ 0 ] on Rule A's variable "Go", with a [ Set Expression ] [ = ] [ 1 ] in its Reset Reaction. Create a corresponding Trigger condition in Rule A that tests [ Expression Value ] [ == ] [ 1 ], and you should be good to go.

    Does that make sense? Hope it helps!

    NOTE: You can also use true / false values for Go and make your Rule A's Trigger condition check for [isTrue] instead.

    G 1 Reply Last reply
    0
  • G Offline
    G Offline
    gwp1
    replied to LibraSun on last edited by
    #9

    @librasun Wait, what? Slow pitch this - I've never played with the expressions before.

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    0
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by
    #10

    Before I do (let's save Expressions for very last...), please explain how MSR could "know" which version of the weather sensor you want enabled?? I'll go re-read your posts from the past 24 hours to see if I can ascertain same.

    1 Reply Last reply
    0
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by LibraSun
    #11

    For instance, I heard you say, "I cannot turn off the OWM ruleset (in MSR) when Ambient API is driving". Couldn't its governing Rule just have an extra Constraint condition like:

    [ Entity Attribute ] [ SiteSensor_156 ] [ x_vera_device.failed ] [ isTRUE ]
    

    so that it refrains from execution while Ambient is in good health?

    1 Reply Last reply
    0
  • G Offline
    G Offline
    gwp1
    wrote on last edited by
    #12

    Fair enough on the explanation - I prob made that typical error of not providing the details that I "just know" in my head. 🙂

    Original Vera setup: two SiteSensors, one for Ambient API, one for OWM API. Ambient is hyper-local (my wx station) and is the daily driver. To save API calls against OWM, the SiteSensor there is set to disabled status normally.

    If Ambient API call returns zero results, the Master API ruleset sees the failure, changes OWM API SiteSensor to enabled. As the query results from Ambient are blank, it is left in enabled status - and there's only one set of data points going to the t-stats.

    Once Ambient API call returns regular results again, the Master API ruleset sees the actual data and changes OWM API SiteSensor to disabled again and life is, once again, good for all.

    Can you define for me "refrains from execution"... are you saying it would not send anything to the t-stats or query the API (or both)?

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    0
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by
    #13

    From all I see (I just stopped short of saying it explicitly earlier), you're asking, "How can I temporarily stop MSR from sending API requests to OWM?" I don't see an immediate way to set that mechanism's sys_system.state= to false, although that was my initial thought.

    I think we'll have to ask @toggledbits to advise on best practices here.

    G 2 Replies Last reply
    0
  • G Offline
    G Offline
    gwp1
    replied to LibraSun on last edited by
    #14

    @librasun I poked at this a bit with what I thought you were getting at. The configuration now (which is a carry-over from Vera Reactor and could prob use some trimming) has the top three rulesets (shown earlier) use to arm the system, ie set the parameters for what qualifies as "I should heat now" or "I should cool now" - and then the five rulesets below are the actual action rules.

    For instance, if the system "qualifies" for (or is armed) for Cooling then only the two rulesets for Cooling are actionable. Same applies for Heating.

    Taking what you said earlier, I added a condition to each of the action rulesets as shown in this example:

    85aed027-5c32-4d64-a0b9-2168f1f7073b-image.png

    I was missing the reality of the action rulesets still running even though none of the qualifiers/armers were, well, armed. The action rulesets were using the last known datapoints stored in the armers - and that's where things were going amiss.

    By adding the extra condition to each action ruleset it seems to have quieted - this may be the solution (not pretty, but a solution.)

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    1
  • G Offline
    G Offline
    gwp1
    replied to LibraSun on last edited by gwp1
    #15

    @librasun The arming rules look like this:

    0e070e1a-1afe-4a22-a702-528632d0deba-image.png

    In my mind, all of these conditions were rolling down to the action rulesets - which is not true.

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    0
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by
    #16

    I'm liking what I see. We both know there are always 1000 avenues to "the right answer" but what you've just presented seems reasonable and suited to your original goal(s).

    G 2 Replies Last reply
    0
  • G Offline
    G Offline
    gwp1
    replied to LibraSun on last edited by
    #17

    @librasun Thanks, and totally agree.

    My goal is always to keep things as uncomplicated as possible as changes or tweaks later get crazy if you have to edit in multiple places. You ALWAYS miss something somewhere and lose countless hours trying to troubleshoot.

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    1
  • G Offline
    G Offline
    gwp1
    replied to LibraSun on last edited by
    #18

    As I'm marking this as [SOLVED] I thought I'd update on how this all ended up playing out:

    Creation of two API rulesets, one for Ambient, one for OWM, that dump their data into Global Expressions. At issue was how to disable OWM to prevent needless API calls - I ended up doing the maths and making adjustments that this isn't an issue any longer. As such, one API ruleset for each dumping to clearly labeled Global Expressions. Yes, they both call out to their respective APIs but the volume is low enough not to trigger either for overuse.

    The only gotcha here is to make sure that you include in the rulesets for the secondary (OWM) a Trigger that checks for the primary API to be returning null so you don't have both flavors of rulesets competing for Honeywell's API (which is notoriously cranky) as you set the t-stats.

    Hubitat C-7 2.3.6.136
    Home Assistant 2023.9.3 running ZST10-700 fw 7.18.3
    MSR on RPi4 bare metal Model B 2GBs, SSD
    MSR latest-23242-5ee8e1d4
    MQTTController-23254
    ZWave Controller-23254

    1 Reply Last reply
    0
  • toggledbitsT toggledbits locked this topic on

Recent Topics

  • CatmanV2C
    Migration to Virtualisation
  • G
    [SOLVED] New iblind and zwaveJScontroller/MSR not communicating
  • PerHP
    Nuke Vera Script
  • akbooerA
    Truncated web pages using wireguard over long distances
  • wmarcolinW
    [Solved] OWM error
  • wmarcolinW
    Host time is wrong
  • R
    Beginner assistance
  • DesTD
    RulesEngine
  • therealdbT
    Replacing Nest Thermostat but....
  • H
    Connect small (torch-sized) light bulb to smart home network
Powered by NodeBB | Contributors
Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
  • Login

  • Don't have an account? Register

  • Login or register to search.