Z-Wave driver not able to complete the interview with a Heatit Z-TRM2 device #1128

larstobi · 2020-11-17T11:52:20Z

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:

Start zwavejs2mqtt with a Heatit Z-TRM2 thermostat in the network
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

The text was updated successfully, but these errors were encountered:

larstobi · 2020-11-17T11:54:44Z

14:45:04.704 CNTRLR   [Node 009] trying to load device config
14:45:04.713 CNTRLR   [Node 009] device config loaded
14:45:04.976 CNTRLR   [Node 009] Beginning interview - last completed stage: NodeInfo
14:45:04.977 CNTRLR   [Node 009] supports Security, but no network key was configured. Continuing in
14:45:04.984 CNTRLR   [Node 009] ManufacturerSpecificCC: doing a partial interview...
14:45:04.984 CNTRLR   [Node 009] [~] [Manufacturer Specific] interviewComple [Endpoint 0] [internal]
14:45:05.121 CNTRLR   [Node 009] VersionCC: doing a partial interview...
14:45:05.121 CNTRLR   [Node 009] [~] [Version] interviewComplete: true => tr [Endpoint 0] [internal]
14:45:05.121 CNTRLR   [Node 009] trying to load device config
14:45:05.153 CNTRLR   [Node 009] device config loaded
14:45:05.153 CNTRLR   [Node 009] ZWavePlusCC: doing a partial interview...
14:45:05.154 CNTRLR   [Node 009] [~] [Z-Wave Plus Info] interviewComplete: t [Endpoint 0] [internal]
14:45:05.154 CNTRLR » [Node 009] querying device endpoint information...
14:45:05.666 DRIVER » [Node 009] [REQ] [SendData]
14:45:05.947 CNTRLR   [Node 009] [+] [Multi Channel] commandClasses: undefin [Endpoint 0] [internal]
14:45:05.947 CNTRLR   [Node 009] [~] [Multi Channel] countIsDynamic: false = [Endpoint 0] [internal]
14:45:05.947 CNTRLR   [Node 009] [~] [Multi Channel] identicalCapabilities:  [Endpoint 0] [internal]
14:45:05.948 CNTRLR   [Node 009] [~] [Multi Channel] individualCount: 4 => 4 [Endpoint 0] [internal]
14:45:05.948 CNTRLR   [Node 009] [~] [Multi Channel] aggregatedCount: 0 => 0 [Endpoint 0] [internal]
14:45:05.949 DRIVER « [Node 009] [REQ] [ApplicationCommand]
14:45:05.954 CNTRLR   [Node 009] The node is alive.
14:45:05.955 CNTRLR « [Node 009] received response for device endpoints:
14:45:05.955 CNTRLR » [Node 009] querying all endpoints...
14:45:09.004 DRIVER » [Node 009] [REQ] [SendData]

15:41:39.151 DRIVER « [Node 009] [REQ] [ApplicationCommand]
15:41:39.382 DRIVER « [Node 009] [REQ] [ApplicationCommand]
15:41:39.383 CNTRLR « [Node 009] received information for parameter #1:
15:41:39.383 CNTRLR » [Node 009] querying parameter #1 value...
15:41:39.386 DRIVER » [Node 009] [REQ] [SendData]
15:41:39.592 CNTRLR   [Node 009] [~] [Configuration] 1: 11 => 11
15:41:39.594 DRIVER « [Node 009] [REQ] [ApplicationCommand]
15:41:39.595 CNTRLR » [Node 009] querying parameter #2 information...
15:41:39.599 DRIVER » [Node 009] [REQ] [SendData]
15:41:39.805 DRIVER « [Node 009] [REQ] [ApplicationCommand]
15:41:39.811 DRIVER » [Node 009] [REQ] [SendData]
15:41:41.535 CNTRLR   [Node 009] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
15:41:42.037 DRIVER » [Node 009] [REQ] [SendData]
15:41:43.800 CNTRLR   [Node 009] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
15:41:44.302 DRIVER » [Node 009] [REQ] [SendData]
15:41:44.411 DRIVER » [Node 009] [REQ] [SendData]
15:41:49.388 DRIVER » [Node 009] [REQ] [SendData]
15:41:49.491 DRIVER » [Node 009] [REQ] [SendData]
15:41:52.152 CNTRLR   [Node 009] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
15:41:52.657 DRIVER » [Node 009] [REQ] [SendData]
15:41:54.368 CNTRLR   [Node 009] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
15:41:54.871 DRIVER » [Node 009] [REQ] [SendData]
15:42:09.472 DRIVER « [Node 009] [REQ] [ApplicationCommand]
15:42:09.473 CNTRLR « [Node 009] received information for parameter #2:
15:42:09.473 CNTRLR » [Node 009] querying parameter #2 value...
15:42:09.476 DRIVER » [Node 009] [REQ] [SendData]
15:42:09.682 CNTRLR   [Node 009] [~] [Configuration] 2: 0 => 0
15:42:09.683 DRIVER « [Node 009] [REQ] [ApplicationCommand]
15:42:09.684 CNTRLR » [Node 009] querying parameter #3 information...
15:42:09.689 DRIVER » [Node 009] [REQ] [SendData]
15:42:09.898 DRIVER « [Node 009] [REQ] [ApplicationCommand]
15:42:09.904 DRIVER » [Node 009] [REQ] [SendData]
15:42:11.633 CNTRLR   [Node 009] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
15:42:12.134 DRIVER » [Node 009] [REQ] [SendData]
15:42:30.293 CNTRLR   [Node 009] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
15:42:30.796 DRIVER » [Node 009] [REQ] [SendData]
15:42:32.461 DRIVER » [Node 009] [REQ] [SendData]
15:42:34.211 CNTRLR   [Node 009] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
15:42:34.714 DRIVER » [Node 009] [REQ] [SendData]
15:42:36.500 CNTRLR   [Node 009] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
15:42:37.004 DRIVER » [Node 009] [REQ] [SendData]
15:42:39.164 CNTRLR   [Node 009] Failed all interview attempts, giving up.

AlCalzone · 2020-11-17T13:31:39Z

What is up with all these devices sending invalid ConfigurationCCInfoReports?
This is a duplicate of #1106

Please update to version 5.4.0.

larstobi · 2020-11-23T15:35:13Z

I did use at least 5.4.0, or rather the current master. I have built again from the most recent master at this moment.

I added the logs as zwave-5.log in https://gist.github.com/larstobi/a644872f2cfb2b96f5a0fb2c1a0d9e5d

AlCalzone · 2020-11-23T15:40:20Z

Ok let me check - I might have looked at the wrong log. If you attach them directly to your comments instead of a gist, it would probably be easier :)

larstobi · 2020-11-23T15:45:39Z

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.

robertsLando · 2020-11-23T15:46:24Z

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

AlCalzone · 2020-11-23T15:46:24Z

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

You can attach files too:

AlCalzone · 2020-11-23T15:50:39Z

@larstobi Ok the problem are the borked InfoReports the device sends. This is 100% an issue in the firmware. As soon as the driver asks for the parameter description, the device goes tits up and sends 256 (i guess) invalid info reports without any content. This causes the following queries to fail too.

larstobi · 2020-11-23T15:54:19Z

I see. Probably the certification process is a bit lacking...

The device kinda works in OpenZwave, the only thing that doesn't work is setting the temperature via Home Assistant. It could be related to an issue which is confirmed present in Z-TRM3, but I couldn't say for certain. OpenZWave/open-zwave#2458

I also have bought a Z-TRM3 and will replace the Z-TRM2 with that one soon.

Is this the sort of thing that will require device special handling to get stuff working?

AlCalzone · 2020-11-23T15:59:02Z

Is this the sort of thing that will require device special handling to get stuff working?

Yup. I would have to add a compatibility flag that can be used in config files telling the driver not to use the V3 command to query configuration info.

It could be related to an issue which is confirmed present in Z-TRM3

Might be. Make sure you install the custom firmware for that.

Shame that there is no good and good-looking thermostat for electrical floor heaters... My MCOHome thermostats frequently lock up and continue heating well past the setpoint 😖

robertsLando · 2020-11-23T16:02:56Z

Shame that there is no good and good-looking thermostat for electrical floor heaters... My MCOHome thermostats frequently lock up and continue heating well past the setpoint

Having same issues with other heatIt products

larstobi · 2020-11-23T16:13:40Z

As I understood it there's that fixed precision number for setpoint that's causing the issue.

AlCalzone · 2020-11-23T16:15:18Z

Yup but that is fixed in the "unofficial" firmware which HeatIt provide on their "official" website. Since zwave-js supports firmware updates, this is what I'd recommend before I have to waste development time on supporting bugged versions.

robertsLando · 2020-11-23T16:25:03Z

@larstobi Also please do it using zjs2m UI I mean send the frimware update, so you can tell me if it's working.

If the device explodes it means it's not working 😆

larstobi · 2020-11-23T16:51:48Z

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

AlCalzone · 2020-11-23T16:57:33Z

If the device explodes it means it's not working 😆

No guarantees 😬

node-zwave-js/packages/zwave-js/src/lib/node/Node.ts

Lines 2278 to 2285 in 51f484a

    
           	/** 
        
           	 * Starts an OTA firmware update process for this node. 
        
           	 * 
        
           	 * **WARNING: Use at your own risk! We don't take any responsibility if your devices don't work after an update.** 
        
           	 * 
        
           	 * @param data The firmware image 
        
           	 * @param target The firmware target (i.e. chip) to upgrade. 0 updates the Z-Wave chip, >=1 updates others if they exist 
        
           	 */

robertsLando · 2020-11-23T17:01:18Z

Actually I don't allow to specify the update target so it will update the chip by default

larstobi · 2020-11-23T17:10:59Z

Okay. I have included the Z-TRM3 now, and it's actually completed the Interview, which is an improvement on the Z-TRM2. It's unknown, though. Now, trying to find the new firmware and will try the zw2m way first.

larstobi · 2020-11-23T17:12:14Z

I can't imagine how all those commercial Z-Wave gateways handle all these device quirks. They should test devices better on different platforms!

robertsLando · 2020-11-23T17:13:26Z

I can't imagine how all those commercial Z-Wave gateways handle all these device quirks. They should test devices better on different platforms!

Me and @AlCalzone think the same, I dunno why and how this could happen on 'certified' devices

larstobi · 2020-11-23T17:18:28Z

I have tried to use the setpoint feature of the unknown Z-TRM3 before firmware update.

I changed the setpoint value to 21.0 in the UI and clicked send. The corresponding entries from the logs are:

17:16:28.596 DRIVER » [Node 055] [REQ] [SendData]
17:16:28.769 DRIVER » [Node 055] [REQ] [SendData]
17:16:29.084 CNTRLR   [Node 055] [~] [Thermostat Setpoint] setpoint[1]: 18.5 => 18.5    [Endpoint 1]
17:16:29.084 CNTRLR   [Node 055] [~] [Thermostat Setpoint] setpointScale[1]: [Endpoint 1] [internal]
17:16:29.085 DRIVER « [Node 055] [REQ] [ApplicationCommand]

What I find a bit weird is that it tries to update with the current setpoint rather than the new one that I typed into the box.

AlCalzone · 2020-11-23T17:35:59Z

[Node 055] [~] [Thermostat Setpoint] setpoint[1]: 18.5 => 18.5 [Endpoint 1]

That is the value update which happens after the report from the device. If you ~~increase the loglevel~~ don't just filter by the node id string, you will see how the correct setpoint is sent and the old one is reported.
(you can set the LOG_NODES env variable to 55 to limit logging to node 55)

larstobi · 2020-11-23T18:29:32Z

Good tip about LOG_NODES!

Also, firmware update didn't pan out.

