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

Adding remotes, scene controllers as entities to MSR

Scheduled Pinned Locked Moved Multi-System Reactor
31 Posts 4 Posters 780 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.
  • A Offline
    A Offline
    Andr
    wrote on last edited by Andr
    #1

    EDIT: 2022.07.01

    So I will try to remake this thread to some kind of guide for future use, or in worst case a documentation of my failure. At least that could also be useful for letting someone know what didn't work...
    I have zero knowledge of programming, so every time I need to edit a config file in HomeAssistant or similar it requires a good portion of googletime and read, re-reading instructions.
    Also is english not my native language, so bear with me.

    Two goals!
    1: Get MSR to take notice (and then actions of course) of pressed buttons on remotes.
    2: Document what I do in hope I can help someone else in the future.

    I will use a Fibaro Keyfob as described below, but what I understand from Togglebits answers most type of remotes should work in similar ways.

    Original thread:
    Fibaro Keyfob support in MSR? (thru Hassio & Z-wave JS)
    Hi-|

    I just bought a Fibaro Keyfob FGKF-601 and plan to give this to my son so he can control some stuff in his own room. Primary some lightning and Sonos, maybe blinds in the future.-|

    As the noob I am it will, of course, not work as I expected.👶🏻-|

    The remote handle 1x, 2x, 3x clicks per button (six of them) and "release button"
    I thought that it would appear like some "scene controller" in HA and that I could make Rules in MSR depending on what scene-entety that was triggered.
    So is not the case, and if that is because of HA, Z-wave JS or MSR I have no idea.
    I found a HA Blueprint that works in HA, but of course I would prefer to keep all automation in MSR.
    I guess a workaround could be using HA virtual switches "Helpers" that I suppose will come up as an on/off trigger in MSR, but before going this way I would like to check with the wisdom of your guys if there is a better way of doing this.-|

    I am using:
    MSR 22168 on windows.
    Home Assistant Core 2022.6.7
    Home Assistant Supervisor 2022.05.3
    Home Assistant OS 7.6
    Z-Wave JS version: 0.1.64-|

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #2

    OK. We're going to have to rush to look at this, as I'm going on a long vacation in a couple of days.

    Go ahead and open a PR in Mantis, and with it post your hass_states.json file (in logs) as an attachment (do not copy-paste the text of it). I also need the entity IDs (Home Assistant's) for the device in question.

    In addition, you haven't "shown the work" as is required for posts here. I need you to show the entities (Entities page, attributes open) that MSR has produced for its version of Home Assistant's entities, as well as any and all rules you've created to try to use them (Rule Status views, not Rule Editor editor). You can also attach all of that to the PR. The guidelines and recommendations for posts are in a pinned topic in this category.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    A 1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    replied to toggledbits on last edited by
    #3

    @toggledbits

    Reported in Mantis now.
    Have a great vacation 🙂

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #4

    Re: PR 0000326:

    The way Home Assistant handles keyfobs is unlike the old Vera model you are used to. There is by default no "device" with variables indicating the state of the buttons. Home Assistant sends events when the buttons are pressed, but it doesn't set values on entities.

    In order to use these devices, you need to follow the configuration instructions here: https://reactor.toggledbits.com/docs/HassController/#handling-home-assistant-events

    What you will be doing is effectively telling HassController to create and maintain a virtual (Reactor) entity to track button state, and use the events sent by Home Assistant to map to state values on that entity. Since Reactor cannot know in advance what events are sent, there is no way for it to automatically "guess" these entities and create them; you've got to do the work. You will be editing/extending the configuration for your HassController in reactor.yaml.

    To help you find the events you need to build config for, add log_events: true to the config: section for your HassController and restart. Then play with your buttons, and observe what is logged to logs/hass_events.log. There will probably be a lot of data, so don't leave this setting on for too long, just for your research. Once you've identified the events sent by the device, you can build the configuration for the event_targets subsection as described in the linked docs.

    Let's keep the conversation here, instead of on the PR, as it's not looking like a bug or device support request at the moment, and the process of getting the config right will probably require some back and forth that would be educational for all to have documented here.

    Here's an example I use for testing... I have an Amcrest camera supported by Hass that sends events when it detects audio (and motion, etc., but this is just audio to keep it simple):

    It logs this event when audio is first detected:

    2022-06-28T16:29:23.885Z amcrest {"id":1656433623424,"type":"event","event":{"event_type":"amcrest","data":{"camera":"Cam2","event":"AudioMutation","payload":{"Code":"AudioMutation","action":"Start","index":"0"}},"origin":"LOCAL","time_fired":"2022-06-28T16:29:23.879133+00:00","context":{"id":"01G6NJASH7Y06R2AM49E7MF5YK","parent_id":null,"user_id":null}}}
    

    ...and this event when audio is no longer detected:

    2022-06-28T16:29:28.301Z amcrest {"id":1656433623424,"type":"event","event":{"event_type":"amcrest","data":{"camera":"Cam2","event":"AudioMutation","payload":{"Code":"AudioMutation","action":"Stop","index":"0"}},"origin":"LOCAL","time_fired":"2022-06-28T16:29:28.294575+00:00","context":{"id":"01G6NJAXV6AJAXPDAX93SJ8ZKT","parent_id":null,"user_id":null}}}
    

    For your review, I would copy-paste your logged data into jsonlint.com to format it and make it more readable. Here's the Start event, reformatted:

    {
    	"id": 1656433623424,
    	"type": "event",
    	"event": {
    		"event_type": "amcrest",
    		"data": {
    			"camera": "Cam2",
    			"event": "AudioMutation",
    			"payload": {
    				"Code": "AudioMutation",
    				"action": "Start",
    				"index": "0"
    			}
    		},
    		"origin": "LOCAL",
    		"time_fired": "2022-06-28T16:29:23.879133+00:00",
    		"context": {
    			"id": "01G6NJASH7Y06R2AM49E7MF5YK",
    			"parent_id": null,
    			"user_id": null
    		}
    	}
    }
    

    The event section the part to focus on, and everything in the config is relative to it. From this, I built this config to drive a binary sensor that's true when my Amcrest camera detects sound:

    controllers:
      - id: hass
        enabled: true
        implementation: HassController
        name: Hass System
        config:
          source: 'ws://192.168.0.10:8123'
          access_token: "X.X.X"
          log_events: true
          event_targets:
            "cam2_audio":
              capabilities: ['binary_sensor']
              primary_attribute: binary_sensor.state
              events:
                - event:
                    event_type: amcrest
                    data:
                      camera: "Cam2"
                      event: "AudioMutation"
                  response:
                    "binary_sensor.state":
                      from: "event.data.payload.action"
                      map:
                        Start: true
                        Stop: false
    

    A quick tour of that: you're telling HassController to build an entity with ID cam2_audio that has (only) binary_sensor capability, and binary_sensor.state as its primary attribute. From there, it looks for just one event: something with an event_type of amcrest, and data.camera equal to Cam2, and data.event equal to AudioMutation. That's what the events: section is describing. The response section that follows tells HassController what to do when it finds a matching event: set binary_sensor.state on the entity using the value of event.data.payload.action, and mapping the word Start to boolean true, and Stop to boolean false.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    wrote on last edited by
    #5

    So, first steps taken - Logging events from HomeAssistant.

    First enable logging by adding marked line in reactor\config\reactor.yaml
    78392197-2613-4579-b354-99083d01ab73-image.png And of course edit false to TRUE when for logging to start, I am done with that part now 🙂

    A little tip.
    I had my file explorer in reactor\logs folder
    So to don't get to much data in the hass_events.log i made a copy of the file as soon I had send the different commands for one of the buttons.
    So now i have one log file for everyone of my six buttons, and every button handle 1x, 2x, 3x click + hold so it feels some what readable.

    1 Reply Last reply
    1
  • A Offline
    A Offline
    Andr
    wrote on last edited by
    #6

    I am reading about MSR abilities, and wonder which one is best in my scenario.

    Standard Capabilities - Reactor - Multi-Hub Automation

    I am thinking about "button" as it should be only one entity for each button on the remote, if I have got it right?

    Any thoughts?

    button

    Used when the device implements the behavior of a pressable button.

    Attributes:

    state — (string) last button state: single (pressed once), double (double-press), triple (triple-press), 4 (four-press), 5 (five-press), hold, release, long, unknown. Not all Controller instances will (or are required to) implement all values; this is dependent on the capabilities of the underlying hub and the device itself.
    
    toggledbitsT 1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    replied to Andr on last edited by
    #7

    @andr great choice!

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    wrote on last edited by Andr
    #8

    ===group

    ===So, a little report of a night of testing what does not work.

    Read @toggledbits tips above together with the manual about Capabilites and put this in my reactor.yaml:

        config:
          source: ':-D'
          access_token: ':-)'
          log_events: false
              # Additions to config section for Lukas Fibaro Keyfob:
          event_targets:    # this section starts the event-receiving entities
            "Keyfob_fyrkant":      # Assign an ID to your entity; each entity must have a unique ID
              name: Lukas Keyfob Fyrkant   # This is optional but recommended, so you have a friendly name
              capabilities: ['button'] # define an array of capabilities to be modified by the event 
               attributes:
                 state:
                   type: string
                   values:
                     - 'single'
                     - 'double'
                     - 'triple'
                     - 'hold'
                     - 'release'
                 since:
                   type: int, timestamp
              events:  # define an array of events that modify capability attributes on the entity
              - event:  # start of an event; each element of the events array begins this way
                  event_type: zwave_js_value_notification
                  data:  # optional section, if further matching to the event data is required
                    property: "Scene 001" # Square button
                    value: "KeyPressed"   # Square button event
                response:  # begin the (required) response section for handling the event
                  "button.state":  # an attribute that the event modifies.
                    expr: "single"   # expression to get attribute value from event data
                    from: "event.data.property.value"  # dot-reference expression to pull value from event message
                    map:                    # optional, map to modify value
                      string: 'single'   # if value is value_in, it is mapped to new_value 
                  # repeat "capability.attribute" section for all attributes modified by the event
          #    - event:  # start of next event for this entity, same form as above
    

    This did not work at all, Reactor would not even start 😲
    Tinkered with a bit, but no luck.
    Anyone see if it is something simple to fix or is this beyond saving?

    Testing something simpler, just to see that I can create some kind of Hass Entity, I copied @toggledbits motion_sensor example above and made some adjustments.

          event_targets:
            "knapp_fyrkant":
              capabilities: ['binary_sensor']
              primary_attribute: binary_sensor.state
              events:
                - event:
                    event_type: zwave_js_value_notification
                    data:
                      property: "Scene 001"
                      value: "KeyPressed"
                  response:
                    "binary_sensor.state":
                      from: "event.data.property.value"
                      map:
                        KeyPressed: true
    

    A tiny, little bit, closer... Reactor starts again and I got myself a fresh new binary sensor "knapp_fyrkant"
    But I am guessing something is wrong in data and/or response section because the "sensor" doesn't changes to true.

    I dont think I really follow how event data and response from relate. I need to sleep on this

    bf818829-c121-4d92-9e22-c2feed752ccd-image.png

    from: "event.data.payload.action"
    

    Here is info from hass event log, for pressing the Square button 1x and 2x.

    2022 - 06 - 29 T21: 15: 44.500 Z zwave_js_value_notification {
    	"id": 1656536987817,
    	"type": "event",
    	"event": {
    		"event_type": "zwave_js_value_notification",
    		"data": {
    			"domain": "zwave_js",
    			"node_id": 15,
    			"home_id": 3523230191,
    			"endpoint": 0,
    			"device_id": "4cfedde34f701262785f27ac571a7f80",
    			"command_class": 91,
    			"command_class_name": "Central Scene",
    			"label": "Scene 001",
    			"property": "scene",
    			"property_name": "scene",
    			"property_key": "001",
    			"property_key_name": "001",
    			"value": "KeyPressed",
    			"value_raw": 0
    		},
    		"origin": "LOCAL",
    		"time_fired": "2022-06-29T21:15:43.082064+00:00",
    		"context": {
    			"id": "01G6RN3S3ASSBZ33RYPHND6QG8",
    			"parent_id": null,
    			"user_id": null
    		}
    	}
    }
    2022 - 06 - 29 T21: 15: 50.890 Z zwave_js_value_notification {
    	"id": 1656536987817,
    	"type": "event",
    	"event": {
    		"event_type": "zwave_js_value_notification",
    		"data": {
    			"domain": "zwave_js",
    			"node_id": 15,
    			"home_id": 3523230191,
    			"endpoint": 0,
    			"device_id": "4cfedde34f701262785f27ac571a7f80",
    			"command_class": 91,
    			"command_class_name": "Central Scene",
    			"label": "Scene 001",
    			"property": "scene",
    			"property_name": "scene",
    			"property_key": "001",
    			"property_key_name": "001",
    			"value": "KeyPressed2x",
    			"value_raw": 3
    		},
    		"origin": "LOCAL",
    		"time_fired": "2022-06-29T21:15:49.475286+00:00",
    		"context": {
    			"id": "01G6RN3ZB3BYRPDZMM9S6CMRZB",
    			"parent_id": null,
    			"user_id": null
    		}
    	}
    }
    

    Just noticed that I have mixed up "property" with "label" so I think I start there tomorrow.
    Good night!

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #9

    This did not work at all, Reactor would not even start

    Not surprised it wouldn't start... it's not properly formatted. Two errors: the attributes line is incorrectly indented (and therefore so is everything underneath it). Second issue, it shouldn't even be there. If it was properly indented, it would be ignored, because the code isn't looking for it. The definition of the button capability is already determined by system files; you don't need to repeat it here.

    As for the rest of it, the - event is also not properly indented, although this may not make it choke.

    Your property value in the event section won't match anything. That value doesn't appear in the example data you posted. It does match label, however, but I don't recommend using that. Change the property value to scene and add property_key with value 001. You probably also want to match the specific device, so that if you have more than one of these, these rules apply only to this one; do this by matching node_id.

    Your response has a few issues. Traversing your sample data, the action field is event.data.value not event.data.property.value. The expr line shouldn't be there, since you're using map to remap the string values grabbed by from. The word string in the map data should be the word KeyPressed (an actual string you are looking for) with the value single (the string you want it to be, which matches the definition of the button.state attribute). If there are other possible strings that map to double, triple, hold and release, those should be added to the map; since you show in your sample data a 2x press, I added that (see below).

    Then, to make sure button.since is correctly updated (modified for each event), you need to specify it as an attribute to be updated as part of the event response, and in this case we will use an expression to set it to the current time.

    Correcting all that, I give you this:

          event_targets:    # this section starts the event-receiving entities
            "Keyfob_fyrkant":      # Assign an ID to your entity; each entity must have a unique ID
              name: Lukas Keyfob Fyrkant   # This is optional but recommended, so you have a friendly name
              capabilities: ['button']  # define an array of capabilities to be modified by the event 
              events:  # define an array of events that modify capability attributes on the entity
                - event:  # start of an event; each element of the events array begins this way
                    event_type: zwave_js_value_notification
                    data:  # optional section, if further matching to the event data is required
                      node_id: 15
                      property: "scene" # Square button
                      property_key: "001"
                  response:  # begin the (required) response section for handling the event
                    "button.state":  # an attribute that the event modifies.
                      from: "event.data.value"  # dot-reference expression to pull value from event message
                      map:                    # optional, map to modify value
                        KeyPressed: 'single'   # if value is value_in, it is mapped to new_value
                        KeyPressed2x: 'double'
                      map_unmatched: 'unknown'
                    "button.since":
                      expr: "time()"
    

    I highly recommend using a syntax-highlighting YAML editor. Check out https://onlineyamltools.com/edit-yaml

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    A 1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    replied to toggledbits on last edited by Andr
    #10

    Many thanks!
    will be digging in to this later tonight again.

    A few follow up questions to check that I understand things correctly.

    capabilities: ['button']
    

    In frase above, somewhere in MSR code, the word 'button' is equal to what I tried to specify with this section and that why that was unnecessary?
    ```
    attributes:

             state:
    
               type: string
    
               values:
    
                 - 'single'
    
                 - 'double'
    
                 - 'triple'
    
                 - 'hold'
    
                 - 'release'
    
             since:
    
               type: int, timestamp
    
    
    About how to fill the 'form' row, in your example you use
    

    from: "event.data.payload.action"

    
    And I assume that this comes from this marked words? 
    ![b80fc4eb-315e-4ba0-af3b-ffe5f470ebc6-image.png](/assets/uploads/files/1656701263037-b80fc4eb-315e-4ba0-af3b-ffe5f470ebc6-image.png) 
    
    I starting to think that yaml file should be read somewhat like a folder tree, would that make sense?
    So, in your example, if the 'start action' was like a .bat-file the way to think about the Form row the adress would be **event\data\payload\action**
    Please say I am on the right track 😂🙏
    1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    wrote on last edited by
    #11

    Sorry for the messy post above, writing from my phone 😳

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #12

    Yeah, you need to fix it. It should not be left like this, as the discussion may be read by others in future, and I can't follow it (also on my phone), and likely nobody would bother

    From what I can see, I don't know why you're stuck on using payload in your from value, that word/key does not appear in your event data.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    wrote on last edited by Andr
    #13

    Ok, for some reason i can't make the mess go away in earlier post, so double post...

    Many thanks!
    will be digging in to this later tonight again.

    A few follow up questions to check that I understand things correctly.

    capabilities: ['button']
    

    In frase above, somewhere in MSR code, the word 'button' is equal to what I tried to specify with this section and that why that was unnecessary?

    attributes:
    
                state:
    
                  type: string
    
                  values:
    
                    - 'single'
    
                    - 'double'
    
                    - 'triple'
    
                    - 'hold'
    
                    - 'release'
    
                since:
    
                  type: int, timestamp
    

    About how to fill the 'form' row, in your example you use

    from: "event.data.payload.action"
    

    And I assume that this comes from this marked words?

    907c3188-47d3-4cac-9e5e-d9660a3eedae-image.png

    I starting to think that yaml file should be read somewhat like a folder tree, would that make sense?
    So, in your example, if the 'start action' was like a .bat-file the way to think about the Form row the adress would be event\data\payload\action
    Please say I am on the right track 😂🙏

    1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    wrote on last edited by
    #14

    Ok, some progress thanks to @toggledbits of course.

    Copied in his code in reactor.yaml and that worked fine of course. Also added a line for 3x click and that worked also.

    event_targets:    # this section starts the event-receiving entities
            "Keyfob_fyrkant":      # Assign an ID to your entity; each entity must have a unique ID
              name: Lukas Keyfob Fyrkant   # This is optional but recommended, so you have a friendly name
              capabilities: ['button']  # define an array of capabilities to be modified by the event 
              events:  # define an array of events that modify capability attributes on the entity
                - event:  # start of an event; each element of the events array begins this way
                    event_type: zwave_js_value_notification
                    data:  # optional section, if further matching to the event data is required
                      node_id: 15
                      property: "scene" # Square button
                      property_key: "001"
                  response:  # begin the (required) response section for handling the event
                    "button.state":  # an attribute that the event modifies.
                      from: "event.data.value"  # dot-reference expression to pull value from event message
                      map:                    # optional, map to modify value
                        KeyPressed: 'single'   # if value is value_in, it is mapped to new_value
                        KeyPressed2x: 'double'
                        KeyPressed3x: 'tripple'
    

    But, still, I can't for some reason really understand the code and how different parts relate to each other.😖

    In 'event data' I was expecting to fill out in the 'label' field from hass_event log because that is an uniq value for each one of the six buttons, and then the 'value' field that identifies the number of keypresses on this specific button.
    In my mind that would give a uniq combination for MSR to identify.
    I did (with very low hopes) tried it also

    event_targets:    # this section starts the event-receiving entities
            "Keyfob_fyrkant":      # Assign an ID to your entity; each entity must have a unique ID
              name: Lukas Keyfob Fyrkant   # This is optional but recommended, so you have a friendly name
              capabilities: ['button']  # define an array of capabilities to be modified by the event 
              events:  # define an array of events that modify capability attributes on the entity
                - event:  # start of an event; each element of the events array begins this way
                    event_type: zwave_js_value_notification
                    data:  # optional section, if further matching to the event data is required
                      node_id: 15
                      label: "Scene 001" # Square button
                      value: "KeyPressed"
                      value: "KeyPressed2x"
                      value: "KeyPressed3x"
                  response:  # begin the (required) response section for handling the event
                    "button.state":  # an attribute that the event modifies.
                      from: "event.data.value"  # dot-reference expression to pull value from event message
                      map:                    # optional, map to modify value
                        KeyPressed: 'single'   # if value is value_in, it is mapped to new_value
                        KeyPressed2x: 'double'
                        KeyPressed3x: 'tripple'
    

    and of course: 💩 💩 💩
    Reactor did not start.

    I would really like to get a grip why this is what is needed in event data

                      property: "scene" # Square button
                      property_key: "001"
    

    Meanwhile, as @toggledbits code of course worked I did the simplest rule with an action, toggle a lamp on off.

    7e171983-e3cc-4c2f-825b-62db8219b87e-image.png

    Here I expected (or hoped) to find triggers for every combination of button presses.
    For now Square: 1x, 2x, 3x
    But I guess I need to set the 'button.state' to 'contains' 'single' 'double' etc.
    But whatever event state MSR caught, it doesn't resest.
    When MSR start the value is NULL, but after a click it holds that value, for example 'single', and I expect it to reset immediately after the 'single' event have passed by.

    So, this is it for today. It is friday night and I am happy to say that I think my wife misses me😉
    Have a great weekend everyone.

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #15

    But, still, I can't for some reason really understand the code and how different parts relate to each other.

    The event section is a filter to look for a specific event. In your version, you have multiple value keys, which is not allowed. Also, you don't want to filter by value, just accept them all and let the response section deal with them. I recommended against using label because it's changeable in ZWave, whereas the property and property_key values are defined by the device and will not change.

    So again, the event section is the filter that determines what incoming event will match, and what will not.

    Once an event matches, the response section determines what to do with it. Each component of the response section is an attribute of an assigned capability and the instructions to set it. In the case of button.state, my version says grab the value from event.data.value, and then, map that value from the device's string to one of Reactor's accepted capability/attribute value. Setting button.since completes the "contract" of the button capability (i.e. makes it work like similar uses of button in other devices and related to other controllers). I'm not sure I can explain it more simply than that.

    It's really just a "if you find this... do this" configuration. The effect is that if a matching button event is detected by the event section, the response section will interpet the value and map it to a Reactor-compatible value to place on the entity attribute button.state, and also update the button.since timestamp. Thus the since timestamp changes every time a button press event is received, but state may not change, because it's possible to press a button once, wait 15 seconds, and press the same button again, which will result in the value single being persistent on the state attribute and not changing. So to detect an event, you have to check both state and since (and this is consistent with all button behavior in Reactor).

    To test button state in a rule, you test button.state for what you want in that rule (equals single, double, triple), and you AND that test with a button.since changes (from any to any). That will send a very short pulse when a matching button press occurs. While testing, to make sure you can see it, add a "sustained for" delay on the changes condition of a few seconds (keep it short), and you'll more easily see what's going on in the status view. Make sure to remove the delay when you're done playing (keeping it will dampen response to buttons when, for example, a single press is done repeatedly within the delay period).

    Example here: https://smarthome.community/assets/uploads/files/1646184651741-cbff18f3-ce2d-4ecd-ae65-2554f77a4a80-image.png

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    A 1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    replied to toggledbits on last edited by
    #16

    @toggledbits

    Ok, I understood it at first that I needed to specify more stuff in the event section, like 'value' so it then could be mapped to right command, otherwise it would not be known.

    But nodeid, property and property key is just to filter out right device, all the other data is still there?
    And in that case, I guess that it would work to skip event data and just mapping commands to MSR functions? (Of course nothing else can send 'Keypressed' command because that would be messy)

    toggledbitsT 1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    replied to Andr on last edited by
    #17

    @andr said in Adding remotes, scene controllers as entities to MSR:

    But nodeid, property and property key is just to filter out right device, all the other data is still there?

    That's right. The event section only filters using the data; it does not modify the data or transform it in any way. Whatever is received in the event structure stays as received.

    @andr said in Adding remotes, scene controllers as entities to MSR:

    And in that case, I guess that it would work to skip event data and just mapping commands to MSR functions?

    I'm not sure what you mean by this. I don't think you want to skip anything. You should filter the incoming events, to make sure that you are handling the right events from the right device. So you need to be specific in the event filter to both the event type and the sending device.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    A 1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    replied to toggledbits on last edited by
    #18

    @toggledbits said in Adding remotes, scene controllers as entities to MSR:

    ||@andr said in Adding remotes, scene controllers as entities to MSR:

    And in that case, I guess that it would work to skip event data and just mapping commands to MSR functions?||

    I'm not sure what you mean by this. I don't think you want to skip anything. You should filter the incoming events, to make sure that you are handling the right events from the right device. So you need to be specific in the event filter to both the event type and the sending device.

    That was just me trying to understand how stuff is related, not something I would try out.
    For example, in my system there is only one device that are sending "Keypressed3x" and that can not be mixed up with anything else. In that case if I had such uniq string to map to MSR command 'triple' I could skip the filtering in event section?

    Again, this is just for my own curiosa trying to learn something new.

    toggledbitsT 1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    wrote on last edited by toggledbits
    #19

    Anyway, some kinds of sucess the last nights 👍

    All buttons are configured and seems to work so far.

    The final reactor.yaml looks like this (just showing the first two buttons as it is just the entity name and 'property key' that differ )

    event_targets:    # this section starts the event-receiving entities
            "Keyfob_Fyrkant":      # Assign an ID to your entity; each entity must have a unique ID
              name: Lukas Keyfob Fyrkant   # This is optional but recommended, so you have a friendly name
              capabilities: ['button']  # define an array of capabilities to be modified by the event 
              events:  # define an array of events that modify capability attributes on the entity
                - event:  # start of an event; each element of the events array begins this way
                    event_type: zwave_js_value_notification
                    data:  # optional section, if further matching to the event data is required
                      node_id: 15
                      property: "scene" # Square button
                      property_key: "001"
                  response:  # begin the (required) response section for handling the event
                    "button.state":  # an attribute that the event modifies.
                      from: "event.data.value"  # dot-reference expression to pull value from event message
                      map:                    # optional, map to modify value
                        KeyPressed: 'single'   # if value is value_in, it is mapped to new_value
                        KeyPressed2x: 'double'
                        KeyPressed3x: 'tripple'
                        KeyHeldDown: 'hold'
                        KeyReleased: 'release'
                    "button.since":  # an attribute that the event modifies.
                      from: "event.context.id"  # dot-reference expression to pull value from event message
            "Keyfob_Ring":      # Assign an ID to your entity; each entity must have a unique ID
              name: Lukas Keyfob Ring   # This is optional but recommended, so you have a friendly name
              capabilities: ['button']  # define an array of capabilities to be modified by the event 
              events:  # define an array of events that modify capability attributes on the entity
                - event:  # start of an event; each element of the events array begins this way
                    event_type: zwave_js_value_notification
                    data:  # optional section, if further matching to the event data is required
                      node_id: 15
                      property: "scene" # Circle button
                      property_key: "002"
                  response:  # begin the (required) response section for handling the event
                    "button.state":  # an attribute that the event modifies.
                      from: "event.data.value"  # dot-reference expression to pull value from event message
                      map:                    # optional, map to modify value
                        KeyPressed: 'single'   # if value is value_in, it is mapped to new_value
                        KeyPressed2x: 'double'
                        KeyPressed3x: 'triple'
                        KeyHeldDown: 'hold'
                        KeyReleased: 'release'
                    "button.since":  # an attribute that the event modifies.
                      from: "event.context.id"  # dot-reference expression to pull value from event message
    

    A thought that crossed my mind recently, to maybe expand the functions of this little remote in the future.
    Fibaro have built in a possibilty for 6 extra scenes that activates after a sequence of button presses I specify. I have not activated this yet as I don't think I really need it, but what I realised is that it probably quite easy to add a lot of differnt button sequences in MSR as long or short that I want?

    Next part is to get some rules and actions set-up that can use the remote.

    1 Reply Last reply
    0
  • A Offline
    A Offline
    Andr
    wrote on last edited by Andr
    #20

    Seems to work like a charm 😁

    Started out with a few rules to let him control a Sonos in his room.
    This one is for starting his favorite playlist, when it not is bedtime and that playlist isn't already playing.

    c9770192-464f-4eb0-854f-9348e4b5b494-image.png

    1 Reply Last reply
    1

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.