-
-
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
"Unsupported device" error logs on interactions with group entities #9218
Comments
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.
|
If you see Try force removing the device and repairing it. |
This is happening to me when I set state from Home Assistant to a group of device. 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. As you can see from the screenshot HAS doesn't see the model and the manufacturer of the light in the group. |
I can confirm this as well. enviorment: Philips hue lights. addressing them individually works fine. |
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. Zigbee2MQTT:warn 2021-11-01 21:00:59: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined' |
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. |
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 |
Same happened to me after updating from 1.18 to 1.22.0-2. |
@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. |
Experiencing the same issue attempting to group two Ikea blinds. Working fine individually both from zigbee2mqtt and HA. Calling the group from HA produces |
Could someone provide the full debug log of this? See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging. |
Hope this is right, it's 'Landing' causing the error in this example |
This is my log. The group "Flur" are 4 IKEA Oswalla. |
log 2.txt |
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"}' |
Seems like these are the relevant logs for me
|
This lamp is a Philips 4080248P9 (node:330) UnhandledPromiseRejectionWarning: Error: Read 0x0017880104531733/11 genLevelCtrl(["currentLevel"], |
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) |
looks good for me now, thank you |
on the dev branch I also no longer see the "Unsupported device" messages in the UI |
thanks for confirming. |
Can’t test the dev branch but this looks promising, thanks for all your hard work @Koenkk! |
What happened
Groups
, I have mapped both entities exposed by this light as a group, with ID5
and nameensis_group
ensis_group
showed up in Home Assistant.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
The text was updated successfully, but these errors were encountered: