I am running 3.3.0, snapshot build #2914 and everything is fine and stable. For a normal user (and i am a quite experienced user) the attempts to upgrade to newer 3.3.0 snapshots or the 3.3.0 Release Build are a disaster. Same is with a 3.4.0 snapshot. I have “no things” (139 things, configured through PaperUI and later MainUI, are missing). All rules from textual configuration (69 rules) are also missing.
I am a Windows10 user on a 64bit Intel Compute Stick. For upgrades i apply the update.bat under …runtime\bin.
The hints for “manual interaction” after the upgrade do not really help. I can only say: “this is not a way into a competitive future” for multiple users.
You certainly meant MainUI, as there is no PaperUI in openHAB 3.
I cannot confirm your experience, all my 130+ Thing did not disappear and came ONLINE after the upgrade without any need to manually interact.
@J-N-K already asked, what is in the logs at first start after upgrade?
Can’t find errors in openhab.log. The warnings are eactly the same as in the working version before. The thing files under … \userdata\jsondb\ are present. Beside the message “no things” some things are detected as “new things” and in the Inbox despite the fact that they already exist…
I went through the whole history of 3.3.0 updating to many snapshots. My running snapshot #2914 is pretty close to the Release Build. I cannot understand how a system can be destructed within a few days in such a way.
Spent the whole day to figure out some root cause but without success.
If openHAB is something which can only be handled by foundation members and maintainers, something seems to go wrong.
Would be happy for any hint where i could search. Have read Kai’s “breaking changes which require manual interaction” at least 5 times. But have no idea what happened or i am standing on the pipe.
Most breaking changes apply for the listed bindings, so if you don’t use one of them, there should be no issue.
Changes to Thing configuraton listed should not result in missing Things, but not coming Online. In those cases, there is an information about incorrect config params.
Not everything that happens to openHAB happens because of openHAB.
For example, after upgrading to 3.3 I lost access to the karaf console and got an error saying that Java_home was missing.
After brainstorming with a friend, he hinted at the fact that portainer (what I use to manage docker containers) likes to add environment variables. Lo and behold I had a Java_home Env in there which, after deletion, allowed me to start the console again.
OpenHAB displayed an issue after the upgrade, but it’s was not caused by the upgrade at all.
So, maybe the issue lies somewhere else.
Another issue I had was openHAB lacking permissions to certain files, can’t write to them and bugs out. That was fun to troubleshoot, since some things worked other did not…
Is it possible to retrieve a release history between 3.3.0, snapshot #2914 and the final Release Build. My problem should have occurred on this short way.
Can you conclude something from the relation between totally missing things and the missing rules from textual configuration. 40 rules created through the rule engine are present.
Thanks for any hint in advance.
Edit: could it be an authorization issue? If i check https://myopenhab.org/rest/things it returns {“error”:{“message”:“Authentication required”,“http-code”:401}}
You can check the release notes from Milestone builds, that’s the only way I can imagine.
No, I can only guess about your issue with the rules. Under some cicumstances, mixing between GUI config and textual config can lead to issues. This might apply to your rules. If you have configured Things both ways, that might be a reason as well.
If file-based rules and things are missing, I would check if the user that runs openHAB has read and write access to the directory that contains the configuration.
Hi Jan, thanks for the hint. Am in Windows10 and folder access rights seem to be okay. Did also not change vs the running snapshot version. But found the following lines in openhab.log which are not present using the running version. Any idea what this is?
2022-07-12 14:14:35.628 [WARN ] [rg.openhab.core.io.net.exec.ExecUtil] - Failed to execute commandLine ‘[arping, --help]’
2022-07-12 14:14:36.059 [WARN ] [.io.rest.auth.internal.TokenResource] - Couldn’t find a user with a session matching the provided refresh_token
2022-07-12 14:14:36.060 [WARN ] [.io.rest.auth.internal.TokenResource] - Token issuing failed: invalid_grant
2022-07-12 14:14:36.963 [WARN ] [rg.openhab.core.io.net.exec.ExecUtil] - Failed to execute commandLine ‘[arping, --help]’
15:58:20.635 | INFO | 93-939e-b31f4daccc0c | el.core.internal.ModelRepositoryImpl | 187 | Loading model 'jdbc.persist'
15:58:22.645 | INFO | 93-939e-b31f4daccc0c | el.core.internal.ModelRepositoryImpl | 187 | Loading model 'test.script'
15:58:22.900 | INFO | OH-lsp-1 | .core.model.lsp.internal.ModelServer | 191 | Started Language Server Protocol (LSP) service on port 5007
15:58:23.007 | INFO | 93-939e-b31f4daccc0c | el.core.internal.ModelRepositoryImpl | 187 | Loading model 'test.rules'
