Replace Failed Node does not re-inteview the new device

steve28 commented 3 years ago

Checklist:

[x] I am not using HomeAssistant. Or: a developer has told me to come here.
[x] I am not using ZWaveJS2MQTT. Or: a developer has told me to come here.
[x] I have checked the troubleshooting section and my problem is not described there.
[x] I have read the changelog and my problem was not mentioned there.

Describe the bug

When using "Replace Failed Node" in the control panel to replace a failed node with a different device (i.e., GE switch with an Inovelli switch), the new device is not interviewed upon inclusion. As a result, it still appears as the old device in the node list and thus has incorrect paramters/config/etc. until a manual re-interview is performed.

Device information I did two replacements of GE/Jasco 45609 on/off switches with Innovelli LZW31 dimmers. I saw the same behavior both times.

Did you change anything?

[ ] Yes: (please describe)
[x] No

Did this use to work before?

[x] Don't know, this is a new device
[ ] No, it never worked anywhere
[ ] Yes, in: (specify application with versions)

How are you using node-zwave-js

[ ] zwavejs2mqtt (latest) docker image
[ ] zwavejs2mqtt (dev) docker image
[ ] zwavejs2mqtt Manual Docker build
- node-zwave-js branch:
- zwavejs2mqtt branch:
[ ] ioBroker.zwave2 adapter
[ ] HomeAssistant version XYZ
[ ] Pkg
[ ] Manual Docker build
- node-zwave-js branch:
- zwavejs2mqtt branch:
[ ] node-red-contrib-zwave-js
- Module version (double click node):
[ ] Manually built (as described in the docs)
[ x] Other: I am using the latest HA add-on, but I am interacting with zwave-js through the control panel, not HA. To Reproduce

Steps to reproduce the behavior:

Have a node that's dead that you want to replace with a different device
open the dead node from the node list
click advanced
Under Failed Nodes, click Replace, answer "no" to secure inclusion.
Include the new node Additional context

Add any other context about the problem here.

Logfile: N/A

blhoward2 commented 3 years ago

Can you tell us what version of zwave-js is being used by the addon? Also, you put N/A for the log but a zwave log of the replace failed node and it skipping the interview would be helpful, at the debug or silly level.

steve28 commented 3 years ago

Can you tell us what version of zwave-js is being used by the addon?

version 6.6.3. I know 7.0.x is out, but they haven't updated the add-on yet.

I'll try to catch a log on my next switch update - hopefully tonight or tomorrow

steve28 commented 3 years ago

Here's the log - looks like it DOES interview:

16:28:43.186 CNTRLR » [Node 009] pinging the node...
16:28:47.316 CNTRLR   [Node 009] Node 9 did not respond after 1 attempts, it is presumed dead
16:28:47.317 CNTRLR   [Node 009] ping failed: Failed to send the command after 1 attempts (Status No
16:29:08.712 CNTRLR » [Node 009] Assigning return route to controller...
16:29:09.637 CNTRLR   [Node 009] Beginning interview - last completed stage: None
16:29:09.637 CNTRLR   [Node 009] new node, doing a full interview...
16:29:09.637 CNTRLR » [Node 009] querying protocol info...
16:29:09.654 CNTRLR « [Node 009] received response for protocol info:
16:29:09.681 CNTRLR   [Node 009] Interview stage completed: ProtocolInfo
16:29:09.681 CNTRLR » [Node 009] pinging the node...
16:29:09.732 CNTRLR « [Node 009] ping successful
16:29:09.733 CNTRLR » [Node 009] querying node info...
16:29:09.890 CNTRLR « [Node 009] node info received
16:29:09.917 CNTRLR   [Node 009] Interview stage completed: NodeInfo
16:29:09.918 CNTRLR » [Node 009] querying securely supported commands...
16:29:20.251 CNTRLR   [Node 009] Timed out while waiting for a response from the node
16:29:20.252 CNTRLR   [Node 009] The node is not included securely. Continuing interview non-securel
16:29:20.348 CNTRLR   [Node 009] ManufacturerSpecificCC: doing a complete interview...
16:29:20.349 CNTRLR » [Node 009] querying manufacturer information...
16:29:20.523 CNTRLR « [Node 009] received response for manufacturer information:
16:29:20.552 CNTRLR   [Node 009] VersionCC: doing a complete interview...
16:29:20.552 CNTRLR » [Node 009] querying node versions...
16:29:20.709 CNTRLR « [Node 009] received response for node versions:
16:29:20.709 CNTRLR » [Node 009] querying CC versions...
16:29:20.709 CNTRLR » [Node 009]   querying the CC version for Multilevel Switch...
16:29:20.890 CNTRLR   [Node 009]   supports CC Multilevel Switch (0x26) in version 2
16:29:20.891 CNTRLR   [Node 009]   skipping query for All Switch (0x27) because max implemented vers
16:29:20.891 CNTRLR » [Node 009]   querying the CC version for Z-Wave Plus Info...
16:29:21.080 CNTRLR   [Node 009]   supports CC Z-Wave Plus Info (0x5e) in version 2
16:29:21.080 CNTRLR » [Node 009]   querying the CC version for Configuration...
16:29:21.270 CNTRLR   [Node 009]   supports CC Configuration (0x70) in version 1
16:29:21.270 CNTRLR » [Node 009]   querying the CC version for Association...
16:29:21.460 CNTRLR   [Node 009]   supports CC Association (0x85) in version 2
16:29:21.460 CNTRLR » [Node 009]   querying the CC version for Association Group Information...
16:29:21.650 CNTRLR   [Node 009]   supports CC Association Group Information (0x59) in version 1
16:29:21.650 CNTRLR   [Node 009]   skipping query for Transport Service (0x55) because max implement
16:29:21.651 CNTRLR » [Node 009]   querying the CC version for Version...
16:29:21.840 CNTRLR   [Node 009]   supports CC Version (0x86) in version 2
16:29:21.840 CNTRLR » [Node 009]   querying the CC version for Manufacturer Specific...
16:29:22.089 CNTRLR   [Node 009]   supports CC Manufacturer Specific (0x72) in version 2
16:29:22.090 CNTRLR   [Node 009]   skipping query for Device Reset Locally (0x5a) because max implem
16:29:22.090 CNTRLR   [Node 009]   skipping query for Powerlevel (0x73) because max implemented vers
16:29:22.090 CNTRLR   [Node 009]   skipping query for Security (0x98) because max implemented versio
16:29:22.090 CNTRLR   [Node 009]   skipping query for Security 2 (0x9f) because max implemented vers
16:29:22.090 CNTRLR   [Node 009]   skipping query for Supervision (0x6c) because max implemented ver
16:29:22.090 CNTRLR » [Node 009]   querying the CC version for Protection...
16:29:22.379 CNTRLR   [Node 009]   supports CC Protection (0x75) in version 2
16:29:22.380 CNTRLR   [Node 009]   skipping query for Application Status (0x22) because max implemen
16:29:22.380 CNTRLR » [Node 009]   querying the CC version for Firmware Update Meta Data...
16:29:22.657 CNTRLR   [Node 009]   supports CC Firmware Update Meta Data (0x7a) in version 4
16:29:22.657 CNTRLR   [Node 009] trying to load device config
16:29:22.677 CNTRLR   [Node 009] device config loaded
16:29:22.697 CNTRLR   [Node 009] ZWavePlusCC: doing a complete interview...
16:29:22.697 CNTRLR » [Node 009] querying Z-Wave+ information...
16:29:22.842 CNTRLR « [Node 009] received response for Z-Wave+ information:
16:29:22.844 CNTRLR   [Node 009] MultilevelSwitchCC: doing a complete interview...
16:29:22.848 CNTRLR » [Node 009] requesting current switch state...
16:29:23.089 CNTRLR   [Node 009] ConfigurationCC: Loading configuration parameters from device confi
16:29:23.108 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#1 value...
16:29:23.335 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#1 has value: 3
16:29:23.336 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#2 value...
16:29:23.549 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#2 has value: 101
16:29:23.549 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#3 value...
16:29:23.734 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#3 has value: 101
16:29:23.735 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#4 value...
16:29:23.924 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#4 has value: 101
16:29:23.924 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#5 value...
16:29:24.112 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#5 has value: 10
16:29:24.112 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#6 value...
16:29:24.303 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#6 has value: 99
16:29:24.303 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#7 value...
16:29:24.493 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#7 has value: 0
16:29:24.493 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#8 value...
16:29:24.682 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#8 has value: 0
16:29:24.682 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#9 value...
16:29:24.893 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#9 has value: 0
16:29:24.894 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#10 value...
16:29:25.193 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#10 has value: 0
16:29:25.193 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#11 value...
16:29:25.383 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#11 has value: 100
16:29:25.383 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#13 value...
16:29:25.572 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#13 has value: 170
16:29:25.573 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#14 value...
16:29:27.028 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#14 has value: 5
16:29:27.029 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#15 value...
16:29:37.775 CNTRLR   [Node 009] Timed out while waiting for a response from the node
16:29:37.775 CNTRLR « [Node 009] received no value for parameter zwave-js/node-zwave-js#15
16:29:37.775 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#17 value...
16:29:38.601 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#17 has value: 3
16:29:38.601 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#21 value...
16:29:41.877 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#21 has value: 0
16:29:41.877 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#22 value...
16:29:42.274 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#22 has value: 0
16:29:42.275 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#51 value...
16:29:42.551 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#51 has value: 1
16:29:42.552 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#52 value...
16:29:54.119 CNTRLR   [Node 009] Timed out while waiting for a response from the node
16:29:54.119 CNTRLR « [Node 009] received no value for parameter zwave-js/node-zwave-js#52
16:29:54.119 CNTRLR » [Node 009] querying parameter zwave-js/node-zwave-js#12 value...
16:29:54.697 CNTRLR « [Node 009] parameter zwave-js/node-zwave-js#12 has value: 15
16:29:54.721 CNTRLR   [Node 009] ProtectionCC: doing a complete interview...
16:29:54.722 CNTRLR » [Node 009] querying protection capabilities...
16:29:54.968 CNTRLR « [Node 009] received protection capabilities:
16:29:54.968 CNTRLR » [Node 009] querying protection status...
16:29:55.414 CNTRLR « [Node 009] received protection status:
16:29:55.436 CNTRLR   [Node 009] AssociationCC: doing a complete interview...
16:29:55.437 CNTRLR » [Node 009] querying number of association groups...
16:29:57.448 CNTRLR « [Node 009] supports 4 association groups
16:29:57.448 CNTRLR » [Node 009] querying association group zwave-js/node-zwave-js#1...
16:29:57.676 CNTRLR « [Node 009] received information for association group zwave-js/node-zwave-js#1:
16:29:57.676 CNTRLR » [Node 009] querying association group zwave-js/node-zwave-js#2...
16:29:57.897 CNTRLR « [Node 009] received information for association group zwave-js/node-zwave-js#2:
16:29:57.897 CNTRLR » [Node 009] querying association group zwave-js/node-zwave-js#3...
16:29:58.206 CNTRLR « [Node 009] received information for association group zwave-js/node-zwave-js#3:
16:29:58.206 CNTRLR » [Node 009] querying association group zwave-js/node-zwave-js#4...
16:29:58.497 CNTRLR « [Node 009] received information for association group zwave-js/node-zwave-js#4:
16:29:58.498 CNTRLR » [Node 009] Controller missing from lifeline group zwave-js/node-zwave-js#1, assigning ourselves...
16:29:58.938 CNTRLR   [Node 009] AssociationGroupInfoCC: doing a complete interview...
16:29:58.938 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#1: Querying name...
16:29:59.130 CNTRLR « [Node 009] Association group zwave-js/node-zwave-js#1 has name "Lifeline"
16:29:59.130 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#1: Querying info...
16:29:59.421 CNTRLR « [Node 009] Received info for association group zwave-js/node-zwave-js#1:
16:29:59.421 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#1: Querying command list...
16:29:59.732 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#2: Querying name...
16:30:00.036 CNTRLR « [Node 009] Association group zwave-js/node-zwave-js#2 has name "On/Off Control"
16:30:00.036 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#2: Querying info...
16:30:00.258 CNTRLR « [Node 009] Received info for association group zwave-js/node-zwave-js#2:
16:30:00.258 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#2: Querying command list...
16:30:00.546 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#3: Querying name...
16:30:00.780 CNTRLR « [Node 009] Association group zwave-js/node-zwave-js#3 has name "Switch Multilevel Set"
16:30:00.780 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#3: Querying info...
16:30:01.045 CNTRLR « [Node 009] Received info for association group zwave-js/node-zwave-js#3:
16:30:01.045 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#3: Querying command list...
16:30:01.659 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#4: Querying name...
16:30:01.850 CNTRLR « [Node 009] Association group zwave-js/node-zwave-js#4 has name "Sw Multi Start/Stop"
16:30:01.850 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#4: Querying info...
16:30:02.097 CNTRLR « [Node 009] Received info for association group zwave-js/node-zwave-js#4:
16:30:02.097 CNTRLR » [Node 009] Association group zwave-js/node-zwave-js#4: Querying command list...
16:30:02.307 CNTRLR   [Node 009] Interview stage completed: CommandClasses
16:30:02.307 CNTRLR   [Node 009] Interview stage completed: OverwriteConfig
16:30:02.307 CNTRLR » [Node 009] requesting node neighbors...
16:30:02.317 CNTRLR « [Node 009]   node neighbors received: 2, 4, 20, 34, 35, 43, 53, 67, 73
16:30:02.317 CNTRLR   [Node 009] Interview stage completed: Neighbors
16:30:02.317 CNTRLR   [Node 009] Interview completed
16:30:02.317 CNTRLR   [Node 009] The node is ready to be used

It must be some display issue where the CP does not update. In this case, I had left the CP for a while (5-10 min) and came back in, then it had populated. I know the first two I replace there was no amount of refresh/reload of the browser that would show me the new info or config params.

blhoward2 commented 3 years ago

@robertsLando Thoughts?

robertsLando commented 3 years ago

The data are sent as soon as I receive them from Zwavejs so excluded any kind of network delays this could just be something on zwavejs side, maybe the interview takes a lot before reaching the ready status, this can be normal with some devices

AlCalzone commented 3 years ago

Can you share the full logfile? I wonder why we try to ping the device first.

steve28 commented 3 years ago

Attached: zwavejs_355 2.log

The one with debug on starts at line 45061, where I replace Node 009.

AlCalzone commented 3 years ago

Ok, the 2nd ping is purely "cosmetical" - shouldn't hurt. I was confused by the 1st one but that is done to ensure the node is really failed.

AlCalzone commented 3 years ago

@robertsLando The interview takes about a minute here but looks pretty normal. I'll let you decide - from the zwave-js perspective this looks normal.

robertsLando commented 3 years ago

@steve28 could you also attach zweavejs2mqtt logs please? I would like to see on my side what's going on

steve28 commented 3 years ago

Attached. The action starts at 2021-03-27 16:28:43.184

I included a bit before, and for about 30 min after.
zwavejs2mqtt.log

robertsLando commented 3 years ago

2021-03-27 16:28:43.184 INFO ZWAVE: Calling api replaceFailedNode with args: [ 9, false, [length]: 2 ]
2021-03-27 16:28:47.434 INFO ZWAVE: Controller status: Non-secure inclusion started
2021-03-27 16:28:47.437 INFO ZWAVE: Success zwave api call replaceFailedNode { success: true, message: 'Success zwave api call', result: true }
2021-03-27 16:29:08.685 INFO ZWAVE: Controller status: Inclusion stopped
2021-03-27 16:29:08.688 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.689 INFO ZWAVE: Node 9: value removed: 114-0-manufacturerId
2021-03-27 16:29:08.690 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.691 INFO ZWAVE: Node 9: value removed: 114-0-productType
2021-03-27 16:29:08.691 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.692 INFO ZWAVE: Node 9: value removed: 114-0-productId
2021-03-27 16:29:08.693 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.693 INFO ZWAVE: Node 9: value removed: 134-0-libraryType
2021-03-27 16:29:08.694 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.694 INFO ZWAVE: Node 9: value removed: 134-0-protocolVersion
2021-03-27 16:29:08.695 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.695 INFO ZWAVE: Node 9: value removed: 134-0-firmwareVersions
2021-03-27 16:29:08.696 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.697 INFO ZWAVE: Node 9: value removed: 37-0-currentValue
2021-03-27 16:29:08.698 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.698 INFO ZWAVE: Node 9: value removed: 37-0-targetValue
2021-03-27 16:29:08.699 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.699 INFO ZWAVE: Node 9: value removed: 112-0-3
2021-03-27 16:29:08.700 INFO ZWAVE: Node 9: metadata updated: 112-0-3
2021-03-27 16:29:08.701 INFO ZWAVE: ValueRemoved: no such node: 9 error
2021-03-27 16:29:08.701 INFO ZWAVE: Node 9: value removed: 112-0-4
2021-03-27 16:29:08.702 INFO ZWAVE: Node 9: metadata updated: 112-0-4
2021-03-27 16:29:08.703 INFO ZWAVE: Node 9: removed
2021-03-27 16:29:08.704 INFO ZWAVE: Node removed 9
2021-03-27 16:29:09.642 INFO ZWAVE: Node 9: added
2021-03-27 16:29:09.644 DEBUG ZWAVE: Node 9 has been added to nodes array
2021-03-27 16:29:09.645 DEBUG ZWAVE: Binding to node 9 events
2021-03-27 16:29:20.518 INFO ZWAVE: Node 9: value added: 114-0-manufacturerId => 798
2021-03-27 16:29:20.520 INFO ZWAVE: Node 9: value added: 114-0-productType => 3
2021-03-27 16:29:20.521 INFO ZWAVE: Node 9: value added: 114-0-productId => 1
2021-03-27 16:29:20.703 INFO ZWAVE: Node 9: value added: 134-0-libraryType => 3
2021-03-27 16:29:20.704 INFO ZWAVE: Node 9: value added: 134-0-protocolVersion => 6.4
2021-03-27 16:29:20.705 INFO ZWAVE: Node 9: value added: 134-0-firmwareVersions => 1.48
2021-03-27 16:29:22.845 INFO ZWAVE: Node 9: metadata updated: 38-0-Up
2021-03-27 16:29:22.847 INFO ZWAVE: Node 9: metadata updated: 38-0-Down
2021-03-27 16:29:23.084 INFO ZWAVE: Node 9: value added: 38-0-targetValue => undefined
2021-03-27 16:29:23.086 INFO ZWAVE: Node 9: value added: 38-0-currentValue => 0
2021-03-27 16:29:23.090 INFO ZWAVE: Node 9: metadata updated: 112-0-1
2021-03-27 16:29:23.092 INFO ZWAVE: Node 9: metadata updated: 112-0-2
2021-03-27 16:29:23.093 INFO ZWAVE: Node 9: metadata updated: 112-0-3
2021-03-27 16:29:23.094 INFO ZWAVE: Node 9: metadata updated: 112-0-4
2021-03-27 16:29:23.094 INFO ZWAVE: Node 9: metadata updated: 112-0-5
2021-03-27 16:29:23.095 INFO ZWAVE: Node 9: metadata updated: 112-0-6
2021-03-27 16:29:23.096 INFO ZWAVE: Node 9: metadata updated: 112-0-7
2021-03-27 16:29:23.097 INFO ZWAVE: Node 9: metadata updated: 112-0-8
2021-03-27 16:29:23.097 INFO ZWAVE: Node 9: metadata updated: 112-0-9
2021-03-27 16:29:23.098 INFO ZWAVE: Node 9: metadata updated: 112-0-10
2021-03-27 16:29:23.099 INFO ZWAVE: Node 9: metadata updated: 112-0-11
2021-03-27 16:29:23.099 INFO ZWAVE: Node 9: metadata updated: 112-0-13
2021-03-27 16:29:23.100 INFO ZWAVE: Node 9: metadata updated: 112-0-14
2021-03-27 16:29:23.101 INFO ZWAVE: Node 9: metadata updated: 112-0-15
2021-03-27 16:29:23.101 INFO ZWAVE: Node 9: metadata updated: 112-0-17
2021-03-27 16:29:23.102 INFO ZWAVE: Node 9: metadata updated: 112-0-21
2021-03-27 16:29:23.103 INFO ZWAVE: Node 9: metadata updated: 112-0-22
2021-03-27 16:29:23.103 INFO ZWAVE: Node 9: metadata updated: 112-0-51
2021-03-27 16:29:23.104 INFO ZWAVE: Node 9: metadata updated: 112-0-52
2021-03-27 16:29:23.105 INFO ZWAVE: Node 9: metadata updated: 112-0-12-1
2021-03-27 16:29:23.106 INFO ZWAVE: Node 9: metadata updated: 112-0-12-2
2021-03-27 16:29:23.106 INFO ZWAVE: Node 9: metadata updated: 112-0-12-4
2021-03-27 16:29:23.107 INFO ZWAVE: Node 9: metadata updated: 112-0-12-8
2021-03-27 16:29:23.333 INFO ZWAVE: Node 9: value added: 112-0-1 => 3
2021-03-27 16:29:23.547 INFO ZWAVE: Node 9: value added: 112-0-2 => 101
2021-03-27 16:29:23.730 INFO ZWAVE: Node 9: value added: 112-0-3 => 101
2021-03-27 16:29:23.922 INFO ZWAVE: Node 9: value added: 112-0-4 => 101
2021-03-27 16:29:24.110 INFO ZWAVE: Node 9: value added: 112-0-5 => 10
2021-03-27 16:29:24.300 INFO ZWAVE: Node 9: value added: 112-0-6 => 99
2021-03-27 16:29:24.491 INFO ZWAVE: Node 9: value added: 112-0-7 => 0
2021-03-27 16:29:24.680 INFO ZWAVE: Node 9: value added: 112-0-8 => 0
2021-03-27 16:29:24.890 INFO ZWAVE: Node 9: value added: 112-0-9 => 0
2021-03-27 16:29:25.002 INFO ZWAVE: Node 16: value updated: 37-0-currentValue false => false
2021-03-27 16:29:25.191 INFO ZWAVE: Node 9: value added: 112-0-10 => 0
2021-03-27 16:29:25.381 INFO ZWAVE: Node 9: value added: 112-0-11 => 100
2021-03-27 16:29:25.571 INFO ZWAVE: Node 9: value added: 112-0-13 => 170
2021-03-27 16:29:25.898 INFO ZWAVE: Node 9: value added: 112-0-14 => 5
2021-03-27 16:29:26.331 INFO ZWAVE: Node 9: value updated: 112-0-14 5 => 5
2021-03-27 16:29:26.786 INFO ZWAVE: Node 9: value updated: 112-0-14 5 => 5
2021-03-27 16:29:27.027 INFO ZWAVE: Node 9: value updated: 112-0-14 5 => 5
2021-03-27 16:29:27.101 INFO ZWAVE: Node 9: value updated: 112-0-14 5 => 5
2021-03-27 16:29:27.338 INFO ZWAVE: Node 9: value added: 112-0-15 => 1
2021-03-27 16:29:38.596 INFO ZWAVE: Node 9: value added: 112-0-17 => 3
2021-03-27 16:29:39.169 INFO ZWAVE: Node 9: value added: 112-0-21 => 0
2021-03-27 16:29:39.740 INFO ZWAVE: Node 9: value updated: 112-0-21 0 => 0
2021-03-27 16:29:40.531 INFO ZWAVE: Node 51: value updated: 32-0-currentValue 255 => 0
2021-03-27 16:29:41.366 INFO ZWAVE: Node 51: value updated: 32-0-currentValue 0 => 0
2021-03-27 16:29:41.790 INFO ZWAVE: Node 51: value updated: 113-0-Home Security-Motion sensor status 8 => 0
2021-03-27 16:29:41.875 INFO ZWAVE: Node 9: value updated: 112-0-21 0 => 0
2021-03-27 16:29:42.272 INFO ZWAVE: Node 9: value added: 112-0-22 => 0
2021-03-27 16:29:42.550 INFO ZWAVE: Node 9: value added: 112-0-51 => 1
2021-03-27 16:29:44.109 INFO ZWAVE: Node 9: value added: 112-0-52 => 0
2021-03-27 16:29:45.837 INFO ZWAVE: Node 36: metadata updated: 48-0-Any
2021-03-27 16:29:45.839 INFO ZWAVE: Node 36: value updated: 48-0-Any true => false
2021-03-27 16:29:46.526 INFO ZWAVE: Node 42: value updated: 113-0-Home Security-Sensor status 2 => 0
2021-03-27 16:29:54.694 INFO ZWAVE: Node 9: value added: 112-0-12-1 => 1
2021-03-27 16:29:54.695 INFO ZWAVE: Node 9: value added: 112-0-12-2 => 1
2021-03-27 16:29:54.695 INFO ZWAVE: Node 9: value added: 112-0-12-4 => 1
2021-03-27 16:29:54.696 INFO ZWAVE: Node 9: value added: 112-0-12-8 => 1
2021-03-27 16:29:54.964 INFO ZWAVE: Node 9: metadata updated: 117-0-local
2021-03-27 16:29:54.965 INFO ZWAVE: Node 9: metadata updated: 117-0-rf
2021-03-27 16:29:55.411 INFO ZWAVE: Node 9: value added: 117-0-local => 0
2021-03-27 16:29:55.412 INFO ZWAVE: Node 9: value added: 117-0-rf => 0
2021-03-27 16:30:01.417 INFO APP: GET /api/store 200 8.205 ms - 1339
2021-03-27 16:30:02.324 INFO ZWAVE: Node 9: value added 9-38-0-targetValue => undefined
2021-03-27 16:30:02.325 INFO ZWAVE: Node 9: value added 9-38-0-duration => [Duration: undefinedseconds]
2021-03-27 16:30:02.329 INFO ZWAVE: Node 9: value added 9-38-0-currentValue => 0
2021-03-27 16:30:02.330 INFO ZWAVE: Node 9: value added 9-38-0-Up => undefined
2021-03-27 16:30:02.330 INFO ZWAVE: Node 9: value added 9-38-0-Down => undefined
2021-03-27 16:30:02.331 INFO ZWAVE: Node 9: value added 9-112-0-1 => 3
2021-03-27 16:30:02.332 INFO ZWAVE: Node 9: value added 9-112-0-2 => 101
2021-03-27 16:30:02.332 INFO ZWAVE: Node 9: value added 9-112-0-3 => 101
2021-03-27 16:30:02.333 INFO ZWAVE: Node 9: value added 9-112-0-4 => 101
2021-03-27 16:30:02.334 INFO ZWAVE: Node 9: value added 9-112-0-5 => 10
2021-03-27 16:30:02.334 INFO ZWAVE: Node 9: value added 9-112-0-6 => 99
2021-03-27 16:30:02.335 INFO ZWAVE: Node 9: value added 9-112-0-7 => 0
2021-03-27 16:30:02.336 INFO ZWAVE: Node 9: value added 9-112-0-8 => 0
2021-03-27 16:30:02.336 INFO ZWAVE: Node 9: value added 9-112-0-9 => 0
2021-03-27 16:30:02.337 INFO ZWAVE: Node 9: value added 9-112-0-10 => 0
2021-03-27 16:30:02.337 INFO ZWAVE: Node 9: value added 9-112-0-11 => 100
2021-03-27 16:30:02.338 INFO ZWAVE: Node 9: value added 9-112-0-13 => 170
2021-03-27 16:30:02.339 INFO ZWAVE: Node 9: value added 9-112-0-14 => 5
2021-03-27 16:30:02.339 INFO ZWAVE: Node 9: value added 9-112-0-15 => 1
2021-03-27 16:30:02.340 INFO ZWAVE: Node 9: value added 9-112-0-17 => 3
2021-03-27 16:30:02.341 INFO ZWAVE: Node 9: value added 9-112-0-21 => 0
2021-03-27 16:30:02.341 INFO ZWAVE: Node 9: value added 9-112-0-22 => 0
2021-03-27 16:30:02.341 INFO ZWAVE: Node 9: value added 9-112-0-51 => 1
2021-03-27 16:30:02.342 INFO ZWAVE: Node 9: value added 9-112-0-52 => 0
2021-03-27 16:30:02.342 INFO ZWAVE: Node 9: value added 9-112-0-12-1 => 1
2021-03-27 16:30:02.343 INFO ZWAVE: Node 9: value added 9-112-0-12-2 => 1
2021-03-27 16:30:02.343 INFO ZWAVE: Node 9: value added 9-112-0-12-4 => 1
2021-03-27 16:30:02.344 INFO ZWAVE: Node 9: value added 9-112-0-12-8 => 1
2021-03-27 16:30:02.344 INFO ZWAVE: Node 9: value added 9-134-0-libraryType => 3
2021-03-27 16:30:02.345 INFO ZWAVE: Node 9: value added 9-134-0-protocolVersion => 6.4
2021-03-27 16:30:02.345 INFO ZWAVE: Node 9: value added 9-134-0-firmwareVersions => 1.48
2021-03-27 16:30:02.346 INFO ZWAVE: Node 9: value added 9-134-0-hardwareVersion => undefined
2021-03-27 16:30:02.346 INFO ZWAVE: Node 9: value added 9-114-0-manufacturerId => 798
2021-03-27 16:30:02.347 INFO ZWAVE: Node 9: value added 9-114-0-productType => 3
2021-03-27 16:30:02.347 INFO ZWAVE: Node 9: value added 9-114-0-productId => 1
2021-03-27 16:30:02.348 INFO ZWAVE: Node 9: value added 9-117-0-local => 0
2021-03-27 16:30:02.348 INFO ZWAVE: Node 9: value added 9-117-0-rf => 0
2021-03-27 16:30:02.349 INFO ZWAVE: Node 9: value added 9-117-0-exclusiveControlNodeId => undefined
2021-03-27 16:30:02.350 INFO ZWAVE: Node 9: value added 9-117-0-timeout => undefined
2021-03-27 16:30:02.351 INFO ZWAVE: Node 9 ready: Inovelli - LZW31 (Black Series Dimmer)
2021-03-27 16:30:02.359 INFO ZWAVE: Node 9: interview completed, all values are updated

It seems everything looks good here, what do you see in the UI? Except the value removed event

robertsLando commented 3 years ago

Just to be sure I would like you to test this with latest 3.0.2

steve28 commented 3 years ago

Over the weekend I upgraded 4 of my 8 year old GE switches to the Inovelli dimmers. My method was:

Replace the old switch with the new one in the wall
Do a Check Failed Node so old node would get marked as dead
Do Replace Failed Node to include the new switch

After I did step 3, the row for that node in the UI would still show the old information. Even clicking on the turn-down arrow, everything was the old information. I reloaded the web page (refresh browser) - still the old info. So I then did a re-interview and that updated the UI to show the new node information.

For 3 of the 4 switches the above is what happened. On the 4th switch, which is the one I captured the logs for, the same thing happened. This time, however, I let it sit for a while... maybe 15-30 min because I got called away. When I came back, the new information was populated in the UI. Because I wasn't watching, I don't know how long that took.

So maybe this a "nothing to see here" thing....

robertsLando commented 3 years ago

:man_shrugging: :rofl:

AlCalzone commented 3 years ago

Interviews can take a while, depending on how much info gets queried.

steve28 commented 3 years ago

I'm ok with closing this... It might be some time until I will attempt this again and it looks like it's a non-event.

zwave-js / zwave-js-ui

Replace Failed Node does not re-inteview the new device #975