Many thanks

@eonnet are you using the supervised version with HAAS os ?

@eonnet said in Who are my Home Assistant + ZWave-JS users?:

Hello, i managed to connect the HA add on to reactor.

As I mentionned earlier in this thread, I also had issues with the zwavejs2mqtt HA addon. The only option I found was to remove the addon and install it stand alone but still in Docker.

I am just curious to know your setup and how you manage to make it work still using the HA addon.

Thanks

Fixed by version 22052.

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.

Yup, all back to normal now. Personnaly I preffer the reactor and Zwavejs logs without the serial interface info leaving that to the server log if needed. It is much cleaner.

Thanks

@toggledbits Did the upgrade to 22051 yesterday evening but before I could start testing, I noticed something not quite right with the logs.

Maybe this is intended. Zwavejs2mqtt is having 2 set of logs.

-One for the zwavejs2mqtt, this one is fine.

-One for the zwavejs. When MSR-zw is running that log is no longer updating. IF I restart zwavejs2mqtt, the log will update for the booting information but as soon as this is done, nothing update anymore. If I stop MSR-zw and restart zwavejs2mqtt all is fine again until MSR-zw is restarted.

As for the MSR log we have a dedicated set of logs for the Zwavejs info but zwave information is also in the regular Reactor.log. Is that the intended behaviur?

Thanks

EDIT: After looking a bit more I change the wording a little.

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

@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 }

@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)

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

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

@toggledbits Since we are at the beginning of this, should we put a header like "ZWAVE-JS" at the begining of the title for every new post related to Zwave-JS just to flag the topic? Or do we keep on going into this thread for all issues, questions, etc...?

How would you like us to proceed?

Finally got there... MSR-zwavejs installation (docker) went very well, no issues there. It was a different story with HASS. I am running an unsupported version of Home Assistant Supervised on a raspberry pi (bulleyes). I had to get rid of the zwave2mqtt addon and install it by itself (still with docker). Then I had to re-install the zwavejs integration. Home assistant documentation for zwave has a procedure to migrate the integratio to a new server without losing any devices. That helped alot.

@toggledbits, you should be seeing some data going you way. If not let me know. I will also complete my transition from vera to zwavejs in the following days. So more devices will eventually show up.

I don't, but I could if that's the way you want to communicate.

Hi,

MSR 22028 on raspbery pi os with docker.

I have a master rule that call other rules based on a random number (1 to 9). Reaction groups are used to run the proper rule depending on the random number.

I would also like to send a message via the Hass notify service to track which of the rule is being run. Is there a way to use variable substitition in the message body?

I can have different messages added to each group but since I have 9 different rules (group) and the message needs to reach 3 devices a total of 27 notify would be required. This number would go down to 3 if I can define them in the reaction section and not in the group.

the following example return: Scenario $ activated

Thanks

No rush at all.

Many thanks

Hi,

MSR v22028 on Raspberry pi OS with Docker

In the following small test (to show the issue), the delay "from start of reaction" behave as "from this point". When I look in Running Reaction widget, I can see that the delay are adding up counting 5 then 10 then 15 between each reaction.

I was expecting a change to be every 5 sec since it is from the start of the reaction. Changed my delays and used "from this point" to avoid the issue for now.

Hi,

I would be happy to assist. I am also using zwavejs2mqtt without the mqtt part activated.

Installed the new version yesterday along with the new guard and all is still fine this morning. Considering that it was failing very quickly before, I consider that issue fixed.