-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Errors with mdl110m lamp, wrong state? #448
Comments
From a quick question to chatgpt I got this answer: From the log messages you shared, it appears the issue is with the handling of the hue-saturation (HS) color model in the Meross custom component. The error message Here are a few steps you could try:
Remember to provide as much detail as possible when reporting the issue, including the exact models of the Meross devices you're using, the version of the component and Home Assistant, and any other relevant information. |
I'm not even sure how to put this in white only, there's no way to do that in homekit or the meross app |
It seems that this lamp doesn't support RGB, only color temperature. This error seems to indicate that the RGB value the integration is trying to convert is None—in other words, the integration doesn't know the current RGB color of the light. |
It seems to be in this method:
It first checks if the device supports light color. If it does, it attempts to get the RGB color and then convert it to an HS color. This is where the error occurs because this device does not support RGB color, but the method supports_light_color() seems to return True. |
please take a look at the PR I created: #449 |
Any news on this? |
Hi! |
Describe the bug
I have this mdl110m lamp from Meross integrated with HA, the problem is when I turn on on the UI, the switch automatically turns off but the lamp stays on.
I'm not sure if the errors on the log are related
Your environment
HomeAssistant version: 2023.6.1
Hassio Version (if applicable): -- PLEASE SPECIFY --
Hardware environment: Home Assistant OS VM using the official KVM (qcow2) on a Proxmox
Logs taken when the issue happened
The text was updated successfully, but these errors were encountered: