-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Limitless LED is not initialized after upgrade from 0.38.1 #6286
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
Comments
After an restart the error has disappeared and was not reproducible even after three restarts. |
Note that |
Please mention in the documentation, that this has changed, as it breaks the component for all existing users. Everyone who used milight before have to set the version to and the port to 8899. Actually I think, we should select the default port according to the version, as the milight controller has no option to manually change the port at all. So it makes no sense, that the user has to change both. And the ports and versions should be mentioned in the documentation. At the moment the only option to find the right port to make the setup working again is by reading the diff of the component. And maybe make the version mandatory, as the component does not work with the more common V5 devices - and just give a meaningless exception. |
Would it be possible to detect if we are trying to connect to a v5 bridge and either use different defaults or at least warn the user? |
At least we get the exception above if we use v6 on a v5 bridge. |
The particular line of code which causes the exception is removed in v1.0.6, and I've tested with this version without getting this error. With v1.0.5 I got this error and traceback quite frequently. |
Uh oh!
There was an error while loading. Please reload this page.
Home Assistant release (
hass --version
): 0.39.1Python release (
python3 --version
): 3.4.2Component/platform: light/limitlessled
Description of problem:
After the upgrade from 0.38.1 to 0.39.1 the limitlessled cmponent does not initialize anymore and a stacktrace is dumped in the log. The "beaking changes" in the release motes say something about the need to define a port/version in this release but the documentation and the code tells its optional.
Expected:
The component should initialize.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
The text was updated successfully, but these errors were encountered: