Hi, I'm wanting to upgrade my Schlage Connect Z-Wave locks (they are starting to go bad) and came across the Phillips 4000 series. I'm also wanting to get away from using Ring for locks and contact sensors and replace with these Phillips locks and Zooz 800 series sensors. I purchased one of the locks to see how I liked it and am having trouble getting it to pair. I have a C8 Pro Hub that I switched to use Z-Wave JS and have the Region set to "US-LR - 908.4 Mhz, 916 Mhz". I would like to eventually move everything I have over to LR using Smart Start and stop using a mesh. I have a handful of 800 LR plugs and it took a while, but I was able to get all but one to pair using the "SmartStart Manager". I finally gave up on the last one. I also have about 20 of the older Inovelli light switches and another 20 of their newer 800 series switches. It took a while to get one to pair using LR, so I have the rest still using the mesh for now. Now I'm having similar issues with this new lock. I have tried everything I know and it stays in the waiting to pair state. I have factory reset the lock multiple times, shut down the Hubitat and unplugged it for at least 30 seconds, etc. I even moved the hub within 2 feet of the lock and still no luck.
Is SmartStart and LR really this difficult and inconsistent, or am I inherently doing something wrong? Another thing to note, when using "SmartStart Manager", it defaults to having both "S0 Unauthenticated" and "S2 Access Control" checked for keys. I don't fully understand the purpose of this, but it seems odd to me to allow the "S0" setting so I unchecked it. Does that mean someone could connect to my lock without any security/hand shaking? I know the device tries the most secure setting first, but doesn't that mean it will allow the least secure when the other isn't available?
Thanks in advance for any help on the matter. I can't see buying more LR devices and trying this route if it doesn't get easier.
Only while it is not paired. Disabling the S0 on SmartStart just disables it pairing to your hub, not on the device itself. Once it is paired it does not really matter anymore. I would suggest not messing with the SmartStart settings.
This is probably a dumb question, but why is selecting any security necessary if all it is used for is the initial pairing to my hub? It seems like I could use no security for everything to reduce traffic. I'm assuming based on what you said that a device knows it is paired to something and once paired, can't be paired to another hub, interrogated by something, etc.
I am using the "SmartStart Manager" app. I should have mentioned in my initial post that I do not have any ghost nodes. All devices paired as a mesh have "Refresh" and "Rebuild route" available to select and my LR devices only have "Refresh" available. On that topic....before I switched to "Z-Wave JS", my LR devices did not show up under the "Z-Wave Details" and they were always listed under "View SmartStart List" in your app. They would show up as "Included". After switching to "Z-Wave JS", now the devices do show up under the "Z-Wave Details" (which is nice), but my "SmartStart List" is empty. Is this normal? I have a 1 Inovelli switch, 1 Zooz contact sensor, and 4 Minoston outlets paired as LR.
Once I know whether this all looks correct, I can try pairing again and see if anything useful is showing up in the live logs while attempting to pair the lock.
The security is used all the time once paired. The settings in SmartStart are only used for pairing. Locks require security or they will fail to pair, so do not change the default settings in SS after you scan the QR code, unless you need to change the boot mode for some reason.
The issue with LR devices not showing under the legacy gateway was a known issue, I guess Zwave JS resolved it for you, so thats good.
The SS List is tied to the Zip / JS gateway, so when you switch to JS for the first time it starts out blank. You do not really need the device in the SS list after it is paired, unless you need to pair it again later and do not have easy access to the QR code.
So for a new light switch or outlet, would it be OK/recommended to change to "No security" in the "SmartStart Manager" and then once it is paired, those devices won't use any security going forward? Just trying to minimized any potential delay at all for light switches and such.
I thought a while back I saw in a post where you had some other application used for additional logging and such that can be useful in these situations. Is this the case, or should I just have live logs open and see what happens?
S2 security works fine on the current platform and C8/Pro hubs so I would just leave it enabled. The traffic overhead is very minimal with S2, and has some advantages like supervision. I think LR also requires S2 if you want to use LR.
There is no additional logging for pairing, just keep the unfiltered live logs open.
No, i definitely didn't start inclusion manually. I have read all of the directions multiple times. All I do is use the newer elevation app to add the device...hit the plus button, choose "add smart start devices, then take a picture of the qr code. That gets it added to the smart start list. I then insert the batteries into the lock.
They must have changed the log messages then, because the last time I used SS the initial log message says something about SmartStart. Those logs you posted are exactly what shows when you manually start pairing.
Either way, you need to figure out why the radio keeps jamming.
