openHAB 5.0 Milestone discussion

@jimtng Weird, but have it fixed. Steps

  1. On restart same errors (this was one of three)
    2025-07-19 10:47:22.831 [WARN ] [ore.common.registry.AbstractRegistry] - Cannot add "StringItem" with key "Downstairs_Mode". It exists already from provider "GenericItemProvider"! Failed to add a second with the same UID from provider "ManagedItemProvider"!

  2. Deleted the UI version (without the lock) 2025-07-19 11:12:16.957 [WARN ] [ore.common.registry.AbstractRegistry] - Provider 'ManagedItemProvider' is not allowed to remove element 'StringItem' with key 'Downstairs_Mode' from the registry because it was added by provider 'GenericItemProvider'.

  3. The weirdness is the first message says the managed version wasn’t created (but it was) and the second said it couldn’t be deleted, (but it was) . Anyway the “hidden” item from the file appeared with the lock in place after the deletion, so all is fine. Thanks

I think that the warning message is just worded somewhat “clumsy”. I think it means that it couldn’t add a second (? Item) with the same UID as the one already provided by ManagedItemProvider.

16 posts were split to a new topic: ZW-JS channels missing

I waited over a day and the list never came back. I remain unable to install the new meter reading template to ensure it works.

I’m not sure what I can do about it.

Note if I open the URL in the error message from a browser I am able to do so without error, so what ever is causing the 429 code is not based on my IP address at least. Though the fact that it works on a restart also points to that conclusion.

If anyone else is able to install the meter reading template, let me know if it worked or not so I can remove the published tag if it doesn’t. It should work but the yaml is finiky and there’s no way to test I got it right except through an installation from the marketplace.

Thanks!

I’m planning to upgrade my 4.3.5 installation to 5.0. My openhab is on a 64bit Ubuntu 22.04 with Openjdk zulu 17. What is the best way to upgrade?
My idea is to stop my openhab instance, install java 21 and then upgrade. Is this a correct way? Thanks a lot.

1 Like

yes

With 5.0 being released and posting activity going sharply up, please let me remind you of general forum posting rules and some special ones that apply to this thread:
Please only post issues here that you have with a 5.0 milestone software since you upgraded there from 4.3, and that you believe applies to other OH users with their setup, too.
Any generic question or individual issue that is specific to your own setup only, please open your own thread.
If you upgraded from some older version, you should be reasonably sure the problem didn’t already exist in 4.3 before you post it here.
There’s equivalent threads for every 4.X you can turn to for your post. Rules apply likewise there.

Thank you for your cooperation.

PS:
There will be opened another likewise thread for 5.0 (release) and the 5.0 release notes will have a section on upgrading

Ok, then it isn’t merely the cache. I’m getting the same error as you when trying to install the add-on, and frankly I have no idea what’s going on:

Unable to retrieve marketplace add-ons: Server returned HTTP response code: 429 for URL: https://community.openhab.org/c/marketplace/69/l/latest?page=6

This is a bit strange though, as it has to do with the “hidden pagination” that is used to pull all the topics, which supposedly, at least publicly, isn’t supported by Discourse. Maybe recent updates to the forum have changed something..?

I still don’t understand it though, as this is used to retrieve the “list of add-on”, and shouldn’t be needed when installing a particular add-on, as the direct link to that add-on is already known.

The 429 might be triggered because of some “rate limiting” on the forum, that a certain IP does more than x number of requests in y seconds. Maybe this has been introduced in a forum update. The OH installation makes requests in quick succession, which might trigger a “guard” like that.

So, I can’t help you test it at this moment, but I think it’s highly likely that this is a wider problem that will affect many. If 5.0 is released tomorrow and “everybody” get errors when trying to update their add-ons, it could become a regular mayhem.

I will need time to try to debug exactly what’s happening, but my bet is on that updates to the forum is what’s causing it.

It’s possible to build logic that prevents such things from happening by having OH wait a certain time between requests, but there’s no time to make that in time for the 5.0 release, and we’d need to know that this is the exact reason, and what the “acceptable request rate” is.

I installed the openHAB 5 release minutes ago as it is already available for download.
I think it is a very, very bad experience for a lot of openHAB users as one of the most important Bindings, the Amazon Echo Control Binding, was not fixed.
I am very disappointed 


2025-07-21 20:50:52.360 [WARN ] [rol.internal.util.HttpRequestBuilder] - Parsing json failed: false
com.google.gson.JsonParseException: Empty result
	at org.openhab.binding.amazonechocontrol.internal.util.HttpRequestBuilder$Builder.lambda$0(HttpRequestBuilder.java:268) ~[?:?]

You are referring to a warning in the logs, not an error. This one can be ignored.

Then it would be great if the binding was working correctly. But it does not. Amazon Things are going offline/online, all of these issues are described in several topics in the last weeks, and there is no solution.

Edit: the (former?) maintainer of the binding even proposed a fix on github, but it looks no other maintainer had the time to take that action 


Can’t you build your own version, with the fix integrated then?

Sorry @sihui, when I noticed the issue ([amazonechocontrol] OH 4.3.5 + OH 5.0.0 Binding is not more working / Channels will not work anymore · Issue #18899 · openhab/openhab-addons · GitHub) and marked it as critical, it was already quite late to get a fix into the release. Nonetheless, I should not have removed the critical label.

While it probably wouldn’t have changed the outcome, it also meant that it wasn’t discussed among the maintainers as it should have been.

I’m confident that since the fix seems straightforward, it’s very likely to be included in the first patch release.

Is there a 4.3.x fix JAR we can download?

Best, Jay

No one has started work on a fix yet. I briefly looked at the changes and realized i’m not familiair enough with the binding and the API to get this done in a reasonable way.

If anyone can contribute, i’m happy to review and merge it as quickly as possible.

I now suspect that it might be caused the fact that there are two add-on’s called “Meter Reading” with different compatibility information. I think there’s a flaw somewhere in the code that leads to an endless loop, which makes the forum respond with 429 in the end. This seems to “bring down” the community marketplace handler so that it won’t do any other tasks until after OH has been restarted.

I haven’t managed to pinpoint the bug, but I see these two in the logs: Meter Reading [3.3.0;3.4.9) and Meter Reading [4.3.0.0;5.9.9.9]. The compatibility information is processed and then stripped from the name, which makes these two “equal” for any code that goes by name only. Try to rename one of them, e.g “Meter Reading II”, and see if that makes it work.

I’m not saying that’s a fix, just that it can confirm or deny my theory, and that it might be a temporary workaround.

Renamed the new one to Meter Reading II and some slight progress. I still get the same error messages, but it doesn’t crash the whole marketplace. The marketplace entries are still there, and I don’t have to restart OH to get them back.

It seems that there are two problems going on and changing the name solved one of them.

1 Like

I still haven’t nailed down exactly where it goes wrong, but I’m relatively confident that it’s a similar problem: They both have UID rules_tools:meter, and I’m almost willing to bet that this causes them to be mixed up somewhere.

The “resource” link must end with .yaml or it is excluded as irrelevant. That still doesn’t explain all of the “weird” behavior found here, but I’ve traced what happens far enough to know that it doesn’t find a link to download from.

I’ve made a little fix that makes it behave a bit nicer where there’s no link, but the biggest problem (how the whole marketplace handler was “crashed”) I still haven’t figured out. I guess I’ll have to make another “test” addon with an identical name to one that’s there to try to debug that.

With my fix, this is logged when trying to install it:

Rule template marketplace:165001 has neither download URL nor embedded content

That should make it a bit easier to figure out what the problem is.

There is absolutely no reason for an excuse.
As a long time openHAB user and a frequent openHAB github reader I know pretty well who is doing all the work on this project.
You and all other maintainers are doing an outstanding job and I would like to thank you for that.
But because the issues for the Amazon Echo Control binding are weeks old, I thought it would get more attention, therefore my disappointment.
Keep up the good work. :+1: