Zigbee/Yale Assure SL poor performance and not updating

[smitopher (Christopher Smith)]

• Platform information:
  • Hardware:x86_64/4Gb/128Gb
  • OS: Ubuntu 20.04
  • Java Runtime Environment: OpenJDK 11
  • openHAB version: 3.2 Snapshot
• Issue of the topic:
  I have setup 2 Yale Assue SL locks with the Zigbee module
  Adding them to OH was straightforward
  
  
  The lock responds very slowly, when it does
  OH does not update when the lock is manually operated

I set the zigbee logging to debug and it’s very verbose

I have 18 Leviton zigbee dimmers and switches so they generate a lot log noise.

Any suggestion on how to filter just for the Locks?
The lock xml
000D6F0010C99F27.xml (106.1 KB)

Log sample
ohlog.log (105.9 KB)

[smitopher (Christopher Smith)]

Any info I can use when contacting Yale support will also be useful

[hmerk (Hans-Jörg Merk)]

Could you please post the full Java version.
From your given information, it looks like an unrecommended version, which could lead to your bad performance…
Zulu 11 would be the right choice.

[smitopher (Christopher Smith)]

:~$ java -version
openjdk version “11.0.11” 2021-04-20
OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04)
OpenJDK 64-Bit Server VM (build 11.0.11+9-Ubuntu-0ubuntu2.20.04, mixed mode, sharing)

I’m pretty sure that OpenJDK is just as supported and preformat as Zulu.

My issue is with the Yale Assure SL lock with the Zigbee module installed

[hmerk (Hans-Jörg Merk)]

No, we do not recommend using OpenJDK, as there are known issues. Pleas try with Zulu 11.

[chris (Chris Jackson)]

@smitopher

Any suggestion on how to filter just for the Locks?

Yes, use the log file viewer -:

ZigBee Log Viewer

Looking at this I can see some delivery failures from the dongle which likely indicates there is a poor connection to the device -:

This shows the first command sent to the device fails - the coordinator was unable to deliver it. The binding then retries this, and it is successful, but we then also receive a number of responses. Again this indicates that there is likely a communications issue between the coordinator and the device.

[smitopher (Christopher Smith)]

Thank you
I’m going to try to move the dongle closer to see if that makes any difference. There a a great number of routers (Leviton dimmers) between the current dongle position and the door. I wonder why there is a comm problem?

[smitopher (Christopher Smith)]

@chris
I want to validate what I see in the event.log and the openhab.log before I go running off to Yale to complain about their terrible Zigbee implementation.

I started OH and waited until all zigbee things were online

From OH, I locked and unlocked the door lock
I then manually locked and unlocked the door lock.
I then, using the lock keypad, I locked and unlocked the doorlock

I then stopped OH

All I see in the events and OH logs are the actions I took using OH, no status changes or events for actions I took directly on the lock and it’s keypad

Do you agree?
TIA

link to logs
https://gist.github.com/smitopher/b28e897bfb881b48ae62f562249dcb4d

[smitopher (Christopher Smith)]

@chris I’m following up
I have a much smaller OH log

Same test
Set Zigbee looging to DEBUG
Lock and unlock Zigbee Yale Assure SL from OH
Lock and unlock manually
Lock and unlock using Yale Assure SL Keypad
Lock and unlock Zigbee Yale Assure SL from OH
Set Zigbee logging to INFO

openhab.log (125.2 KB)

Log viewer

I see my OH commands and state updates, I don’t see much that I understand in-between the OH lock/unlock iteration. Definitely no state updates for operations performed on the lock itself.

Do we need to get lower level trace?
Is this enough for me to complain to Yale?
Yale tech support suggested that my lock is not close enough
This test was performed with the lock and Zigbee hub in the same room.

[rpwong (Russ)]

@smitopher

All I see in the events and OH logs are the actions I took using OH, no status changes or events for actions I took directly on the lock and it’s keypad

This sounds an awful lot like the same behaviour as Yale/Schlage Z-Wave locks. In those cases, you have to use the alarm_raw channel to get updates from the lock. But I don’t know if the same thing exists with Zigbee.

Schlage BE469ZP smart lock: Is this an improvement over BE468?

Yep, that’s correct. Here’s the original solution, from a thread that started with a Yale lock. https://community.openhab.org/t/zwave-yale-yrd220-lock/34180/5 In OH3, you can apply the JSONPATH transformation directly to the channel, so that it will only send the information you want to the item. [image] I’ve isolated the event and use a simple case statement in a rule to update the lock status. switch (Door_Lock_Alarm_Raw.state.toString) { case "1", case "3", case "5" : { Door_Lock.pos…

