#kwikset home connect 620 / zwave issue

63 messages · Page 1 of 1 (latest)

fringe kernel
#

Hi!

I've recently had some issues with my home connect 620 updating the state correctly.
It was locking and unlocking just fine, but it wouldn't update the state, so I didn't know if it was locked or not from the home assistant UI.

So I started clicking buttons inside the Zwave JS UI, and I THINK I broke something.

I tried a bunch of things, re-intereviewed, refreshed the values, tried rebuilding routes... all of that didn't change functionality and the lock was still cycling, but state wasn't updating.

I then tried clearing the associations, and now everything is undefined.

The lock still shows up in the UI, and I can reinterview it, but states aren't showing up (which tracks, because the dialog that pops up when you go to clear associations says that'll happen until you set up a lifeline association) I have no idea how to set that up.

Can anyone help?

fringe kernel
#

API calls are working, like, I can set a user code from a call in HA, and it passes the code to Zwave JS UI... But the states still aren't updating... any thoughts?

#

I THINK it's on the return route that is having an issue, but I'm not sure how to fix it

image.png
opal thicket
#

The Lifeline association is required to send updates to the controller

#

Re-interview should have fixed that, but double check

fringe kernel
#

So I actually figured it out just now

#

Ultimately... I power cycled the lock lol

opal thicket
#

What do the route stats show now? The screenshot repeater signals are very low.

fringe kernel
#

Pulled the battery pack off and let it run dry, then back in, and repaired the connections

#

One sec

#

Where is the easiest place to grab that?

opal thicket
#

same logs

#

or network map in ZUI

fringe kernel
opal thicket
#

it's on the links connecting the nodes

#

i can kind of see the failed ones, NLWR

fringe kernel
opal thicket
#

3 hop with low RSSI, not ideal 😬

fringe kernel
#

So I'm not TOTALLY surprised, that lock is like 160ish feet from the nearest node

#

It's on a shop door, there's a wellhouse in-between, but nothing in there, and in order to bounce off something directly, it needs to be a secure node, so the only route I can manually set is straight to the controller

opal thicket
#

Ok, makes sense then.

#

I don't have many multi-hops, but the last one is usually around -50 dBm in my network

fringe kernel
#

node 32 here is the only other thing I have that I could bounce off, and I might throw that in the wellhouse to see if it improves latency

image.png
#

It's currently in use for our christmas trainset that I haven't put away yet lol

opal thicket
#

Locks seem to be pretty touchy

fringe kernel
#

but I bet I can find a reasonable repeater that'll do the job and cut the distance in half... I'm planning on doing a bunch out there in the shop at some point anyway

#

This was a nightmare to get working correctly.

opal thicket
#

You could try a second network, if you have an ethernet connection in the shop.

fringe kernel
#

I dunno if I will. Haven't ran power out there yet, but that's on the table

#

Can you link two networks?

opal thicket
#

well, they're linked via HA. it can support multiple Z-Wave integrations.

#

a POE-based controller, or small SBC + USB stick/GPIO are "easy" ways to get a controller in a remote location

#

I'd probably try another repeater somewhere first, but if you're expanding in that location a 2nd network might make sense too.

fringe kernel
#

Ooh, interesting. I'd have to look into how that would be set up, I have my current controller plugged into the HA box, how do you tell HA to use a controller on another box?

opal thicket
#

either run ZUI on the SBC, and connect the same way, or use ZUI somewhere else and connect via TCP serial (ser2net) with a POE controller

#

HA just connects to a websocket server (ZUI hosts it)

fringe kernel
#

ahhhh got it

#

that's cool

opal thicket
#

the POE one you need to run ser2net somewhere, and the run ZUI somewhere (remotely or same host) to connect to the TCP serial port

fringe kernel
#

Wasn't even considering that. I'm running zwave in its own docker container, so that was just a duh moment

opal thicket
#

err, actually that's not quite accurate, the POE controller runs the ser2net equivalent, so only need ZUI

#

then easy if you aren't using add-ons, you can just spinup a 2nd container

fringe kernel
#

Yup

opal thicket
fringe kernel
#

just couldn't do any of the stuff I'm not using anyway (Like group actions without the host)

#

Oooh that's cool.

#

I'd probably have a multi-use box out there for a screen or something, so I'd probably just run a zwave controller on it and link it back to my host over the network

opal thicket
#

yeah, that works well

fringe kernel
#

Probably should run ethernet... lol

opal thicket
#

preferably (not over wifi)

fringe kernel
#

Power's going to cost $1500USD, the extra conduit for the CAT5 won't be that much more of a lift

#

Neat. good chat. Thanks for the input. I'll try a repeater for the short term, but I think you're right, a second network is probably a better option... unless I can find a decent LR repeater

opal thicket
#

well, LR doesn't support repeaters

fringe kernel
#

whelp. that's out lol

opal thicket
#

LR is another option, except there's like only one lock on the market currently. Also the upcoming Nabu Casa controller (soon ) is supposed to have great range.

#

An 800-series device still might make a better repeater, as the chips themselves have better range.

fringe kernel
#

Actually, will my 700 series controller even work with that?

#

looks like it

opal thicket
#

yes, they are all fully compatible

#

I don't usually like dedicated repeater devices, since you get actual functionality from something like a switch or plug. At least that one has a power notification.