17:39:51.746 DRIVER « [Node 055] [REQ] [ApplicationCommand]
17:39:51.747 CNTRLR » [Node 055] Sending firmware fragment 6638 / 6643
17:39:51.751 DRIVER » [Node 055] [REQ] [SendData]
17:39:51.810 DRIVER « [Node 055] [REQ] [ApplicationCommand]
17:39:51.811 CNTRLR » [Node 055] Sending firmware fragment 6639 / 6643
17:39:51.815 DRIVER » [Node 055] [REQ] [SendData]
17:39:51.875 DRIVER « [Node 055] [REQ] [ApplicationCommand]
17:39:51.876 CNTRLR » [Node 055] Sending firmware fragment 6640 / 6643
17:39:51.879 DRIVER » [Node 055] [REQ] [SendData]
17:39:51.939 DRIVER « [Node 055] [REQ] [ApplicationCommand]
17:39:51.940 CNTRLR » [Node 055] Sending firmware fragment 6641 / 6643
17:39:51.943 DRIVER » [Node 055] [REQ] [SendData]
17:39:52.003 DRIVER « [Node 055] [REQ] [ApplicationCommand]
17:39:52.004 CNTRLR » [Node 055] Sending firmware fragment 6642 / 6643
17:39:52.007 DRIVER » [Node 055] [REQ] [SendData]
17:39:52.066 DRIVER « [Node 055] [REQ] [ApplicationCommand]
17:39:52.067 CNTRLR » [Node 055] Sending firmware fragment 6643 / 6643
17:39:52.071 DRIVER » [Node 055] [REQ] [SendData]
17:39:58.640 DRIVER « [Node 055] [REQ] [ApplicationCommand]
17:39:58.641 CNTRLR « [Node 055] Firmware update failed with status Error_InsufficientMemory
17:40:17.870 CNTRLR   [Node 055] [~] [Thermostat Mode] mode: 1 => 1                     [Endpoint 1]
17:40:17.871 DRIVER « [Node 055] [REQ] [ApplicationCommand]
17:40:17.898 CNTRLR   [Node 055] [~] [Thermostat Setpoint] setpoint[1]: 18.5 => 18.5    [Endpoint 1]
17:40:17.898 CNTRLR   [Node 055] [~] [Thermostat Setpoint] setpointScale[1]: [Endpoint 1] [internal]
17:40:17.899 DRIVER « [Node 055] [REQ] [ApplicationCommand]
17:40:17.916 CNTRLR   [Node 055] [~] [Thermostat Operating State] state: 0 => 0         [Endpoint 1]

AlCalzone · 2020-11-23T18:46:08Z

Error_InsufficientMemory

That is a report by the node, I'm assuming that is not the correct firmware or it has the wrong format (some need to be converted first). @robertsLando how do you handle the firmware files?

For reference: This works with Aeotec devices:
https://github.com/AlCalzone/ioBroker.zwave2/blob/ad27caa8ed4aadfd8cb973db37ee7d2346bf3bf8/src/main.ts#L1155-L1189

and

https://github.com/AlCalzone/ioBroker.zwave2/blob/master/src/lib/firmwareUpdate.ts

robertsLando · 2020-11-23T19:42:24Z

I read the file as a binary buffer and I send it to the backend

https://github.com/zwave-js/zwavejs2mqtt/blob/master/src/components/ControlPanel.vue#L1229

https://github.com/zwave-js/zwavejs2mqtt/blob/master/src/App.vue#L144

https://github.com/zwave-js/zwavejs2mqtt/blob/master/lib/ZwaveClient.js#L1654

Is there something wrong? @AlCalzone

larstobi · 2020-11-23T20:10:58Z

The file I used is this one: https://drive.google.com/file/d/16RaxbnKDC9Mlqs2C6bUDNo9JDnm9cd75/view

It has a .otz filename ending. Not sure if it needs converting...

larstobi · 2020-11-25T14:24:12Z

It eventually got Complete, and I have now started FW update. Currently "Sending firmware fragment 641 / 2362"

larstobi · 2020-11-25T14:37:08Z

14:26:45.774 CNTRLR » [Node 055] Sending firmware fragment 2361 / 2362
14:26:45.778 DRIVER » [Node 055] [REQ] [SendData]
14:26:45.838 DRIVER « [Node 055] [REQ] [ApplicationCommand]
14:26:45.839 CNTRLR » [Node 055] Sending firmware fragment 2362 / 2362
14:26:45.842 DRIVER » [Node 055] [REQ] [SendData]
14:26:53.773 DRIVER « [Node 055] [REQ] [ApplicationCommand]
14:26:53.775 CNTRLR « [Node 055] Firmware update completed with status OK_RestartPending
14:26:53.775 CNTRLR   [Node 055] Firmware updated, scheduling interview in 30 ms...
14:26:53.843 CNTRLR   [Node 055] Beginning interview - last completed stage: None
14:26:53.843 CNTRLR   [Node 055] new node, doing a full interview...
14:26:53.843 CNTRLR » [Node 055] querying protocol info...
14:26:53.853 CNTRLR « [Node 055] received response for protocol info:
14:26:53.853 CNTRLR   [Node 055] Interview stage completed: ProtocolInfo
14:26:53.854 CNTRLR » [Node 055] pinging the node...
14:26:53.857 DRIVER » [Node 055] [REQ] [SendData]
14:27:01.568 CNTRLR   [Node 055] Node 55 did not respond after 1 attempts, it is presumed dead
14:27:01.572 CNTRLR   [Node 055] The node is now dead.
14:27:01.574 CNTRLR   [Node 055] ping failed: Failed to send the command after 1 attempts (Status No
14:27:01.574 CNTRLR » [Node 055] querying node info...
14:27:01.575 CNTRLR » [Node 055] pinging the node...
14:27:01.583 DRIVER » [Node 055] [REQ] [SendData]
14:27:08.933 CNTRLR   [Node 055] Node 55 did not respond after 1 attempts, it is presumed dead
14:27:08.934 CNTRLR   [Node 055] ping failed: Failed to send the command after 1 attempts (Status No
14:27:08.935 CNTRLR   [Node 055] Interview attempt (1/5) failed, node is dead.
14:27:43.169 CNTRLR   [Node 055] [+] [Thermostat Mode] mode: 1                          [Endpoint 1]
14:27:43.171 DRIVER « [Node 055] [REQ] [ApplicationCommand]
14:27:43.175 CNTRLR   [Node 055] The node is now alive.
14:27:43.176 CNTRLR   [Node 055] Beginning interview - last completed stage: ProtocolInfo
14:27:43.176 CNTRLR » [Node 055] pinging the node...
14:27:43.182 DRIVER » [Node 055] [REQ] [SendData]
14:27:43.195 CNTRLR   [Node 055] [Thermostat Setpoint] setpoint[1]: metadata updated    [Endpoint 1]
14:27:43.196 CNTRLR   [Node 055] [+] [Thermostat Setpoint] setpoint[1]: 18.5            [Endpoint 1]
14:27:43.197 CNTRLR   [Node 055] [+] [Thermostat Setpoint] setpointScale[1]: [Endpoint 1] [internal]
14:27:43.198 DRIVER « [Node 055] [REQ] [ApplicationCommand]
14:27:43.220 CNTRLR « [Node 055] ping successful
14:27:43.220 CNTRLR » [Node 055] querying node info...
14:27:43.225 DRIVER » [Node 055] [REQ] [RequestNodeInfo]

larstobi · 2020-11-25T14:42:37Z

And setpoint actually works, with a caveat. If I try to set "23.5" it gets converted to "23", and then the thermostat shows "23.0". The thermostat supports setting half degrees C from the arrow buttons.

AlCalzone · 2020-11-25T15:01:35Z

If I try to set "23.5" it gets converted to "23", and then the thermostat shows "23.0"

Could you show me that part in a log? Just to make sure that it is not a bug on my end.

larstobi · 2020-11-25T15:25:03Z


15:24:36.682 DRIVER » [Node 055] [REQ] [SendData]
15:24:36.717 DRIVER » [Node 055] [REQ] [SendData]
15:24:36.761 CNTRLR   [Node 055] [~] [Thermostat Setpoint] setpoint[1]: 23 => 23        [Endpoint 1]
15:24:36.762 CNTRLR   [Node 055] [~] [Thermostat Setpoint] setpointScale[1]: [Endpoint 1] [internal]
15:24:36.764 DRIVER « [Node 055] [REQ] [ApplicationCommand]

larstobi · 2020-11-25T15:25:54Z

And the same zwavejs2mqtt log:



  z2m:App Zwave api call: writeValue [
  {
    nodeId: 55,
    commandClass: 67,
    endpoint: 1,
    property: 'setpoint',
    propertyKey: 1
  },
  23
] +50s
  z2m:Zwave Node 55: value updated: 67-1-setpoint-1 23 => 23 +26s
  z2m:Zwave Success zwave api call writeValue  +3ms
???

larstobi · 2020-11-25T15:27:52Z

When I type 23.5 into the user parameter field called "undefined (55-67-1-setpoint-1)" and press the send arrow, it gets converted to an integer at once in the form field.

robertsLando · 2020-11-25T15:31:18Z

@larstobi Fixed in master

AlCalzone · 2020-11-25T15:34:56Z

oh, so it was a bug in z2m?

AlCalzone · 2020-11-25T15:36:57Z

15:24:36.682 DRIVER » [Node 055] [REQ] [SendData]
15:24:36.717 DRIVER » [Node 055] [REQ] [SendData]

For the reference: I usually need the log without filtered lines :) These two just tell me that some command was sent.

robertsLando · 2020-11-25T15:38:31Z

oh, so it was a bug in z2m?

Yep no worries it's already fixed. I have used a parseInt instead od Number to convet the value in the UI before sending it to the backend

AlCalzone · 2020-11-25T15:47:49Z

You might want to use parseFloat instead:

robertsLando · 2020-11-25T16:01:50Z

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

Cyberwizzard · 2020-11-28T07:56:44Z

As author of OpenZWave/open-zwave#2458 I'd like to point out that the whole goal of that pull request is to fix the Z-trm3 setpoint command without flashing firmware first.

If that PR would be included any Z-TRM3 would just work out of the box.

I'm not sure if that fix would also be applicable to the Z-TRM2 but since its relying on a compat flag in the device xml it should be easy to test for someone with that device.

AlCalzone · 2020-11-28T11:30:11Z

If that PR would be included any Z-TRM3 would just work out of the box.

I've thought about it too. But since zwave-js supports firmware updates without having to use dedicated software and re-including devices, that is currently my preferred solution so I can focus my time on issues that cannot be solved with a firmware update.

That being said, the above issue with Z-TRM2 should be fixed with a compat flag. And if anyone wants to fix the Z-TRM3 issue here with a compat flag too, feel free to open a PR.

larstobi · 2020-11-29T18:37:28Z

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

jkaberg · 2021-01-07T06:48:23Z

@AlCalzone A bit unsure reading the comments in this thread, did this ever get solved? I have https://github.com/zwave-js/zwavejs2mqtt/issues/160 (probably in the wrong place now I see - want me to move it?)

The z-trm2fx is "gen 2" of z-trm2 - and possibly with the same faults regarding the interview process? I'm running them with the very latest FW available (3.06).

AlCalzone · 2021-01-07T07:33:03Z

I think you're right. We got a bit off track with the firmware update for the ztrm3.

jkaberg · 2021-01-07T07:42:09Z

Let me know if you need anything!

I'm gonna provide you with a fresh pair of debug logs of the inclusion process for one of these sometime today (just gota figure out how to enable debug in zwavejs2mqtt Docker - setting it in the UI doesn't seem to work 😄)

robertsLando · 2021-01-07T08:22:16Z

just gota figure out how to enable debug in zwavejs2mqtt Docker

What?

jkaberg · 2021-01-07T08:25:18Z

@robertsLando I tried to enable debug in the UI (in the zwavejs2mqtt Docker) for both Zwave and Gateway, however STDOUT only showed me INFO?

larstobi · 2021-01-07T09:03:59Z

I returned my own Z-TRM2, in exchange for a Z-TRM3, so I can't help further, unfortunately.

robertsLando · 2021-01-07T09:14:29Z

@jkaberg Because actually I have no debug level logs. I have switched to winston logger recently and I still have to add verbose/debug logging

larstobi added the bug Something isn't working label Nov 17, 2020

larstobi assigned AlCalzone Nov 17, 2020

AlCalzone closed this as completed Nov 17, 2020

AlCalzone reopened this Nov 23, 2020

larstobi closed this as completed Nov 25, 2020

robertsLando reopened this Nov 25, 2020

larstobi closed this as completed Nov 29, 2020

AlCalzone reopened this Jan 7, 2021

jkaberg mentioned this issue Jan 7, 2021

[bug] Unable to properly include Thermofloor Z-TRM2FX thermostats #1309

Closed

3 tasks

AlCalzone mentioned this issue Jan 10, 2021

feat(config): add compat option skipConfigurationInfoQuery #1341

Merged

AlCalzone closed this as completed in #1341 Jan 11, 2021

Z-Wave driver not able to complete the interview with a Heatit Z-TRM2 device #1128

Z-Wave driver not able to complete the interview with a Heatit Z-TRM2 device #1128

Comments

larstobi commented Nov 17, 2020

larstobi commented Nov 17, 2020 • edited Loading

AlCalzone commented Nov 17, 2020

larstobi commented Nov 23, 2020

AlCalzone commented Nov 23, 2020

larstobi commented Nov 23, 2020 • edited Loading

robertsLando commented Nov 23, 2020 • edited Loading

AlCalzone commented Nov 23, 2020

AlCalzone commented Nov 23, 2020

larstobi commented Nov 23, 2020 • edited Loading

AlCalzone commented Nov 23, 2020 • edited Loading

robertsLando commented Nov 23, 2020 • edited Loading

larstobi commented Nov 23, 2020

AlCalzone commented Nov 23, 2020 • edited Loading

robertsLando commented Nov 23, 2020

larstobi commented Nov 23, 2020

AlCalzone commented Nov 23, 2020 • edited Loading

robertsLando commented Nov 23, 2020

larstobi commented Nov 23, 2020

larstobi commented Nov 23, 2020

robertsLando commented Nov 23, 2020 • edited Loading

larstobi commented Nov 23, 2020

AlCalzone commented Nov 23, 2020 • edited Loading

larstobi commented Nov 23, 2020

AlCalzone commented Nov 23, 2020 • edited Loading

robertsLando commented Nov 23, 2020 • edited Loading

larstobi commented Nov 23, 2020

larstobi commented Nov 25, 2020

larstobi commented Nov 25, 2020

larstobi commented Nov 25, 2020

AlCalzone commented Nov 25, 2020

larstobi commented Nov 25, 2020

larstobi commented Nov 25, 2020

larstobi commented Nov 25, 2020

robertsLando commented Nov 25, 2020

AlCalzone commented Nov 25, 2020

AlCalzone commented Nov 25, 2020

robertsLando commented Nov 25, 2020 • edited Loading

AlCalzone commented Nov 25, 2020

robertsLando commented Nov 25, 2020 • edited Loading

Cyberwizzard commented Nov 28, 2020

AlCalzone commented Nov 28, 2020

larstobi commented Nov 29, 2020

jkaberg commented Jan 7, 2021 • edited Loading

AlCalzone commented Jan 7, 2021

jkaberg commented Jan 7, 2021 • edited Loading

robertsLando commented Jan 7, 2021

jkaberg commented Jan 7, 2021

larstobi commented Jan 7, 2021

robertsLando commented Jan 7, 2021

larstobi commented Nov 17, 2020 •

edited

Loading

larstobi commented Nov 23, 2020 •

edited

Loading

robertsLando commented Nov 23, 2020 •

edited

Loading

larstobi commented Nov 23, 2020 •

edited

Loading

AlCalzone commented Nov 23, 2020 •

edited

Loading

robertsLando commented Nov 23, 2020 •

edited

Loading

AlCalzone commented Nov 23, 2020 •

edited

Loading

AlCalzone commented Nov 23, 2020 •

edited

Loading

robertsLando commented Nov 23, 2020 •

edited

Loading

AlCalzone commented Nov 23, 2020 •

edited

Loading

AlCalzone commented Nov 23, 2020 •

edited

Loading

robertsLando commented Nov 23, 2020 •

edited

Loading

robertsLando commented Nov 25, 2020 •

edited

Loading

robertsLando commented Nov 25, 2020 •

edited

Loading

jkaberg commented Jan 7, 2021 •

edited

Loading

jkaberg commented Jan 7, 2021 •

edited

Loading