Complete frustration :: Start over? Throw in the towel? Jump?

Hope this is an appropriate category. I think this may be a Lock Manager topic.

C-8 Pro
2.3.9.136

I am beyond frustrated. The HE worked well some months ago. Things started getting inconsistent. My debugging over the months has me running in circles. The list of things that do not work is a lot longer than the list of what does work. Won't list all the things I've tried. Voluminous.

I started the journey about 7 years ago. Now have a collection of around 58 devices; Zwave, Zigbee, wifi. Primarily Shelly switches, Sonoff & Aqara motion, 2 Yale locks, a couple different brands of dimmers, a few 110 wall plugsb. Things began getting less and less reliable. Just today migrated from a C-8 to a C-8 Pro hoping I simply had a hardware failure. No such luck.

I would love to go back to zero and start over but the thought of unpairing and repairing Zwave devices is overwhelming. I suppose the same would be true for Zigbee devices.

As an example let's talk about the locks. 2 @ YRD256

  • They worked initially. Added users and codes.
  • Later I couldn't add codes for users.
  • Now can't create users and can't add codes to the existing
  • Activity on one lock shows up in the logs but lock #2 does not.
  • I see the lock manager (I think) going through a retry loop in the logs. Will include a little of that.
  • Tried to delete the Lock Manager and re-install. The config data seems pervasive. After the reinstall the same users and codes were there.
  • Both locks are about 20' from the hub
  • Have them set for verbose logging
app:8202024-05-25 04:17:51.472 PMtracegetLockCodesFromDevices- device:Lock :: Front Door
app:8202024-05-25 04:17:51.467 PMinfogetLockCodesFromDevices- devices:[Lock :: Front Door, Lock :: Apartment]
dev:5642024-05-25 04:01:40.029 PMwarnNo event seen from the device for over 3 hours! Something is not right... (consecutive events: 499)
dev:5632024-05-25 03:56:10.025 PMinfoNo VALID lastCheckin event available! This should be resolved by itself within 1 or 2 hours and is perfectly NORMAL as long as the same device don't get this multiple times per day...
dev:3292024-05-25 03:32:59.218 PMinfoLights :: Apt Door Exterior button null was pushed
dev:5642024-05-25 03:28:57.033 PMwarnEvent interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
dev:5642024-05-25 03:28:57.028 PMwarnOne or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 90662 (maximum expected 90)
app:8202024-05-25 03:28:54.613 PMinfogetLockCodesFromDevices- complete
app:8202024-05-25 03:28:54.610 PMdebuggetLockCodesFromDevices- lockCode:2={code=1963, name=Simona}
app:8202024-05-25 03:28:54.607 PMdebuggetLockCodesFromDevices- lockCode:1={code=5862, name=Elisa}
app:8202024-05-25 03:28:54.603 PMtracegetLockCodesFromDevices- device:Lock :: Apartment
app:8202024-05-25 03:28:54.600 PMdebuggetLockCodesFromDevices- lockCode:3={code=7775, name=David}
app:8202024-05-25 03:28:54.597 PMdebuggetLockCodesFromDevices- lockCode:2={code=5862, name=Elisa}
app:8202024-05-25 03:28:54.594 PMdebuggetLockCodesFromDevices- lockCode:1={code=1963, name=Simona}
app:8202024-05-25 03:28:54.591 PMtracegetLockCodesFromDevices- device:Lock :: Front Door
app:8202024-05-25 03:28:54.588 PMinfogetLockCodesFromDevices- devices:[Lock :: Front Door, Lock :: Apartment]
app:8202024-05-25 03:24:36.249 PMinfogetLockCodesFromDevices- complete
app:8202024-05-25 03:24:36.247 PMdebuggetLockCodesFromDevices- lockCode:2={code=1963, name=Simona}
app:8202024-05-25 03:24:36.244 PMdebuggetLockCodesFromDevices- lockCode:1={code=5862, name=Elisa}
app:8202024-05-25 03:24:36.240 PMtracegetLockCodesFromDevices- device:Lock :: Apartment
app:8202024-05-25 03:24:36.238 PMdebuggetLockCodesFromDevices- lockCode:3={code=7775, name=David}
app:8202024-05-25 03:24:36.235 PMdebuggetLockCodesFromDevices- lockCode:2={code=5862, name=Elisa}
app:8202024-05-25 03:24:36.232 PMdebuggetLockCodesFromDevices- lockCode:1={code=1963, name=Simona}
app:8202024-05-25 03:24:36.228 PMtracegetLockCodesFromDevices- device:Lock :: Front Door
app:8202024-05-25 03:24:36.226 PMinfogetLockCodesFromDevices- devices:[Lock :: Front Door, Lock :: Apartment]
app:8202024-05-25 03:24:19.716 PMwarnactions: User junkuser, code 5555 --will be added to [Lock :: Front Door]
app:8202024-05-25 03:24:19.713 PMinfogetCodeUsage- result:[]
app:8202024-05-25 03:24:19.709 PMdebuggetCodeUsage- lockCodes:[[did:257, code:1963, name:Simona, codeNumber:1, codeState:e, codeOption:e], [did:257, code:5862, name:Elisa, codeNumber:2, codeState:e, codeOption:e], [did:257, code:7775, name:David, codeNumber:3, codeState:e, codeOption:e], [did:416, code:5862, name:Elisa, codeNumber:1, codeState:e, codeOption:e], [did:416, code:1963, name:Simona, codeNumber:2, codeState:e, codeOption:e]], code:5555
app:8202024-05-25 03:24:19.705 PMinfogetNameUsage- result:[]
app:8202024-05-25 03:24:19.701 PMdebuggetNameUsage- lockCodes:[[did:257, code:1963, name:Simona, codeNumber:1, codeState:e, codeOption:e], [did:257, code:5862, name:Elisa, codeNumber:2, codeState:e, codeOption:e], [did:257, code:7775, name:David, codeNumber:3, codeState:e, codeOption:e], [did:416, code:5862, name:Elisa, codeNumber:1, codeState:e, codeOption:e], [did:416, code:1963, name:Simona, codeNumber:2, codeState:e, codeOption:e]], name:junkuser

