Hey,
The kar file is located in the addons folder, but is an optional package.
I like to have things offline there-fore i use the offline add-ons.
You can download them on the openhab download page at the bottom of the page.
I’ve upgraded to openhab 2.5.2, and i’m now using the 2.5.2 addons, with remote back to false, the problem is now gone.
Michael
Ok, where can I find older addons? 2.4 was working flawlessly so they would works will be perfect. But I don’t find downloads archive at OpenHab site
Where do I disable remote back and what is it for? (Sorry, I know I’m asking too much, but want to have home stable as I had with 2.4, but need 2.5 for RPi4 compatibility
The RPI4 needs the newer Linux kernel in the latest Raspbian. As far as I know openHAB 2.4 should run in that OS. It is somewhat OS independent. Some of your devices may need the newer version & bindings though.
I know, but the actual openhabian image comes with 2.5, and I’m too old and too lazy to install stock raspbian and configure everything from the scratch. In my mind it makes a lot more sense to focus my efforts in trying to do whatever is necessary in order to fix 2.5 rather than be struck in an older version
The problem is that it is the first time I face and issue where logs does not give me a single clue of what binding is failing or what is going on. I tried clearing cache, reviewing /var/lib/openhab2/config/org/openhab/addons.config file for wrong restdocs reference, and my last attempt was to install a fresh system restoring the backup on it. Don’t know what else to do to get 2.5 working and prefer not to rollback to my working 2.4 backup, if possible
Forget about the idea of running a 2.5 core with 2.4 addons. It won’t work, and the problem with rules to reload is in the core, not in addons so you won’t get rid of it by that action.
Then again, it does not happen all by itself, only if you change at least an OH thing.
Try to find out what that trigger momentum is on your system. Enable org.eclipse.smarthome.model.script.rules debug level so you get appropriate messages when rules reload, then try to correlate that with events (from events.log) shortly before to get at least ideas what rule or thing may be causing this to happen.
If you manage to identify that you can probably also work around the problem.
may be some clues in this recent thread
This is exactly it!! thank you very much
I think I see the same. I have one rule triggered by system start. I noticed that it triggers sometimes when I save rule files, especially when I save the file it is in. I have not paid any attention to it as I saw no other issue and thought it was maybe a feature not a bug.
If it is a bug then I will check more carefully exactly what circumstances causes it to trigger.
Openhabian OH2.5.2 RPi4