Great! If jabba (Java?) now works for you.
I am using jabba (Java Version Manager) to test
openHAB 3, and it seems it didn’t work the first time.
Are the breaking changes documented anywhere, e.g. the change in syntax for
As well as the change in syntax, the result of
executeCommandLine now seems to include a new line character which it didn’t previously.
Currently have OH2 installed with openhabian on Ubuntu. What will I break if I run the upgrade commands
sudo apt update && sudo apt install openhab?
Edit: I tried doing exactly this on a cloned VM for science. It works but there’s a lot complaining about missing services in the logs. Will investigate more.
Lots can break as openhab2 uses folder paths with
openhab2 in them and openhab3 changes that to just
openhab. This will effect any urls that use the static html server. I recommend that you don’t upgrade a working setup until you setup a test server to have a play and understand the situation better. It also gives you a chance to test your backups to see how easy it is to get your system running from a backup.
Under the “Upgrade from openHAB 2” section in Guide: Installing and testing OH3 snapshots using APT and YUM, it seems to suggest that the installer is able to detect the system is an existing OH2 system and migrate the files automatically. Unless I’m understanding it wrong?
My query was more about openhabian being broken forever in the future from the manual update as I would like to reuse openhabian-config whenever it has been upgraded to support OH3.
Perhaps it can Move the files, but what about inside your rules, sitemaps, configs of bindings and much more. Don’t expect a 100% smooth upgrade. You are going to need to spend hours fixing spot fires when making such a big jump. I would setup a test server or second hard drive you swap out to get it going and then move over when your happy.
Also there are advantages to setting up with the semantic system, you may want to use this and model your home as intended which means going back to scratch in some areas.
I don’t use sitemaps, only HABPanel. Don’t recall rules or bindings config referencing static openhab2 directory. If these are the only issues then there’s probably no issues.
I did try using a fresh installation but the guide above mentions that configs are only copied/migrated automatically if they were already present on a OH2 system during installation phase.
I’m seeing the same in miio binding from 2.5.9 though no changes in the code, maybe some version changed in jetty caused this?
Alexa discovery is broken at the moment. https://github.com/openhab/openhab-alexa/issues/366
Fix should be merged soon and updated on Amazon side.
Try this in your rule
import java.time.Duration executeCommandLine(Duration.ofSeconds(15),<command string>,<parameters string>)
time is in seconds. more than one parameters should be seperated by comma.
Is the Wake On Lan Binding missing on 3.0.0M1 ?
The WoL binding has now been superceded by a WoL feature in the Network binding, which is compatible with OH3.
ah… thanks, have to look in to it.
Dunno about that, but it’s probably because you changed from the v1 binding to a v2 one as you need to use in OH3.
That in turn is not an OH3 breaking changing, has nothing to do with that in fact as you could have moved already in OH2 at any time .
Seeing errors during startup relating to mapdb:
2020-10-13 10:40:28.414 [WARN ] [pdb.internal.MapDbPersistenceService] - Deserialized invalid item: [FAILED toString()] 2020-10-13 10:40:28.438 [WARN ] [ence.mapdb.internal.StateTypeAdapter] - Couldn't deserialize state 'org.openhab.core.library.types.OnOffType@@@OFF': org.openhab.core.library.types.OnOffType cannot be found by org.openhab.persistence.mapdb_220.127.116.11010120355
Just a warning, no error. Simply ignore it.
Not sure about that since I can’t see any evidence of my persisted items being restored on startup.
Question on OpenHAB 3, has a solution for expire binding been found? I am unsure if it converted or was obsoleted. I think this is my only tricky part for me to move oh3 to production.
Thanks for any suggestions.
There is a discussion on this in git hub https://github.com/openhab/openhab-core/issues/1620. As far as in understand the Binding is obsolete, but the new functionality is under development and should be compatible to the binding