[New device support]: ZT-LP-ZEU2S-WH-MS MOES #19405
Labels
new device support
New device support request
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. |
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:
and
I implore you to email them yourself (use their website contact form to establish comms). They response times aren't bad... |
|
Have you asked with the right wording?
|
|
@mathieuruellan - not quite.
Moes Response:
Me:
Moes Response:
Me:
Moes Response: 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. |
|
I wrote them just now - i'll keep you all posted. |
Done that and it works :)
Here it is - it's basic and honestly inspired by @chris-1243's ones but it does the job: This is for the 2 gang (i have only that) and works without the need to define an external converter. If anybody has time to test it and provide feedbacks, it would be appreciated.
-- EDIT |
|
Here are the logs of the pairing on 2.1.3-dev commit: 53e8226 (zigbee-herdsman-converters 23.12.0) : Pairing :1st press left :1st press right :2nd press left :3rd press left :2nd press right :3rd press right :Is the device discovered as a sensor because the generic GP definition doesn't expose the action property ? zigbee2mqtt/lib/extension/homeassistant.ts Line 1091 in fc35ac5 Discovery (from the pairing, on the "wrong" device type and missing the action topic) : |
The generated definition should have an action property, you can confirm it by looking at the "Exposes" tab of the device in the z2m frontend. What do you get when creating a device trigger in a HA automation? 
|
|
The action property is indeed present in the expose tab :
HA doesn't see any triger for the device :
This is because the action is not published on the discovery topic :
|
|
You should see it under |
|
I should, but I don't :( :
|
|
@skuizy did you try removing the device from Z2M, shutting down Z2M, restarting it, and then doing the pairing again? Also grab latest latest-dev while you're at it. |
|
Just did on 2.1.3-dev commit: 0a41af5 and still the same :( |
|
Could you provide the debug log from starting z2m until pressing buttons on this device? See this on how to enable debug logging. |
|
Here you go ! |
|
@skuizy could you provide your |
|
Hello I installed the last version os Z2M 2.2.0 But I still not able to use this devices
Can some one please confirm that with this version are able to use this devices ? Tks |
|
@MiAutomations the devices will remain unsupported, because they rely on the generated definition (which is not considered "supported"), but they should work nonetheless. The "unsupported" is only cosmetic really in this case. There is no way to properly identify them since they keep changing address, this unfortunately won't change. You can use the instructions above to create an external converter and that will make them supported, but any time you re-pair them, you will have to change the external converter since the address will change. |
|
@Koenkk Don't give up, I will provide in a week or two. |
Thank you, I deleted the devices and re-paired the devices, now I'm abale to see the states changes in the Z2M Action, and for a few seconds I'm able to use the Switches over the automations, but after this time (seconds) the device stop report the changes of the states... And this is occurring with both of the switches that I have. |
|
@MiAutomations can you try to enable permit join, and see if it reports again? |
Yes it works, but only during the time of the pairing mode is available |
|
Can you make sure you followed the pairing procedure to the letter (I don't know what it is for that device)? It seems your device stays in commissioning after it's paired (hence, messages are dropped by the parent if permit is off), this would indicate it wasn't "fully paired". If that doesn't work, maybe try pairing to a different "supporting" GP parent... |
|
@MiAutomations the same is for me - it works only if permit join is enabled. |
@Nerivec sorry what you mean with pairing procedure to the letter? Related to the Enocean GP devices, i think this is little different, or not? Do I need any pairing proceder different from the one that is mentioned on the device manual? Tks |
@MaxwellJK My setup is a coordinator based on SMLZB device with a lot of router devices, I successfully added these device to the my Z2M instance, but the device only works when the paring mode still active. After this the device stop reporting any status change. What you mean with the "My only solution (for now) was to enable always permit via the ikea bulb"? Tks |
Encoean is slightly different, sure. What Nerivec said is to strictly follow the pairing procedure and not to play with the device until the pairing is done completely. |
|
@MiAutomations @MaxwellJK same here, only work when pairing mode is active. |
|
From what I can see @skuizy logs are showing @skuizy can you describe the pairing procedure you used, just to be sure? If not the pairing procedure, the other difference that I can see is the stack. @skuizy is pairing to an EmberZNet coordinator, while @MaxwellJK to a zStack coordinator. @MaxwellJK can you try pairing the Moes to the Ikea GP proxy directly (permit join only on the Ikea before pairing) and confirm if the Moes keeps on working after permit join expires or you turn it off? (PS: the bug you mentioned here should also be fixed now) |
Ahh interesting - is it on the dev branch too? if so i'll download the last available and test it. |
|
It's in release & latest-dev yes. You must have an older commit (not sure which one that sha maps to). |
|
oh yes, it is an old commit - my image was created on Thanks again for all the work you are putting into this :) |
|
'afternoon @Nerivec, I tested the switch again, just permitting pairing via the Ikea proxy and I confirm that:
Here a full log, including enabling pairing, pairing, pressing 2 times the right button, 2 times the left button and disable pairing Once pairing is disabled, messages are discarded - they start coming through after pairing is enabled again |
|
Let's move the conversation about permit join troubles to #25620 since this is no longer about the Moes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
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: