[New device support]: ZT-LP-ZEU2S-WH-MS MOES

[MiAutomations]

Link

https://moeshouse.com/products/zigbee-wireless-self-powered-scene-switch

Database entry

{"id":76,"type":"GreenPower","ieeeAddr":"0x00000000a3970ea3","nwkAddr":3747,"manufId":null,"modelId":"GreenPower_2","epList":[242],"endpoints":{"242":{"epId":242,"inClusterList":[],"outClusterList":[],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"interviewCompleted":true,"meta":{},"lastSeen":1698149193664,"defaultSendRequestWhen":"immediate"}

Comments

Hello

I try to add this device but the device appears in the list as not supported yet.

Can you please add this device to a supported list devices in a new future release ?

Thank you for your support and best regards

External converter

No response

Supported color modes

No response

Color temperature range

No response

[Chartreusito]

If you own it, you can help supporting new devices : https://www.zigbee2mqtt.io/advanced/support-new-devices/02_support_new_tuya_devices.html

[MiAutomations]

If you own it, you can help supporting new devices : https://www.zigbee2mqtt.io/advanced/support-new-devices/02_support_new_tuya_devices.html

I'm not familiarized with the external converter But if you can help me I can try.

[Chartreusito]

I assumed you device was tuya, but first have a look at the general documentation : https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html#_2-adding-your-device The key here is to trigger your device to identify which cluster it uses and then try to find a working configuration among the other herdmans converter

[mathieuruellan]

Hello, I've tried to add default converters, but there is no converter for "commandNotification". I'm beginning in home automation and zigbee, if you have a js converter link, i could try.

here my logs

Zigbee2MQTT:debug 2024-01-06 16:39:39: Received Zigbee message from 'switch1', type 'commandNotification', cluster 'greenPower', data '{"commandID":79,"frameCounter":163,"srcID":793774560}' from endpoint 242 with groupID null Zigbee2MQTT:debug 2024-01-06 16:39:39: No converter available for 'GreenPower_2' with cluster 'greenPower' and type 'commandNotification' and data '{"commandID":79,"frameCounter":163,"srcID":793774560}' Zigbee2MQTT:info 2024-01-06 16:39:39: MQTT publish: topic 'zigbee2mqtt/switch1', payload '{"device":{"friendlyName":"switch1","ieeeAddr":"0x000000002f5009e0","manufacturerID":null,"model":"GreenPower_2","networkAddress":2528,"type":"GreenPower"},"last_seen":"2024-01-06T16:39:39.164Z","linkquality":209}

[igor-semenov]

фев 02 17:32:19 raspberrypi bash[19752]: Zigbee2MQTT:info  2024-02-02 17:32:19: Device '0x00000000ed5e4506' joined
фев 02 17:32:20 raspberrypi bash[19752]: Zigbee2MQTT:info  2024-02-02 17:32:20: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00000000ed5e4506","ieee_address":"0x00000000ed5e4506"},"type":"device_joined"}'
фев 02 17:32:20 raspberrypi bash[19752]: Zigbee2MQTT:info  2024-02-02 17:32:20: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x00000000ed5e4506"},"type":"device_connected"}'
фев 02 17:32:20 raspberrypi bash[19752]: Zigbee2MQTT:info  2024-02-02 17:32:20: Successfully interviewed '0x00000000ed5e4506', device has successfully been paired
фев 02 17:32:20 raspberrypi bash[19752]: Zigbee2MQTT:warn  2024-02-02 17:32:20: Device '0x00000000ed5e4506' with Zigbee model 'GreenPower_2' and manufacturer name 'undefined' is NOT supported, please follow https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
фев 02 17:32:20 raspberrypi bash[19752]: Zigbee2MQTT:info  2024-02-02 17:32:20: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":null,"friendly_name":"0x00000000ed5e4506","ieee_address":"0x00000000ed5e4506","status":"successful","supported":null},"type":"device_interview"}'
фев 02 17:32:20 raspberrypi bash[19752]: Zigbee2MQTT:info  2024-02-02 17:32:20: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"friendly_name":"0x00000000ed5e4506","supported":false},"type":"pairing"}'

[igor-semenov]

I've added new js file for device, but every time I press the same button, it produces different commands:

фев 04 23:18:53 raspberrypi bash[3066]: Zigbee2MQTT:debug 2024-02-04 23:18:53: Received Zigbee message from '0x00000000af79b9e0', type 'commandCommissioningNotification', cluster 'greenPower', data '{"commandFrame":{"raw":{"data":[61,61,216,74,14,215,98],"type":"Buffer"}},"commandID":41,"frameCounter":1324,"gppGddLink":216,"gppNwkAddr":15677,"options":2864,"payloadSize":0,"srcID":2943990240}' from endpoint 242 with groupID 0
фев 04 23:19:01 raspberrypi bash[3066]: Zigbee2MQTT:debug 2024-02-04 23:19:01: Received Zigbee message from '0x00000000af79b9e0', type 'commandCommissioningNotification', cluster 'greenPower', data '{"commandFrame":{"raw":{"data":[223,26,214,4,164,177,194],"type":"Buffer"}},"commandID":3,"frameCounter":1333,"gppGddLink":214,"gppNwkAddr":6879,"options":2864,"payloadSize":0,"srcID":2943990240}' from endpoint 242 with groupID 0
фев 04 23:19:04 raspberrypi bash[3066]: Zigbee2MQTT:debug 2024-02-04 23:19:04: Received Zigbee message from '0x00000000af79b9e0', type 'commandCommissioningNotification', cluster 'greenPower', data '{"commandFrame":{"raw":{"data":[223,26,214,204,153,107,228],"type":"Buffer"}},"commandID":201,"frameCounter":1342,"gppGddLink":214,"gppNwkAddr":6879,"options":2864,"payloadSize":0,"srcID":2943990240}' from endpoint 242 with groupID 0

[ngeissel]

I'm interrested too (since a few hours) into finding a way to handle MOE green power switch.

Same here for commands, but since it is as switch does it really matters ? :

Debug 2024-02-08 11:44:22Received Zigbee message from '0x00000000e91c2afd', type 'commandCommissioningNotification', cluster 'greenPower', data '{"commandFrame":{"raw":{"data":[35,64,155,35,28,185,7],"type":"Buffer"}},"commandID":155,"frameCounter":1387,"gppGddLink":155,"gppNwkAddr":16419,"options":2608,"payloadSize":0,"srcID":3910937341}' from endpoint 242 with groupID 0
Debug 2024-02-08 11:44:23Received Zigbee message from '0x00000000e91c2afd', type 'commandCommissioningNotification', cluster 'greenPower', data '{"commandFrame":{"raw":{"data":[35,64,155,74,187,160,95],"type":"Buffer"}},"commandID":252,"frameCounter":1396,"gppGddLink":155,"gppNwkAddr":16419,"options":2608,"payloadSize":0,"srcID":3910937341}' from endpoint 242 with groupID 0
Debug 2024-02-08 11:44:27Received Zigbee message from '0x00000000e91c2afd', type 'commandCommissioningNotification', cluster 'greenPower', data '{"commandFrame":{"raw":{"data":[35,64,153,15,212,74,125],"type":"Buffer"}},"commandID":70,"frameCounter":1405,"gppGddLink":153,"gppNwkAddr":16419,"options":2608,"payloadSize":0,"srcID":3910937341}' from endpoint 242 with groupID 0
Debug 2024-02-08 11:44:27Received Zigbee message from '0x00000000e91c2afd', type 'commandCommissioningNotification', cluster 'greenPower', data '{"commandFrame":{"raw":{"data":[35,64,149,233,198,137,178],"type":"Buffer"}},"commandID":81,"frameCounter":1414,"gppGddLink":149,"gppNwkAddr":16419,"options":2608,"payloadSize":0,"srcID":3910937341}' from endpoint 242 with groupID 0

[NilkOne]

Hello, any news if it possible to add it on zigbee2mqtt ?

I bought a 2-scenes and a 3-scenes switch but Not supported yet

[igor-semenov]

The fundamental thing I don't understand is whether I need any specific hardware (new USB stick maybe) to connect ZGP device? My USB stick allows me to pair device, I can see commands from it when I press buttons, but commandId is random every time I press same button, and I see no way to find out, which button of my 2-gang is pressed....

[psummo]

The fundamental thing I don't understand is whether I need any specific hardware (new USB stick maybe) to connect ZGP device? My USB stick allows me to pair device, I can see commands from it when I press buttons, but commandId is random every time I press same button, and I see no way to find out, which button of my 2-gang is pressed....

The problem seems that GreenPower devices works with high level encryption. So it's not device limitation, but software limitation.

BTW I'm here with the same request. I test it with tuya hub with smartlife app and works really nice. I'm waiting for zigbee2mqtt support! I tried with custom adapter, but there is no way to debug it or understand how to intercept single click actions

[igor-semenov]

BTW I'm here with the same request. I test it with tuya hub with smartlife app and works really nice. I'm waiting for zigbee2mqtt support! I tried with custom adapter, but there is no way to debug it or understand how to intercept single click actions

Could you please share link to tuya hub, which you use?

[Namyts]

I also bought this device recently without realising the lack of compatibility with ZGP with an existing network. I agree with @psummo that this looks like it's a software issue but it should also have a software fix. The fact that other's have gotten similar devices working in their network by adding ZGP interpreters/translators/re-publishers (eg the IKEA lightbulb, certain Phillips Hue devices) mean that's the "encrypted" signal from this switch isn't vendor locked, instead there is just missing functionality in the network which could be fulfilled by another device (maybe the device running zigbee2mqtt) (?)
What am I misunderstanding?

[psummo]

BTW I'm here with the same request. I test it with tuya hub with smartlife app and works really nice. I'm waiting for zigbee2mqtt support! I tried with custom adapter, but there is no way to debug it or understand how to intercept single click actions

Could you please share link to tuya hub, which you use?

I bought the hub 1 year ago. I swear that I didn't know that the hub is Moes also ahahah I noticed it now. Btw it's a normal tuya hub that you can buy on aliexpress also. The model is MoesGo ZHUB-W, Zigbee 3.0. If anybody know /want try investigate with this hub in some way in order to understand what happen with this kind of switch, I'm available

[psummo]

I also bought this device recently without realising the lack of compatibility with ZGP with an existing network. I agree with @psummo that this looks like it's a software issue but it should also have a software fix. The fact that other's have gotten similar devices working in their network by adding ZGP interpreters/translators/re-publishers (eg the IKEA lightbulb, certain Phillips Hue devices) mean that's the "encrypted" signal from this switch isn't vendor locked, instead there is just missing functionality in the network which could be fulfilled by another device (maybe the device running zigbee2mqtt) (?) What am I misunderstanding?

The problem could be also in the zigbee dongle (I've the sonoff) at this point, I'm newbie in this so I'm not able to understand if it's only the software (zigbee2mqtt) or also the firmware

[Namyts]

I also use the same dongle with the multiprotocol firmware (& docker container). Same questions too. The fact we can see the logs makes me think it's something that can be interpreted, but it also feels like there might be some missing information to translate this information into exact button presses...

For record, below are my almost identical logs:

Zigbee2MQTT:debug 2024-04-09 10:49:22: Received Zigbee message from 'James Kinetic Switch', type 'commandNotification', cluster 'greenPower', data '{"commandID":126,"frameCounter":222,"srcID":1939043194}' from endpoint 242 with groupID null
Zigbee2MQTT:debug 2024-04-09 10:49:22: Skipping message, still interviewing
Zigbee2MQTT:info  2024-04-09 10:49:22: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch', payload '{"last_seen":"2024-04-09T09:49:22.916Z","linkquality":212}'
Zigbee2MQTT:info  2024-04-09 10:49:22: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/last_seen', payload '2024-04-09T09:49:22.916Z'
Zigbee2MQTT:info  2024-04-09 10:49:22: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/linkquality', payload '212'
Zigbee2MQTT:debug 2024-04-09 10:49:23: Received Zigbee message from 'James Kinetic Switch', type 'commandNotification', cluster 'greenPower', data '{"commandID":95,"frameCounter":231,"srcID":1939043194}' from endpoint 242 with groupID null
Zigbee2MQTT:debug 2024-04-09 10:49:23: Skipping message, still interviewing
Zigbee2MQTT:info  2024-04-09 10:49:23: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch', payload '{"last_seen":"2024-04-09T09:49:23.865Z","linkquality":210}'
Zigbee2MQTT:info  2024-04-09 10:49:23: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/last_seen', payload '2024-04-09T09:49:23.865Z'
Zigbee2MQTT:info  2024-04-09 10:49:23: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/linkquality', payload '210'

[psummo]

I also use the same dongle with the multiprotocol firmware (& docker container). Same questions too. The fact we can see the logs makes me think it's something that can be interpreted, but it also feels like there might be some missing information to translate this information into exact button presses...

For record, below are my almost identical logs:

Zigbee2MQTT:debug 2024-04-09 10:49:22: Received Zigbee message from 'James Kinetic Switch', type 'commandNotification', cluster 'greenPower', data '{"commandID":126,"frameCounter":222,"srcID":1939043194}' from endpoint 242 with groupID null
Zigbee2MQTT:debug 2024-04-09 10:49:22: Skipping message, still interviewing
Zigbee2MQTT:info  2024-04-09 10:49:22: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch', payload '{"last_seen":"2024-04-09T09:49:22.916Z","linkquality":212}'
Zigbee2MQTT:info  2024-04-09 10:49:22: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/last_seen', payload '2024-04-09T09:49:22.916Z'
Zigbee2MQTT:info  2024-04-09 10:49:22: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/linkquality', payload '212'
Zigbee2MQTT:debug 2024-04-09 10:49:23: Received Zigbee message from 'James Kinetic Switch', type 'commandNotification', cluster 'greenPower', data '{"commandID":95,"frameCounter":231,"srcID":1939043194}' from endpoint 242 with groupID null
Zigbee2MQTT:debug 2024-04-09 10:49:23: Skipping message, still interviewing
Zigbee2MQTT:info  2024-04-09 10:49:23: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch', payload '{"last_seen":"2024-04-09T09:49:23.865Z","linkquality":210}'
Zigbee2MQTT:info  2024-04-09 10:49:23: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/last_seen', payload '2024-04-09T09:49:23.865Z'
Zigbee2MQTT:info  2024-04-09 10:49:23: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/linkquality', payload '210'

do you have a custom adpter right? Could you please send it to me? Because I'm still having errors and not info logs :D

[ngeissel]

I also use the same dongle with the multiprotocol firmware (& docker container). Same questions too. The fact we can see the logs makes me think it's something that can be interpreted, but it also feels like there might be some missing information to translate this information into exact button presses...

For record, below are my almost identical logs:

Zigbee2MQTT:debug 2024-04-09 10:49:22: Received Zigbee message from 'James Kinetic Switch', type 'commandNotification', cluster 'greenPower', data '{"commandID":126,"frameCounter":222,"srcID":1939043194}' from endpoint 242 with groupID null
Zigbee2MQTT:debug 2024-04-09 10:49:22: Skipping message, still interviewing
Zigbee2MQTT:info  2024-04-09 10:49:22: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch', payload '{"last_seen":"2024-04-09T09:49:22.916Z","linkquality":212}'
Zigbee2MQTT:info  2024-04-09 10:49:22: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/last_seen', payload '2024-04-09T09:49:22.916Z'
Zigbee2MQTT:info  2024-04-09 10:49:22: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/linkquality', payload '212'
Zigbee2MQTT:debug 2024-04-09 10:49:23: Received Zigbee message from 'James Kinetic Switch', type 'commandNotification', cluster 'greenPower', data '{"commandID":95,"frameCounter":231,"srcID":1939043194}' from endpoint 242 with groupID null
Zigbee2MQTT:debug 2024-04-09 10:49:23: Skipping message, still interviewing
Zigbee2MQTT:info  2024-04-09 10:49:23: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch', payload '{"last_seen":"2024-04-09T09:49:23.865Z","linkquality":210}'
Zigbee2MQTT:info  2024-04-09 10:49:23: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/last_seen', payload '2024-04-09T09:49:23.865Z'
Zigbee2MQTT:info  2024-04-09 10:49:23: MQTT publish: topic 'zigbee2mqtt/James Kinetic Switch/linkquality', payload '210'

How did you manage to get such clean logs ? This could help us to go forward

[Namyts]

@ngeissel I am running zigbee2mqtt in a docker container using docker compose. It looks like this:

services:
  zigbee2mqtt:
    container_name: zigbee2mqtt
    image: koenkk/zigbee2mqtt
    restart: unless-stopped
    volumes:
      - ./data:/app/data
      - /run/udev:/run/udev:ro
      - ./switch.js:/app/data/switch.js
    ports:
      - 8080:8080
    network_mode: host
    environment:
      - TZ=Europe/London

In the /data/configuration.yaml I have a few lines like this:

advanced:
  log_level: debug
  output: attribute_and_json
  last_seen: ISO_8601

I then look at the logs by using: docker logs -f zigbee2mqtt

[psummo]

@Namyts without any custom converter?

[ngeissel]

I think we should be interrested in you - ./switch.js:/app/data/switch.js ;) ? (or something locally overriden)

[Namyts]

The switch.js file is a placeholder, sadly I don't have the knowledge yet to successfully write the converter. That's one of the reasons I am here :)

[psummo]

I don't know if there is the way to log everything, I need it as debugging

[psummo]

I try with this guide. https://www.zigbee2mqtt.io/advanced/support-new-devices/02_support_new_tuya_devices.html and https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html#instructions

And this is what I produced converter.js.txt The file is JS, but since of limitation on github I can only update txt. Btw Seems nothing is change. and I don't know why, sometimes converter is "recognized" and z2m doesn't give me error during pairing, sometimes yes.

I'm not expert and I tried only create the adapter following the guide for tuya.

[Namyts]

I've messaged MoesHouse for assistance. Hopefully they can help explain the protocol better.
I haven't been able to improve on your converter @psummo :(

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const {hasAlreadyProcessedMessage} = require('zigbee-herdsman-converters/lib/utils');

const my_converter = {
    cluster: 'greenPower',
    type: ['commandNotification', 'commandCommissioningNotification'],
    convert: (model, msg) => {
        const commandID = msg.data.commandID;
        if (hasAlreadyProcessedMessage(msg, model, msg.data.frameCounter, `${msg.device.ieeeAddr}_${commandID}`)) {return}
        if (commandID === 224) return;

        return {action: 'left'}
    }
}

const definition = {
    fingerprint: [
        {
            modelID: 'GreenPower_2',
            manufacturerName: undefined,
        },
    ],
    model: 'GreenPower_2',
    vendor: 'GreenPower_2',
    description: 'kinetic switch',
    meta: {multiEndpoint: true},
    fromZigbee: [tuya.fz.datapoints, fz.ignore_basic_report, my_converter],
    toZigbee: [],
    configure: tuya.configureMagicPacket,
    exposes: []
};

module.exports = definition;

The best this achieves is making both buttons send the "left" action, which can be picked up by home assistant. We need a better way of fingerprinting this device, and a way of using the commandId, frameCounter (& encryption/security keys?) to map to the real commands issued by the device...

Ive been reading this but haven't gotten anywhere yet. Hopefully Moes can clear it up.

[igor-semenov]

I've messaged MoesHouse for assistance. Hopefully they can help explain the protocol better.

Have you got any response from MoesHouse?

[Namyts]

@igor-semenov

Have you got any response from MoesHouse?

They replied the next day, but after exchanging a couple of emails they seem unwilling to help. Sample from response:

It is recommended that you go to this website to consult professionals to get solutions---https://www.zigbee2mqtt.io/

and

Sorry, we can't provide it for you. This zigbee is Tuya's protocol, and Tuya has not opened it to us.

I implore you to email them yourself (use their website contact form to establish comms). They response times aren't bad...
It is a shame because if they provide sufficient information, we might be able to add compatibility for their product with an entirely new ecosystem...

[mathieuruellan]

Have you asked with the right wording?

https://www.zigbee2mqtt.io/advanced/support-new-devices/02_support_new_tuya_devices.html#_4-mapping-the-datapoints

[Namyts]

@mathieuruellan - not quite. Me:

Hi, I am trying to integrate your device: https://moeshouse.com/products/zigbee-wireless-self-powered-scene-switch with Zigbee2MQTT but I am having some issues. Please could you send me the UART protocol for the device? Or maybe send the Zigbee protocol? Currently it looks like the device sends a random commandId every time I press either switch, but I am certain that with your help I can get this integration working! This will help me and many others :) Kind regards,

Moes Response:

We recommend using our zigbee device on smart life/tuya smart/MOES app. Since Home Assistant is an open source platform and cannot be used commercially, it is mainly aimed at individual enthusiast users; Our zigbee devices can be used normally when connected to the gateway. If you use this platform, there is no guarantee that there will be any problems It is recommended that you go to this website to consult professionals to get solutions---https://www.zigbee2mqtt.io/

Me:

Thanks for replying so quickly. I understand that Tuya is the hub which Moes recommends. Zigbee2MQTT is also an open source tool, and compatibility is added by software developers such as myself! https://github.com/Koenkk/zigbee-herdsman-converters/tree/master/src/devices - you can see in this page a huge list of supported products for Zigbee2MQTT... including some of Moes products https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/moes.ts ! I am trying to provide compatibility for the Moes self-powered switch (you're welcome 🙂 ), but am having a few issues because the command id sent by the device each time a switch is pressed appears to be random... I am contacting you to ask if you could provide some documentation around the protocol that your switch is using, and with this information I can write the code to make your switch compatible with Zigbee2MQTT (which will also make your device compatible with a LOT of other technologies! (for example: home assistant)) I hope you can help me by sending this info, Kind regards,

Moes Response:

Sorry, we can't provide it for you. This zigbee is Tuya's protocol, and Tuya has not opened it to us.

Me:

I understand that you are unable to provide any information about how Tuya works. However, if you were to share information about how your MOES self-powered switch uses Tuya, I could probably work out the rest and write some code to integrate your product with Zigbee2MQTT. It is worth noting that Zigbee2MQTT already supports a huge number of Tuya devices: https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/tuya.ts by having this information. As well as providing instructions on how to add support for non-supported devices: https://www.zigbee2mqtt.io/advanced/support-new-devices/02_support_new_tuya_devices.html . The reason I am reaching out is that your device seems to behave more strangely than other Tuya devices since it is using Zigbee Green Power to send signals to the Tuya hub. If you were to provide some information how your team integrated the device with Tuya, I will work and write some code to make the device compatible with Zigbee2MQTT. Zigbee is an open communication standard used by most smart home devices, not something created by Tuya. This means that sharing the Zigbee implementation of the device will allow for easy integrations. Together we can make your product even better! Kind regards,

Moes Response: ~ they ignored me

I welcome anybody else to send them an email to more clearly ask them for the info we'll need to resolve this issue :) Perhaps more emails would show more interest? Or it might land with a more co-operative support agent. Not too sure how we will resolve this issue without some external help, or someone with deeper understanding of ZGP.

[MaxwellJK]

I wrote them just now - i'll keep you all posted. I am not sure i have the knowledge to work on the implementation myself but i'll share here anything useful (if they sahre it with me)

[MaxwellJK]

This zigbee is Tuya's protocol, and Tuya has not opened it to us. Quick update - i was given the same kind of answer unfortunately Either they don't want to share the details or it is true that this zigbee protocol is owned by Tuya and they don't have any technical details. I was thinking to reach out to Tuya and check if they are willing to share the details.

[gurrier]

@Namyts Just noticed... Should the manufacturerName: undefined not have quotes? like this... manufacturerName: 'undefined'