Zone Status Notification Change seen in sniffer but not in serial port.

What is your host application?

Note: the endpoint i have on coordinator is profile ID 0x104

I suggest you to use sniffer to check if notification is sent to registered endpoint of your coordinator 

This is the log. ( I see DestinationEP = 0?) 

Key: 0xaabbcceeff00112233445566778899

SmokeAlarmCantReceiveValue.rar

Your device sends notification to endpoint 0 which is incorrect. I suppose you use Develco device in your test and I think you need to contact manufacture to know why the device sends notification to incorrect endpoint.

You are right, using develco products.

Binded to the correct EP and for some reason it sends to DestinationEP = 0; 

They don't help unless you have a support agreement with them

Then, I suggest you to skip integration with such device.

I know, but due to Work I can't just drop it. Will ask to have a support agreement.

Also: when does the Smoke Alarm decide to which EP send the Zone Status Notification? Maybe after CIE Address write?

Yes, it should be CIE address write would assign EP of notification.

Well, interesting enough if you look at the "match descriptor request" for cluster 0x0500 ( which I registered to the endpoint 1 both as Input and Output Cluster) it says both destination and source ep = 0.

Is this a normal behaviour?

This is my endpoint code.

int[] pacchettoAFRegister = DoPacket.AF_REGISTER(
                0X01,
                DoPacket.HOME_AUTOMATION,
                DoPacket.DEVICE_ID_DEFAULT,
                7,
                new int[] {0x0019, 0x0009, 0x000a, 0x0000, 0x0020, 0x0500, 0x0003},
                2,
                new int[] {0x0500, 0x0019}
        );

ZDP match request is usually sent by broadcast so I think it’s normal to see it using endpoint 0 but it seems that you miss MatchList, which is a list of bytes, each represents an 8 bit endpoint, in your Match response from coordinator.

Match Response is sent automatically by the coordinator, not me via Tool. It always worked for OTA and much more, but when it comes to IAS Zone it doesnt,

Should I craft the response packet I send it myself?

What coordinator do you use?

SonOff Dongle CC2562P with ZStack 3.x.0

I suppose this is ZNP running on your dongle, right? I mean to ask what is your host application? Is it TI Z-Tool?

Host Application is written in Java. Yes, ZNP running on dongle

Please refer to Monitor and Test API document to revise your Java program to send correct Match response.

Wait, I send Monitor And Test API command via serial port in java

Match Desc Response get sent by the dongle automatically

Interesting enough all match responses are correct, but when it comes to ias zone it says endpoint count = 0 and can't match the cluster although is in the endpoint

No, I think Match response is sent by host application not ZNP.

Let me clarify: I have this Sonoff dongle with ZigBee2MQTT firmware on it and I just send AF_DATA_REQUEST and AF_REGISTER, BDB Commissioning Commands via Serial Port. Just like ZigBee2MQTT.

I never sent any Match Desc Request and all worked by just registering the cluster in the endpoint AF_REGISTER

Maybe try to update ZNP to latest SDK 6.40 version.

Nothing changes.

How do your use AF_REGISTER to register endpoint?

Took huge inspiration by this project: GitHub - zsmartsystems/com.zsmartsystems.zigbee: ZigBee Cluster Library Java framework supporting multiple dongles

Af_register code: com.zsmartsystems.zigbee/com.zsmartsystems.zigbee.dongle.cc2531 at master · zsmartsystems/com.zsmartsystems.zigbee · GitHub

I basically craft the packet in java and send it via serial port.

I mean to ask what in/out clusters you register to endpoint of your coordinator? And, also make sure you use correct endpoint, not 0.

output cluster: OTA and IAS_ZONE

Input cluster: OTA, ias_zone, time and 3 more (non relevant)

Anyway, it is good to know you figure out where the bug is.