Schlage BE469 battery change out issues

[Ajax]

Ok, wanted to check if I am doing something wrong. My batteries in my lock last me a couple months, but once they are dead and I replace them with new ones I cannot get the lock to connect back to the ISY? Each time I have to take the lock off to get it close enough to do a secure connection, do a master reset( gives me a cannot connect secure device error, if I dont) then exclude it x2 and then I can add it to the ISY.

 

I have tried to heal the network etc, after a battery swap but since this is a battery device it probable in sleep mode, so that does not help.

 

Any advice, thanks

[Jimbo.Automates]

You shouldn't have both do that. I've replaced batteries a few times with no issue, although I never let them completly die. Also, I have been using the Duracell procell which last longer. Is your lock a direct neighbor of the ISY or does it repeat thru another device? And if so, what device?

 

Sent from my Pixel C using Tapatalk

[Ajax]

Its going thru an Aeon siren repeater. Will have to give those batteries a shot, thanks 

[Jimbo.Automates]

Its going thru an Aeon siren repeater. Will have to give those batteries a shot, thanks

That's what I use as well, so not sure what the problem would be.

 

Sent from my Pixel C using Tapatalk

[Xathros]

I too have replaced batteries in my 469 a few times without any relinking needed.  Like Jimbo, I never let mine die completely but pretty sure it took me long enough with the batteries out during replacement to simulate a completely dead state.

 

-Xathros

[stusviews]

Just a note of caution. Do not use lithium batteries for locks. Although they last longer, lithium batteries are known to die without warning.

[Ajax]

Nope these are just standard duracell ones.

[stusviews]

Try placing the lock in linking mode, then try heal again. BTW, have you tried synchronize? BTW, I've also replaced batteries w/o a need to include the lock.

[Ajax]

Thanks guys will give that a shot next battery change and report back.

[jbisson]

I have a similar issue with my BE469 when I change batteries.  After replacing the batteries, I have one way communication: ISY receive the status update from the lock when I lock/unlock, but I cannot lock/unlock from the ISY (error is "Cannot communicate with ...  Please check connections").

So I have to start over by including the device again, and then update all my programs to use the "new" device.

I've tried heal, synchronize and "heal in linking mode" (like stusviews suggest), reboot isy, but nothing worked.

Anything else to suggest?

Thanks

[Ajax]

Yeah I havent found a solution yet either. Just changed mine out again this weekend. Same thing-I can see the status updates but no control... I had I txt alert set for battery level 95% to see if I change it out before it gets too low, but that did not help either. Something I thought was about the repeater siren-Does that have to be added securely as well? BC I havent tried that yet. 

[stusviews]

I use all of the siren, doorbell and Gen6 repeater. Only the Gen 6 repeater needs to be added securely, the other two devices include security when they're added.

Select Tools, Diagnostics. Set the Level to 3. Right click on the lock. Select Z-Wave, Show Information in Event Viewer. Network Details.

Find the line that says your "Deadbolt has the following neighbors." If included correctly, then the siren should be listed.

[Ajax]

OK looks like it does not have the siren as a neighbor even tho its installed. So jus remove and add the siren back? Or how to I make them "neighbors" Taking them a beer seems so much easier! 

 

[lilyoyo1]

If your siren is part of your network, I would recommend doing a network heal

 

[stusviews]

If heal is not successful, then try Synchronize Nodes.

[Ajax]

Did a battery swap again, same issue my Siren does not show as a neighbor, heal and synchronize does not fix it either.

 

 

Error when I try to sync

 

[MWareman]

Did a battery swap again, same issue my Siren does not show as a neighbor, heal and synchronize does not fix it either.

 

 
Error when I try to sync
 

What does the log look like while a ‘Heal’ is running?

[lilyoyo1]

I'd exclude the siren and the include it again. Once done run another heal

[Ajax]

Just tried removing the siren, that did not work, 

 

[Ajax]

[dbuss]

22 minutes ago, Ajax said:

Just tried removing the siren, that did not work, 

 

 

38 minutes ago, Ajax said:

Just tried removing the siren, that did not work, 

 

Were you able to successfully exclude and then successfully include the siren?

[lilyoyo1]

Plug the siren in closer to the ISY and try it. If it doesn't work, it may be a bad siren

[PhanTomiZ]

HI,

Why when updating neighbors the time allowed is only 20 seconds?  When I do a Z-Wave Heal, the time allowed is 72 seconds.  Most times it either passes in around 20 to 40 seconds and fails closer to 70 seconds.

[Ajax]

Where would I change the time? I did remove it correctly I believe. I even did it a couple times before I would add it back in. One time it gave me an error that it could not add secure device and I excluded it twice and it worked to add it back in but still errors

 

[PhanTomiZ]

I don't know how one would change the time, but I'll bet it's not adjustable.  Maybe the time is dependent on how many Z-Wave devices are in your system.  Hopefully somebody can chime in on this part of the question.

What I have done today to Heal my Z-Wave and come up with "Success" is:

1.Run the Heal
2.When it gets to the device that is Failing, go to the said device and right click the device and synchronize(again I have 72 seconds to do this to get a Success).  When I started to read this post, I decide to try it for myself with my intermittent Kwikset lock.