Closed wilvancleve closed 2 years ago
Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zwave_js documentation zwave_js source (message by IssueLinks)
Please provide a driver debug level log of the inclusion.
2021-12-13T01:44:09.126Z CNTRLR Starting inclusion process with strategy Default...
2021-12-13T01:44:09.136Z SERIAL » 0x0105004ac17100 (7 bytes)
2021-12-13T01:44:09.137Z DRIVER » [REQ] [AddNodeToNetwork]
payload: 0xc171
2021-12-13T01:44:09.140Z SERIAL « [ACK] (0x06)
2021-12-13T01:44:09.142Z SERIAL « 0x0107004a71010000c2 (9 bytes)
2021-12-13T01:44:09.143Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:09.144Z DRIVER « [REQ] [AddNodeToNetwork]
payload: 0x71010000
2021-12-13T01:44:09.149Z CNTRLR The controller is now ready to add nodes
2021-12-13T01:44:18.272Z SERIAL « 0x0107004a71020000c1 (9 bytes)
2021-12-13T01:44:18.273Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:18.275Z DRIVER « [REQ] [AddNodeToNetwork]
payload: 0x71020000
2021-12-13T01:44:18.278Z DRIVER handling request AddNodeToNetwork (74)
2021-12-13T01:44:18.278Z DRIVER 1 handler registered!
2021-12-13T01:44:18.279Z DRIVER invoking handler #0
2021-12-13T01:44:18.281Z CNTRLR handling add node request (status = NodeFound)
2021-12-13T01:44:18.470Z SERIAL « 0x0119004a7103771204080620818772314042444543867080856007 (27 bytes)
2021-12-13T01:44:18.473Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:18.475Z DRIVER « [REQ] [AddNodeToNetwork]
payload: 0x71037712040806208187723140424445438670808560
2021-12-13T01:44:18.478Z DRIVER handling request AddNodeToNetwork (74)
2021-12-13T01:44:18.479Z DRIVER 1 handler registered!
2021-12-13T01:44:18.479Z DRIVER invoking handler #0
2021-12-13T01:44:18.480Z CNTRLR handling add node request (status = AddingSlave)
2021-12-13T01:44:18.486Z DRIVER the message was handled
2021-12-13T01:44:32.428Z SERIAL « 0x0107004a71057700b1 (9 bytes)
2021-12-13T01:44:32.430Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:32.432Z DRIVER « [REQ] [AddNodeToNetwork]
payload: 0x71057700
2021-12-13T01:44:32.434Z DRIVER handling request AddNodeToNetwork (74)
2021-12-13T01:44:32.435Z DRIVER 1 handler registered!
2021-12-13T01:44:32.436Z DRIVER invoking handler #0
2021-12-13T01:44:32.437Z CNTRLR handling add node request (status = ProtocolDone)
2021-12-13T01:44:32.438Z CNTRLR finishing inclusion process...
2021-12-13T01:44:32.443Z SERIAL » 0x0105004ac57207 (7 bytes)
2021-12-13T01:44:32.444Z DRIVER » [REQ] [AddNodeToNetwork]
payload: 0xc572
2021-12-13T01:44:32.446Z SERIAL « [ACK] (0x06)
2021-12-13T01:44:32.508Z SERIAL « 0x0107004a72067700b1 (9 bytes)
2021-12-13T01:44:32.509Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:32.511Z DRIVER « [REQ] [AddNodeToNetwork]
payload: 0x72067700
2021-12-13T01:44:32.522Z SERIAL » 0x0105004ac50075 (7 bytes)
2021-12-13T01:44:32.523Z DRIVER » [REQ] [AddNodeToNetwork]
payload: 0xc500
2021-12-13T01:44:32.527Z SERIAL « [ACK] (0x06)
2021-12-13T01:44:32.530Z CNTRLR The inclusion process was stopped
2021-12-13T01:44:32.531Z CNTRLR finished adding node 119:
basic device class: Routing Slave
generic device class: Thermostat
specific device class: General Thermostat V2
supported CCs:
· Basic (0x20)
· Manufacturer Specific (0x72)
· Thermostat Mode (0x40)
· Thermostat Setpoint (0x43)
· Version (0x86)
· Clock (0x81)
· Indicator (0x87)
· Multilevel Sensor (0x31)
· Thermostat Operating State (0x42)
· Thermostat Fan Mode (0x44)
· Thermostat Fan State (0x45)
· Configuration (0x70)
· Battery (0x80)
· Association (0x85)
· Multi Channel (0x60)
controlled CCs:
2021-12-13T01:44:32.533Z CNTRLR » [Node 119] Assigning SUC return route...
2021-12-13T01:44:32.539Z SERIAL » 0x010500517773af (7 bytes)
2021-12-13T01:44:32.540Z DRIVER » [Node 119] [REQ] [AssignSUCReturnRoute]
payload: 0x7773
2021-12-13T01:44:32.542Z SERIAL « [ACK] (0x06)
2021-12-13T01:44:32.551Z SERIAL « 0x0104015101aa (6 bytes)
2021-12-13T01:44:32.552Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:32.554Z DRIVER « [RES] [AssignSUCReturnRoute]
was executed: true
2021-12-13T01:44:32.640Z SERIAL « 0x010500517301d9 (7 bytes)
2021-12-13T01:44:32.641Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:32.642Z DRIVER « [REQ] [AssignSUCReturnRoute]
callback id: 115
transmit status: NoAck
2021-12-13T01:44:32.648Z CNTRLR [Node 119] Beginning interview - last completed stage: None
2021-12-13T01:44:32.650Z CNTRLR [Node 119] new node, doing a full interview...
2021-12-13T01:44:32.651Z CNTRLR » [Node 119] querying protocol info...
2021-12-13T01:44:32.656Z SERIAL » 0x0104004177cd (6 bytes)
2021-12-13T01:44:32.657Z DRIVER » [REQ] [GetNodeProtocolInfo]
payload: 0x77
2021-12-13T01:44:32.661Z DRIVER the message was handled
2021-12-13T01:44:32.663Z SERIAL « [ACK] (0x06)
2021-12-13T01:44:32.665Z SERIAL « 0x01090141d29c00040806f2 (11 bytes)
2021-12-13T01:44:32.666Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:32.668Z DRIVER « [RES] [GetNodeProtocolInfo]
payload: 0xd29c00040806
2021-12-13T01:44:32.673Z CNTRLR « [Node 119] received response for protocol info:
basic device class: Routing Slave
generic device class: Thermostat
specific device class: General Thermostat V2
node type: Routing End Node
is always listening: true
is frequent listening: false
can route messages: true
supports security: false
supports beaming: true
maximum data rate: 40000 kbps
protocol version: 2
2021-12-13T01:44:32.694Z CNTRLR [Node 119] Interview stage completed: ProtocolInfo
2021-12-13T01:44:32.695Z CNTRLR » [Node 119] querying node info...
2021-12-13T01:44:32.700Z SERIAL » 0x0104006077ec (6 bytes)
2021-12-13T01:44:32.701Z DRIVER » [Node 119] [REQ] [RequestNodeInfo]
payload: 0x77
2021-12-13T01:44:32.703Z SERIAL « [ACK] (0x06)
2021-12-13T01:44:32.709Z SERIAL « 0x01040160019b (6 bytes)
2021-12-13T01:44:32.711Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:32.712Z DRIVER « [RES] [RequestNodeInfo]
payload: 0x01
2021-12-13T01:44:32.812Z SERIAL « 0x0106004981000031 (8 bytes)
2021-12-13T01:44:32.814Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:32.816Z DRIVER « [REQ] [ApplicationUpdateRequest]
payload: 0x0000
2021-12-13T01:44:32.822Z CNTRLR [Node 119] Querying the node info failed
2021-12-13T01:44:32.823Z CNTRLR [Node 119] Interview attempt 1/5 failed, retrying in 5000 ms...
2021-12-13T01:44:37.827Z CNTRLR [Node 119] Beginning interview - last completed stage: ProtocolInfo
2021-12-13T01:44:37.828Z CNTRLR » [Node 119] querying node info...
2021-12-13T01:44:37.837Z SERIAL » 0x0104006077ec (6 bytes)
2021-12-13T01:44:37.838Z DRIVER » [Node 119] [REQ] [RequestNodeInfo]
payload: 0x77
2021-12-13T01:44:37.840Z SERIAL « [ACK] (0x06)
2021-12-13T01:44:37.847Z SERIAL « 0x01040160019b (6 bytes)
2021-12-13T01:44:37.848Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:37.849Z DRIVER « [RES] [RequestNodeInfo]
payload: 0x01
2021-12-13T01:44:37.994Z SERIAL « 0x0106004981000031 (8 bytes)
2021-12-13T01:44:37.996Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:37.997Z DRIVER « [REQ] [ApplicationUpdateRequest]
payload: 0x0000
2021-12-13T01:44:38.003Z CNTRLR [Node 119] Querying the node info failed
2021-12-13T01:44:38.003Z CNTRLR [Node 119] Interview attempt 2/5 failed, retrying in 10000 ms...
2021-12-13T01:44:48.007Z CNTRLR [Node 119] Beginning interview - last completed stage: ProtocolInfo
2021-12-13T01:44:48.008Z CNTRLR » [Node 119] querying node info...
2021-12-13T01:44:48.015Z SERIAL » 0x0104006077ec (6 bytes)
2021-12-13T01:44:48.016Z DRIVER » [Node 119] [REQ] [RequestNodeInfo]
payload: 0x77
2021-12-13T01:44:48.019Z SERIAL « [ACK] (0x06)
2021-12-13T01:44:48.024Z SERIAL « 0x01040160019b (6 bytes)
2021-12-13T01:44:48.025Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:48.026Z DRIVER « [RES] [RequestNodeInfo]
payload: 0x01
2021-12-13T01:44:48.142Z SERIAL « 0x0106004981000031 (8 bytes)
2021-12-13T01:44:48.144Z SERIAL » [ACK] (0x06)
2021-12-13T01:44:48.146Z DRIVER « [REQ] [ApplicationUpdateRequest]
payload: 0x0000
2021-12-13T01:44:48.151Z CNTRLR [Node 119] Querying the node info failed
2021-12-13T01:44:48.152Z CNTRLR [Node 119] Interview attempt 3/5 failed, retrying in 15000 ms...
2021-12-13T01:45:03.154Z CNTRLR [Node 119] Beginning interview - last completed stage: ProtocolInfo
2021-12-13T01:45:03.156Z CNTRLR » [Node 119] querying node info...
2021-12-13T01:45:03.164Z SERIAL » 0x0104006077ec (6 bytes)
2021-12-13T01:45:03.165Z DRIVER » [Node 119] [REQ] [RequestNodeInfo]
payload: 0x77
2021-12-13T01:45:03.167Z SERIAL « [ACK] (0x06)
2021-12-13T01:45:03.179Z SERIAL « 0x01040160019b (6 bytes)
2021-12-13T01:45:03.180Z SERIAL » [ACK] (0x06)
2021-12-13T01:45:03.181Z DRIVER « [RES] [RequestNodeInfo]
payload: 0x01
2021-12-13T01:45:03.246Z SERIAL « 0x0106004981000031 (8 bytes)
2021-12-13T01:45:03.247Z SERIAL » [ACK] (0x06)
2021-12-13T01:45:03.248Z DRIVER « [REQ] [ApplicationUpdateRequest]
payload: 0x0000
2021-12-13T01:45:03.252Z CNTRLR [Node 119] Querying the node info failed
2021-12-13T01:45:03.253Z CNTRLR [Node 119] Interview attempt 4/5 failed, retrying in 20000 ms...
As you can see, inclusion is successful, but interview attempts fail, and the node is eventually marked dead.
@AlCalzone do you see the problem from the log above?
transmit status: NoAck
RF connectivity problem between controller and the device.
I would have thought the same, but device has been at the same location with no problem in connectivity for years, and is able to initially pair. Why can it pair but not do subsequent steps?
On Thu, Dec 16, 2021 at 06:38 AlCalzone @.***> wrote:
transmit status: NoAck
Connectivity problem between controller and the device.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/61630#issuecomment-995877042, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCO3IV5JK3L6KJMQNXWBBTURH2W5ANCNFSM5J4ZI22Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
--
Whenever you find yourself on the side of the majority, it is time to pause and reflect.
- Samuel Clemens
Why can it pair but not do subsequent steps?
I can't say, but there is definitely something going on. 14 seconds to just exchange the protocol info (1 message) is a LOT.
2021-12-13T01:44:18.480Z CNTRLR handling add node request (status = AddingSlave)
...
2021-12-13T01:44:32.437Z CNTRLR handling add node request (status = ProtocolDone)
Anyhow, something must have changed in your setup or why are you including the device again? Did you switch Z-Wave sticks? Or did you do something else? If you switched sticks, what's the new one and which firmware version? Is it on a USB extension cord?
No new stick. It fell off the network on its own at some point, and so I tried an exclude repair. No changes in network topology, devices, house, etc etc. Happy to look at the question of whether location improves issues.
On Thu, Dec 16, 2021 at 07:13 AlCalzone @.***> wrote:
Why can it pair but not do subsequent steps?
I can't say, but there is definitely something going on. 14 seconds to just exchange the protocol info (1 message) is a LOT.
2021-12-13T01:44:18.480Z CNTRLR handling add node request (status = AddingSlave) ... 2021-12-13T01:44:32.437Z CNTRLR handling add node request (status = ProtocolDone)
Anyhow, something must have changed in your setup or why are you including the device again? Did you switch Z-Wave sticks? Or did you do something else? If you switched sticks, what's the new one and which firmware version? Is it on a USB extension cord?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/61630#issuecomment-995908655, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCO3ITWMLFWYLD35Y6YGBLURH63DANCNFSM5J4ZI22Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
--
Whenever you find yourself on the side of the majority, it is time to pause and reflect.
- Samuel Clemens
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Describe the issue you are experiencing
Not sure which update of the zwave js add-on is to blame here, but my CT101 thermostat, which once upon a time paired with Zwave JS just fine (albeit with two created thermostat devices instead of just one), no longer pairs at all.
Here's an example of the logs during pairing. The CT101 is hardwired to power. I have tried factory reseting and unpairing the device multiple times.
As you can see, the device is created, but all subsequent attempts to interview fail. Again, this device had been in successful use in this location and with this same network setup until very recently. Grateful for any thoughts anyone might have.
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Debian
Which add-on are you reporting an issue with?
Z-Wave JS
What is the version of the add-on?
0.1.50
Steps to reproduce the issue
Don't think you'll be able to reproduce without my hardwre.
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
No response