I have two 8235.112.ZW Baldwin locks, burning through batteries in 2 weeks. Looking at the logs, over 200 entries per minute. Is there a feature that could slow or shut off these entries?
A small sample:
dev:12026-03-12 04:14:26.104 PMinfolast code 30 fetched, fetch complete
dev:12026-03-12 04:14:26.102 PMdebugno changes to codeNumber:30, code:null, codeMap:[:]
dev:12026-03-12 04:14:26.099 PMdebugUserCodeReport- cmd: UserCodeReport(userIdentifier:30, userIdStatus:0, userCode:null)
dev:12026-03-12 04:14:26.095 PMdebugparse: zw device: 0A, command: 6303, payload: 1E 00 00 00 00 00 , isMulticast: false
dev:12026-03-12 04:14:25.930 PMdebugfetchLockCode- 30
dev:12026-03-12 04:14:25.928 PMtracetrying to fetch code:30
dev:12026-03-12 04:14:25.927 PMinfocode:29 fetched
dev:12026-03-12 04:14:25.925 PMdebugno changes to codeNumber:29, code:null, codeMap:[:]
First use of the Hubitat Hub. Any help appreciated.
Is it constantly fetching codes? .. This should not be all the time..
Bryan, The options for the lock are these:
Enable lockCode encryption - set to not enabled
Enable debug logging - set to enabled
Enable descriptionText logging - set to enabled
Enable command retry logic - set to not enabled
I just replaced the 4 AA, Settings were showing 0% before, now at 60%.
Thoughts?
Mike
We need to figure out why it's seems to be continuously fetching codes.. That will wipe out the battery quick as it's constantly transmitting..
Can you PM me your hub id so I can pull logs?
Bryan,
----REDACTED HUB ID----
I tried turning off some of the items on one of the locks but not enough time to declare good/bad. Like Wednesday PM. New batteries in both yesterday.
Mike
Thanks for looking!
Remove your hub ID from your post and send it via PM. You don't want that out here for all to see.
Join the owners group if you are currently unable to send a PM.
That doesn't seem right, what type battery are you using? Rechargable? NiMh? Lithium? Alkaline?
Were they known good fresh batteries?
Myself and others over the years have noticed that if you don't have enough repeating devices, or your repeaters aren't close enough to the lock, the lock will burn up batteries like this. The lock will struggle to communicate with the hub.
Do you have a lot of Z-wave devices? Are they battery powered, or line powered (i.e. plugged in or hardwired)? Approximately how many of each (battery vs line power)?
I have 40+ ZWave devices but these two locks are the only devices not under Z-10 URC Hub. Vast majority of the URC Z Waves are hard wired.
Re battery - less than 2 month old rechargeables, Duracell.
Front door within 10' of the hub, back door about 60 feet away,
I do not have any stand alone repeaters.
Just started here so not aware of a PM.
Mike
Please clarify this.
-
So you have about 40 devices on a different hub?
-
And these two locks are the only Z-wave on Hubitat?
Those Z-wave devices, whether they repeat or not, don't do one bit of good (and maybe even hamper) your locks if you don't have them in Hubitat.
That 60% indication is about what you will get for rechargeable batteries. Their chemistry and their full charged voltage is different than alkaline. The lock and hub simply go by voltage, and the voltage curve of different chemistries varies. I suspect the manual calls for alkalines here, most smart home devices do unless they call for Lithiums.
In addition, I doubt these Duracell are low-self-discharge batteries. Typical Nickel Metal Hydride (NiMh) lose a portion of their charge due to time, not usage. A typical NiMH can lose 13.9% to 70.6% per month at room temperature, just sitting there.
If you insist on using rechargeables, (I use them) then be sure to get a low self discharge (LSD) NiMH. Eneloops are one well known brand, but there are many other that have this too. And be prepared to charge the batteries fairly regularly, I go about 2-3 months on a charge instead of the year or so with Alkalines.
Clarification:
URC/Total Control/Control4 manage the 40+ Z Wave switches, screens etc. and I do not have access to the program, have to pay $225/hour for any support. During Alexa 2.0 upgrade, the URC Z 10 hub would not allow Alexa to open or close the locks.
I went with the Hubitat as a trial and only the 2 locks are on it and so far so good, just the battery life on the locks seems off.
It would take me the a few days to add any of the URC controlled devices to Hubitat. I could get some Z Wave plugs to place midway between the back door and hub. Not sure if that would help the logging events.
Regarding batteries, they Duracell rechargeable, shows as NiMh type, 400 charges available. No idea if LSD type.
Next?
You don't need their support to remove Z-wave devices, just do a factory reset and join the devices to Hubitat. Hubitat can do the exclusion of a device before doing an inclusion. As long as the device is on the compatibility list (or known to work with Hubitat) you should be fine. It is no different than if a hub (of any brand) died, you could do an exclusion then inclusion both with the new hub. This is from the Hubitat documentation Add Device | Hubitat Documentation
If you cannot for whatever reason move the other devices, I would get a couple Z-wave repeaters, or even replace some old light switches with newer versions. Zooz always has good sales, you can get a very nice switch/dimmer for $25-35.
How did these locks work previous to Hubitat? Were you using the same batteries?
So as @neonturbo pointed out. Lack of repeaters are likely the the issue. Since the control 4 devices are a separate mesh from Hubitat, those locks won't use them so they are connecting directly to the hub. This happens to a lot of locks (and other devices) when there are no repeaters.
That would certainly help with repeating. Put one as close to the hub as you can. then one half way to the hub. Remove batteries from the lock and reinstall (to power cycle) and wait a couple of days for the mesh to settle and see how things behave.
