Skip to content
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

ThingManagerImpl: Channel types or config descriptions for thing .. are missing in the respective registry for more than 120s #4518

Open
andrewfg opened this issue Dec 23, 2024 · 0 comments

Comments

@andrewfg
Copy link
Contributor

andrewfg commented Dec 23, 2024

When a binding is trying to update a channel type from version 0 (where the channel has a local channel type) to version 1 (where the channel uses a system channel type), the ThingManagerImpl logs the following warning:

2024-12-23 15:17:13.145 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'govee:govee-light:64f91eceab' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2024-12-23 15:17:13.146 [INFO ] [core.thing.internal.ThingManagerImpl] - Updating 'govee:govee-light:64f91eceab' from version 0 to 1

The log says "Channel types or config descriptions .. are missing" -- which is really helpful since it is not clear if the problem is due to the channel types (and if so which of them) or the config descriptions (and if so which of them). And furthermore the log gives no clue if it relates to the attributes provided by the prior binding version, or the respective same attributes provided by the new binding version after the update. As I said: really helpful indeed.

But anyway comparing the before and after thing code in UI it seems that everything was, and is now, all as it should be.

So I don't know if this issue is a bug in the binding (either before or after) or a bug in OH core. The log message comes from the registry, and only appears on the first update run, so I am inclined to think the issue is not in the new binding. Ergo: I think this is a bug in OH Core

Old

image

New

image

Originally posted by @andrewfg in openhab/openhab-addons#17812 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant