[device dont work correct]: LED-Trading 9126 Friends of Hue Module dont work correctly

[Oggymator]

Link

https://www.zigbee2mqtt.io/devices/9133.html

Database entry

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

Comments

Hi,

the product has the same functions like a Friends of Hue Module from Sunricher or Vimar, so like EnOcean PTM https://www.zigbee2mqtt.io/devices/PTM_215Z.html

In Z2M it was found as a PTM 215Z, that is correct, but in Home Assistant I can only use in Automations ""release_4" action". All other functions are missing.

Can anybody figuered out what could be the problem?

thanks and kind regards Tobias

External converter

No response

Supported color modes

No response

Color temperature range

No response

[jophut]

I've figured out that the labeling on the case differs from the reported payload "action": K1: gives "press_3" and "release_3" K2: gives "press_4" and "release_4" K3: gives "press_1" and "release_1" K4: gives "press_2" and "release_2"

Thus it seems that inputs 1 is interchanged with 3 and 4 is interchanged with 2 Also simultaneously K1+K3 gives (correctly) "press_1_and_3" and "release_1_and_3". and K2+K4 gives (correctly) "press_2_and_4" and "release_2_and_4"

Unfortunately I've never received a long press or hold action...

MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{ "definition":{"description":"Pushbutton transmitter module", "exposes":[{"access":1,"description":"Triggered action (e.g. a button click)", "label":"Action", "name":"action", "property":"action","type":"enum", "values":["press_1","release_1","press_2","release_2","press_3","release_3","press_4","release_4", "press_1_and_3","release_1_and_3","press_2_and_4","release_2_and_4","press_energy_bar"]}, {"access":1,"description":"Link quality (signal strength)", "label":"Linkquality","name":"linkquality", "property":"linkquality", "type":"numeric","unit":"lqi","value_max":255, "value_min":0}], "model":"PTM 215Z","options":[],"supports_ota":false,"vendor":"EnOcean"}, "friendly_name":"0x00000000017184da", "ieee_address":"0x00000000017184da","status":"successful","supported":true}, "type":"device_interview"}'

The "action": "press_energy_bar" is also never received.

edit: Also make sure you start paring using your own Zigbee channel: Channel 15 -> K3 (press_1) Channel 20 -> K4 (press_2) Channel 11 -> K1 (press_3) Channel 25 -> K2 (press_4)

And complete by briefly pressing buttons K4 (2) and K1 (3) simultaneously.

[Oggymator]

I've figured out that the labeling on the case differs from the reported payload "action": K1: gives "press_3" and "release_3" K2: gives "press_4" and "release_4" K3: gives "press_1" and "release_1" K4: gives "press_2" and "release_2"

But if the labeling was not correct, why does it work with the Philips Hue Bridge without any problem. If the labeling was not correct, the pairing with the Hue would not work...

[lanwin]

I created a pullrequest to add this info to the docs https://github.com/Koenkk/zigbee2mqtt.io/pull/2844

Thank @jophut for figuring it out.

[philippnbg]

Actually I had success pairing the pushbutton module by pressing K1 (for channel 11) for >10 seconds, wait 3 seconds for z2m to recognise the pairing request and then confirming the pairing request by again pushing K1 for >10 seconds. Very handy if you use the modules in a DIN rail encasement and hard wired setup with single buttons in multiple rooms. This allowed me to do it on my own :)

A video of the process can be seen here (https://youtu.be/j8RFxQjE2Qc?t=140&si=lADK6xsyk7-XXAms , german)