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

"Unsupported device" error logs on interactions with group entities #9218

Closed
SHxKM opened this issue Oct 18, 2021 · 24 comments
Closed

"Unsupported device" error logs on interactions with group entities #9218

SHxKM opened this issue Oct 18, 2021 · 24 comments
Labels
problem Something isn't working

Comments

@SHxKM
Copy link

SHxKM commented Oct 18, 2021 •
edited

What happened

  1. I have paired the Philips Hue Ensis light, which in the list of supported products. It exposes two entities (its top light, and its bottom/main light).
  2. In Z2M UI, under Groups, I have mapped both entities exposed by this light as a group, with ID 5 and name ensis_group
  3. The light entity ensis_group showed up in Home Assistant.
  4. Whenever I interact with this light entity, the device responds accordingly, but I get these errors in the logs:

    Info: MQTT publish: topic 'zigbee2mqtt/ensis_remote/action', payload 'on-press'
    Debug: Received MQTT message on 'zigbee2mqtt/ensis_group/set' with data '{"state": "ON", "transition": 0.5, "brightness": 254}'
    Debug: Publishing 'set' 'brightness' to 'ensis_group'
    Debug: Ignoring message from coordinator
    Warning: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
    Warning: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
    Debug: Publishing 'set' 'transition' to 'ensis_group'
    Info MQTT publish: topic 'zigbee2mqtt/ph_ensis_main', payload '{"brightness":254,"color":{"h":32,"hue":32,"s":82,"saturation":82,"x":0.4599,"y":0.4106},"color_mode":"color_temp","color_temp":370,"color_temp_startup":370,"linkquality":247,"state":"ON","update":{"state":"available"},"update_available":true}'

  5. At first I thought it was a blueprint-based automation I'm running, but I can easily reproduce the errors with the following: 
    service: light.turn_on 
data:   
    entity_id: light.ensis_group   
    brightness: 120     
    transition: 0.25
  6. To re-iterate: everything is functioning fine, but these errors flood the UI and the logs. There are actually quite a few devices I'd like to map as Zigbee groups.

What did you expect to happen

No errors emitted in logs.

How to reproduce it (minimal and precise)

See "What happened".

Debug info

Zigbee2MQTT version: 1.21.2-1
Adapter hardware: Conbee II
@SHxKM SHxKM added the problem Something isn't working label Oct 18, 2021
@uvjim
Copy link

uvjim commented Oct 20, 2021 •
edited

I'm getting the same. Until reading this I hadn't worked out it was to do with the group. I have a single group that consists of two Philips Hue GU10s.

Like you it is all working fine, just getting these warnings in the log.

Zigbee2MQTT:warn  2021-10-20 20:40:19: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Zigbee2MQTT:warn  2021-10-20 20:40:19: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
Zigbee2MQTT:warn  2021-10-20 20:40:25: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Zigbee2MQTT:warn  2021-10-20 20:40:25: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

@Koenkk
Copy link
Owner

Koenkk commented Oct 21, 2021

If you see Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined' the device has not been paired properly. I except in the frontend there will be a red question mark next to it.

Try force removing the device and repairing it.

@uvjim
Copy link

uvjim commented Oct 21, 2021

I haven't added any new devices recently and there are none that have a red question mark against them.

image

Happy to turn on some debugging if that might help.

@SHxKM
Copy link
Author

SHxKM commented Oct 21, 2021

I haven't added any new devices recently and there are none that have a red question mark against them.

image

Happy to turn on some debugging if that might help.

Just want to chime in and say that it’s the same for me. Also happy to provide any logs needed.

@mada199122
Copy link

mada199122 commented Oct 30, 2021 •
edited

This is happening to me when I set state from Home Assistant to a group of device.
The group of device is created in Zigbee2MQTT...

For example I have two Ikea bulb LED2003G10. If I group them in Z2M and I set the state of the group in Home Assistant, I receive the error message...

If I set the state of the light individually I don't have that error.

Screenshot 2021-10-30 at 09 41 35

As you can see from the screenshot HAS doesn't see the model and the manufacturer of the light in the group.

@Nimmsis
Copy link

Nimmsis commented Nov 1, 2021 •
edited

I can confirm this as well.

enviorment:
HA: 2021.10.6
zigbee2mqtt 1.22.0-2 and 1.21.2-1 tested (1.22.0-2 was released 20 min ago)
Hardware: Intel NUC
Adapter: Conbee II

Philips hue lights.
error message appears when interacting with group. (on/ off from HA, but also setting brightness level for example)
the order gets sent to the devices and for example it turns on. but error message appears.

addressing them individually works fine.

@strandbein
Copy link

The same at me. I have tested this with several groups, always the same warning with /set or /get. All devices - Hue and IKEA - do what they should. When they are controlled individually there is no message. Repairing changes nothing.
Current HA and AddOn version, Raspi4, Conbee II.

Zigbee2MQTT:warn 2021-11-01 21:00:59: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Zigbee2MQTT:warn 2021-11-01 21:00:59: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

@hmorkemo
Copy link

hmorkemo commented Nov 9, 2021

The same happens here, even with a group consisting of one "Philips Hue White A60 Single bulb E27/B22". Controlling it with the group gives the warning. Controlling it directly doesn't.

@Sku1ly
Copy link

Sku1ly commented Nov 10, 2021 •
edited

Chiming in to say the same with IKEA GU10 - LED1537R6/LED1739R5 and Philips Hue 1746330P7.

Only when interacting with the z2m groups in Home Assistant

@michal-krasowski-red
Copy link

Same happened to me after updating from 1.18 to 1.22.0-2.

@SHxKM
Copy link
Author

SHxKM commented Nov 26, 2021

@Koenkk any updates or insights regarding this? I’m willing to contribute to a fix, just need some guidance if you happen to know where the problem may be.

@hwestman
Copy link

Experiencing the same issue attempting to group two Ikea blinds. Working fine individually both from zigbee2mqtt and HA. Calling the group from HA produces Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'. Other groups seem work fine.

@Koenkk
Copy link
Owner

Koenkk commented Nov 27, 2021

Could someone provide the full debug log of this?

See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging.

@Sku1ly
Copy link

Sku1ly commented Nov 27, 2021

Zigbee2MQTT:info 2021-11-27 10:45:48: MQTT publish: topic 'zigbee2mqtt/Flora Light Switch', payload '{"action":null,"battery":0,"brightness":191,"counter":1,"linkquality":255,"update":{"state":"available"},"update_available":true}' Zigbee2MQTT:info 2021-11-27 10:45:48: Update available for 'Flora Light Switch' Zigbee2MQTT:info 2021-11-27 10:45:48: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Update available for 'Flora Light Switch'","meta":{"device":"Flora Light Switch","status":"available"},"type":"ota_update"}' 2021-11-27T10:45:48.960Z zigbee-herdsman:controller:endpoint CommandResponse 0x00178801020ec5c9/2 genOta.queryNextImageResponse({"status":149}, {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) 2021-11-27T10:45:48.961Z zigbee-herdsman:deconz:adapter zclFrame.payload: 2021-11-27T10:45:48.962Z zigbee-herdsman:deconz:adapter { status: 149 } 2021-11-27T10:45:48.962Z zigbee-herdsman:deconz:adapter no response expected 2021-11-27T10:45:48.965Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x790b EP:2 SeqNr. 21 request id: 4 2021-11-27T10:45:48.967Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 4 status: 0 2021-11-27T10:45:48.967Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:48.976Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110 2021-11-27T10:45:48.977Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:48.981Z zigbee-herdsman:deconz:driver query aps data confirm 2021-11-27T10:45:48.987Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 22 2021-11-27T10:45:48.988Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x790b request id: 4 confirm status: 0 2021-11-27T10:45:48.988Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:48.989Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 3 Zigbee2MQTT:debug 2021-11-27 10:45:49: Received MQTT message on 'zigbee2mqtt/Landing/set' with data '{"state": "OFF"}' Zigbee2MQTT:debug 2021-11-27 10:45:49: Publishing 'set' 'state' to 'Landing' 2021-11-27T10:45:49.017Z zigbee-herdsman:controller:group Command 30 genOnOff.off({}) 2021-11-27T10:45:49.018Z zigbee-herdsman:deconz:adapter zclFrame to group - zclFrame.payload: 2021-11-27T10:45:49.018Z zigbee-herdsman:deconz:adapter {} 2021-11-27T10:45:49.018Z zigbee-herdsman:deconz:adapter sendZclFrameToGroup - message send 2021-11-27T10:45:49.019Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x1e SeqNr. 23 request id: 5 2021-11-27T10:45:49.021Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 5 status: 0 2021-11-27T10:45:49.021Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:49.026Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010 2021-11-27T10:45:49.026Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:49.030Z zigbee-herdsman:deconz:driver query aps data indication 2021-11-27T10:45:49.035Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 24 2021-11-27T10:45:49.037Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 24 srcAddr: 0x0 destAddr: 0x1e profile id: 0x104 cluster id: 0x6 lqi: 255 2021-11-27T10:45:49.037Z zigbee-herdsman:deconz:frameParser response payload: 17,4,0 2021-11-27T10:45:49.038Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":4,"manufacturerCode":null,"commandIdentifier":0},"Payload":{},"Command":{"ID":0,"parameters":[],"name":"off"}},"address":0,"endpoint":1,"linkquality":255,"groupID":30,"wasBroadcast":true,"destinationEndpoint":2}' Zigbee2MQTT:debug 2021-11-27 10:45:49: Received Zigbee message from 'Coordinator', type 'commandOff', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 30 Zigbee2MQTT:warn 2021-11-27 10:45:49: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined' Zigbee2MQTT:warn 2021-11-27 10:45:49: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. 2021-11-27T10:45:49.041Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:49.068Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110 2021-11-27T10:45:49.068Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:49.073Z zigbee-herdsman:deconz:driver query aps data confirm 2021-11-27T10:45:49.078Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 25 2021-11-27T10:45:49.082Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x1e request id: 5 confirm status: 0 2021-11-27T10:45:49.082Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 Zigbee2MQTT:info 2021-11-27 10:45:49: MQTT publish: topic 'zigbee2mqtt/Landing 1', payload '{"brightness":254,"linkquality":null,"power_on_behavior":null,"state":"OFF","update":{"state":"idle"},"update_available":false}' Zigbee2MQTT:info 2021-11-27 10:45:49: MQTT publish: topic 'zigbee2mqtt/Landing', payload '{"brightness":254,"state":"OFF"}' Zigbee2MQTT:info 2021-11-27 10:45:49: MQTT publish: topic 'zigbee2mqtt/Landing 2', payload '{"brightness":254,"linkquality":null,"power_on_behavior":null,"state":"OFF","update":{"state":"idle"},"update_available":false}' Zigbee2MQTT:info 2021-11-27 10:45:49: MQTT publish: topic 'zigbee2mqtt/Landing 3', payload '{"brightness":254,"linkquality":null,"power_on_behavior":null,"state":"OFF","update":{"state":"idle"},"update_available":false}' Zigbee2MQTT:info 2021-11-27 10:45:49: MQTT publish: topic 'zigbee2mqtt/Landing 4', payload '{"brightness":102,"linkquality":null,"power_on_behavior":null,"state":"OFF","update":{"state":"idle"},"update_available":false}' Zigbee2MQTT:info 2021-11-27 10:45:49: MQTT publish: topic 'zigbee2mqtt/Landing 5', payload '{"brightness":254,"linkquality":null,"power_on_behavior":null,"state":"OFF","update":{"state":"available"},"update_available":true}' 2021-11-27T10:45:49.097Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 26 2021-11-27T10:45:49.098Z zigbee-herdsman:deconz:frameParser device state: 10100010 2021-11-27T10:45:49.098Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 Zigbee2MQTT:debug 2021-11-27 10:45:49: Received MQTT message on 'homeassistant/sensor/GH-PC01/availability' with data 'online' 2021-11-27T10:45:52.319Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010 2021-11-27T10:45:52.319Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:52.323Z zigbee-herdsman:deconz:driver query aps data indication 2021-11-27T10:45:52.329Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 27 2021-11-27T10:45:52.334Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 27 srcAddr: 0xc6bd destAddr: 0xfffd profile id: 0x0 cluster id: 0x6 lqi: 63 2021-11-27T10:45:52.334Z zigbee-herdsman:deconz:frameParser response payload: 46,253,255,94,192,1,25,0,0 2021-11-27T10:45:52.334Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 Zigbee2MQTT:debug 2021-11-27 10:45:52: Received MQTT message on 'zigbee2mqtt/Landing/set' with data '{"state": "ON"}' Zigbee2MQTT:debug 2021-11-27 10:45:52: Publishing 'set' 'state' to 'Landing' 2021-11-27T10:45:52.423Z zigbee-herdsman:controller:group Command 30 genOnOff.on({}) 2021-11-27T10:45:52.423Z zigbee-herdsman:deconz:adapter zclFrame to group - zclFrame.payload: 2021-11-27T10:45:52.423Z zigbee-herdsman:deconz:adapter {} 2021-11-27T10:45:52.423Z zigbee-herdsman:deconz:adapter sendZclFrameToGroup - message send 2021-11-27T10:45:52.424Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x1e SeqNr. 28 request id: 6 2021-11-27T10:45:52.426Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 6 status: 0 2021-11-27T10:45:52.426Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:52.432Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010 2021-11-27T10:45:52.432Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:52.435Z zigbee-herdsman:deconz:driver query aps data indication 2021-11-27T10:45:52.440Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 29 2021-11-27T10:45:52.443Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 29 srcAddr: 0x0 destAddr: 0x1e profile id: 0x104 cluster id: 0x6 lqi: 138 2021-11-27T10:45:52.443Z zigbee-herdsman:deconz:frameParser response payload: 17,5,1 2021-11-27T10:45:52.444Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":5,"manufacturerCode":null,"commandIdentifier":1},"Payload":{},"Command":{"ID":1,"parameters":[],"name":"on"}},"address":0,"endpoint":1,"linkquality":138,"groupID":30,"wasBroadcast":true,"destinationEndpoint":1}' Zigbee2MQTT:debug 2021-11-27 10:45:52: Received Zigbee message from 'Coordinator', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 30 Zigbee2MQTT:warn 2021-11-27 10:45:52: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined' Zigbee2MQTT:warn 2021-11-27 10:45:52: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. 2021-11-27T10:45:52.447Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:52.477Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110 2021-11-27T10:45:52.478Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:52.480Z zigbee-herdsman:deconz:driver query aps data confirm 2021-11-27T10:45:52.486Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 30 2021-11-27T10:45:52.494Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x1e request id: 6 confirm status: 0 2021-11-27T10:45:52.494Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1 Zigbee2MQTT:info 2021-11-27 10:45:52: MQTT publish: topic 'zigbee2mqtt/Landing 1', payload '{"brightness":254,"linkquality":null,"power_on_behavior":null,"state":"ON","update":{"state":"idle"},"update_available":false}' Zigbee2MQTT:info 2021-11-27 10:45:52: MQTT publish: topic 'zigbee2mqtt/Landing', payload '{"brightness":254,"state":"ON"}' Zigbee2MQTT:info 2021-11-27 10:45:52: MQTT publish: topic 'zigbee2mqtt/Landing 2', payload '{"brightness":254,"linkquality":null,"power_on_behavior":null,"state":"ON","update":{"state":"idle"},"update_available":false}' Zigbee2MQTT:info 2021-11-27 10:45:52: MQTT publish: topic 'zigbee2mqtt/Landing 3', payload '{"brightness":254,"linkquality":null,"power_on_behavior":null,"state":"ON","update":{"state":"idle"},"update_available":false}' Zigbee2MQTT:info 2021-11-27 10:45:52: MQTT publish: topic 'zigbee2mqtt/Landing 4', payload '{"brightness":102,"linkquality":null,"power_on_behavior":null,"state":"ON","update":{"state":"idle"},"update_available":false}' Zigbee2MQTT:info 2021-11-27 10:45:52: MQTT publish: topic 'zigbee2mqtt/Landing 5', payload '{"brightness":254,"linkquality":null,"power_on_behavior":null,"state":"ON","update":{"state":"available"},"update_available":true}' 2021-11-27T10:45:53.876Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010 2021-11-27T10:45:53.876Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1 2021-11-27T10:45:53.880Z zigbee-herdsman:deconz:driver query aps data indication 2021-11-27T10:45:53.886Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 31 2021-11-27T10:45:53.889Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 31 srcAddr: 0x790b destAddr: 0x0 profile id: 0x104 cluster id: 0x19 lqi: 255 2021-11-27T10:45:53.889Z zigbee-herdsman:deconz:frameParser response payload: 24,3,11,2,128 2021-11-27T10:45:53.890Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":3,"manufacturerCode":null,"commandIdentifier":11},"Payload":{"cmdId":2,"statusCode":128},"Command":{"ID":11,"name":"defaultRsp","parameters":[{"name":"cmdId","type":32},{"name":"statusCode","type":32}]}},"address":30987,"endpoint":2,"linkquality":255,"groupID":null,"wasBroadcast":false,"destinationEndpoint":1}' 2021-11-27T10:45:53.891Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1

Hope this is right, it's 'Landing' causing the error in this example

@strandbein
Copy link

This is my log. The group "Flur" are 4 IKEA Oswalla.

log.txt

@strandbein
Copy link

log 2.txt
another example

@strandbein
Copy link

strange also the message "UnhandledPromiseRejectionWarning" that appears every now and then:

Zigbee2MQTT:info 2021-11-27 19:32:11: MQTT publish: topic 'z2m/Thermostat Bad', payload '{"battery_low":false,"current_heating_setpoint":20,"local_temperature":18.7,"local_temperature_calibration":0,"system_mode":"heat"}'
(node:330) UnhandledPromiseRejectionWarning: Error: Read 0x0017880104531733/11 genLevelCtrl(["currentLevel"], {"sendWhenActive":false,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)
at DeconzAdapter.sendZclFrameToEndpoint (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:645:23)
at runNextTicks (internal/process/task_queues.js:60:5)
at processTimers (internal/timers.js:497:9)
at Endpoint.read (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:405:28)
at Object. (/app/lib/extension/bind.ts:469:29)
(node:330) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)
Zigbee2MQTT:info 2021-11-27 19:32:19: MQTT publish: topic 'z2m/Thermostat 1 Wohnzimmer', payload '{"battery_low":false,"current_heating_setpoint":23,"local_temperature":22.5,"local_temperature_calibration":-2,"system_mode":"heat"}'

@hwestman
Copy link

Seems like these are the relevant logs for me

Received MQTT message on 'zigbee2mqtt/attic_group_blinds/set' with data 'CLOSE'
Debug Publishing 'set' 'state' to 'attic_group_blinds'
Debug Received Zigbee message from 'Coordinator', type 'commandDownClose', cluster 'closuresWindowCovering', data '{}' from endpoint 1 with groupID 103
Warning Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Warning Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

@strandbein
Copy link

This lamp is a Philips 4080248P9
Deleted, re-paired, no change.

(node:330) UnhandledPromiseRejectionWarning: Error: Read 0x0017880104531733/11 genLevelCtrl(["currentLevel"],

Koenkk added a commit that referenced this issue Nov 28, 2021
@Koenkk
Ignore messages from coordinator. #9218
cd4ac0c
@Koenkk
Copy link
Owner

Koenkk commented Nov 28, 2021

Should be fixed now, could someone confirm?

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

@strandbein
Copy link

looks good for me now, thank you

@maboehm
Copy link

maboehm commented Nov 29, 2021

on the dev branch I also no longer see the "Unsupported device" messages in the UI

@Koenkk
Copy link
Owner

Koenkk commented Nov 29, 2021

thanks for confirming.

@Koenkk Koenkk closed this as completed Nov 29, 2021
@SHxKM
Copy link
Author

SHxKM commented Nov 29, 2021

Can’t test the dev branch but this looks promising, thanks for all your hard work @Koenkk!

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