Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Issue with Zooz Zen14 outlet and Zwavejs
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor

Issue with Zooz Zen14 outlet and Zwavejs

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 2 Posters 959 Views 2 Watching
  • 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.
  • T Offline
    T Offline
    tamorgen
    wrote on last edited by tamorgen
    #1

    Good morning,
    I'm having an issue with controlling my Zooz Zen14 outdoor double outlet. I should be able to control each outlet individually, and this does work when use Home Assistant (haas) from Reactor.

    When I use zwavejs, I see 3 entries:

    8305eccf-a99e-421f-ad18-1f08da9c8c9c-image.png

    The first entry is for the overall device. I can turn both outlets on and off (in theory) by setting the power_switch state to on or off. This does turn them on and off when using zwavejs.

    When I go to the individual outlets, performing the power_switch.on or power_switch.off actions turns them all (main, 1 and 2) on or off, and not just the individual outlets. When I perform the same action from haas, turning on outlet 1 will turn on the main switch and 1, but not 2.

    I reviewed the logs for that node and I'm not seeing anything obvious.

    :~/reactor/logs$ cat reactor.log.1 | grep ZWaveJSController#zwavejs | grep "node 216"
    [latest-24212]2024-08-07T00:19:00.233Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "endpoint": 0, "property": "targetValue", "newValue": true, "prevValue": false, "propertyName": "targetValue" } }
    [latest-24212]2024-08-07T00:19:00.235Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": false, "propertyName": "currentValue" } }
    [latest-24212]2024-08-07T00:19:00.321Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "currentValue" } }
    [latest-24212]2024-08-07T00:19:00.322Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "targetValue" } }
    [latest-24212]2024-08-07T00:19:00.323Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 0, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
    [latest-24212]2024-08-07T00:19:02.189Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "currentValue" } }
    [latest-24212]2024-08-07T00:19:02.192Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "targetValue" } }
    [latest-24212]2024-08-07T00:19:02.193Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 1, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
    [latest-24212]2024-08-07T05:32:30.127Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 0 (entity "216-0")
    [latest-24212]2024-08-07T05:32:30.127Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 1 (entity "216-1")
    [latest-24212]2024-08-07T05:32:30.128Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 2 (entity "216-2")
    

    I'm running:

    Reactor (Multi-hub) latest-24212-3ce15e25
    ZWaveJSController [0.1.23326] (with zwavejs_data from 7/25/2024)

    HA:
    Core 2024.7.3
    Supervisor 2024.08.0
    Operating System 12.3
    Frontend 20240710.0

    toggledbitsT 1 Reply Last reply
    0
    • T tamorgen

      Good morning,
      I'm having an issue with controlling my Zooz Zen14 outdoor double outlet. I should be able to control each outlet individually, and this does work when use Home Assistant (haas) from Reactor.

      When I use zwavejs, I see 3 entries:

      8305eccf-a99e-421f-ad18-1f08da9c8c9c-image.png

      The first entry is for the overall device. I can turn both outlets on and off (in theory) by setting the power_switch state to on or off. This does turn them on and off when using zwavejs.

      When I go to the individual outlets, performing the power_switch.on or power_switch.off actions turns them all (main, 1 and 2) on or off, and not just the individual outlets. When I perform the same action from haas, turning on outlet 1 will turn on the main switch and 1, but not 2.

      I reviewed the logs for that node and I'm not seeing anything obvious.

      :~/reactor/logs$ cat reactor.log.1 | grep ZWaveJSController#zwavejs | grep "node 216"
      [latest-24212]2024-08-07T00:19:00.233Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "endpoint": 0, "property": "targetValue", "newValue": true, "prevValue": false, "propertyName": "targetValue" } }
      [latest-24212]2024-08-07T00:19:00.235Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": false, "propertyName": "currentValue" } }
      [latest-24212]2024-08-07T00:19:00.321Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "currentValue" } }
      [latest-24212]2024-08-07T00:19:00.322Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "targetValue" } }
      [latest-24212]2024-08-07T00:19:00.323Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 0, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
      [latest-24212]2024-08-07T00:19:02.189Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "currentValue" } }
      [latest-24212]2024-08-07T00:19:02.192Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "targetValue" } }
      [latest-24212]2024-08-07T00:19:02.193Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 1, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
      [latest-24212]2024-08-07T05:32:30.127Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 0 (entity "216-0")
      [latest-24212]2024-08-07T05:32:30.127Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 1 (entity "216-1")
      [latest-24212]2024-08-07T05:32:30.128Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 216 endpoint 2 (entity "216-2")
      

      I'm running:

      Reactor (Multi-hub) latest-24212-3ce15e25
      ZWaveJSController [0.1.23326] (with zwavejs_data from 7/25/2024)

      HA:
      Core 2024.7.3
      Supervisor 2024.08.0
      Operating System 12.3
      Frontend 20240710.0

      toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #2

      @tamorgen If you don't already have separate logging configuration for ZWaveJSController, add the following to your logging.yaml and restart Reactor:

        # These lines are indented 2 **spaces** (no tabs) in logging.yaml
        ZWaveJSController:
          level: 5
          streams:
            - type: file
              name: zwavejs.log
              keep: 2
              level: 999
              recycle: true
      

      If you already have this kind of entry for ZWaveJSController, then just change level to 5.

      After restarting Reactor and letting everything settle, turn endpoint 1 (entity 216-1) on, then off. Then, go through the logs looking for the text _set_value(...stuff) and setting value ...stuff -- these lines should be close to each other, probably adjacent, and of course, close to the end of the file. I need the lines that specifically (and only) relate to the node in question (216). Post what you find. It should look something like this (this is for turning off switch 1):

      [xxxx]2024-08-07T22:03:16.733Z <ZWaveJSController#zwavejs:5:ZWaveJSController.js:1751> ZWaveJSController#zwavejs _set_value(216,1,37,targetValue,(undefined),false)
      [xxxx]2024-08-07T22:03:16.734Z <ZWaveJSController#zwavejs:5> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 216, "endpoint": 1, "valueId": { "commandClass": 37, "property": "targetValue" }, "value": false }
      

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

      T 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        @tamorgen If you don't already have separate logging configuration for ZWaveJSController, add the following to your logging.yaml and restart Reactor:

          # These lines are indented 2 **spaces** (no tabs) in logging.yaml
          ZWaveJSController:
            level: 5
            streams:
              - type: file
                name: zwavejs.log
                keep: 2
                level: 999
                recycle: true
        

        If you already have this kind of entry for ZWaveJSController, then just change level to 5.

        After restarting Reactor and letting everything settle, turn endpoint 1 (entity 216-1) on, then off. Then, go through the logs looking for the text _set_value(...stuff) and setting value ...stuff -- these lines should be close to each other, probably adjacent, and of course, close to the end of the file. I need the lines that specifically (and only) relate to the node in question (216). Post what you find. It should look something like this (this is for turning off switch 1):

        [xxxx]2024-08-07T22:03:16.733Z <ZWaveJSController#zwavejs:5:ZWaveJSController.js:1751> ZWaveJSController#zwavejs _set_value(216,1,37,targetValue,(undefined),false)
        [xxxx]2024-08-07T22:03:16.734Z <ZWaveJSController#zwavejs:5> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 216, "endpoint": 1, "valueId": { "commandClass": 37, "property": "targetValue" }, "value": false }
        
        T Offline
        T Offline
        tamorgen
        wrote on last edited by tamorgen
        #3

        @toggledbits

        Here's what I got from that powering on and off....

        ~/reactor/logs$ cat reactor.log | grep ZWaveJSController#zwavejs | grep "node 216" | grep 2024-08-08T00:22:
        [latest-24212]2024-08-08T00:22:11.117Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "endpoint": 0, "property": "targetValue", "newValue": true, "prevValue": false, "propertyName": "targetValue" } }
        [latest-24212]2024-08-08T00:22:11.118Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:targetValue:"=true: [Array][  ]
        [latest-24212]2024-08-08T00:22:11.124Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": false, "propertyName": "currentValue" } }
        [latest-24212]2024-08-08T00:22:11.125Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:currentValue:"=true: [Array][ "power_switch.state" ]
        [latest-24212]2024-08-08T00:22:11.170Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "currentValue" } }
        [latest-24212]2024-08-08T00:22:11.170Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:currentValue:"=true: [Array][ "power_switch.state" ]
        [latest-24212]2024-08-08T00:22:11.174Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 0, "newValue": true, "prevValue": true, "propertyName": "targetValue" } }
        [latest-24212]2024-08-08T00:22:11.175Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 0, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
        [latest-24212]2024-08-08T00:22:11.176Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:targetValue:"=true: [Array][  ]
        [latest-24212]2024-08-08T00:22:11.177Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:duration:"=[Object]{ "value": 0, "unit": "seconds" }: [Array][  ]
        [latest-24212]2024-08-08T00:22:11.418Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "currentValue" } }
        [latest-24212]2024-08-08T00:22:11.419Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "1:37:currentValue:"=true: [Array][ "power_switch.state" ]
        [latest-24212]2024-08-08T00:22:11.426Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 1, "newValue": true, "prevValue": false, "propertyName": "targetValue" } }
        [latest-24212]2024-08-08T00:22:11.427Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 1, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
        [latest-24212]2024-08-08T00:22:11.428Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "1:37:targetValue:"=true: [Array][  ]
        [latest-24212]2024-08-08T00:22:11.433Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "1:37:duration:"=[Object]{ "value": 0, "unit": "seconds" }: [Array][  ]
        [latest-24212]2024-08-08T00:22:11.978Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "2:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 2, "newValue": true, "prevValue": false, "propertyName": "currentValue" } }
        [latest-24212]2024-08-08T00:22:11.978Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "2:37:currentValue:"=true: [Array][ "power_switch.state" ]
        [latest-24212]2024-08-08T00:22:11.984Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "2:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 2, "newValue": true, "prevValue": false, "propertyName": "targetValue" } }
        [latest-24212]2024-08-08T00:22:11.985Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "2:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 2, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
        [latest-24212]2024-08-08T00:22:11.986Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "2:37:targetValue:"=true: [Array][  ]
        [latest-24212]2024-08-08T00:22:11.989Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "2:37:duration:"=[Object]{ "value": 0, "unit": "seconds" }: [Array][  ]
        [latest-24212]2024-08-08T00:22:30.188Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "endpoint": 0, "property": "targetValue", "newValue": false, "prevValue": true, "propertyName": "targetValue" } }
        [latest-24212]2024-08-08T00:22:30.189Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:targetValue:"=false: [Array][  ]
        [latest-24212]2024-08-08T00:22:30.194Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": false, "prevValue": true, "propertyName": "currentValue" } }
        [latest-24212]2024-08-08T00:22:30.196Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:currentValue:"=false: [Array][ "power_switch.state" ]
        [latest-24212]2024-08-08T00:22:30.242Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 0, "newValue": false, "prevValue": false, "propertyName": "currentValue" } }
        [latest-24212]2024-08-08T00:22:30.242Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:currentValue:"=false: [Array][ "power_switch.state" ]
        [latest-24212]2024-08-08T00:22:30.245Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 0, "newValue": false, "prevValue": false, "propertyName": "targetValue" } }
        [latest-24212]2024-08-08T00:22:30.246Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "0:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 0, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
        [latest-24212]2024-08-08T00:22:30.247Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:targetValue:"=false: [Array][  ]
        [latest-24212]2024-08-08T00:22:30.248Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "0:37:duration:"=[Object]{ "value": 0, "unit": "seconds" }: [Array][  ]
        [latest-24212]2024-08-08T00:22:30.487Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 1, "newValue": false, "prevValue": true, "propertyName": "currentValue" } }
        [latest-24212]2024-08-08T00:22:30.487Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "1:37:currentValue:"=false: [Array][ "power_switch.state" ]
        [latest-24212]2024-08-08T00:22:30.488Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 1, "newValue": false, "prevValue": true, "propertyName": "targetValue" } }
        [latest-24212]2024-08-08T00:22:30.488Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "1:37:targetValue:"=false: [Array][  ]
        [latest-24212]2024-08-08T00:22:30.491Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "1:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 1, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
        [latest-24212]2024-08-08T00:22:30.491Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "1:37:duration:"=[Object]{ "value": 0, "unit": "seconds" }: [Array][  ]
        [latest-24212]2024-08-08T00:22:31.048Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "2:37:currentValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "currentValue", "endpoint": 2, "newValue": false, "prevValue": true, "propertyName": "currentValue" } }
        [latest-24212]2024-08-08T00:22:31.048Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "2:37:currentValue:"=false: [Array][ "power_switch.state" ]
        [latest-24212]2024-08-08T00:22:31.055Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "2:37:targetValue:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "targetValue", "endpoint": 2, "newValue": false, "prevValue": true, "propertyName": "targetValue" } }
        [latest-24212]2024-08-08T00:22:31.056Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs update node 216 value "2:37:duration:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 216, "args": { "commandClassName": "Binary Switch", "commandClass": 37, "property": "duration", "endpoint": 2, "newValue": { "value": 0, "unit": "seconds" }, "prevValue": { "value": 0, "unit": "seconds" }, "propertyName": "duration" } }
        [latest-24212]2024-08-08T00:22:31.057Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "2:37:targetValue:"=false: [Array][  ]
        [latest-24212]2024-08-08T00:22:31.059Z <ZWaveJSController:5:ZWaveJSController.js:465> ZWaveJSController#zwavejs updating attributes for node 216 value "2:37:duration:"=[Object]{ "value": 0, "unit": "seconds" }: [Array][  ]
        

        I don't see test about set_value or setting_value when I tried to grep. When I performed the Action power_switch.on from the Entities page, each of the three entries turned green momentarily while the primary value changed to true.

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

          You need to grep in the zwavejs.log file.

          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
          • T Offline
            T Offline
            tamorgen
            wrote on last edited by tamorgen
            #5

            @toggledbits
            I ran two separate tests. I ran a test from Home Assistant dashboard, turning on and off one of the outlets while tailing the zwavejs.log file. I then ran the same test from from Entities in MSR, only trying to power the one outlet on the double outlet. I provided a link to the log files below.

            From HAAS

            From MRS

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

              Try build 24232 of ZWaveJSController just posted. This is an interim build.

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

              T 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                Try build 24232 of ZWaveJSController just posted. This is an interim build.

                T Offline
                T Offline
                tamorgen
                wrote on last edited by
                #7

                @toggledbits said in Issue with Zooz Zen14 outlet and Zwavejs:

                Try build 24232 of ZWaveJSController just posted. This is an interim build.

                That appears to have fixed the issue. Thanks!

                1 Reply Last reply
                1
                • toggledbitsT toggledbits locked this topic on
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                Recent Topics

                • [Reactor] Bug when sending MQTT boolean payloads
                  toggledbitsT
                  toggledbits
                  0
                  4
                  90

                • Genuinely impressed with Zigbee and HA / Reactor
                  therealdbT
                  therealdb
                  1
                  8
                  241

                • Difficulty defining repeating annual period
                  G
                  gwp1
                  0
                  5
                  45

                • Need help with sequence
                  therealdbT
                  therealdb
                  0
                  3
                  30

                • Possible feature request?
                  therealdbT
                  therealdb
                  0
                  5
                  140

                • Copying a global reaction
                  tunnusT
                  tunnus
                  0
                  1
                  38

                • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                  CatmanV2C
                  CatmanV2
                  0
                  11
                  296

                • Time series documentation
                  tunnusT
                  tunnus
                  0
                  11
                  378

                • Tuya Wifi to Tasmota flashing
                  CatmanV2C
                  CatmanV2
                  0
                  1
                  84

                • MQTT templates for ZIgbee scene controller, or a better way?
                  CatmanV2C
                  CatmanV2
                  0
                  3
                  144

                • Reset a delay
                  CatmanV2C
                  CatmanV2
                  0
                  8
                  204

                • Zigbee2mqtt installed! sytemctl not happy :(
                  CatmanV2C
                  CatmanV2
                  0
                  4
                  175
                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