networkSecurityLevel: ZWAVE_S2_FAILED vs ZWAVE_S0_DOWNGRADE

[JDRoberts]

@Marta

Thanks JDRoberts!
Know I know the DTH abbreviation and that we are using the “Z wave lock out of the box” DTH. I will in some hours take another Hub and pair 10-20 new locks to see if the problem occurs again on another hub. If it does it seems to be some kind of problems when a certain number of locks are paired. My goal is to have approx. 200 locks to one single hub.

Marta

Can I ask why you are trying to accomplish that with a single hub? Smartthings is not a very stable system to begin with, and certainly not something I would deploy in a commercial installation like a school or an apartment building because of all the unexpected glitches. It’s just not commercial grade. They have told us many times that their typical customer has 15 or fewer devices total and never uses any custom code at all.

You might take a look at the following thread if you get a chance:

How to: Planning for Outages

There was one community member who had deployed it for an apartment complex with about 200 units, but they wrote their own management software to run above it, and to be honest, I don’t even know if they’re still using the same system, that was a couple years ago.

Also, they have told us that the classic app will be going away, although there’s no timeframe for that yet. And with the new app, you are quite limited in control of smart locks. You used to be able to trigger the locks with any smartthings event, including Geopresence, A keyfob device, etc.

But with the new app they changed their design philosophy with regard to security devices, and now you have to open the app and use that to unlock the lock. But perhaps that fits your use case, and you are just using the app to set codes and track usage.

Different things work for different people. But 200 locks is certainly testing the limits of the system. And just the fact that you cannot delay or defer updates isn’t typically a good match for a commercial use case.

Also, are you planning on having a repeating device for each lock? Because I am sure the hub cannot handle the message traffic from that many locks all at once. And one thing about locks is that you tend to get “traffic jam“ periods where most of the locks in a multiunit building are all being used at about the same time.

FAQ: why would I need another beaming repeater if my zwave lock is already close to my hub?

This question comes up a lot. Suppose you have a Z wave lock, but the status doesn’t seem to update or commands don’t always seem to work. Typically someone in the community will recommend that you add another beaming repeater within 10 feet or so of the lock. So the question is why would you need that if the lock is already pretty close to the hub? The short answer is that the hub is busy, and it takes some load off of it if you have a separate beaming repeater near your lock. The long answer is in the following thread (this is a clickable link) Also, since I get asked all the time what’s an inexpensive Zwave plus beaming repeater, for the US hub the Minoston miniplug is often on sale for right around $20. It should not require any custom code, it’s just a very simple one socket on/…

And 200 locks + 200 repeaters would be 400 devices, which is more than any zwave network can handle ( there is a hard limit of 231 zwave devices for a single hub) . So that’s not even technically possible.