Zigate receive NACK on everything

[pipiche]

I think you are mixing some stuff.

This is normal that you receive NACK, because the device get disconnected. The only think that you have with the parameter is to not take any action out of the NACK.

So don't focus on those messages, we need to identify why the device is getting disconnected. Could be related to the plugin

[ronaldbro]

I just tried to reconnect a tradfri with the reset button, but that doesn't work. Poweroff/on now does nothing.

I'm thinking of a hard reset and try to join everything again. What do you think?

[pipiche]

This sound indeed a good idea

[ronaldbro]

And I did, but it was a hassle...

First I switched to latest stable (I already wanted to stay on stable, but trouble brought me to beta again)
I did a full reset. (Noticed it can't be done from the admin portal anymore so I used the plugin settings)
But now binding didn't work. Tried to bind a tradfri, gredopto and a xiaomi PIR, nothing worked.
Switched to an older version of the plugin (4.7.001) but still no binding.
Another erase hardware and still no luck.
Flashed back to firmware 3.1a and another erase just to be sure.
I could bind again
Switched to latest stable and binding still works.
Flashed to firmare 3.1c again
And my already binded devices still work, did not receive NACK on those. Only on devices I had to bind again.
Bind other devices, created groups and everything works. Get no NACK anymore.

Wifi and zigbee channels are still the same, zigate locations is the same so basically nothing changed.

My conclusion, there's a bug in firmware 3.1c which can cause a blocked zigate.

[abroeders]

I still have my device that causes NACK. I don't want to go through the trouble of resetting and rebinding 48 devices at the moment. My Tradfri bulb has to wait, luckily the energy consumption of the light bulbs isn't too big.

Can it have something to do with the amount of devices? I remember a discussion before about some maximum devices. I know you have a lot of devices too Ronald.
Another thing, my raw devices.json is about 5 times bigger as yours. I think you have more devices as I do. What is the size of this device.json now, after you rejoined everything again?

[pipiche]

Maximum number of devices is 40

[abroeders]

Hi Pipiche,

40 is then the maximum directly attached to the ZiGate right? I remember indirectly the Zigate could address about 70 devices. Is this correct? Otherwise i'm over the maximum already.

Firmware 3.0b states: "Up to 80 devices. 50 ZiGate's children and 30 others devices linked to routers". Is this capability shrunk in later versions?

Could it be that in rare cases where an other device linked through a router tries to connect directly to the Zigate removes/cripples some other entry in the Zigate?

I'm just trying to speculate on what could be happening.

Also, a bit offtopic but to cleanup my Zigate, my Zigate was paired with two battery powered remotes that I don't use anymore. I removed the domoticz devices, but the configuration still exists in the zigate plugin (and probably in the Zigate too). With non battery powered devices I noticed a garbage bin icon in the plugin to remove the configuration, but this doesn't exist for battery powered devices?

[ronaldbro]

Unfortunately my luck didn't last long. NACK is back
It started when I added some more end devices. Xiaomi door sensors and a Xiaomi/honeywell smoke detector. So I'm going to flash back to 3.1a and see how that goes.

@abroeders firmware can handle 40 devices directly and 30 via routers so a total of 70 in theory. But most devices prefer to connect to the zigate directly which means that if a router disconnects for some reason and an end device takes it place at the zigate that the router can't rejoin. I had this problem before with 45 devices and because of this I moved the hue bulbs back to hue and some of the Xiaomi's back to Xiaomi leaving only 30 devices on my Zigate.

[pipiche]

Unfortunately my luck didn't last long. NACK is back
It started when I added some more end devices. Xiaomi door sensors and a Xiaomi/honeywell smoke detector. So I'm going to flash back to 3.1a and see how that goes.

@abroeders firmware can handle 40 devices directly and 30 via routers so a total of 70 in theory. But most devices prefer to connect to the zigate directly which means that if a router disconnects for some reason and an end device takes it place at the zigate that the router can't rejoin. I had this problem before with 45 devices and because of this I moved the hue bulbs back to hue and some of the Xiaomi's back to Xiaomi leaving only 30 devices on my Zigate.

That is exactly my point. Never go above 40 devices. It is no senses for me to rely on the routers topics ! I know that Akila is working on a Larger Zigate, but I have not idea on when it is coming.

[ronaldbro]

It worked fine for a while for me and I guess it can work if the devices above 40 are far enough away from the zigate that they never can reach the zigate without the routers.

Just switched back to firmware 3.1a and the startup took a lot longer. Had to discover groups again but most is working again but with a delay. Think I need a resetConfigureReporting/resetReadAttributes

[pipiche]

Honestly I don't understand why you are falling back to 3.1a

Mst-likely the resetConfigureReporting could help re-establishing the bindings with the main powered devices. I don't think the resetReadAttributes will provide any benefits

[ronaldbro]

That’s because I think 3.1c contains a bug which blocked outgoing commands. That’s the only explanation I could think off for which I experienced.
But I still have trouble. (Didn’t do a hard reset after switching back)

[ronaldbro]

That’s because I think 3.1c contains a bug which blocked outgoing commands. That’s the only explanation I could think off for which I experienced.
But I still have trouble. (Didn’t do a hard reset after switching back)

[pipiche]

There is no evidence of a bug as such, or at least it has not been demonstrated. I have plenty of users with a similar environment as yours without this behaviour.

In your case , you had NACK because the device was disconnected from the Zigbee network.

Last as you did downgrade the firmware, you must do an Erase EEPROM and then later an ErasePDM in order to work with a clean Zigate memory

[abroeders]

Pipiche,

If I buy an extra Zigate and split my network in 2 channels, can I migrate devices from the first to the second network and preserve the devices in domoticz? If migration is possible, should I just bind the device to the new network and the plugin re-establishes the link with the existing domoticz device?

Then, how to remove the device from the old network without removing the domoticz device? Is there some way to cleanup an existing Zigate and remove obsoleted devices.

Also, can I create groups containing devices from both networks? Are there other users known that use more instances of the Zigate plugin on 1 system?

[pipiche]

Pipiche,

If I buy an extra Zigate and split my network in 2 channels, can I migrate devices from the first to the second network and preserve the devices in domoticz? If migration is possible, should I just bind the device to the new network and the plugin re-establishes the link with the existing domoticz device?

Devices created in domoticz are linked to a plugin instance. So with a 2nd Zigate you will get a 2nd plugin instance which won't see any of the existing devices.

Now, if you play with Sqllite in order to do the shift in Domoticz and then Edit DeviceList and split it, it could work, but I would say that you won't get much support from there. And especially on the Domoticz DB I have no clue if there is no relation between different tables.

To finish on Domoticz, for widgets like Temperatures ... there is a way to keep the history through and Update button you have on the widget and where you can merge a new widget with an old one

Then, how to remove the device from the old network without removing the domoticz device? Is there some way to cleanup an existing Zigate and remove obsoleted devices.

Not easy , as battery device removal doesn't work, as the removal has to come from the device itself and with Xiaomi it doesn't work well.

Also, can I create groups containing devices from both networks?

You cannot. Native Zigbee group is per Zigbee coordinator and so per zigate

Are there other users known that use more instances of the Zigate plugin on 1 system?

I have that on my dev system where I have 3 Zigate connected ( USB, PiZiGate and DIn-Zigate). and it works well with 3 Web Admin interfaces
Someone is having a production where there are 2 Wifi Zigate operated under the same Domoticz. Basically the split that he has done, is one Zigate for floor 1 and one Zigate for Ground floor

[ronaldbro]

Hi Pipiche,

I'm willing to give the new firmware another try. I moved my pi to the living room and want to start only with devices downstairs. Devices upstairs will be bound to hue and xiaomi hub. Xiaomi is on channel 15, hue on 20 and zigate on 26. WiFi still on channel 1.

I flashed to 3.1c again. At this moment I still have NACK's. But at this moment I can put the blame on flashing firmware forward and back. So I want to be really sure I start with a clean zigate.
What's the best way to erase EEPROM and erase PDM? I noticed that this is removed from the settings tab on the admin portal.
Please advice.

[ronaldbro]

@Pipiche, Can you help me reseting the ZiGate. Really don't know how to do this using Firmware 3.1c and the latest beta. Last week I did it by flashing bak to 3.1a and using an old plugin, but this should be necessary.

In the admin webportal the option is gone and I already tried the hard reset in the domoticz plugin settings but when I do that it's not possible to bind anything. Please help.

[ronaldbro]

I'm 100% frustrated right now
Flashed back to 3.1a and beta plugin of december 22nd (last before 3.1c when everything still worked perfect), did an ErasePDM and hard reset and can't join anything. Zigate does nothing.
I guess it died

[pipiche]

Quiet surprise that the Zigate died with such actions.

I think this is an USB Zigate. If so you can test it on windows with the SGUI user interface ( https://zigate.fr/documentation/tester-la-zigate-usb/ )
In case it doesn't work:
- Try to do a Firmware flash . Make sure to have the Erase EEPROM
- Try again with ZGUI

If there is no success, the best is to contact the Zigate vendor