ZGP Requirements & Pairing

[jamesonuk]

I am just trying to work out some missing pieces around ZGP.

I have got hold of a Moes ZT-LP-ZEU2S (#19405) but I can't pair it.
I know there are lots of things happening around ZGP and this won't be fully supported but I can't can't get it to pair but I I don't understand enough about ZGP.

There is talk about needing translator devices to act as a proxy between the ZGP device and the network. This tends to mention Hue products but with no other detail. I have loads of Ikea bulbs which get mentioned too and I see they have the Green Power clusters but does that mean they will act as a proxy?

What else needs to happen for pairing? Will the coordinator (using a Conbee II right now) make a difference or should the proxy translate the ZGP message into a standard Zigbee one which can be sent to the coordinator? Do I need to explicitly set a device for pairing or should I just use all?

(The switch is set to the right channel btw)

Any ideas what I am missing to pair this?

Edit: I had read https://www.zigbee2mqtt.io/advanced/zigbee/01_zigbee_network.html#green-power-devices but just going back through it I see the difference between selecting the pair to device (only device will act as proxy) or all (all devices will act as proxy and will broadcast messages). I did put the device next to an IKEA 2103G5 which is on the list as definitely supporting I still can't get anything to pair.

[jamesonuk]

so I started sniffing and I can see
976 2025-04-14 17:40:24.238443 0xe5c5 0x0000 ZigBee GP 104 ZCL Green Power: GP Commissioning Notification, Seq: 47
which is coming from the Ikea bulb I had set to allow pairing (different one to the above one)

Full message

Frame 976: 104 bytes on wire (832 bits), 104 bytes captured (832 bits) on interface ZigBee/0/11, id 0
IEEE 802.15.4 Data, Src: 0xe5c5, Dst: 0x0000
ZigBee Network Layer Data, Dst: 0x0000, Src: 0xe5c5
    Frame Control Field: 0x0248, Frame Type: Data, Discover Route: Enable, Security Data
    Destination: 0x0000
    Source: 0xe5c5
    Radius: 30
    Sequence Number: 247
    [Extended Source: SiliconLabor_ff:fe:70:b9:75 (28:76:81:ff:fe:70:b9:75)]
    [Origin: 191]
    ZigBee Security Header
ZigBee Application Support Layer Data, Dst Endpt: 242, Src Endpt: 242
    Frame Control Field: Data (0x40)
    Destination Endpoint: 242
    Cluster: Green Power (0x0021)
    Profile: Green Power (0xa1e0)
    Source Endpoint: 242
    Counter: 108
ZigBee Cluster Library Frame
    Frame Control Field: Cluster-specific (0x11)
    Sequence Number: 47
    Command: GP Commissioning Notification (0x04)
    Options: 0x0800, ApplicationID: 0b000 4b SrcID; no Endpoint, SecurityLevel: No security, SecurityKeyType: No key, Proxy info present
    SrcID: 0xb1d8d4bb
    Frame counter: 158
    ZGPD CommandID: Commissioning (0xe0)
    Payload size: 43
    Command Frame: Commissioning
        ZGPD Command ID: Commissioning (0xe0)
        ZGPD Device ID: Generic: GP On/Off Switch (0x02)
        Options Field: 0x89, MAC Sequence number capability, Extended Option Field
            .... ...1 = MAC Sequence number capability: True
            .... ..0. = RxOnCapability: False
            .... .0.. = Application information present: False
            ...0 .... = PANId request: False
            ..0. .... = GP Security Key Request: False
            .0.. .... = Fixed Location: False
            1... .... = Extended Option Field: True
        Extended Options Field: 0xf3, Key Type: Individual, out of the box GPD key, GPD Key Present, GPD Key Encryption, GPD Outgoing present
            .... ..11 = Security Level Capabilities: 0x3
            ...1 00.. = Key Type: Individual, out of the box GPD key (0x4)
            ..1. .... = GPD Key Present: True
            .1.. .... = GPD Key Encryption: True
            1... .... = GPD Outgoing present: True
        Security Key: 05b5557934a8ba0545ebbff6ad31e91c
        GPD Key MIC: 0x48c51d32
        GPD Outgoing Counter: 0x0000089e
    GPP short address: 0xe5c5
    GPP-GPD link: 0xda, LQI: Excellent
        ..01 1010 = RSSI: 0x1a
        11.. .... = LQI: Excellent (0x3)
Data (16 bytes)
    Data: 7165726837706f7840475030303031ef
    [Length: 16]

Is this a result of the Conbee II not supporting ZGP and without switching coordinator this will never work?

[Nerivec]

I don't know how well GP works with deconz. Like chris said, it hasn't had a maintainer for too long, it's no longer recommended...
If you use a GPP (proxy) for pairing, I assume it should work though, since it's then just plain ZCL messages that the coordinator receives...

You can't get it to pair even with that Ikea bulb? If you have a sniff, you can send it over, I'll take a look (can find me on Discord if you prefer, or in private repo).

Note that technically, any ZigBee 3.0 router should be able to proxy (it's a requirement for the certification), but this is not always followed, and some devices are better at it for sure.

[jamesonuk]

I don't know how well GP works with deconz. Like chris said, it hasn't had a maintainer for too long, it's no longer recommended... If you use a GPP (proxy) for pairing, I assume it should work though, since it's then just plain ZCL messages that the coordinator receives...

You can't get it to pair even with that Ikea bulb? If you have a sniff, you can send it over, I'll take a look (can find me on Discord if you prefer, or in private repo).

If I tried to enable pairing for all and for the ikea bulb specifically (If I understand the docs correctly, the former will use broadcast and try to pair via any device and the latter should use unicast and pair via that device.

As above the ZGP Commissioning message is seen (so must have been translated by the bulb) but nothing is added to Z2M. Not sure the sniff pcap will help really, from what I can understand I just see the commissioning messages being sent but nothing else at Zigbee level. If you think it will help I can send it.

If is just that it seems that the message enters Zigbee but coordinator (and hence Z2M?) just ignores it (hence my thought that it is down to the coordinator. I have 150 devices and the thought of re-pairing everything to a new co-ordinator isn't something I have the energy for just yet but I know I will have to bite the bullet at some point.

[jamesonuk]

By the way, have you tried to pair this switch directly to the coordinator?

I have enabled permit all but I haven't tried permit on just the coordinator (but I do not believe the Conbee II works as a ZGP translator but I thought that if an IKEA bulb handled the translation it should handle the rest)

[chris-1243]

I have enabled permit all but I haven't tried permit on just the coordinator (but I do not believe the Conbee II works as a ZGP translator but I thought that if an IKEA bulb handled the translation it should handle the rest)

It is worth a try. Silabs chip are able but not TI for the moment... No idea how Deconz is managing this

[Nerivec]

As above the ZGP Commissioning message is seen (so must have been translated by the bulb) but nothing is added to Z2M

You'd have to check the sniff with the debug log of Z2M, to see where the message "gets lost" (i.e. if you see anything in the logs when the commissioning command happens in the sniff).