"Timed out while waiting for a response from the node" - remedies?

Configuration Z-Wave
1

EDIT: Is this such a freak occurrence that I should just give up? No responses here, and I’m googling my fingers off finding nothing… not complaining, I’m new to HA and would just really like to know if this is in the realm of “possibly fixable”, or if I need to make other IoT decisions.

OK, so… in the ongoing saga of devices which register, but contain no entities, I seem to have found the problem, see: the header of this topic :grin:

The only change I can see after acquiring a USB extension cable & improving connectivity is that, in stead of a single “Timed out while waiting for a response” message, there’s several (oh, and also, under “Z-Wave Info”, the device is listed as “Ready: Yes” instead of “No”).

Searching the forums, the most similar, reasonably recent situation I’ve found is this one, in which the poster mentions the network key. This is well above my skill level, but is it something that might be relevant to my issue?

Inclusion debug log below, the result is the same when re-interviewing. Healing also doesn’t help, and I’ve reloaded Z-Wave, restarted HASS, and even rebooted the Pi, also to no avail.

Thanks in advance for any help!! :pray:

(If bumping my issue in this way is frowned upon, just let me know; I am simply trying to narrow my questions & make them as accurate as I can :slight_smile:)

Subscribed to Z-Wave JS Log Messages…
2022-10-29T06:40:05.025Z CNTRLR » [Node 021] pinging the node...
2022-10-29T06:40:05.040Z SERIAL » 0x01080013150100254693                                              (10 bytes)
2022-10-29T06:40:05.042Z DRIVER » [Node 021] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      70
                                  └─[NoOperationCC]
2022-10-29T06:40:05.045Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:05.050Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-10-29T06:40:05.051Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:05.053Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-10-29T06:40:06.116Z SERIAL « 0x010700134601006bc7                                                 (9 bytes)
2022-10-29T06:40:06.119Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:06.121Z DRIVER « [REQ] [SendData]
                                    callback id:     70
                                    transmit status: NoAck
2022-10-29T06:40:06.134Z CNTRLR   [Node 021] The node did not respond after 1 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2022-10-29T06:40:06.135Z CNTRLR   [Node 021] The node is now asleep.
2022-10-29T06:40:06.145Z CNTRLR   [Node 021] ping failed: Failed to send the command after 1 attempts (Status No
                                  Ack) (ZW0204)
2022-10-29T06:40:06.153Z SERIAL » 0x010500611547c9                                                     (7 bytes)
2022-10-29T06:40:06.154Z DRIVER » [REQ] [RemoveFailedNode]
                                    payload: 0x1547
2022-10-29T06:40:06.157Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:06.163Z SERIAL « 0x01040161009b                                                       (6 bytes)
2022-10-29T06:40:06.165Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:06.166Z DRIVER « [RES] [RemoveFailedNode]
                                    payload: 0x00
2022-10-29T06:40:07.084Z SERIAL « 0x010500614701dd                                                     (7 bytes)
2022-10-29T06:40:07.088Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:07.090Z DRIVER « [REQ] [RemoveFailedNode]
                                    payload: 0x4701
2022-10-29T06:40:07.101Z CNTRLR   [Node 021] [-] [Manufacturer Specific] manufacturerId (was 2)     [Endpoint 0]
2022-10-29T06:40:07.103Z CNTRLR   [Node 021] [Manufacturer Specific] manufacturerId: metadata updat [Endpoint 0]
                                  ed
2022-10-29T06:40:07.105Z CNTRLR   [Node 021] [-] [Manufacturer Specific] productType (was 32773)    [Endpoint 0]
2022-10-29T06:40:07.107Z CNTRLR   [Node 021] [Manufacturer Specific] productType: metadata updated  [Endpoint 0]
2022-10-29T06:40:07.109Z CNTRLR   [Node 021] [-] [Manufacturer Specific] productId (was 2)          [Endpoint 0]
2022-10-29T06:40:07.110Z CNTRLR   [Node 021] [Manufacturer Specific] productId: metadata updated    [Endpoint 0]
2022-10-29T06:40:07.112Z CNTRLR   [Node 021] [-] [Manufacturer Specific] interviewComple [Endpoint 0] [internal]
                                  te (was true)
2022-10-29T06:40:07.113Z CNTRLR   [Node 021] [-] [Version] interviewComplete (was true)  [Endpoint 0] [internal]
2022-10-29T06:40:07.115Z CNTRLR   [Node 021] [-] [Manufacturer Proprietary] interviewCom [Endpoint 0] [internal]
                                  plete (was true)
2022-10-29T06:40:08.821Z CNTRLR   Starting inclusion process with strategy Default...
2022-10-29T06:40:08.833Z SERIAL » 0x0105004ac14839                                                     (7 bytes)
2022-10-29T06:40:08.835Z DRIVER » [REQ] [AddNodeToNetwork]
                                    node type:    Any
                                    high power:   true
                                    network wide: true
                                    callback id:  72
2022-10-29T06:40:08.838Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:08.840Z SERIAL « 0x0107004a48010000fb                                                 (9 bytes)
2022-10-29T06:40:08.842Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:08.845Z DRIVER « [REQ] [AddNodeToNetwork]
                                    status:      Ready
                                    callback id: 72
2022-10-29T06:40:08.851Z CNTRLR   The controller is now ready to add nodes
2022-10-29T06:40:11.246Z SERIAL « 0x010c004a48021505040804917208                                      (14 bytes)
2022-10-29T06:40:11.250Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:11.252Z DRIVER « [REQ] [AddNodeToNetwork]
                                    status:      NodeFound
                                    callback id: 72
2022-10-29T06:40:11.258Z DRIVER   handling request AddNodeToNetwork (74)
2022-10-29T06:40:11.258Z DRIVER     1 handler registered!
2022-10-29T06:40:11.259Z DRIVER     invoking handler #0
2022-10-29T06:40:11.260Z CNTRLR   handling add node request (status = NodeFound)
2022-10-29T06:40:11.262Z SERIAL « 0x010c004a48031505040804917209                                      (14 bytes)
2022-10-29T06:40:11.263Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:11.265Z DRIVER « [REQ] [AddNodeToNetwork]
                                    status:      AddingSlave
                                    callback id: 72
2022-10-29T06:40:11.267Z DRIVER   handling request AddNodeToNetwork (74)
2022-10-29T06:40:11.268Z DRIVER     1 handler registered!
2022-10-29T06:40:11.269Z DRIVER     invoking handler #0
2022-10-29T06:40:11.270Z CNTRLR   handling add node request (status = AddingSlave)
2022-10-29T06:40:11.274Z DRIVER       the message was handled
2022-10-29T06:40:11.718Z SERIAL « 0x0107004a48051500ea                                                 (9 bytes)
2022-10-29T06:40:11.720Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:11.723Z DRIVER « [REQ] [AddNodeToNetwork]
                                    status:      ProtocolDone
                                    callback id: 72
2022-10-29T06:40:11.728Z DRIVER   handling request AddNodeToNetwork (74)
2022-10-29T06:40:11.729Z DRIVER     1 handler registered!
2022-10-29T06:40:11.731Z DRIVER     invoking handler #0
2022-10-29T06:40:11.732Z CNTRLR   handling add node request (status = ProtocolDone)
2022-10-29T06:40:11.733Z CNTRLR   finishing inclusion process...
2022-10-29T06:40:11.745Z SERIAL » 0x0105004ac5493c                                                     (7 bytes)
2022-10-29T06:40:11.746Z DRIVER » [REQ] [AddNodeToNetwork]
                                    action:       Stop
                                    high power:   true
                                    network wide: true
                                    callback id:  73
2022-10-29T06:40:11.749Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:11.798Z SERIAL « 0x0107004a49061500e8                                                 (9 bytes)
2022-10-29T06:40:11.799Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:11.802Z DRIVER « [REQ] [AddNodeToNetwork]
                                    status:      Done
                                    callback id: 73
2022-10-29T06:40:11.821Z SERIAL » 0x0105004ac50075                                                     (7 bytes)
2022-10-29T06:40:11.822Z DRIVER » [REQ] [AddNodeToNetwork]
                                    action:       Stop
                                    high power:   true
                                    network wide: true
                                    callback id:  0
2022-10-29T06:40:11.825Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:11.842Z CNTRLR   The inclusion process was stopped
2022-10-29T06:40:11.845Z CNTRLR   finished adding node 21:
                                    basic device class:    Routing Slave
                                    generic device class:  Thermostat
                                    specific device class: Setpoint Thermostat
                                    supported CCs: 
                                    · Manufacturer Specific (0x72)
                                    · Multi Command (0x8f)
                                    · Thermostat Setpoint (0x43)
                                    · Version (0x86)
                                    · Manufacturer Proprietary (0x91)
                                    controlled CCs: 
2022-10-29T06:40:11.850Z CNTRLR » [Node 021] Assigning SUC return route...
2022-10-29T06:40:11.861Z SERIAL » 0x01050051154af4                                                     (7 bytes)
2022-10-29T06:40:11.864Z DRIVER » [Node 021] [REQ] [AssignSUCReturnRoute]
                                    payload: 0x154a
2022-10-29T06:40:11.868Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:11.877Z SERIAL « 0x0104015101aa                                                       (6 bytes)
2022-10-29T06:40:11.879Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:11.881Z DRIVER « [RES] [AssignSUCReturnRoute]
                                    was executed: true
2022-10-29T06:40:12.579Z SERIAL « 0x010500514a00e1                                                     (7 bytes)
2022-10-29T06:40:12.582Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:12.585Z DRIVER « [REQ] [AssignSUCReturnRoute]
                                    callback id:     74
                                    transmit status: OK
2022-10-29T06:40:12.596Z CNTRLR   [Node 021] Beginning interview - last completed stage: None
2022-10-29T06:40:12.597Z CNTRLR   [Node 021] new node, doing a full interview...
2022-10-29T06:40:12.599Z CNTRLR » [Node 021] querying protocol info...
2022-10-29T06:40:12.606Z DRIVER       the message was handled
2022-10-29T06:40:12.610Z SERIAL » 0x0104004115af                                                       (6 bytes)
2022-10-29T06:40:12.611Z DRIVER » [REQ] [GetNodeProtocolInfo]
                                    payload: 0x15
2022-10-29T06:40:12.616Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:12.618Z SERIAL « 0x01090141518c0004080463                                            (11 bytes)
2022-10-29T06:40:12.619Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:12.621Z DRIVER « [RES] [GetNodeProtocolInfo]
                                    payload: 0x518c00040804
2022-10-29T06:40:12.626Z CNTRLR « [Node 021] received response for protocol info:
                                  basic device class:    Routing Slave
                                  generic device class:  Thermostat
                                  specific device class: Setpoint Thermostat
                                  node type:             End Node
                                  is always listening:   false
                                  is frequent listening: false
                                  can route messages:    true
                                  supports security:     false
                                  supports beaming:      false
                                  maximum data rate:     40000 kbps
                                  protocol version:      1
2022-10-29T06:40:12.627Z CNTRLR   [Node 021] The node is now awake.
2022-10-29T06:40:12.629Z CNTRLR   [Node 021] Interview stage completed: ProtocolInfo
2022-10-29T06:40:12.630Z CNTRLR » [Node 021] querying node info...
2022-10-29T06:40:12.640Z SERIAL » 0x01040060158e                                                       (6 bytes)
2022-10-29T06:40:12.641Z DRIVER » [Node 021] [REQ] [RequestNodeInfo]
                                    payload: 0x15
2022-10-29T06:40:12.644Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:12.648Z SERIAL « 0x01040160019b                                                       (6 bytes)
2022-10-29T06:40:12.650Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:12.652Z DRIVER « [RES] [RequestNodeInfo]
                                    payload: 0x01
2022-10-29T06:40:12.678Z SERIAL « 0x010b00498415050408049172c2                                        (13 bytes)
2022-10-29T06:40:12.681Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:12.683Z DRIVER « [Node 021] [REQ] [ApplicationUpdateRequest]
                                    payload: 0x15050408049172
2022-10-29T06:40:12.693Z CNTRLR « [Node 021] node info received
                                  supported CCs:
                                  · Manufacturer Proprietary
                                  · Manufacturer Specific
2022-10-29T06:40:12.694Z CNTRLR   [Node 021] Interview stage completed: NodeInfo
2022-10-29T06:40:12.696Z CNTRLR   [Node 021] Interviewing Manufacturer Specific...
2022-10-29T06:40:12.696Z CNTRLR » [Node 021] querying manufacturer information...
2022-10-29T06:40:12.704Z SERIAL » 0x0109001315027204254bea                                            (11 bytes)
2022-10-29T06:40:12.705Z DRIVER » [Node 021] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      75
                                  └─[ManufacturerSpecificCCGet]
2022-10-29T06:40:12.707Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:12.712Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-10-29T06:40:12.713Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:12.714Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-10-29T06:40:12.729Z SERIAL « 0x010700134b000002a2                                                 (9 bytes)
2022-10-29T06:40:12.730Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:12.732Z DRIVER « [REQ] [SendData]
                                    callback id:     75
                                    transmit status: OK
2022-10-29T06:40:12.740Z SERIAL « 0x010e000400150872050002800500021a                                  (16 bytes)
2022-10-29T06:40:12.741Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:12.744Z CNTRLR   [Node 021] [Manufacturer Specific] manufacturerId: metadata updat [Endpoint 0]
                                  ed
2022-10-29T06:40:12.746Z CNTRLR   [Node 021] [+] [Manufacturer Specific] manufacturerId: 2          [Endpoint 0]
2022-10-29T06:40:12.747Z CNTRLR   [Node 021] [Manufacturer Specific] productType: metadata updated  [Endpoint 0]
2022-10-29T06:40:12.748Z CNTRLR   [Node 021] [+] [Manufacturer Specific] productType: 32773         [Endpoint 0]
2022-10-29T06:40:12.750Z CNTRLR   [Node 021] [Manufacturer Specific] productId: metadata updated    [Endpoint 0]
2022-10-29T06:40:12.751Z CNTRLR   [Node 021] [+] [Manufacturer Specific] productId: 2               [Endpoint 0]
2022-10-29T06:40:12.752Z DRIVER « [Node 021] [REQ] [ApplicationCommand]
                                  └─[ManufacturerSpecificCCReport]
                                      manufacturer id: 0x02
                                      product type:    0x8005
                                      product id:      0x02
2022-10-29T06:40:12.758Z CNTRLR « [Node 021] received response for manufacturer information:
                                    manufacturer: Danfoss (0x02)
                                    product type: 0x8005
                                    product id:   0x02
2022-10-29T06:40:12.759Z CNTRLR   [Node 021] [+] [Manufacturer Specific] interviewComple [Endpoint 0] [internal]
                                  te: true
2022-10-29T06:40:12.761Z CNTRLR   [Node 021] Interviewing Version...
2022-10-29T06:40:12.761Z CNTRLR » [Node 021]   querying the CC version for Version...
2022-10-29T06:40:12.769Z SERIAL » 0x010a00131503861386254c8a                                          (12 bytes)
2022-10-29T06:40:12.771Z DRIVER » [Node 021] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      76
                                  └─[VersionCCCommandClassGet]
                                      CC: Version
2022-10-29T06:40:12.773Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:12.778Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-10-29T06:40:12.778Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:12.780Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-10-29T06:40:12.795Z SERIAL « 0x010700134c000002a5                                                 (9 bytes)
2022-10-29T06:40:12.796Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:12.798Z DRIVER « [REQ] [SendData]
                                    callback id:     76
                                    transmit status: OK
2022-10-29T06:40:13.849Z CNTRLR   [Node 021] Timed out while waiting for a response from the node (ZW0201)
2022-10-29T06:40:13.850Z CNTRLR   [Node 021] CC version query for Version timed out - assuming the node supports
                                   version 1...
2022-10-29T06:40:13.852Z CNTRLR » [Node 021] querying node versions...
2022-10-29T06:40:13.860Z SERIAL » 0x0109001315028611254d0d                                            (11 bytes)
2022-10-29T06:40:13.861Z DRIVER » [Node 021] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      77
                                  └─[VersionCCGet]
2022-10-29T06:40:13.863Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:13.868Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-10-29T06:40:13.869Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:13.871Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-10-29T06:40:13.885Z SERIAL « 0x010700134d000002a4                                                 (9 bytes)
2022-10-29T06:40:13.886Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:13.888Z DRIVER « [REQ] [SendData]
                                    callback id:     77
                                    transmit status: OK
2022-10-29T06:40:14.933Z CNTRLR   [Node 021] Timed out while waiting for a response from the node (ZW0201)
2022-10-29T06:40:14.935Z CNTRLR » [Node 021] querying CC versions...
2022-10-29T06:40:14.936Z CNTRLR » [Node 021]   querying the CC version for Manufacturer Specific...
2022-10-29T06:40:14.950Z SERIAL » 0x010a00131503861372254e7c                                          (12 bytes)
2022-10-29T06:40:14.952Z DRIVER » [Node 021] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      78
                                  └─[VersionCCCommandClassGet]
                                      CC: Manufacturer Specific
2022-10-29T06:40:14.954Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:14.958Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-10-29T06:40:14.960Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:14.961Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-10-29T06:40:14.975Z SERIAL « 0x010700134e000002a7                                                 (9 bytes)
2022-10-29T06:40:14.977Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:14.979Z DRIVER « [REQ] [SendData]
                                    callback id:     78
                                    transmit status: OK
2022-10-29T06:40:16.022Z CNTRLR   [Node 021] Timed out while waiting for a response from the node (ZW0201)
2022-10-29T06:40:16.024Z CNTRLR   [Node 021] CC version query for Manufacturer Specific timed out - assuming the
                                   node supports version 1...
2022-10-29T06:40:16.025Z CNTRLR   [Node 021]   skipping query for Multi Command (0x8f) because max implemented v
                                  ersion is 1
2022-10-29T06:40:16.027Z CNTRLR » [Node 021]   querying the CC version for Thermostat Setpoint...
2022-10-29T06:40:16.039Z SERIAL » 0x010a00131503861343254f4c                                          (12 bytes)
2022-10-29T06:40:16.040Z DRIVER » [Node 021] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      79
                                  └─[VersionCCCommandClassGet]
                                      CC: Thermostat Setpoint
2022-10-29T06:40:16.043Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:16.047Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-10-29T06:40:16.049Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:16.050Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-10-29T06:40:16.065Z SERIAL « 0x010700134f000002a6                                                 (9 bytes)
2022-10-29T06:40:16.066Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:16.068Z DRIVER « [REQ] [SendData]
                                    callback id:     79
                                    transmit status: OK
2022-10-29T06:40:17.110Z CNTRLR   [Node 021] Timed out while waiting for a response from the node (ZW0201)
2022-10-29T06:40:17.111Z CNTRLR   [Node 021] CC version query for Thermostat Setpoint timed out - assuming the n
                                  ode supports version 1...
2022-10-29T06:40:17.113Z CNTRLR   [Node 021]   skipping query for Manufacturer Proprietary (0x91) because max im
                                  plemented version is 1
2022-10-29T06:40:17.115Z CNTRLR » [Node 021] querying if Z-Wave Software Get is supported...
2022-10-29T06:40:17.127Z SERIAL » 0x0109001315028615255014                                            (11 bytes)
2022-10-29T06:40:17.128Z DRIVER » [Node 021] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      80
                                  └─[VersionCCCapabilitiesGet]
2022-10-29T06:40:17.131Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:17.135Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-10-29T06:40:17.136Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:17.138Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-10-29T06:40:17.152Z SERIAL « 0x0107001350000003b8                                                 (9 bytes)
2022-10-29T06:40:17.153Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:17.155Z DRIVER « [REQ] [SendData]
                                    callback id:     80
                                    transmit status: OK
2022-10-29T06:40:18.198Z CNTRLR   [Node 021] Timed out while waiting for a response from the node (ZW0201)
2022-10-29T06:40:18.200Z CNTRLR   [Node 021] [+] [Version] interviewComplete: true       [Endpoint 0] [internal]
2022-10-29T06:40:18.210Z CNTRLR   [Node 021] Embedded device config loaded
2022-10-29T06:40:18.212Z CNTRLR   [Node 021] Interviewing Thermostat Setpoint...
2022-10-29T06:40:18.213Z CNTRLR » [Node 021] retrieving supported setpoint types...
2022-10-29T06:40:18.220Z SERIAL » 0x01090013150243042551c1                                            (11 bytes)
2022-10-29T06:40:18.221Z DRIVER » [Node 021] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      81
                                  └─[ThermostatSetpointCCSupportedGet]
