Docs and issue template: Mention typical troubleshooting steps

[AlCalzone]

Like:

• [x] FIRST OF ALL: LOOK IN THE DRIVER LOG!
• [x] controller on extension cord
• [ ] update to 7.15 when healing fails
• [x] Re-interview nodes when configuration parameters don't match the device DB
• [x] Hard pull and re-insertion of USB controller when it stops responding
• [x] Are all associations still there? (https://github.com/zwave-js/node-zwave-js/issues/3346) -> re-interview fixes that
• [ ] How to decide if the issue lies in HA or zwavejs
• [ ] Aeotec Stick 5 requires a powered usb hub if not the + model
• [ ] For the docs: I'm pushing the scene button and nothing is happening (platform specific how to get to the scene events)
• [x] The state doesn't update when I control locally (needs polling)
• [ ] Cannot open device file error message (zwave stick is in use)
• [ ] The container starts but I can't connect to it via HA (stick not configured)
• [ ] Whatever the error says when a stick is not configured in zjs2mqtt and you start it
• [ ] My mesh is slow or buggy (heal network)
• [ ] One device works more slowly than others or not at all (heal node, and likely intermediate hop nodes)
• [ ] My lock won't pair (range issues?)
• [x] My lock has only sensors (needs secure inclusion)
• [ ] My battery devices are stuck interviewing (multiple wake ups needed)
• [ ] Cannot deserialize error (missing support for CC, open issue if necessary for operation)
• [ ] Device doesn't respond to Supervision command (whatever the inovelli Bug was that we disabled)
• [ ] When I operate one switch both endpoints change state (mapping issue, may need compat flag)
• [ ] Inclusion fails (reset device, range issues)
• [ ] The manual has a parameter but it's not displayed
• [ ] The manual says a parameter has a value but I get whatever error an out of range set causes
• [ ] Timeout errors (heal network, need repeaters)

[kpine]

• Re-interview nodes when configuration parameters don't match the device DB
• Hard pull and re-insertion of USB controller when it stops responding

[blhoward2]

For the docs, should these live at Zjs2mqtt? I worry most users don't know to look here.

[blhoward2]

More in no specific order. Some of these are less troubleshooting and more FAQ territory but so they're all in one place.

• How to decide if the issue lies in HA or zwavejs
• Aeotec Stick 5 requires a powered usb hub if not the + model
• For the docs: I'm pushing the scene button and nothing is happening (platform specific how to get to the scene events)
• The state doesn't update when I control locally (needs polling)
• Cannot open device file error message (zwave stick is in use)
• The container starts but I can't connect to it via HA (stick not configured)
• Whatever the error says when a stick is not configured in zjs2mqtt and you start it
• My mesh is slow or buggy (heal network)
• One device works more slowly than others or not at all (heal node, and likely intermediate hop nodes)
• My lock won't pair (range issues?)
• My lock has only sensors (needs secure inclusion)
• My battery devices are stuck interviewing (multiple wake ups needed)
• Cannot deserialize error (missing support for CC, open issue if necessary for operation)
• Device doesn't respond to Supervision command (whatever the inovelli Bug was that we disabled)
• When I operate one switch both endpoints change state (mapping issue, may need compat flag)
• Inclusion fails (reset device, range issues)
• The manual has a parameter but it's not displayed
• The manual says a parameter has a value but I get whatever error an out of range set causes
• Timeout errors (heal network, need repeaters)

[AlCalzone]

* The state doesn't update when I control locally (needs polling)

Or the associations need to be changed. Maybe the device just needs a re-interview if updating from an older driver that behaved differently. Maybe the device file needs a compat flag to hide/preserve an endpoint.

[AlCalzone]

• Apparently some S2-capable battery-powered devices give you a grand total of 20 seconds from starting the inclusion to entering the PIN (ZCOMBO being one example). According to the specs this should be 8 minutes (4 for granting keys, 4 for entering PIN).

[mhutch]

• Apparently some S2-capable battery-powered devices give you a grand total of 20 seconds from starting the inclusion to entering the PIN (ZCOMBO being one example). According to the specs this should be 8 minutes (4 for granting keys, 4 for entering PIN).

@AlCalzone I don't feel like I've collected enough info for a proper bug report yet, but I suspect something like this is happening with my Ring gen 2 motion sensor, given that the manual for the device describes entering the PIN into the controller before activating "classic inclusion" on the device.

[AlCalzone]

I've started working on this in https://github.com/zwave-js/node-zwave-js/pull/3530 If anyone wants to help out or chime in, please go ahead. It is very much appreciated.