Smart Implant move from UNSECURED to S0 mode, lost from Installer App

[Martin_N 143]

Hello,

I'm solving an interesting problem right now - it happened to me at home.
To add: Two days ago there was a power outage in the entire city.

I have been running several Smart Implants with fw 5.1 on HC3 for several years.
All were installed in UNSECURED mode.
One of them (node id 22) suddenly disappeared from my network (I think that everything did not start properly after the power failure).
This SI didn't send commands, couldn't be reconfigured, didn't respond to pool queries... I tried to force a mesh reconfiguration on this device via the Installer app - without success.
Zniffer clearly showed routing errors and no direct packet went out to the network.
I disconnected the SI from the power supply, connected it, soft reconfiguration and everything started up, the scenes work, the button report to the history works, everything can be controlled - in short, everything is full of sunshine. It still has (node id 22). Zniffer already happily shows both direct and routed packets from/to this device.

But be careful. It is now in S0 security level.
Why?
Also, I lost this device from Installer App. It's just nowhere to be seen.

Has anyone encountered anything similar?
Mainly spontaneous migration of settings from UNSECURED to S0?
Why to S0 and not to S2?

 

Before I remove the whole thing to add it back to insecure mode and set everything up again (scene bindings, etc.), I'd like to know if anyone else has had this happen to them.
Maybe I'll leave it at that.

 

Thanks, eM.

[Neo Andersson 149]

3 hours ago, Martin_N said:

Hello,

I'm solving an interesting problem right now - it happened to me at home.
To add: Two days ago there was a power outage in the entire city.

I have been running several Smart Implants with fw 5.1 on HC3 for several years.
All were installed in UNSECURED mode.
One of them (node id 22) suddenly disappeared from my network (I think that everything did not start properly after the power failure).
This SI didn't send commands, couldn't be reconfigured, didn't respond to pool queries... I tried to force a mesh reconfiguration on this device via the Installer app - without success.
Zniffer clearly showed routing errors and no direct packet went out to the network.
I disconnected the SI from the power supply, connected it, soft reconfiguration and everything started up, the scenes work, the button report to the history works, everything can be controlled - in short, everything is full of sunshine. It still has (node id 22). Zniffer already happily shows both direct and routed packets from/to this device.

But be careful. It is now in S0 security level.
Why?
Also, I lost this device from Installer App. It's just nowhere to be seen.

Has anyone encountered anything similar?
Mainly spontaneous migration of settings from UNSECURED to S0?
Why to S0 and not to S2?

 

Before I remove the whole thing to add it back to insecure mode and set everything up again (scene bindings, etc.), I'd like to know if anyone else has had this happen to them.
Maybe I'll leave it at that.

 

Thanks, eM.

Really interesting...This should be addressed to support to investigate, but only thing i know..why not S2 ?? Becasue it is only supported in zwave engine 3.

[m.roszak 481]

On 5/4/2024 at 2:23 PM, Martin_N said:

Why to S0 and not to S2?

It is impossible on the protocol level to change the security level without full inclusion after exclusion (or factory reset).
The device had to be added in S0 from the begging.