Pipiche

https://github.com/badzz/Zigate-Router > On 11 Aug 2020, at 17:54, dusscloud wrote: > > > It seems that by default the python library cset-up the zigate as a coordinator and creates its...

The firmware are available there: https://github.com/badzz/Zigate-Router/tree/master/Router/Build Then you have to use the same procedure as the standard firmware to flash the router firmware on the ZiGate.

Have a similar issue on Fedora distribution on a PI3B+ platform. While ttyS1 is enabled: ``` dmesg | grep ttyS1 [ 4.361009] 3f215040.serial: ttyS1 at MMIO 0x3f215040 (irq = 53,...

Thanks for picking up. As this happen only time to time, it is hard to use gdb Yes this is in a multiple threads environment. For the other question, I...

From my end, I think at the end is the best place, as we can differentiate from one version to the other based on the length of the payload.

This is right. In fact It would be easier to document the data structure when in firmware 3.0d or in firmware 3.0f

Tested with the pre-firmware version. I indeed get a value, but the short address given doesn't correspond to any of my devices short address !

Here is a payload I'm geting `d000ae27` ae27 is unknown in my Devices list ! And as already reported: The first by which are expected to be u8NwkStatus seems to...

I might have a clue. In case NwkStatus & Status are not equal to 0x00, u16DstAddress seems to be invalid.

> NXP documentation doesn't have any notes about u16DstAddress being invalid in some cases, but that doesn't mean it cant be so. Should we discard address when statuses aren't both...