search

zwave-js / node-zwave-js

Z-Wave driver written entirely in JavaScript/TypeScript
https://zwave-js.github.io/node-zwave-js/
MIT License
751 stars 603 forks source link

Secondary controller: Investigate if node ready events need to be emitted #7227

Open AlCalzone opened 1 month ago

eliasisrael commented 1 month ago

Tell me if you need diagnostic data.

AlCalzone commented 1 month ago

A driver log of the addon startup on loglevel debug would be good. Please attach it here as a file (drag & drop into the text field).

eliasisrael commented 1 month ago

Hey, just so that you don't think I ghosted you...

I have tried to turn on logging to file, but it won't let me because the S2 and S0 keys are not in the config.

I'll attach a screen capture.

I imagine I can use the Silicon Labs software to extract the right keys from the device and then input those. I'll try that next.

Screenshot 2024-10-10 at 9 26 55 AM Screenshot 2024-10-10 at 9 26 34 AM

AlCalzone commented 1 month ago

Uhhh. How was it working before the update then? This means you didn't have secure communication before either, which seems weird for communication with an alarm panel.

AlCalzone commented 1 month ago

Also @robertsLando having no keys isn't necessarily an error.

eliasisrael commented 1 month ago

For all I know, it's a glitch in the display of that form, where information that is known to zwave-js is somehow not showing as far as the UI is concerned? Maybe it's because it's a secondary, and is using the keys provisioned for it by the primary?

I'm afraid that my ignorance of the zwave protocols and terminology prevents me from giving a complete answer.

eliasisrael commented 2 weeks ago

OK. I apologize for the long delay, but I finally understand what was going on here.

I still had the z-wave JS add-on installed and I didn't realize that I should remove it, configure z-wave-js-ui, and then enable the INTEGRATION (not the add-on) using the z-wave-js server.

Now that I have done that, I see a much happier result.