2022-10-29T06:40:18.226Z SERIAL « [ACK]                                                                   (0x06)
2022-10-29T06:40:18.229Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-10-29T06:40:18.230Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:18.232Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-10-29T06:40:18.244Z SERIAL « 0x0107001351000002b8                                                 (9 bytes)
2022-10-29T06:40:18.245Z SERIAL » [ACK]                                                                   (0x06)
2022-10-29T06:40:18.247Z DRIVER « [REQ] [SendData]
                                    callback id:     81
                                    transmit status: OK
2022-10-29T06:40:19.288Z CNTRLR   [Node 021] Timed out while waiting for a response from the node (ZW0201)
2022-10-29T06:40:19.290Z CNTRLR   [Node 021] Querying supported setpoint types timed out, skipping interview...
2022-10-29T06:40:19.292Z CNTRLR   [Node 021] ManufacturerProprietaryCC: skipping interview refresh because the m
                                  atching proprietary CC is not implemented...
2022-10-29T06:40:19.294Z CNTRLR   [Node 021] [+] [Manufacturer Proprietary] interviewCom [Endpoint 0] [internal]
                                  plete: true
2022-10-29T06:40:19.297Z CNTRLR   [Node 021] Interview stage completed: CommandClasses
2022-10-29T06:40:19.299Z CNTRLR   [Node 021] Interview stage completed: OverwriteConfig
2022-10-29T06:40:19.300Z CNTRLR   [Node 021] Interview completed
2022-10-29T06:40:19.301Z CNTRLR   [Node 021] The node is ready to be used
2

I see this when the node is either far away from the controller, or goes to sleep.
Some battery devices allow you to put them in a mode that keeps them awake. Some you might have to keep pressing buttons to keep awake.

But if you have issues, try including the device close to the controller and be sure the whole interview process is complete and then put it into the location its going. If it works OK close by, and you can ping it from the device info page, then have problems after, its not the device, its the range and you dont have enough powered devices between the controller and node.

Also if you add lots of devices in a short time (like you would when building a network or moving from one controller to another) - be patient. It takes a while for the network to calculate routes and settle down if you add more than one node a day. Devices will keep trying to re-interview until the config is completed normally (aside from quirks with the 700 series stuff thats ongoing). I’ve had some devices that i’d tried all sorts to get to fully interview/add, but in the background the network was just too busy and got timeouts.
Left it, and the next day they had all the attributes. Same goes for OTA firmware updates that ‘failed’

Many devices are capable of being included with no security, and the network keys are now automatically generated if you don’t set them anyway, so i’d guess that secure inclusion or not isnt the problem.

Sometimes patience is key. I have over 60 z wave nodes on my network. I (very often) get timed out messages when adding/including, and the live logs don’t show that the device is being interviewed. But oddly the device has acted like it was included… then a few minutes later the device appears and is configured.
Probably a glitch I should report actually.

3

Thank you for a comprehensive response!

Unfortunately, I’m past all of your otherwise brilliant advice. The Aeotec stick is literally a foot away from the device, and well clear of anything that might interfere. I’ve tried keeping the devices awake, I’ve tried adding one and waiting for days (I have one added now that I haven’t touched since my previous post almost a week ago), and I’ve tried with lower or no security.

It seems like I’m just out of luck with these devices; my other Z-Wave items, including almost identical ones, work fine.

Off to the store, I guess :stuck_out_tongue:

4

As the interview completes just fine, I don’t think these events should be worrying. I have them as well and everything just works fine. Or is something actually not working for you? If so, could you please share info on your setup (hardware used, including host setup, like usb connected devices etc)

5

The devices don’t work at all - there are no entities for me to interact with.

My setup is a Pi400 (the keyboard one) with an Aeotec Gen5 Z-Stick (on a USB extension cord to avoid interference). The devices in question are Danfoss LC-13 thermostats. I have two Danfoss LCZ251 thermostats as well, which are basically identical, and they work fine. Also on Z-Wave I have a NorthQ E-Reader which also works fine.

:slightly_smiling_face: