I'm running a first generation Eisy with the latest IoX (recent update). I have the Z-Matter Dongle where I have my Zigbee devices communicating to the Eisy system. The dongle is directly connected to the Eisy's USB port on the side, no extension cable in the mix. This setup has worked flawlessly for years through many updates and rebuilds... I've never had any issues with Zigbee devices suddenly not communicating.

I performed the update as instructed by doing the Z-Wave backup first, backing up IoX, PG3, then updating and everything seemingly went just fine except Zigbee is failing to communicate. I see a lot of threads where Z-Wave and Zigbee seem to be a special case, so before I just start clicking things to try to get it to work and make matters worse, I'd like to see if anyone can help troubleshoot this.

I'm getting this message when I query any one of the Zigbee devices. It seems that there is possibly one node from one device that is working (alarm siren) however all other nodes from this device seem to be blank and unavailable... I just can't remember if they were like that before or not. The alarm sensors (water alarm sensors) all seem to be failing to communicate.

When I query it I get:

Here's a list of these devices (my only Zigbee devices):

When I log into the web UI, I get this yellow banner across the bottom left which as you can see is clearly related to the Zigbee issue(s):

Also in the Java Admin Console, I'm seeing this when I click on the Zigbee menu across the top:

Also, yes, it is all turned on in the configuration pane:

Not sure where to go from here, if anyone could please help it would be greatly appreciated!

Thank you in advance!

Edited Monday at 02:16 PM2 days by StangManD

I do remember a similar recent case where someone had upgraded from 6.0.4 to 6.0.5 and his zigbee failed like that. UDI helped them to roll back to 6.0.4 and that fixed it. It was never explained what went wrong. And if I remember right, that person later upgraded to 6.1.1 later and that went well. Myself I have a eisy running 6.1.1 and a Polisy on 6.1.2, both with ZMatter dongles and zigbee is working fine on both.

You might need to open a ticket on this one.

6 minutes ago, Guy Lavoie said:

I do remember a similar recent case where someone had upgraded from 6.0.4 to 6.0.5 and his zigbee failed like that. UDI helped them to roll back to 6.0.4 and that fixed it. It was never explained what went wrong. And if I remember right, that person later upgraded to 6.1.1 later and that went well. Myself I have a eisy running 6.1.1 and a Polisy on 6.1.2, both with ZMatter dongles and zigbee is working fine on both.

You might need to open a ticket on this one.

Thanks Guy. I'm currently trying a graceful powerdown (Eisy button press x6) then a power cable pull for a minute... will report back if that jump starts anything.

3 minutes ago, StangManD said:

Thanks Guy. I'm currently trying a graceful powerdown (Eisy button press x6) then a power cable pull for a minute... will report back if that jump starts anything.

That's a good first step.

Well it looks like that kick-started all of the Zigbee devices (they seem to be reading states now in the admin console) however I am still getting that same "Pending Operations" message and now see this in the web UI when I hover over the device:

The Zigbee menu across the top of the Admin Console is now live and working correctly... so wondering if there's something that needs to be done and triggered now that the dongle is awake?

I tried to "write changes" from the admin console first and then from the web UI and nothing happens... looks like that device is somehow stuck for some reason however it's showing the alarm state itself, so I'm not sure what's going on. I've created a support ticket, I'll post back what we find. Thanks again.

26 minutes ago, StangManD said:

Well it looks like that kick-started all of the Zigbee devices (they seem to be reading states now in the admin console) however I am still getting that same "Pending Operations" message and now see this in the web UI when I hover over the device:

The Zigbee menu across the top of the Admin Console is now live and working correctly... so wondering if there's something that needs to be done and triggered now that the dongle is awake?

Is the device (the ZY 003 Sound Switch) a battery powered device? If so, do whatever is needed to activate it, and then do "Write Changes" (by right clicking on the node in Admin Console).

39 minutes ago, Guy Lavoie said:

Is the device (the ZY 003 Sound Switch) a battery powered device? If so, do whatever is needed to activate it, and then do "Write Changes" (by right clicking on the node in Admin Console).

This seems to have done the trick... it's a plug-in siren that has a built in battery backup. I pulled it from the wall outlet to force it onto battery then performed write changes and it updated all of the icons to what they were before in the admin console. The "write changes" is still there however I think it's working now. Thank you!