[chris (Chris Jackson)]

@rpwong

This sounds an awful lot like the same behaviour as Yale/Schlage Z-Wave locks. In those cases, you have to use the alarm_raw channel to get updates from the lock. But I don’t know if the same thing exists with Zigbee.

Zigbee is totally different to ZWave and the same channels do not exist.

[chris (Chris Jackson)]

@smitopher

Definitely no state updates for operations performed on the lock itself.

You can try to reinitialise the device. Possibly the device did not get initialised fully and is not sending reports back to the binding when the device state is updated.

[smitopher (Christopher Smith)]

==> /var/log/openhab/openhab.log <==
2021-12-08 16:02:59.598 [ERROR] [ng.zigbee.handler.ZigBeeThingHandler] - 000D6F0010C7023F: Exception creating channels
java.lang.NullPointerException: null
  at org.openhab.binding.zigbee.internal.converter.ZigBeeConverterDoorLock.initializeDevice(ZigBeeConverterDoorLock.java:75) ~[bundleFile:?]
  at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.initializeDevice(ZigBeeThingHandler.java:514) ~[bundleFile:?]
  at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.doNodeInitialisation(ZigBeeThingHandler.java:377) [bundleFile:?]
  at org.openhab.binding.zigbee.handler.ZigBeeThingHandler$1.call(ZigBeeThingHandler.java:227) [bundleFile:?]
  at org.openhab.binding.zigbee.handler.ZigBeeThingHandler$1.call(ZigBeeThingHandler.java:1) [bundleFile:?]
  at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
  at java.lang.Thread.run(Thread.java:829) [?:?]

==> /var/log/openhab/events.log <==

2021-12-08 16:02:59.600 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:cd9edd5897:000d6f0010c7023f' changed from UNKNOWN to OFFLINE (HANDLER_INITIALIZING_ERROR)

[smitopher (Christopher Smith)]

I see this allot in my log

[smitopher (Christopher Smith)]

Disable then enable thing

==> /var/log/openhab/events.log <==
2021-12-08 16:11:05.505 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:cd9edd5897:000d6f0010c7023f' changed from OFFLINE (HANDLER_INITIALIZING_ERROR) to UNINITIALIZED
2021-12-08 16:11:05.517 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:cd9edd5897:000d6f0010c7023f' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2021-12-08 16:11:09.470 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:cd9edd5897:000d6f0010c7023f' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2021-12-08 16:11:09.475 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:cd9edd5897:000d6f0010c7023f' changed from INITIALIZING to UNKNOWN
2021-12-08 16:11:09.475 [INFO ] [penhab.event.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:device:cd9edd5897:000d6f0010c7023f changed to UNKNOWN.

==> /var/log/openhab/openhab.log <==

2021-12-08 16:11:34.542 [ERROR] [ng.zigbee.handler.ZigBeeThingHandler] - 000D6F0010C7023F: Exception creating channels
java.lang.NullPointerException: null
  at org.openhab.binding.zigbee.internal.converter.ZigBeeConverterDoorLock.initializeDevice(ZigBeeConverterDoorLock.java:75) ~[bundleFile:?]
  at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.initializeDevice(ZigBeeThingHandler.java:514) ~[bundleFile:?]
  at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.doNodeInitialisation(ZigBeeThingHandler.java:377) [bundleFile:?]
  at org.openhab.binding.zigbee.handler.ZigBeeThingHandler$1.call(ZigBeeThingHandler.java:227) [bundleFile:?]
  at org.openhab.binding.zigbee.handler.ZigBeeThingHandler$1.call(ZigBeeThingHandler.java:1) [bundleFile:?]
  at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
  at java.lang.Thread.run(Thread.java:829) [?:?]

==> /var/log/openhab/events.log <==

2021-12-08 16:11:34.543 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:device:cd9edd5897:000d6f0010c7023f' changed from UNKNOWN to OFFLINE (HANDLER_INITIALIZING_ERROR)

[chris (Chris Jackson)]

Please use the latest snapshot and let me know if this helps.

[smitopher (Christopher Smith)]

smitopher@myth-server:~$ openhab-cli info

Version:     3.2.0-SNAPSHOT (#2613)

No difference

[chris (Chris Jackson)]

@smitopher

No difference

This version is too old. You need to use the latest zigbee snapshot - not from yesterday!

[smitopher (Christopher Smith)]

I installed using apt, I’ll try again tomorrow and perhaps it will be in the snapshot repo by then

[chris (Chris Jackson)]

Yes, if you don’t want to install manually, then I think you have to wait for the nightly update. Sorry.