3 hours ago3 hr TL;DR- If you are using the UD ZMatter ZWAVE/Zigbee dongle and are using Zigbee devices... DO NOT UPGRADE TO v6.0.5! (Rolling back to v6.0.4 restored zigbee ability)I've been a Universal Devices user for over 10 years and have been happy with the performance and upgrades I've experienced so far... at least until last week when I upgraded from EISY v6.0.0 to v6.0.5. When I upgraded to v6.0.5, my zigbee devices stopped working. I couldn't query or add ANY zigbee device back to my system that actually worked. I tried factory resetting the zigbee side of the UD ZMatter Zwave/Zigbee dongle and that didn't help either. When attempting to add a Zigbee device, it would be discovered as a generic device that wouldn't update status or control anything. (See screenshot attached). I opened up a ticket with UD and much to my surprise, Michel responded on a Sunday! Kudos to the support team!They asked for the Zigbee log which I sent them, they replied that my previously working zigbee devices were using "old security keys or credentials" but that clearly wasn't the case. Current status is that Michel is working with the developer and will update at some point. Until then, I'll stay happy with v6.0.4.I'll update if I get new information.-EdThe log snippets:[2026-03-22 17:29:24.643] [E] [...] Ember status 0x66 - The APS layer attempted to send or deliver a message, but it failed.Which end up with :[2026-03-22 17:29:26.268] [I] [...] Interview for Node #50232 failed. Try to force interview or re-inclusion.I think the issue may be that, for some reason, those devices are using old security keys/credentials. Interview is not going to fix this. You may want to try: a) factory reset the device, b) reinclude it, and c) in most cases, you will have to restart the Admin Console after it's added.
Create an account or sign in to comment