What next? Any ideas? I'm lost.

A simple question .... how can the "app:nnn" or "dev:nnn" value be correlated back to the Application or Device? Thank you

Thanks much for any help
David

Someone else will need to help with lock manager as it is an app that I do not use, but:

If you click on the “Info”, “Debug”, “Warn” or “Error” highlighted text in the logs, it will bring you directly to the device or the rule.

If you click on the “Dev” or the “App”, it will filter the logs to show only that app or device.

Also note that the preferred method to share logs in the community is through screenshots.

4 Likes

People tend to think Lock Code Manager is magic, but it's not: it just read the attributes from your lock devices and sends commands to them -- for example, to read and set the codes. That's where the codes are really stored, and it's why removing LCM ultimately has no effect.

If you're having trouble with Lock Code Manager (and want it to handle everything for you), I'd suggest deleting all codes from each lock. Once you have that done, try to set up things in LCM again.

To delete the codes from each lock:

  1. Navigate to the device detail page for one of the affected locks.
  2. Look under "Current States" for the "lockCodes" attribute. You will likely have something here like {"1": {"name":"John","code":"1234"}}. The goal is to make this list empty, or {}.
  3. To do that, run the "Delete Code" command one for each code you see. They are numbered, the only one in my example above being 1 (yours will be different and you will likely have more). Put this number in the "Code position" box under the "Delete Code" command, then click/tap the button to run the command. Wait a few seconds, and hopefully that code/position disappears from the lockCodes list.
  4. Repeat for each lock.

(Editing to add that I don't see any errors in your log that appear related, though you are likely using an unmaintained third-party Zigbee driver for some other device -- fine if it still works but you may want to look into other options for that.)

1 Like

Thank you, Seastian.

Dang, never noticed being able to click (or hover) over the "Info" etc tags. Very helpful. I did figure out the filtering on the device or app ID.

Noted. Screenshots are preferred. Thanks for the coaching.

Be well
David

1 Like

You say you have problems with other things as well. Can you start by showing us your z-wave details screen in it's entirety? (Use windows snip) This will give us a lot of info about the structure of your mesh.

1 Like

To be honest, I have had so many problems with Lock Code Manager that I just stopped using it for anything other than storing codes on a virtual lock. I kind of use this as my "user/code store". I then activate and deactivate codes on my Yale locks using Rule Machine. It's clunky AF.

It's funny though, sometimes lock code manager even fails to save codes to a virtual lock... There is obviously no zwave/ZigBee communication issues going on in this case...

It kind of annoys me that they have "official" apps like Lock Code Manager that simply don't work very well. I could name a few others too.. Oh well, rant over.

Appreciate your thoughts, @bertabcd1234

Trouble is .... the HE and the lock #2 doesn't seem to be talking any longer. For lock #2, when I lock or unlock nothing appears in the logs. That suggests to me they are not talking.

I guess my frustration is getting in my way of thinking through effectively, @rlithgow1 . Didn't even look at the Zwave mesh until you suggested it. Sheesh!

It appears completely empty. See the attached capture. Ugly. :frowning_face:

And, was able to lock and unlock lock #1 with the C-8, prior to replacing it with the C-8 Pro.

2024-05-26_13-09-36

The Zigbee networks seem to be similarly boring.

2024-05-26_13-12-57

The hub LED shows green currently and turned off lights this morning. Shelly switches (IP devices)

The hub talked with the thermostat earlier today

Thank you @rlithgow1

Thank you @a.mcdear

I'm not at all certain of the problems' source. Maybe not LCM? Certainly possible. I picked it cuz it is one of the most important to me.

Today, there is no communications with the motion detectors (Aqara, Sonoff, Zigbee) in the logs. Also no comms with the wall plugs (Zigbee).

Will keep your observations in mind when we solve some of the underlying issues. Thank you!

So, have you tried the, shutdown hub, unplug power from wall (not at hub), wait a couple of minutes, reconnect power, wait for startup.

Then check zwave details in settings.

Hey @TArman ... thought about doing so. At the moment, trying to keep it in its current state in case some debug info is needed. That is what I've done consistently in the past to get things working again. Will do that if there is no request for current state.

Thank you!

Can you shut down the hub, unplug power for 2 mins and power back up? Then post your z-wave details page? (the one with all the columns) and see how it shapes up. (shutting down and unplugging clears the z-wave radio)

If you migrate from encryption enabled in lock code manager that can cause problems. So if you had encryption enabled when you migrated, I would definitely suggest you delete all lock codes from the locks, and then put them on again as a part of your troubleshooting.

But definitely do the shutdown pull power wait 30 seconds and restart dance as suggested by @rlithgow1, that is very hopeful in many cases and won't remove any logs or anything.

1 Like

Works fine for me. And others, presumably.

3 Likes

Works perfectly for me on 3 locks.

3 Likes

Thank you, @rlithgow1
Done

No signs of life

Did not use the encrypted feature, @danabw

Yep. Done. Posted the screen capture. Pretty blank. Uggg

Appreciate the thoughts!

Bizarre...can you still control your Z-Wave devices from there Device pages? I think you were saying above that control via device pages was working.

Negative, Ghost Rider :wink:

No luck there @danabw . Have tried poking at the devices through devices/device_name and they are unresponsive.

Thank you!

(I've been trying not to cloud this conversation with the Zigbee issue. Suspect that is a distraction to this conversation.

Things are inconsistent in the Zigbee domain. Some devices can be controlled while others cannot, and it changes over time.

The Shelly switches seem like the most consistent and reliable, though they sometimes go away, also. One of the Shelly's ... the tile on the dashboard does not control the device. Doing devices/device_name does not switch the device. Connecting to the Shelly interface at 192.168.1.53 allows on and off just dandy and the state is shown properly in devices/device_name ; e.g. "on" and "off".

This may be interesting because they are wifi and not RF?

There is both an Aqara and Sonoff motion detectors in this room with me. When I move, I see them trigger. Nothing in the live logs. they are listed in the Zigbee Details table. They were functioning a few days ago and controlling the room lights. No longer true.

Same story with a CMARS US-101, a Zigbee plug. No longer functional.

This may be useful because there is Zwave, Zigbee, and wifi device evidence?)

Do you have Hub Protect?