Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to include new devices #1069

Closed
Juggler00 opened this issue Apr 16, 2021 · 9 comments
Closed

Unable to include new devices #1069

Juggler00 opened this issue Apr 16, 2021 · 9 comments

Comments

@Juggler00
Copy link

Running the latest version of zwavejs2mqtt as a docker container on an RPi with attached Aeotec Zwave stick gen5. All of the current nodes were included prior to migration.

zwavejs2mqtt: 3.3.0
zwave-js: 7.2.2

I'm trying to include a new device. From the web interface, when I click on add device, I get the following in my logs and the inclusion stops:

2021-04-16 09:59:30.323 INFO ZWAVE: Calling api startInclusion with args: [ false, [length]: 1 ]
2021-04-16 09:59:30.445 INFO ZWAVE: The inclusion could not be started. startInclusion { success: false, message: 'The inclusion could not be started.' }
2021-04-16 09:59:30.519 INFO ZWAVE: Controller status: Inclusion stopped

I have tried reboot, restarting docker etc, but always the same message.

@robertsLando
Copy link
Member

@Juggler00 Please provide also zwave-js logs

@Juggler00
Copy link
Author

Juggler00 commented Apr 19, 2021

I found a log in /usr/src/app/store/zwavejs_1.log. Is this what you're looking for?

2021-04-19T00:49:32.278Z CNTRLR   starting inclusion process...
2021-04-19T00:49:32.362Z CNTRLR   handling add node request (status = Failed)
2021-04-19T00:49:32.363Z CNTRLR     starting the inclusion failed
2021-04-19T00:49:32.364Z CNTRLR   stopping inclusion process...
2021-04-19T00:49:32.452Z CNTRLR   handling add node request (status = Done)
2021-04-19T00:49:32.452Z CNTRLR   done called for 0
2021-04-19T00:49:32.453Z CNTRLR   the inclusion process was stopped

@robertsLando
Copy link
Member

Yeah but I need the full log file. Enable log to file in settings please

@Juggler00
Copy link
Author

Sorry, the log level was set to Info. Here is the output at "Debug":

2021-04-19T12:49:49.110Z CNTRLR   starting inclusion process...
2021-04-19T12:49:49.118Z SERIAL » 0x0105004ac11766                                                     (7 bytes)
2021-04-19T12:49:49.119Z DRIVER » [REQ] [AddNodeToNetwork]
                                    payload: 0xc117
2021-04-19T12:49:49.123Z SERIAL « [ACK]                                                                   (0x06)
2021-04-19T12:49:49.171Z SERIAL « 0x0107004a17070000a2                                                 (9 bytes)
2021-04-19T12:49:49.172Z SERIAL » [ACK]                                                                   (0x06)
2021-04-19T12:49:49.172Z DRIVER « [REQ] [AddNodeToNetwork]
                                    payload: 0x17070000
2021-04-19T12:49:49.176Z DRIVER   handling request AddNodeToNetwork (74)
2021-04-19T12:49:49.176Z DRIVER     1 handler registered!
2021-04-19T12:49:49.177Z DRIVER     invoking handler #0
2021-04-19T12:49:49.177Z CNTRLR   handling add node request (status = Failed)
2021-04-19T12:49:49.178Z CNTRLR     starting the inclusion failed
2021-04-19T12:49:49.178Z CNTRLR   stopping inclusion process...
2021-04-19T12:49:49.254Z SERIAL » 0x0105004ac5186d                                                     (7 bytes)
2021-04-19T12:49:49.255Z DRIVER » [REQ] [AddNodeToNetwork]
                                    payload: 0xc518
2021-04-19T12:49:49.260Z SERIAL « [ACK]                                                                   (0x06)
2021-04-19T12:49:49.264Z DRIVER       the message was handled
2021-04-19T12:49:49.307Z SERIAL « 0x0107004a18060000ac                                                 (9 bytes)
2021-04-19T12:49:49.307Z SERIAL » [ACK]                                                                   (0x06)
2021-04-19T12:49:49.308Z DRIVER « [REQ] [AddNodeToNetwork]
                                    payload: 0x18060000
2021-04-19T12:49:49.310Z DRIVER   handling request AddNodeToNetwork (74)
2021-04-19T12:49:49.310Z DRIVER     1 handler registered!
2021-04-19T12:49:49.310Z DRIVER     invoking handler #0
2021-04-19T12:49:49.310Z CNTRLR   handling add node request (status = Done)
2021-04-19T12:49:49.311Z CNTRLR   done called for 0
2021-04-19T12:49:49.311Z CNTRLR   the inclusion process was stopped
2021-04-19T12:49:49.313Z DRIVER       the message was handled

@robertsLando
Copy link
Member

I don't see anything wrong in the debug logs, I suggest you to enable log to file and upload the entire file.

/cc @AlCalzone

@Juggler00
Copy link
Author

Thank you for looking into this.
zwavejs_1.log

@AlCalzone
Copy link
Member

status = Failed is the controller telling us that it cannot include devices right now.
If that doesn't change, your best bet is: shut down the host, pull the stick put it back in and start again.

@blhoward2
Copy link
Collaborator

I've seen similar issues in the past. Try a USB extension cable. USB ports are notorious for interference causing weird issues with the sticks. Depending on which Rpi you have and which Gen 5 stick you may instead need a powered USB 2.0 hub due to issues with the earlier generation devices.

@tommyjlong
Copy link

I just ran into this issue. The solution for me was to stop zwavejs2mqtt, pull out the Aeotec Gen5 stick, wait a minute or so, and plugged it back in, and restart zwavejs2mqtt. After that I could successfully run inclusion.

As an FYI, another symptom of this issue is when you re-interview a node; it will fail (all 5 attempts) and come up unknown. After doing the above (unplug/replug), the re-interview succeeds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants