You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to make a request for support of a ceiling light that itself reports as model "ceila". The light works as all other ceiling lights, discovery works as well, just the model does not seem to be supported. As a guess it could work as "ceiling light with night mode". Actually it's a family of ceiling lights, end user information is provided here: https://en.yeelight.com/product/led-ceiling-light-c2001-series/
I would like to note, that the discovery results in an exception currently which is not caught properly. So the "scan" button shows nothing and the exception just pops up in the log file after increasing the loglevel above "info". I would propose to show at least in the log file as "warn" or "info" level a respective message indicating that a device had been found but could not be identified. This would increase the user friendliness a little.
The text was updated successfully, but these errors were encountered:
I'd like to make a request for support of a ceiling light that itself reports as model "ceila". The light works as all other ceiling lights, discovery works as well, just the model does not seem to be supported. As a guess it could work as "ceiling light with night mode". Actually it's a family of ceiling lights, end user information is provided here: https://en.yeelight.com/product/led-ceiling-light-c2001-series/
Below is the output of the discovery:
I would like to note, that the discovery results in an exception currently which is not caught properly. So the "scan" button shows nothing and the exception just pops up in the log file after increasing the loglevel above "info". I would propose to show at least in the log file as "warn" or "info" level a respective message indicating that a device had been found but could not be identified. This would increase the user friendliness a little.
The text was updated successfully, but these errors were encountered: