-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enocean PTM 215Z Greenpower not working after upgrade 1.36.1=> 1.37 or later #23814
Comments
I have a PTM 215Z on my network and it works without issues running 1.39.1-1. So i think i will wait upgrading to 1.40 for now.. |
It might be related to @coendaar How did you pair your PTM215Z ? |
@chris-1243
I don’t reallly get how the log in v1.31 can be full of |
As I told you and from Z2M 1.31 to the latest 1.40, some changes might have occured in Would you try to pair one of your PTM215Z as suggested in this link https://www.zigbee2mqtt.io/advanced/zigbee/01_zigbee_network.html#green-power-devices |
It has to be the deconz driver as i upgraded to 1.40 and no problems here using Tubezb controller. |
As requested:
Next steps:
The switch doesn't work. Log in v 1.40:
Then i tried:
Then i tried
Then I tried
After digging in the logs I find this Assertionerror during the join process:
This one from joining the Ikea light:
This from joining the adurosmart device
And searching the log for 'green' shows (top left button press+release, wait 10 seconds, top right button press+release):
So conclusions/assumptions:
|
I had a look in the thread you referenced and it seems related to I guess something is not working/coded correctly in The best way to know if your PTM215Z are paired as |
Assuming the
The changelogs show significant refactoring of deconz and Greenpower between these versions. Most of it from @Koenkk But i would have expected other users to have also noticed this. Only this user seems to have same issue, and he is also stuck on 1.36.1: #22578 (comment) |
@Koenkk I suggest starting by re-writing private checkReceivedGreenPowerIndication(ind: gpDataInd): void {
const gpdHeader = Buffer.alloc(15); // applicationId === IEEE_ADDRESS ? 20 : 15
gpdHeader.writeUInt8(0b00000001, 0); // frameControl: FrameType.SPECIFIC + Direction.CLIENT_TO_SERVER + disableDefaultResponse=false
gpdHeader.writeUInt8(ind.seqNr!, 1);
gpdHeader.writeUInt8(ind.id!, 2); // commandIdentifier
gpdHeader.writeUInt16LE(0, 3); // options, only srcID present
gpdHeader.writeUInt32LE(ind.srcId!, 5);
// omitted: gpdIEEEAddr (ieeeAddr)
// omitted: gpdEndpoint (uint8)
gpdHeader.writeUInt32LE(ind.frameCounter!, 9);
gpdHeader.writeUInt8(ind.commandId!, 13);
gpdHeader.writeUInt8(ind.commandFrameSize!, 14);
// TODO: change `commandFrame` parsing type to Buffer to avoid unnecessary re-conversion
const payBuf = Buffer.concat([gpdHeader, Buffer.from(ind.commandFrame!)]);
const payload: Events.ZclPayload = {
header: Zcl.Header.fromBuffer(payBuf),
data: payBuf,
clusterID: Zcl.Clusters.greenPower.ID,
address: ind.srcId! & 0xffff,
endpoint: ZSpec.GP_ENDPOINT,
linkquality: 127,// bogus
groupID: ZSpec.GP_GROUP_ID,
wasBroadcast: true,// TODO: take the codepath that doesn't require `gppNwkAddr` (true) or not (false)?
destinationEndpoint: ZSpec.GP_ENDPOINT,
};
this.waitress.resolve(payload);
this.emit('zclPayload', payload);
} It should clean things up and align behavior with |
Thanks @Nerivec ! I was able to reproduce the issue ( @coendaar can you see if this fixes the issue: docker exec -it CONTAINER_NAME sh
apk add nano
echo > /app/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js
nano /app/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js
# Update with https://gist.github.com/Koenkk/3f8a69b8aefeefa27a3a1ed5d13801a6
# save and exit nano
exit
docker restart CONTAINER_NAME |
@Koenkk thanx for looking in to this. Do i need to re-pair the switch to test this? Or try if works instantly? |
@coendaar try to send the pairing command again (so holding button of the corresponding channel + energy bar for 7 secs) |
Ok. |
Ok.
|
and the pairing (permit join: all) gives an error:
|
after deleting the switch and permit join to an ikea https://www.zigbee2mqtt.io/devices/LED1733G7.html#ikea-led1733g7 The switch still doesn't work (but i'm not sure if the 1733G7 is a suitable ZGP translator the log is as follow:
|
Updated https://gist.github.com/Koenkk/3f8a69b8aefeefa27a3a1ed5d13801a6, can you try again? |
Sure. Here’s the second attempt: join-all without prior removal:
Join-all after force-remove error@14:37:35:
Join Ikea bulb after force remove:
A button press is still not registered unfortunately |
@coendaar to be sure, can you update your conbee to the latest versions? |
@Koenkk sure. I’ll try later tonight when I’m back home. Just to be sure: https://www.zigbee2mqtt.io/guide/adapters/deconz.html still mentions an issue:
Is it safe to update to https://deconz.dresden-elektronik.de/deconz-firmware/deCONZ_ConBeeII_0x26780700.bin.GCF ? |
It seems you are already on a new firmware than the problematic one so I guess it should be fine |
|
@Koenkk Since your last gist revision reverts the srcID/nwkAddr masking in ZclPayload, it shows the received data seems to come in sometimes as plain GP (shows srcID instead since no longer masked in ZclPayload):
and sometimes as proxied GP (shows proper nwkAddr):
It's receiving the commissioning in duplicate too, once as plain, and once as proxied GP. Either way, it's acting like the device never joined?? so it never processes regular cluster commands. |
@coendaar could you provide the debug logging again of pairing + a command with:
|
ok. here we go: pairing (join all) after a force remove:
and a button press:
|
ok.
|
* fix: Fix Deconz Green power implementation Koenkk/zigbee2mqtt#23814 * process feedback
Yes but I would say this is a feature and not a bug. It means that every GPP proxy will now forward messages of this GP device, which allows you to move the device around freely. Since if only 1 GPP proxy would forward messages and the GP device gets out of range, you will not get any messages at all. Note that although you get multiple messages for the same click, only 1 action is published ( I've merged Koenkk/zigbee-herdsman#1175 so the GPP part is fixed now. That still leaves the undelete bug which I cannot reproduce. Can you:
|
@Koenkk Nice!
|
Looks good, seems that the added logging changes the behaviour. @Nerivec just did a nice improvement in this area (Koenkk/zigbee-herdsman#1176). Can you check again with the latest-dev if all works? (without any changed, also check the force remove -> repair case) |
testing: force remove:
re-pair join all:
and a button push. pay attention to line 3. Still an unhandled command? Button works fine though:
everything seems to work. yay |
Thanks for the feedback 😉 |
i have updated to 1.40.1-1. still not working at my end.. in zigbee2Mqtt it shows the correct payload |
@tluethi71 Looks like something didn't get updated. Try this:
|
@Nerivec thank you for you answer. Did not work.
and still not showing the status in mqtt. |
Did you try removing it and re-pairing it instead? These GP devices have a reset procedure, do that too, that will ensure you have a clean slate. |
Hey @Nerivec, yes i did.
|
What do you see if you click on |
triggers:
does it help? |
|
@Koenkk
|
Nothing strange here, could you provide the debug log when starting z2m + waiting for 1 minute? See this on how to enable debug logging. |
sure.. i did a restart of the whole system.. hmm, due to limited character per post I could not post the whole log.. Does it help. Looks kind of not reader friendly..
|
@tluethi71 please upload the full log as a file |
It doesn't contain the startup sequence of z2m, make sure it contains e.g. |
Found the issue, settings |
perfect!!! thanks a lot. It works perfectly.. I needed also to create an automation to trigger the actions (see #22578 (comment)) |
Hello, I updated to 2.0.0-2 and it is not working anymore. I added |
What happened?
After upgrading from 1.31.2 to 1.40.0 the Enocean PTM215Z no longer works. All other devices still work.
After downgrading back to 1.31.2 it works again.
I've tried
What did you expect to happen?
This is logging from version 1.31.2:
Where it's clear that the PTM215Z with address 1718f82 sends a few button presses and they are directly read
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.37.0 and later
Adapter firmware version
0x26680700
Adapter
conbee II
Setup
docker on synology ds216+II
Debug log
log_v140_truncated.log
The text was updated successfully, but these errors were encountered: