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. [Solved] Zwave Refresh for a particular attribute
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

[Solved] Zwave Refresh for a particular attribute

Scheduled Pinned Locked Moved Multi-System Reactor
zwave-js
10 Posts 2 Posters 1.1k 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.
  • V Offline
    V Offline
    vezinpi
    wrote on last edited by vezinpi
    #1

    My thermostat (CT100 plus) has been very intermittent in updating its operating"State" (idle, heating or cooling), in a timely manner. Update were coming but sometimes 15 min after the fact. The other attributes are updating just fine. It was like that when paired with my vera plus, and it did not improved since it is on the Hass/Zwavejs2MQTT.

    Back on the vera days, my only option was to use polling but that generated alot of traffic( Thermostat have many attributes). So I kept the polling to a minimum and that did not helped very much. Hass Zwavejs integration only allows polling entire device (like vera I think). I then found out that with Zwave2MQTT, we can poll individual attribute rather than the whole device. This reduced the amount of trafic dramatically, almost 15 to 1. I think that it would be a nice addition for MSR. Why refresh the whole device if only one attribute is needed.

    Following is the screen capture of the zwavejs2MQTT interface for doing this. I did not find a way to attach files but I have one zwavejs2mqtt log file for a MSR refresh and one for the MQTT operating state 66 refresh. The funny thing is that a refresh from MSR trigger all values to be updated, except for the "operating state"! (This thermostat has a mind of its own)

    I can add the 2 files if of any interest (One of them is quite long).

    9032bb53-d675-4723-a585-a9327ada3af7-image.png

    Using MSR 25016 on Docker, on a Raspberry Pi with Bookworm. Home Assistant, Z-Wave JS-UI

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

      Are you on today's 22049 or the first release?

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

      V 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        Are you on today's 22049 or the first release?

        V Offline
        V Offline
        vezinpi
        wrote on last edited by vezinpi
        #3

        @toggledbits Sorry should have mentionned it. 22049 on Raspberry pi OS with Docker.

        I did most of the work on the initial version but did the upgrade before posting. Just double check and cannot see how I can make rule that trigger every 30 or 60 sec that would set a reaction with Zwave_device_refresh on the thermostat "Operating state" only. That what the zwave2mqtt allow you to do to cope with older zwave devices or in my case, device that do not want to play nice. For the people using the standard zwave-js server, they have no option (that I can think of)

        c2106288-9a63-4658-a96d-1e6ec762bacb-image.png

        EDIT: As for the "ThermostatOperatingStateCCGet" not being part of the refresh, I just compare the logs between a refresh from MSR and a refresh from ZwaveJS2MQTT and they are identical (beside callback ID and checksum).

        Using MSR 25016 on Docker, on a Raspberry Pi with Bookworm. Home Assistant, Z-Wave JS-UI

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

          No worries. I noted a bug in the thermostat support when I plugged your data in on my end that would have prevented, at least to my view of it, the operating state from being correct at all. If you have state, even an old one, that bug was fixed, so we're moving on...

          There is polling already, mentioned in the documentation as a "there but don't use it yet" feature. I've just finished (is anything ever finished?) and extended it to include specific command classes that will work with either zwavejs2mqtt or zwave-js-server (and therefore either is fine with Reactor). That will be out in today's build, along with updated docs.

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

          V 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            No worries. I noted a bug in the thermostat support when I plugged your data in on my end that would have prevented, at least to my view of it, the operating state from being correct at all. If you have state, even an old one, that bug was fixed, so we're moving on...

            There is polling already, mentioned in the documentation as a "there but don't use it yet" feature. I've just finished (is anything ever finished?) and extended it to include specific command classes that will work with either zwavejs2mqtt or zwave-js-server (and therefore either is fine with Reactor). That will be out in today's build, along with updated docs.

            V Offline
            V Offline
            vezinpi
            wrote on last edited by vezinpi
            #5

            @toggledbits Just installed version 22050.

            Almost there! When MSR is restarted after changing the poll configuration, the node is poll with the proper command class. However the Interval time is not taken into consideration. I seems that the global poll interval is taken. Also noticed in the log that the next time (for the poll to be executed) is "Local Time". Not sure if that is normal. Here is my config and the logs. (the config file ident get screwed up with the paste but it is fine)

            Hope this help

            Reactor.yaml

            controllers:
              - id: zwavejs
                implementation: ZWaveJSController
                enabled: true
                config:
                  source: ws://192.168....
                  auth: >
                    HIt54tjRUlqaUShB...
                    
                  poll_interval: 3600
                  poll_frequency: 20
                  poll_nodes:
                    - entity: Thermostat
                      command_class: Thermostat Operating State
                      interval: 100
            

            Log: i.e. my TZ is -5

            [zwavejs-22050]2022-02-20T15:46:02.192Z <ZWaveJSController:5:ZWaveJSController.js:1506> ZWaveJSController#zwavejs node 9 eligible for polling
            [zwavejs-22050]2022-02-20T15:46:02.206Z <ZWaveJSController:5:ZWaveJSController.js:1519> ZWaveJSController#zwavejs polling node 9 command class 0x"42" (Thermostat Operating State)
            2022-02-20T15:46:02.212Z CNTRLR » [Node 009] querying thermostat operating state...
            2022-02-20T15:46:02.238Z SERIAL » 0x010e00a9010902420225000000001522                                  (16 bytes)
            2022-02-20T15:46:02.240Z DRIVER » [Node 009] [REQ] [SendDataBridge]
                                              │ source node id:   1
                                              │ transmit options: 0x25
                                              │ route:            0, 0, 0, 0
                                              │ callback id:      21
                                              └─[ThermostatOperatingStateCCGet]
            2022-02-20T15:46:02.250Z SERIAL « [ACK]                                                                   (0x06)
            2022-02-20T15:46:02.256Z SERIAL « 0x010401a90152                                                       (6 bytes)
            [zwavejs-22050]2022-02-20T15:46:02.263Z <ZWaveJSController:6:ZWaveJSController.js:710> ZWaveJSController#zwavejs handling controller event statistics updated
            2022-02-20T15:46:02.259Z SERIAL » [ACK]                                                                   (0x06)
            2022-02-20T15:46:02.266Z DRIVER « [RES] [SendDataBridge]
                                                was sent: true
            2022-02-20T15:46:02.304Z SERIAL « 0x011d00a91500000502c47f7f7f7f00000305060000030100007f7f7f7f7fe0    (31 bytes)
            2022-02-20T15:46:02.307Z SERIAL » [ACK]                                                                   (0x06)
            2022-02-20T15:46:02.311Z DRIVER « [REQ] [SendDataBridge]
                                                callback id:            21
                                                transmit status:        OK, took 50 ms
                                                repeater node IDs:      5, 6
                                                routing attempts:       1
                                                protocol & route speed: Z-Wave, 100 kbit/s
                                                ACK RSSI:               -60 dBm
                                                ACK RSSI on repeaters:  N/A, N/A
                                                ACK channel no.:        0
                                                TX channel no.:         0
            [zwavejs-22050]2022-02-20T15:46:02.325Z <ZWaveJSController:5:ZWaveJSController.js:652> ZWaveJSController#zwavejs handling node event statistics updated entity Entity#zwavejs>9-0
            [zwavejs-22050]2022-02-20T15:46:02.328Z <ZWaveJSController:6:ZWaveJSController.js:702> ZWaveJSController#zwavejs received statistics for Entity#zwavejs>9-0: [Object]{ "commandsTX": 3, "commandsRX": 3, "commandsDroppedRX": 0, "commandsDroppedTX": 0, "timeoutResponse": 0 }
            2022-02-20T15:46:02.428Z SERIAL « 0x010c00a80001090342030000c2d3                                      (14 bytes)
            2022-02-20T15:46:02.430Z CNTRLR   [Node 009] [~] [Thermostat Operating State] state: 0 => 0         [Endpoint 0]
            [zwavejs-22050]2022-02-20T15:46:02.438Z <ZWaveJSController:5:ZWaveJSController.js:652> ZWaveJSController#zwavejs handling node event value updated entity Entity#zwavejs>9-0
            [zwavejs-22050]2022-02-20T15:46:02.441Z <ZWaveJSController:5:ZWaveJSController.js:788> ZWaveJSController#zwavejs update value [Object]{ "source": "node", "event": "value updated", "nodeId": 9, "args": { "commandClassName": "Thermostat Operating State", "commandClass": 66, "endpoint": 0, "property": "state", "newValue": 0, "prevValue": 0, "propertyName": "state" } }
            [zwavejs-22050]2022-02-20T15:46:02.443Z <ZWaveJSController:5:ZWaveJSController.js:800> ZWaveJSController#zwavejs updating attributes for node 9 value "0:66:state:"=0: [Array][ "hvac_control.state", "hvac_heating_unit.state", "hvac_cooling_unit.state" ]
            [zwavejs-22050]2022-02-20T15:46:02.448Z <ZWaveJSController:5:ZWaveJSController.js:817> ZWaveJSController#zwavejs setting Entity#zwavejs>9-0.x_zwave_values.Thermostat_Operating_State_state to 0
            2022-02-20T15:46:02.438Z SERIAL » [ACK]                                                                   (0x06)
            2022-02-20T15:46:02.441Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                              │ RSSI: -62 dBm
                                              └─[ThermostatOperatingStateCCReport]
                                                  state: Idle
            **[zwavejs-22050]2022-02-20T15:46:02.454Z <ZWaveJSController:5:ZWaveJSController.js:1525> ZWaveJSController#zwavejs poll Entity#zwavejs>9-0 succeeded, next at 1645375562452<****2/20/2022, 11:46:02 AM****>**
            [zwavejs-22050]2022-02-20T15:46:02.510Z <ZWaveJSController:6:ZWaveJSController.js:710> ZWaveJSController#zwavejs handling controller event statistics updated
            [zwavejs-22050]2022-02-20T15:46:02.575Z <ZWaveJSController:5:ZWaveJSController.js:652> ZWaveJSController#zwavejs handling node event statistics updated entity Entity#zwavejs>9-0
            [zwavejs-22050]2022-02-20T15:46:02.576Z <ZWaveJSController:6:ZWaveJSController.js:702> ZWaveJSController#zwavejs received statistics for Entity#zwavejs>9-0: [Object]{ "commandsTX": 3, "commandsRX": 4, "commandsDroppedRX": 0, "commandsDroppedTX": 0, "timeoutResponse": 0 }
            

            Using MSR 25016 on Docker, on a Raspberry Pi with Bookworm. Home Assistant, Z-Wave JS-UI

            toggledbitsT 1 Reply Last reply
            1
            • V vezinpi

              @toggledbits Just installed version 22050.

              Almost there! When MSR is restarted after changing the poll configuration, the node is poll with the proper command class. However the Interval time is not taken into consideration. I seems that the global poll interval is taken. Also noticed in the log that the next time (for the poll to be executed) is "Local Time". Not sure if that is normal. Here is my config and the logs. (the config file ident get screwed up with the paste but it is fine)

              Hope this help

              Reactor.yaml

              controllers:
                - id: zwavejs
                  implementation: ZWaveJSController
                  enabled: true
                  config:
                    source: ws://192.168....
                    auth: >
                      HIt54tjRUlqaUShB...
                      
                    poll_interval: 3600
                    poll_frequency: 20
                    poll_nodes:
                      - entity: Thermostat
                        command_class: Thermostat Operating State
                        interval: 100
              

              Log: i.e. my TZ is -5

              [zwavejs-22050]2022-02-20T15:46:02.192Z <ZWaveJSController:5:ZWaveJSController.js:1506> ZWaveJSController#zwavejs node 9 eligible for polling
              [zwavejs-22050]2022-02-20T15:46:02.206Z <ZWaveJSController:5:ZWaveJSController.js:1519> ZWaveJSController#zwavejs polling node 9 command class 0x"42" (Thermostat Operating State)
              2022-02-20T15:46:02.212Z CNTRLR » [Node 009] querying thermostat operating state...
              2022-02-20T15:46:02.238Z SERIAL » 0x010e00a9010902420225000000001522                                  (16 bytes)
              2022-02-20T15:46:02.240Z DRIVER » [Node 009] [REQ] [SendDataBridge]
                                                │ source node id:   1
                                                │ transmit options: 0x25
                                                │ route:            0, 0, 0, 0
                                                │ callback id:      21
                                                └─[ThermostatOperatingStateCCGet]
              2022-02-20T15:46:02.250Z SERIAL « [ACK]                                                                   (0x06)
              2022-02-20T15:46:02.256Z SERIAL « 0x010401a90152                                                       (6 bytes)
              [zwavejs-22050]2022-02-20T15:46:02.263Z <ZWaveJSController:6:ZWaveJSController.js:710> ZWaveJSController#zwavejs handling controller event statistics updated
              2022-02-20T15:46:02.259Z SERIAL » [ACK]                                                                   (0x06)
              2022-02-20T15:46:02.266Z DRIVER « [RES] [SendDataBridge]
                                                  was sent: true
              2022-02-20T15:46:02.304Z SERIAL « 0x011d00a91500000502c47f7f7f7f00000305060000030100007f7f7f7f7fe0    (31 bytes)
              2022-02-20T15:46:02.307Z SERIAL » [ACK]                                                                   (0x06)
              2022-02-20T15:46:02.311Z DRIVER « [REQ] [SendDataBridge]
                                                  callback id:            21
                                                  transmit status:        OK, took 50 ms
                                                  repeater node IDs:      5, 6
                                                  routing attempts:       1
                                                  protocol & route speed: Z-Wave, 100 kbit/s
                                                  ACK RSSI:               -60 dBm
                                                  ACK RSSI on repeaters:  N/A, N/A
                                                  ACK channel no.:        0
                                                  TX channel no.:         0
              [zwavejs-22050]2022-02-20T15:46:02.325Z <ZWaveJSController:5:ZWaveJSController.js:652> ZWaveJSController#zwavejs handling node event statistics updated entity Entity#zwavejs>9-0
              [zwavejs-22050]2022-02-20T15:46:02.328Z <ZWaveJSController:6:ZWaveJSController.js:702> ZWaveJSController#zwavejs received statistics for Entity#zwavejs>9-0: [Object]{ "commandsTX": 3, "commandsRX": 3, "commandsDroppedRX": 0, "commandsDroppedTX": 0, "timeoutResponse": 0 }
              2022-02-20T15:46:02.428Z SERIAL « 0x010c00a80001090342030000c2d3                                      (14 bytes)
              2022-02-20T15:46:02.430Z CNTRLR   [Node 009] [~] [Thermostat Operating State] state: 0 => 0         [Endpoint 0]
              [zwavejs-22050]2022-02-20T15:46:02.438Z <ZWaveJSController:5:ZWaveJSController.js:652> ZWaveJSController#zwavejs handling node event value updated entity Entity#zwavejs>9-0
              [zwavejs-22050]2022-02-20T15:46:02.441Z <ZWaveJSController:5:ZWaveJSController.js:788> ZWaveJSController#zwavejs update value [Object]{ "source": "node", "event": "value updated", "nodeId": 9, "args": { "commandClassName": "Thermostat Operating State", "commandClass": 66, "endpoint": 0, "property": "state", "newValue": 0, "prevValue": 0, "propertyName": "state" } }
              [zwavejs-22050]2022-02-20T15:46:02.443Z <ZWaveJSController:5:ZWaveJSController.js:800> ZWaveJSController#zwavejs updating attributes for node 9 value "0:66:state:"=0: [Array][ "hvac_control.state", "hvac_heating_unit.state", "hvac_cooling_unit.state" ]
              [zwavejs-22050]2022-02-20T15:46:02.448Z <ZWaveJSController:5:ZWaveJSController.js:817> ZWaveJSController#zwavejs setting Entity#zwavejs>9-0.x_zwave_values.Thermostat_Operating_State_state to 0
              2022-02-20T15:46:02.438Z SERIAL » [ACK]                                                                   (0x06)
              2022-02-20T15:46:02.441Z DRIVER « [Node 009] [REQ] [BridgeApplicationCommand]
                                                │ RSSI: -62 dBm
                                                └─[ThermostatOperatingStateCCReport]
                                                    state: Idle
              **[zwavejs-22050]2022-02-20T15:46:02.454Z <ZWaveJSController:5:ZWaveJSController.js:1525> ZWaveJSController#zwavejs poll Entity#zwavejs>9-0 succeeded, next at 1645375562452<****2/20/2022, 11:46:02 AM****>**
              [zwavejs-22050]2022-02-20T15:46:02.510Z <ZWaveJSController:6:ZWaveJSController.js:710> ZWaveJSController#zwavejs handling controller event statistics updated
              [zwavejs-22050]2022-02-20T15:46:02.575Z <ZWaveJSController:5:ZWaveJSController.js:652> ZWaveJSController#zwavejs handling node event statistics updated entity Entity#zwavejs>9-0
              [zwavejs-22050]2022-02-20T15:46:02.576Z <ZWaveJSController:6:ZWaveJSController.js:702> ZWaveJSController#zwavejs received statistics for Entity#zwavejs>9-0: [Object]{ "commandsTX": 3, "commandsRX": 4, "commandsDroppedRX": 0, "commandsDroppedTX": 0, "timeoutResponse": 0 }
              
              toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by
              #6

              @vezinpi Got it. Fix in next release.

              It would be helpful if you enclosed config and log stuff in "block code" formatting. To do that, put three backticks (```) one their own line before and after the pasted stuff. If you don't do that, the formatting gets corrupted, and when looking at YAML, that's particularly misleading; you can see that for yourself in your post, I'm sure. Example, before and after formatting:

              this is a code block --
              this line is indented, can you tell?
              put the backticks on their own line
              before AND after the code block.

              You make it look like this while editing:

              ```
              this is a code block --
              this line is indented, can you tell?
              put the backticks on their own line
              before AND after the code block.
              ```

              That ends up looking like this in the final post:

              this is a code block --
                  this line is indented, can you tell?
                      put the backticks on their own line
                          before AND after the code block.
              

              I see some non-US keyboard layouts don't have the backtick on a key, but a handy alternative is to select the text/code/config block and hit the button below in this site's post editing tools, or hit the tool first and then paste-replace the default contents:

              2ce6e20f-f45d-415e-aaeb-d1d9ebcb4a43-image.png

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

              V 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                @vezinpi Got it. Fix in next release.

                It would be helpful if you enclosed config and log stuff in "block code" formatting. To do that, put three backticks (```) one their own line before and after the pasted stuff. If you don't do that, the formatting gets corrupted, and when looking at YAML, that's particularly misleading; you can see that for yourself in your post, I'm sure. Example, before and after formatting:

                this is a code block --
                this line is indented, can you tell?
                put the backticks on their own line
                before AND after the code block.

                You make it look like this while editing:

                ```
                this is a code block --
                this line is indented, can you tell?
                put the backticks on their own line
                before AND after the code block.
                ```

                That ends up looking like this in the final post:

                this is a code block --
                    this line is indented, can you tell?
                        put the backticks on their own line
                            before AND after the code block.
                

                I see some non-US keyboard layouts don't have the backtick on a key, but a handy alternative is to select the text/code/config block and hit the button below in this site's post editing tools, or hit the tool first and then paste-replace the default contents:

                2ce6e20f-f45d-415e-aaeb-d1d9ebcb4a43-image.png

                V Offline
                V Offline
                vezinpi
                wrote on last edited by vezinpi
                #7

                @toggledbits said in Zwave Refresh for a particular attribute:

                It would be helpful if you enclosed config and log stuff in "block code" formatting. To do that, put three backticks (```) one their own line before and after the pasted stuff.

                I have been looking for that for a long time. I am not really a "Forum" type of person. Lot's to learn, thanks for letting me know and your patience.

                Using MSR 25016 on Docker, on a Raspberry Pi with Bookworm. Home Assistant, Z-Wave JS-UI

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

                  No worries! For most forum use, it's not the kind of thing one needs to know. When things get technical as we do here, it's a big help, though. Thanks for updating, too. The updated post is lovely! 🙂

                  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
                  • V Offline
                    V Offline
                    vezinpi
                    wrote on last edited by vezinpi
                    #9

                    Gave it a try again. It was working as advertised initially but if the zwavejs2mqtt server is restarted/updated then the polling does not resume. It will only resume when MSR is restarted.

                    Using MSR 25016 on Docker, on a Raspberry Pi with Bookworm. Home Assistant, Z-Wave JS-UI

                    1 Reply Last reply
                    0
                    • V Offline
                      V Offline
                      vezinpi
                      wrote on last edited by
                      #10

                      Fixed by version 22052. 💪

                      Using MSR 25016 on Docker, on a Raspberry Pi with Bookworm. Home Assistant, Z-Wave JS-UI

                      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

                      • Gradually turn on lights.
                        G
                        gwp1
                        0
                        4
                        139

                      • Stop the MSR by an external switch on Hubitat.
                        wmarcolinW
                        wmarcolin
                        0
                        1
                        35

                      • Error After Upgrade
                        G
                        gwp1
                        0
                        4
                        105

                      • Reset attribute value of entity in event handler
                        R
                        RHCPNG
                        0
                        5
                        205

                      • Need help figuring out how to delay a reset on reaction
                        G
                        gwp1
                        0
                        22
                        929

                      • Way to search for rules (rule state) in other rules
                        T
                        tamorgen
                        0
                        3
                        101

                      • Links to MSR from HA
                        Tom_DT
                        Tom_D
                        0
                        1
                        91

                      • Set Reaction > Script Action
                        wmarcolinW
                        wmarcolin
                        0
                        11
                        437

                      • Wiring Samotech SM308-S into light fitting
                        akbooerA
                        akbooer
                        0
                        2
                        151

                      • Errors after updating to MQTTController build 25139
                        toggledbitsT
                        toggledbits
                        0
                        6
                        238

                      • 🎉 My very first MSR controller: OpenSprinkler
                        therealdbT
                        therealdb
                        5
                        13
                        919

                      • Advice reqeusted to migrate MSR from Bare Metal to Container
                        T
                        tamorgen
                        0
                        5
                        262
                      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