node-zwave-js: Z-Wave driver not able to complete the interview with a Heatit Z-TRM2 device

Describe the bug Node 009 is not able to complete the Interview. I can see that Node 009 is having a hard time being Interviewed. It’s a Heatit Z-TRM2 device.

To Reproduce Steps to reproduce the behavior:

  1. Start zwavejs2mqtt with a Heatit Z-TRM2 thermostat in the network
  2. Observe the not completed interview. Last completed stage is NodeInfo.

Device information Which device(s) is/are affected? HeatIt Z-TRM2 What are the node IDs? 9

Logfile: I added the debug log in https://gist.github.com/larstobi/a644872f2cfb2b96f5a0fb2c1a0d9e5d as zwave-4.log

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 67 (63 by maintainers)

Most upvoted comments

@robertsLando I can confirm that your fix made it possible to set half degrees on the Z-TRM3. Thanks! 😃

You might want to use parseFloat instead:

There is no advantages to use parseFloat in this situation as the input type for numbers is number, I think I have added that check because for some reason vue is sending me it as string, I should add to the v-model .number to parse it but I’m using the same input for text values: https://github.com/zwave-js/zwavejs2mqtt/blob/master/src/components/ValueId.vue#L13-L30

@larstobi Fixed in master

I’ve just started zwavejs2mqtt with the latest master branch. Will report back in a jiffy!

@larstobi Try to pull master, last commit should fix the firmware update

I will try using zjs2m right now. I actually bought a cheap Windows laptop just for this purpose…but I guess I don’t need it after all, haha…

I thought the logs would be too big to past directly into here

You can attach files too: grafik

I thought the logs would be too big to past directly into here. There are more than 2000 lines of Node 009 in the log. However, I can try to pick out a selection.

I think he means to attach them to the comment 😃