-
Notifications
You must be signed in to change notification settings - Fork 712
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
[Device Support Request] Aubess/Tuya TS0505B by _TZ3210_it1u8ahz RGBCC bulb. Minor fix. #2365
Comments
In the diagnostic section i find this:
0x1888 has no matching entries in ZCL lightning.py hence endpoint_attribute is null. |
@TheJulianJES @MattWestb @javicalle Any idea of where I should start looking to fix this? |
Sorry im not one code worrier so i cant helping but our friends 110% can do that :-)) |
@TheJulianJES & @javicalle Bumping this :-) |
@TheJulianJES It might fix the log errors. What is the easiest way to test this? |
Making one local quirk for your device and adding the signature and importing and use the 0x1888 cluster in it then the system shall trying using the commands from the 0x1888 cluster / attributes of it but i think its a not working one on this device. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions. |
Problem description
Device is throwing log errors on the color cluster 0X300 (768) (see log)
Solution description
Device seems to be working, but would be nice to get rid of the errors cluttering the log.
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]
Device signature
Device signature
Diagnostic information
Diagnostic information
Logs
Logs
Custom quirk
No custom quirks or core quirks are loaded.
Additional information
Have tried re-pairing the devices with no effect.
The device is listed as Zigbee 3.0 compatible, so ideally this should not occur.
The text was updated successfully, but these errors were encountered: