errors updating the Zigate firmware

[pocock]

I made Debian packages for JennicModuleProgrammer

https://gitlab.com/dpocock/jennicmodule ... debian/sid

and zigate-flasher

https://gitlab.com/dpocock/zigate-flash ... debian/sid

I'll publish them after confirming they work. The first one doesn't have a free license but maybe it can be published in non-free or an unofficial Zigate repository for users of Debian and Debian-like systems.

Anybody can make a local build of either package, e.g.

git clone https://gitlab.com/dpocock/jennicmoduleprogrammer
git checkout debian/sid
dpkg-buildpackage -rfakeroot -i.git -b

git clone https://gitlab.com/dpocock/zigate-flasher
git checkout debian/sid
dpkg-buildpackage -rfakeroot -i.git -b


If it complains about missing build dependencies, just install them with apt.

Both of them are failing with an error about baud rate. I found other threads and bug reports where people complain about similar problems. Can somebody please advise how to fix the error?


$ JennicModuleProgrammer -V 6 -P 115200 -f ZiGate_Coordinator_v3.1a.bin -s /dev/ttyUSB0
JennicModuleProgrammer Version: 0.6 (r56124)
Setting baudrate: 115200
Error setting baudrate


$ zigate-flasher -p /dev/ttyUSB0 \
-w ~/Downloads/ZiGate_Coordinator_v3.1a.bin
Unpack failed, length: 0, msg
Change baudrate failed
NoneType: None
Unpack failed, length: 0, msg
Change baudrate failed
NoneType: None
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "./zigate-flasher.py", line 208, in change_baudrate
raise SystemExit(1)
SystemExit: 1


I am using the Zigate USB stick, I have two of them here. I tried both commands on a laptop and also on a Raspberry Pi 3 and it always fails.

[pipiche]

Is the Zigate in flash mode when you are trying to flash ?

To put the Zigate in flash mode you have to press on the button on the zigbee module while inserting the Zigate in the USB port.
End result is bleu led with a very light blue and the red one on Ttl module on


Envoyé de mon iPhone en utilisant Tapatalk

[pocock]

Thanks for that feedback, it was not in flash mode. I put it in flash mode and tested both utilities successfully.

Using the zigate-plugin (stable branch) it complains:

Status: (zigate0) Initialized version 4.3.4, author 'zaraki673 pipiche38'
Status: (zigate0) Installer Version Number: 031a
Error: (zigate0) Firmware 031a is not yet supported
Status: (zigate0) Plugin with Zigate firmware 031a correctly initialized


but with 030f it doesn't complain.

I've updated README.Debian in the packages for the programmer utilities to tell people about the button.

[pipiche]

Thanks for your work, and indeed 3.1a is currently not supported on stable/4.3 (which doesn't mean it won't work)

[pocock]

I'm shortly going to announce the packages and repository URL for anybody who wants to install them easily using apt.

Before I do that, can you suggest the combination of components I should offer there?

Domoticz: 4.10717 or beta 4.11005?

Domoticz-zigate plugin: 4.3.4 (git: 4172d74b01..) or beta?

Firmware: 030f or 031a?

The packages are currently based on 4.10717 + 4.3.4

Is any permutation valid? Or does the beta branch of the plugin require a minimum firmware version or a particular Domoticz version?

[pipiche]

plugin (stable) 4.3 / Firmware 3.1f / Domoticz stable or beta

plugin (beta) 4.4 / Firmware 3.1a / Domoticz beta 4.11005 is optimum

[pocock]

Based on your feedback I think it is better to release packages of 4.4 + Domoticz 4.11005

Would you know which Git commit corresponds to 4.11005? I want to make sure I build the package from the same commit that was used to build the binaries on the download page.

[pipiche]

DomoticzVersion: 4.11008
Git commit: e888954de701ed33f849da6ad89fc4b9bb25581c

[pipiche]

On the other hand, if you wait 2 to 3 weeks, I'm planning to push the 4.4 to stable branch

[pocock]

I tried updating to the latest domoticz (4.11020), domoticz-zigate beta (fb9f5650e8e3ad32096307299985d0403fc9fa86)

It was working with firmware 3.0f

It is not working immediately with firmware 3.1a. When I tried to turn a switch on or off it gave me messages like this in the log:

(zigate0) UpdateDevice - (zigate0 - FNB56-SKT1EHG1.2_LvlControl-xxxxx-0b) 1:On
(zigate0) timedOutDevice unit zigate0 - FNB56-SKT1EHG1.2_LvlControl-xxxxxxxx-0b nwkid: aa59
Error: (zigate0) Command: 0x0092:On/Off failed on
Error: (zigate0) - Device: zigate0 - FNB56-SKT1EHG1.2_LvlControl-xxxxxxxx-0b NwkID: aa59 IEEE: xxxxxxxxxxxx
Error: (zigate0) - Code: d4 Status: Unicast frame does not have a route available but it is buffered for automatic resend
(zigate0) Decode8701 - Route discovery has been performed, status: 00 Nwk Status: d0


I rolled back the firmware, I saw messages like this, it is still not working:

Error: (zigate0) - Code: e9 Status: No acknowledgement received when expected

Then I pressed the button on the device to put it in join mode again, now it works again (still on 3.0f)

I updated to 3.1a again and tested the device again and it is working.

[pipiche]

Code: Select all

(zigate0) UpdateDevice - (zigate0 - FNB56-SKT1EHG1.2_LvlControl-xxxxx-0b) 1:On
(zigate0) timedOutDevice unit zigate0 - FNB56-SKT1EHG1.2_LvlControl-xxxxxxxx-0b nwkid: aa59
Error: (zigate0) Command: 0x0092:On/Off failed on
Error: (zigate0) - Device: zigate0 - FNB56-SKT1EHG1.2_LvlControl-xxxxxxxx-0b NwkID: aa59 IEEE: xxxxxxxxxxxx
Error: (zigate0) - Code: d4 Status: Unicast frame does not have a route available but it is buffered for automatic resend
(zigate0) Decode8701 - Route discovery has been performed, status: 00 Nwk Status: d0

Those errors indicate a communication issue ! Nothing to do with plugin nor firmware

[abroeders]

All of a sudden (during my holidays) this has started with me too. From the 27 devices, only 9 online, others have "Code: d4 Status: Unicast frame does not have a route available but it is buffered for automatic resend" messages in the log. Even the devices that are nearby(within 5 meter) the zigate interface.

Did you manage to recover from this? I was on the latest stable domoticz and zigate plugin 4.2. Now upgraded to latest beta domoticz, latest stable zigate plugin 4.5.2 and upgraded the pizigate fimware to 031a but the issue still occurs. Devices seem to randomly get unreachable and the topology scan only shows a few devices

Is there a way to force a rescan of my network and update all routes and connections to get this solved?

[abroeders]

After further searching I read on https://www.domoticz.com/forum/viewtopi ... 68&t=29062 for Xiaomi devices to set FCC mode in stead of CE. After switching to FCC it seems my network is coming to life again. I can control most of my hue's and tradfri's again. Now waiting for the new network topology report.

[pipiche]

Some explanation on FCC versus CE.

CE / FCC is related to the Power transmission certification. In Europe we should comply to CE which is IKEA, Philips ...., While the Xiaomi comply to FCC.
FCC means more power comparing to CE.

Don't make mistakes, it is not because FCC means more transmission power that you should set the Zigate to FCC. Why , because while the Zigate in FCC will be able to reach the Ikea and other CE compliant devices, in return those device might not be in the range of the Zigate due to the CE power level.

This is vice-versa when using Xiaomi devices which are FCC compliant. They will reach the Zigate, while the Zigate (or other CE router) might have some issues to reach them back .

In case you want to have more information, please go to the Zigate.fr/forum