Securely included node doesn't show up as secure #1089
Comments
Either the device does not support security (then a "secure" inclusion will just be a normal inclusion) or you need to do a special activation sequence during inclusion. Aeotec devices for example require a double press of the button. Not sure about Qubino |
|
The device does support security (but only S0 and not S2 according to Qubino) and there is no special inclusion procedure documented in the manual to enable it. |
|
Ok could you re-include it and send me a log of that? The log file should be enough, I don't need the console output. |
|
The log I provided should already contain the inclusion part, doesn't it? |
|
Oh yeah, you're right. The node information frame it sends definitely does not include the |
|
I did factory reset it before inclusion... |
|
Then I don't know what to do. If the device does not tell the controller that it supports Security, it cannot be included securely. |
|
This is weird, because if I recall correctly OZW 1.4 used to show my devices as secure, while OZW 1.6 has the same issue as zwave-js. This is a screenshow of latest openzwave2mqtt, but unfortunately I don't remember what I did differently to show such specific device as secure :( |
|
I actually believe it is a problem of your specific device. I remember a report (Qubino ZMNHSD1) where the device completely forgot that it supports I think it would be worth contacting the Qubino support with that problem. When you do, please include the following log excerpt, so they can parse the device information themselves from that serial message. Otherwise they'll probably tell you it is a problem with the controller software: Edit: found the report... A few days later it looks like this: which is pretty messed up, since it is now basically impossible to interact with it. |
|
@darkbasic There are a couple of options:
|
I've bought 25 of them on December 2018. The reseller didn't have any stock so they came directly from Qubino.
This is the first time I see this. In the copy of the manual I downloaded from your website when I first bought these devices there is no mention of parameter 250 at all.
Why could it fail?
I do have a network key, not sure if I need a separate one just for S0 but I can't configure more than one Also please note that I experience the same issue with my Flush Shutters (I bought 16 of them on Dicemeber 2018) with a VERY recent firmware because I had to return all of them in 2020 to update the firmware due to bugs. |
Missing required messages, elapsed timeouts between subsequent messages, etc.. This shouldn't be the case since the S0 bootstrapping takes place after the
zwave-js only supports S0 so far, so there is only one key.
Can you check in the dashboard if it is there? The config file for ZMNHDD does have that parameter. |
It's in the dashboard, but the config contains parameters for all different kind of firmwares.
Really? That's a big problem because lots of devices don't support S0 at all because of bugs in the zwave SDK which lead to all sort of problems including packets loss. Some vendors have patched it, others only support S2. |
|
@petrovcicklemen the same problem happens with latest openzwave by the way |
I already have a S2 supporting device lying on my TODO heap. Implementing it is not trivial, especially without devices to test (which I didn't until someone lent me one recently). OZW and OpenHAB do not support S2 either, so if everything goes as planned, |
|
> I've bought 25 of them on December 2018. The reseller didn't have any stock so they came directly from Qubino. > This is the first time I see this. In the copy of the manual I downloaded from your website when I first bought these devices there is no mention of parameter 250 at all. > Also please note that I experience the same issue with my Flush Shutters (I bought 16 of them on Dicemeber 2018) with a VERY recent firmware because I had to return all of them in 2020 to update the firmware due to bugs. |
@petrovcicklemen I'm not talking about the website manual available right now, I'm talking about the website manual I downloaded and printed when I initially bought my devices:
As you can see it says SW version S3 (the one I have) and it doesn't mention parameter 250 at all.
I did, but as you can see from the following images there is no mention of parameter 250 either:
The whole thing is completely undocumented.
I would need to get a Windows PC in order to do so, because my sole OS is Linux.
I tried parameter 250 and it works. It should really have been documented. |
|
@AlCalzone this is the log with parameter 250 enabled: |
|
@darkbasic My apologies for the outdated manual. I also though the installation manual, provided in the blisters would list the supported command classes, since the last time I looked at them, I think they did. Noted. |
That looks good! I'm gonna go ahead and close this issue, since it was a configuration/device issue. |
I tried to include a Qubino Flush Dimmer in zwavejs2mqtt but unfortunately it shows up as non-secure. What's wrong?
zwave-284642.log
The text was updated successfully, but these errors were encountered: