[New device support]: ZT-LP-ZEU2S-WH-MS MOES #19405
Comments
|
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. |
|
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 |
|
Hello, I've tried to add default converters, but there is no converter for "commandNotification". here my logs
|
|
|
I've added new js file for device, but every time I press the same button, it produces different commands: |
|
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 ? : |
|
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 |
|
The fundamental thing I don't understand is whether I need any specific hardware (new USB stick maybe) to connect ZGP device? |
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 |
Could you please share link to tuya hub, which you use? |
|
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) (?) |
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 |
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 |
|
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: |
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 |
How did you manage to get such clean logs ? This could help us to go forward |
|
@ngeissel I am running zigbee2mqtt in a docker container using docker compose. It looks like this: In the I then look at the logs by using: |
|
@Namyts without any custom converter? |
|
I think we should be interrested in you - ./switch.js:/app/data/switch.js ;) ? (or something locally overriden) |
|
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 :) |
|
I don't know if there is the way to log everything, I need it as debugging |
|
I try with this guide. And this is what I produced I'm not expert and I tried only create the adapter following the guide for tuya. |
|
I've messaged MoesHouse for assistance. Hopefully they can help explain the protocol better. 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. |
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
The text was updated successfully, but these errors were encountered: