Zigate receive NACK on everything

[ronaldbro]

Hi Pipiche,

It’s a PiZigate, so windows won’t work.
How do I do an erase EEPROM?

[pipiche]

So ErasePDM is the onlyoption.

So if it doesn't work, contact the ZIgate vendor, might give you more hints

[ronaldbro]

ErasePDM is the only option in the old plugin. In the current plugin there is no option at all

[pipiche]

The ErasePDM option is on the Hardware Menu when Updating the plugin .
So then I understand that you did the firmware downgrade without Erase, which explain all of your issues

[ronaldbro]

No, I did the ErasePDM with the admin portal of an old plugin and on the plugin settings in Domoticz. Didn't know for sure is the option in de settings page of domoticz was working well because there used to be an ErasePDM checkbox in the portal and a hard reset button.

[abroeders]

There must be something wrong with this NACK thing... I can't imagine nobody else has any problem with this.

I ordered a new ZiGate Wifi last week because i had more as 40 devices, so I wanted to split my network in 2 segments. Beside of that, I wanted to clean up my domoticz so installed a new domoticz server; upgraded to latest beta of domotics and Zigate plugin 4.7.005 (latest stable). Set a different channel (25) with no overlap. (My other zigbee network is on channel 11)

Last night i bound 26 devices to this new domoticz server. This morning:

2020-02-23 12:56:07.798 Status: User: arno initiated a switch command (31/Kleurenlamp Woonkamer/On)
2020-02-23 12:56:13.288 (Zigate1 channel 25) UpdateDevice - (Kleurenlamp Woonkamer) 1:48
2020-02-23 12:56:13.257 Status: User: arno initiated a switch command (31/Kleurenlamp Woonkamer/Set Level)
2020-02-23 12:56:14.408 (Zigate1 channel 25) Receive NACK from Kleurenlamp Woonkamer (99ee)
2020-02-23 12:56:14.510 (Zigate1 channel 25) Receive NACK from Kleurenlamp Woonkamer (99ee)
2020-02-23 12:56:14.510 (Zigate1 channel 25) Receive NACK from Kleurenlamp Woonkamer (99ee)

uncontrolable!

Distance between this brandnew ZiGate and this tradfri bulb: about 3 meters without any obstacles.

After power cycle:
2020-02-23 13:07:34.490 Status: (Zigate1 channel 25) Device Announcement Addr: 99ee, IEEE: 90fd9ffffe1fc29d Join Flag: 0x00 - join a network through association RSSI: 162

At least this bulb is controllable again after powercycle. Last time a power cycle didn't help and even rebinding did not help (this was on a zigate with 48 devices)

Pipiche, is there something I can help to pinpoint this problem.

Another interesting thing.. binding a number of devices in sequence often fails. Switching 'Accept new devices' from on to off, restarting the plugin, and switching 'Accept new devices' from off to on again lets me bind another 2 to 4 devices. After some device bindings I get timouts while binding and have to do this again.

[pipiche]

Pairing a new device, is quiet a complex process, indeed you must do it one device at a time.

[pipiche]

There must be something wrong with this NACK thing... I can't imagine nobody else has any problem with this.

I ordered a new ZiGate Wifi last week because i had more as 40 devices, so I wanted to split my network in 2 segments. Beside of that, I wanted to clean up my domoticz so installed a new domoticz server; upgraded to latest beta of domotics and Zigate plugin 4.7.005 (latest stable). Set a different channel (25) with no overlap. (My other zigbee network is on channel 11)

I don't think it is a good idea to have channel 11 and channel 25. What is the Wifi 2.4 channel ?
If Wifi is on Wifi 2.4 channel 11, I would use Zigbee channel 11 and 12. That would be more than enought.

Last night i bound 26 devices to this new domoticz server. This morning:

2020-02-23 12:56:07.798 Status: User: arno initiated a switch command (31/Kleurenlamp Woonkamer/On)
2020-02-23 12:56:13.288 (Zigate1 channel 25) UpdateDevice - (Kleurenlamp Woonkamer) 1:48
2020-02-23 12:56:13.257 Status: User: arno initiated a switch command (31/Kleurenlamp Woonkamer/Set Level)
2020-02-23 12:56:14.408 (Zigate1 channel 25) Receive NACK from Kleurenlamp Woonkamer (99ee)
2020-02-23 12:56:14.510 (Zigate1 channel 25) Receive NACK from Kleurenlamp Woonkamer (99ee)
2020-02-23 12:56:14.510 (Zigate1 channel 25) Receive NACK from Kleurenlamp Woonkamer (99ee)

uncontrolable!

Distance between this brandnew ZiGate and this tradfri bulb: about 3 meters without any obstacles.

After power cycle:
2020-02-23 13:07:34.490 Status: (Zigate1 channel 25) Device Announcement Addr: 99ee, IEEE: 90fd9ffffe1fc29d Join Flag: 0x00 - join a network through association RSSI: 162

At least this bulb is controllable again after powercycle. Last time a power cycle didn't help and even rebinding did not help (this was on a zigate with 48 devices)

Pipiche, is there something I can help to pinpoint this problem.

Check interferences.

Another interesting thing.. binding a number of devices in sequence often fails. Switching 'Accept new devices' from on to off, restarting the plugin, and switching 'Accept new devices' from off to on again lets me bind another 2 to 4 devices. After some device bindings I get timouts while binding and have to do this again.

Definitiveley not a good idea. You are putting so much load on the zigate, that for sure some will failed. Do one pairing at the time. Then control that it works, then you can go to the next one.
Otherwise:
- You have no control on what is done
- You have a lot of load on the Zigate which predict such behaviour

[abroeders]

I don't think it is a good idea to have channel 11 and channel 25. What is the Wifi 2.4 channel ?
If Wifi is on Wifi 2.4 channel 11, I would use Zigbee channel 11 and 12. That would be more than enought.

Wifi channel is temporary on channel 6. I did this because I want my new Zigbee networks on channels 25 and 26 because they show the best signal strength in the energy level scan. According to my Unifi network scan, Wifi channels 11-13 are the most quiet. So after everything is moved from Zigbee channel 11, my Wifi goes to channel 1. I think WiFi channel 6 shouldn't interference with zigbee 11 and 25.

Check interferences.

I'll do my best. Strange thing is that the zigbee device at 3 meters with clear line of sight fails, but zigbee bulbs in the garden at the other side of the house, signal going through 2 walls have no problem. I also don't have any CRC errors or whatever.

Another interesting thing.. binding a number of devices in sequence often fails. Switching 'Accept new devices' from on to off, restarting the plugin, and switching 'Accept new devices' from off to on again lets me bind another 2 to 4 devices. After some device bindings I get timouts while binding and have to do this again.

Definitiveley not a good idea. You are putting so much load on the zigate, that for sure some will failed. Do one pairing at the time. Then control that it works, then you can go to the next one.
Otherwise:
- You have no control on what is done
- You have a lot of load on the Zigate which predict such behaviour

I think we have a misunderstanding. With in sequence (sequential), i mean one-by-one, so after eachother, not at the same time. After binding I do check if the device works before going to the next. After binding about 4 new devices (one-by-one, not all together, not at the same time) this way, without disabling 'accept new devices' in between, binding fails with timeouts and i have to disable/enable accept new devices and/or restart the zigate plugin. I'm not 100% sure if only disable/enable works without restarting the zigate plugin, or, if restarting the zigate plugin without toggle disable/enable will also solve the problem. I'll investigate this further when I'm going to move the channel 11 devices to channel 26.