The only reason I’m upgrading to OH 5.x is the Amazon Echo Control binding has been reported it works 100%. The Amazon Echo Control 4.3.9 version does NOT work 100%.
Glad to hear this. Some things are hard to understand .
I upgraded recently from OH 3.4.6 to OH 4.3.8 as a intermediate step. But now i hesitate to jump on OH 5. My current feeling after roughly a week on OH 4.3.8 is, that this release is by far not competitive to OH 3.4.6 w.r.t. stability and overall performance. But i was indirectly forced to make this step due to the bindings “Amazon Echo Control” and “iCloud” which both stopped to work. And a solution for OH 3.4.6 was not provided for “Amazon Echo Control” what is understandable on one side.
But in my view, the upgade stragtegy of the “OH makers” is a bit fast versus generating really stable versions at high performance.
Interesting. I am using openHAB since version 1.8, and the 3.x series was the worst.
So it definitely depends on which bindings and on which hardware you are using openHAB.
Only what is considered “important fixes” is backported to 4.x, so you shouldn’t normally see performance degradation between versions like these. Could you share some light on exactly what got worse?
That said, I do understand the hesitancy to upgrade, I myself am still running 4.2.3, for the simple reason that it works for the things I use, and the “surprise factor” of doing an upgrade is just not something I appreciate.
Am a Windows11 user and run OH 4.3.8 / Zulu17 on a Dell Pro Micro Desktop. Intel(R) Core™ i9-14900K (3.20 GHz), 32GB RAM.
Okay, i try to specify my findings up to now:
OH startup takes up to 5 minutes. Have 300 things, 2000 items and 130 rules.
Marketplace appears and disappears. A lot has been reported on that but no solution yet.
In main UI something like the “thing handler” is lost after probably a day. Means that i can’t disable/enable things any longer. Up to now, i found only an OH restart as helpful.
Have “MercedesMe” from marketplace and downloaded “eBUS” as .kar and “SONOFF” as well as “Neato/Vorwerk” as .jar into the addons folder. “SONOFF” is not working as it should.
Integrated “Shelly” looses online states for devices while they might still work.
Get error messages “ZonedDateTime” is deprecated for rules but they still work out as usual.
“Modbus” binding makes trouble with transformations after 1-2 days. Use the recommended “Java-Script Scripting” binding. Have to investigate more here. “Modbus” was one of the most reliable bindings in OH 3.4.6.
Means under the line, that i had to restart OH basically every day while OH 3.4.6 ran over many weeks without any issue.
If i upgrade to OH 5, “MercedesMe”, “eBUS” and “Amazon Echo Control” are promised to be available. “SONOFF” and “Neato/Vorwerk” will probably be broken? And many other special effects are already reported about OH 5.X.
How long did it use to take in 4.3.6? How do you determine “when startup is finished”?
I’m not familiar with that, is this a 4.3.8 specific issue? Marketplace issues are often related to the forum, not the OH version.
For which binding(s)? Or are you saying that this is a generic issue that can happen to Things from any bindings?
All these worked properly in 4.3.6? I’d think that many of the bindings would be unchanged between 4.3.6 and 4.3.8.
Deprecated warnings usually work like that - they tell you of something that might disappear in the future, and that you should rewrite your rules to use whatever function that is recommended instead.
As far as I can tell, there have been no changes to the Modbus binding between 3.4.6 and 3.4.8. My guess is that you have some problem, perhaps one binding, that makes trouble for your whole installation. Have you looked in the log for clues? It could also be worth enabling DEBUG logging briefly (don’t run with that, as it generates a lot of logs) to look for clues as to what goes wrong.
If you manage to figure out which binding is causing the trouble, “everything else” might start acting normally if you disable that one. It would also potentially make it possible to fix the bug with that binding, if that’s in fact the cause. It could be something else, but it seems most likely to me that it’s a binding, otherwise “everybody” would experience the same problems.
Look at /etc/openhabian.conf (change openhab4 to openHAB for the branch)
sudo apt install openhab=5.0.3-1 (I choose the stable branch)
sudo apt install openhab-addons=5.0.3-1
nano /etc/default/openhab (I have 8 GB RAM on the Pi5, hence the large RAM settings)
EXTRA_JAVA_OPTS=“-Xms2g -Xmx4g -XX:-TieredCompilation -XX:TieredStopAtLevel=1 -XX:+ExitOnOutOfMemoryError -Dxtext.qn.interning=true -Duser.timezone=America/Chicago”
Clean Cache/Tmp
Reboot Pi5
sudo apt-mark hold openhab → lock down OH so you don’t accidentally upgrade it
sudo apt-mark hold openhab-addons → lock down OH so you don’t accidentally upgrade it
I couldn’t be happier with the speed of everything. When I started with OH 2.x it took over an hour to startup, 3.x took 50 minutes and 4.x took 35 minutes. 5.x on a x64 platform completely starts up in 21 minutes!
.