Berry/Zigbee reading attributes_final doesn't answer as described in docs #22623
-
PROBLEM DESCRIPTIONA clear and concise description of what the problem is. With tasmota 14.3.0 on my ZB-GW03 it prints "shortaddr=Ox1C69 event_type=attributes_final attr_list={"AppVersion":101,"0000/FFE2":53,"0000/FFE4":0,"Endpoint":true,"LinkQuality":true}". The endpoint is correct on the level "event_type=frame_received", but starting with "event_type=attributes_raw" the endpoint switches to "true". REQUESTED INFORMATIONMake sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Configuration output here:
Rules output here:
STATUS 0 output here:
04:46:45.165 RSL: STATUS = {"Status":{"Module":0,"DeviceName":"Tasmota","FriendlyName":["Tasmota"],"Topic":"tasmota_C25A74","ButtonTopic":"0","Power":"0","PowerLock":"0","PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0}}
04:46:45.169 RSL: STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"","RestartReason":"Software reset CPU","Uptime":"0T22:56:21","StartupUTC":"2024-12-09T21:50:24","Sleep":50,"CfgHolder":4617,"BootCount":52,"BCResetTime":"2023-10-19T09:41:15","SaveCount":107}}
04:46:45.172 RSL: STATUS2 = {"StatusFWR":{"Version":"14.3.0(tasmota)","BuildDateTime":"2024-12-09T21:41:22","Core":"3_1_0","SDK":"5.3.1.240924","CpuFrequency":240,"Hardware":"ESP32-D0WD-V3 v3.1","CR":"314/699"}}
04:46:45.178 RSL: STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":3,"LogHost":"","LogPort":514,"SSId":["",""],"TelePeriod":300,"Resolution":"55C180C0","SetOption":["00000001","2805C80001000600003C5A0A192800000000","000000A0","00004000","00004000","00000000"]}}
04:46:45.186 RSL: STATUS4 = {"StatusMEM":{"ProgramSize":1531,"Free":1349,"Heap":144,"StackLowMark":3,"PsrMax":0,"PsrFree":0,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"1640EF","FlashFrequency":40,"FlashMode":"DIO","Features":["0809","9F8A07DF","00500001","000000CF","010013C0","00000000","40024080","00200000","0400002C","00000080","00000004"],"Drivers":"1,!2,!3,!4,!5,!8,9,10,11,!12,20,!21,23,38,!41,50,52,62,!68,82,121","Sensors":"1,2,3,5,6,127","I2CDriver":"7"}}
04:46:45.191 RSL: STATUS5 = {"StatusNET":{"Hostname":"tasmota-C25A74-6772","IPAddress":"0.0.0.0","Gateway":"192.168.178.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.178.1","DNSServer2":"2a02:2761:21f8:1700:464e:6dff:fe33:8b35","Mac":"24:DC:C3:C2:5A:74","IP6Global":"","IP6Local":"","Ethernet":{"Hostname":"tasmota-C25A74-6772-eth","IPAddress":"192.168.178.30","Gateway":"192.168.178.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.178.1","DNSServer2":"2a02:2761:21f8:1700:464e:6dff:fe33:8b35","Mac":"24:DC:C3:C2:5A:77","IP6Global":"2a02:2761:21f8:1700:26dc:c3ff:fec2:5a77","IP6Local":"fe80::26dc:c3ff:fec2:5a77%en1"},"Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
04:46:45.197 RSL: STATUS7 = {"StatusTIM":{"UTC":"2024-12-10T20:46:45Z","Local":"2024-12-11T04:46:45","StartDST":"2024-03-31T02:00:00","EndDST":"2024-10-27T03:00:00","Timezone":"+08:00","Sunrise":"15:34","Sunset":"23:52"}}
04:46:45.200 RSL: STATUS10 = {"StatusSNS":{"Time":"2024-12-11T04:46:45"}}
04:46:45.203 RSL: STATUS11 = {"StatusSTS":{"Time":"2024-12-11T04:46:45","Uptime":"0T22:56:21","UptimeSec":82581,"Heap":143,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":5,"Objects":88}}}
Console output here:
TO REPRODUCESteps to reproduce the behavior: to "def attributes_final(event_type, frame, attr_list, idx)" my ZB-GW03 prints "shortaddr=Ox1C69 event_type=attributes_final attr_list={"AppVersion":101,"0000/FFE2":53,"0000/FFE4":0,"Endpoint":true,"LinkQuality":true}". EXPECTED BEHAVIOURA clear and concise description of what you expected to happen. The tasmota berry docs say, to "def attributes_final(event_type, frame, attr_list, idx)" it should print as example "shortaddr=OxC1BC event_type=attributes_final attr_list={"ActivePower":261.612,"(ActivePower)":"0B04/050B","Endpoint":21,"LinkQuality":21}" I need the correct endpoint-number for further processing, not just "true". SCREENSHOTSIf applicable, add screenshots to help explain your problem. ADDITIONAL CONTEXTAdd any other context about the problem here. (Please, remember to close the issue when the problem has been addressed) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Hard to reproduce without even knowing what the Zigbee device is, and without the log at the relevant time. It might depend on what device it is, and details from the log. With one of my devices I'm seeing: |
Beta Was this translation helpful? Give feedback.
-
Thanks for reporting this bug. It is now fixed in the latest version in the |
Beta Was this translation helpful? Give feedback.
Thanks for reporting this bug. It is now fixed in the latest version in the
development
branch.