Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Müller Licht 404049D sends "action" twice since update to 2.0.0 #25877

Closed
dkneisz opened this issue Jan 18, 2025 · 7 comments
Closed

Müller Licht 404049D sends "action" twice since update to 2.0.0 #25877

dkneisz opened this issue Jan 18, 2025 · 7 comments
Labels
problem Something isn't working

Comments

@dkneisz
Copy link

dkneisz commented Jan 18, 2025

What happened?

Since I updated to version 2.0.0 I have the issue, that my Müller Licht Tint remotes are sending the action twice (see debug log). It seems that only the value for "action" is sent twice, but not the rest of the attributes and also not the JSON in the device topic (which for now I used as a workaround). This did not happen in version 1.42.0.

What did you expect to happen?

I expect that the "action" is only sent once.

How to reproduce it (minimal and precise)

  • enable to send attributes in separate topics (forgot what that option is called)
  • press an action button on the Müller Licht Tint remote

Zigbee2MQTT version

2.0.0

Adapter firmware version

20221226

Adapter

zzh!

Setup

Running in a docker container on a x64 mini PC running Debian 12

Debug log

[2025-01-18 08:23:40] debug: 	z2m: Received Zigbee message from '<Device>', type 'write', cluster 'genBasic', data '{"16389":1}' from endpoint 1 with groupID 16387
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>', payload '{"action":"scene_1","action_group":16387,"device":{"applicationVersion":0,"friendlyName":"<Device>","hardwareVersion":0,"ieeeAddr":"0xa4c13800aa431e4b","manufacturerID":4635,"manufacturerName":"MLI","model":"404049D","networkAddress":2663,"powerSource":"Battery","softwareBuildID":"MDRM001","stackVersion":2,"type":"EndDevice","zclVersion":3},"last_seen":"2025-01-18T08:23:40+01:00","linkquality":102}'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/last_seen', payload '2025-01-18T08:23:40+01:00'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/linkquality', payload '102'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/action', payload 'scene_1'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/action_group', payload '16387'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-friendlyName', payload '<Device>'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-model', payload '404049D'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-ieeeAddr', payload '0xa4c13800aa431e4b'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-networkAddress', payload '2663'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-type', payload 'EndDevice'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-manufacturerID', payload '4635'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-powerSource', payload 'Battery'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-applicationVersion', payload '0'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-stackVersion', payload '2'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-zclVersion', payload '3'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-hardwareVersion', payload '0'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-dateCode', payload ''
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-softwareBuildID', payload 'MDRM001'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/device-manufacturerName', payload 'MLI'
[2025-01-18 08:23:40] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<Device>/action', payload 'scene_1'
@dkneisz dkneisz added the problem Something isn't working label Jan 18, 2025
@Koenkk
Copy link
Owner

Koenkk commented Jan 19, 2025

Could you provide the debug log of this?

See this on how to enable debug logging.

@dkneisz
Copy link
Author

dkneisz commented Jan 20, 2025

I already sent the debug log. There was nothing more on this topic in the log. I will try it again, but I did this multiple times and there was nothing more in the log (and I set it to debug, as there is a debug message in the first line). I set this through the UI. Maybe it's different if I set it in configuration.yaml and restart the docker container. Do I need to set anything else or perhaps I missed some entries.

@dkneisz
Copy link
Author

dkneisz commented Jan 20, 2025

So I tried this again and there is not much more. There are some debug messages before and after that, but I'm not sure if they belong to other devices. Here is the whole thing from after the publish action of the device before to before the publish action of the device after the remote:

"<[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: <-- [254,29,68,129,3,64,0,0,103,10,1,1,0,105,0,215,218,38,0,0,9,20,27,18,202,2,5,64,32,1,103,10]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --- parseNext [254,29,68,129,3,64,0,0,103,10,1,1,0,105,0,215,218,38,0,0,9,20,27,18,202,2,5,64,32,1,103,10]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: <-- [29,124]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --- parseNext [254,29,68,129,3,64,0,0,103,10,1,1,0,105,0,215,218,38,0,0,9,20,27,18,202,2,5,64,32,1,103,10,29,124]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --> parsed 29 - 2 - 4 - 129 - [3,64,0,0,103,10,1,1,0,105,0,215,218,38,0,0,9,20,27,18,202,2,5,64,32,1,103,10,29] - 124
[2025-01-20 19:33:42] debug: 	zh:zstack:znp: <-- AREQ: AF - incomingMsg - {"groupid":16387,"clusterid":0,"srcaddr":2663,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":105,"securityuse":0,"timestamp":2546391,"transseqnumber":0,"len":9,"data":{"type":"Buffer","data":[20,27,18,202,2,5,64,32,1]}}
[2025-01-20 19:33:42] debug: 	zh:controller: Received payload: clusterID=0, address=2663, groupID=16387, endpoint=1, destinationEndpoint=1, wasBroadcast=false, linkQuality=105, frame={"header":{"frameControl":{"frameType":0,"manufacturerSpecific":true,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"manufacturerCode":4635,"transactionSequenceNumber":202,"commandIdentifier":2},"payload":[{"attrId":16389,"dataType":32,"attrData":1}],"command":{"ID":2,"name":"write","parameters":[{"name":"attrId","type":33},{"name":"dataType","type":32},{"name":"attrData","type":1000}],"response":4}}
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2025-01-20 19:33:42] debug: 	z2m: Received Zigbee message from '<device>', type 'write', cluster 'genBasic', data '{"16389":1}' from endpoint 1 with groupID 16387
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>', payload '{"action":"scene_1","action_group":16387,"device":{"applicationVersion":0,"friendlyName":"<device>","hardwareVersion":0,"ieeeAddr":"0xa4c13800aa431e4b","manufacturerID":4635,"manufacturerName":"MLI","model":"404049D","networkAddress":2663,"powerSource":"Battery","softwareBuildID":"MDRM001","stackVersion":2,"type":"EndDevice","zclVersion":3},"last_seen":"2025-01-20T19:33:42+01:00","linkquality":105}'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/last_seen', payload '2025-01-20T19:33:42+01:00'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/linkquality', payload '105'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/action', payload 'scene_1'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/action_group', payload '16387'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-friendlyName', payload '<device>'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-model', payload '404049D'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-ieeeAddr', payload '0xa4c13800aa431e4b'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-networkAddress', payload '2663'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-type', payload 'EndDevice'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-manufacturerID', payload '4635'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-powerSource', payload 'Battery'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-applicationVersion', payload '0'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-stackVersion', payload '2'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-zclVersion', payload '3'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-hardwareVersion', payload '0'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-dateCode', payload ''
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-softwareBuildID', payload 'MDRM001'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/device-manufacturerName', payload 'MLI'
[2025-01-20 19:33:42] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/<device>/action', payload 'scene_1'
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: <-- [254,9,69,196,68,56,3,153,47,82,202,220,181,176,254,35,68,129,0,0,0,0,68,56,1,1,0,163,0,13,5,39]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --- parseNext [254,9,69,196,68,56,3,153,47,82,202,220,181,176,254,35,68,129,0,0,0,0,68,56,1,1,0,163,0,13,5,39]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --> parsed 9 - 2 - 5 - 196 - [68,56,3,153,47,82,202,220,181] - 176
[2025-01-20 19:33:42] debug: 	zh:zstack:znp: <-- AREQ: ZDO - srcRtgInd
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --- parseNext [254,35,68,129,0,0,0,0,68,56,1,1,0,163,0,13,5,39]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: <-- [0,0,15,8,122,10,1,0,32,192,226,255,32,54,228,255,32,0,220,181,26,195]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --- parseNext [254,35,68,129,0,0,0,0,68,56,1,1,0,163,0,13,5,39,0,0,15,8,122,10,1,0,32,192,226,255,32,54,228,255,32,0,220,181,26,195]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --> parsed 35 - 2 - 4 - 129 - [0,0,0,0,68,56,1,1,0,163,0,13,5,39,0,0,15,8,122,10,1,0,32,192,226,255,32,54,228,255,32,0,220,181,26] - 195
[2025-01-20 19:33:42] debug: 	zh:zstack:znp: <-- AREQ: AF - incomingMsg - {"groupid":0,"clusterid":0,"srcaddr":14404,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":163,"securityuse":0,"timestamp":2557197,"transseqnumber":0,"len":15,"data":{"type":"Buffer","data":[8,122,10,1,0,32,192,226,255,32,54,228,255,32,0]}}
[2025-01-20 19:33:42] debug: 	zh:controller: Received payload: clusterID=0, address=14404, groupID=0, endpoint=1, destinationEndpoint=1, wasBroadcast=false, linkQuality=163, frame={"header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0},"transactionSequenceNumber":122,"commandIdentifier":10},"payload":[{"attrId":1,"dataType":32,"attrData":192},{"attrId":65506,"dataType":32,"attrData":54},{"attrId":65508,"dataType":32,"attrData":0}],"command":{"ID":10,"name":"report","parameters":[{"name":"attrId","type":33},{"name":"dataType","type":32},{"name":"attrData","type":1000}]}}
[2025-01-20 19:33:42] debug: 	zh:controller:endpoint: ZCL command 0xa4c1389ad423e657/1 genBasic.defaultRsp({"cmdId":10,"statusCode":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"reservedBits":0,"transactionSequenceNumber":122,"writeUndiv":false})
[2025-01-20 19:33:42] debug: 	zh:zstack: sendZclFrameToEndpointInternal 0xa4c1389ad423e657:14404/1 (0,0,1)
[2025-01-20 19:33:42] debug: 	zh:zstack:znp: --> SREQ: AF - dataRequest - {"dstaddr":14404,"destendpoint":1,"srcendpoint":1,"clusterid":0,"transid":92,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,122,11,10,0]}}
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:writer: --> frame [254,15,36,1,68,56,1,1,0,0,92,0,30,5,24,122,11,10,0,114]
[2025-01-20 19:33:42] debug: 	zh:zstack:unpi:parser: --- parseNext []

@tadasdanielius
Copy link

Having same problem. I have Aqara wall switches. For some I am getting events twice, thus lights goes on immediately off, while others works fine.

@Koenkk
Copy link
Owner

Koenkk commented Jan 21, 2025

@dkneisz could you paste your configuration.yaml (and devices.yaml in case you have one) here + database.db file?

@dkneisz
Copy link
Author

dkneisz commented Jan 23, 2025

Here you go:
z2m-data.zip

Koenkk added a commit that referenced this issue Jan 23, 2025
@Koenkk
fix: Fix duplicate action publish when advanced.output has `attri…
26fb126 
…bute` #25877
@Koenkk Koenkk mentioned this issue Jan 23, 2025
Merged
@Koenkk
Copy link
Owner

Koenkk commented Jan 23, 2025

Found and fixed the issue in #25963

Changes will be available in the dev branch in a few hours from now.

@Koenkk Koenkk closed this as completed Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
problem Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Koenkk @tadasdanielius @dkneisz