Tried to perform an upgrade thru the openhabian console but i believe im stuck in the old bintray source paradox.
Is there a .cfg i can modify so that it uses a different repo source maybe? I think i would prefer the in-place upgrade scenario but am happy to defer to those with more experience here, maybe standing up a “new” OH3 Pi and attempt a piecemeal migration is a less heart attack-inducing experience?
I would recommend to leave your prev. system & install working as is and invest into a new sd card, build a new system from ground up.
I ran into many problems with oh3 on a rpi 3b. Java errors, error messages pointing to RAM being scarce. I can’t recall the details, just that I felt rather frustrated at some point and set up a virtual box vm, debian and OH3. And suddenly everything worked much faster and smoother. Running it like that ever since.
Well, i bit the bullet and paid over the odds a bit for a new RPi 4 and did a side-by-side upgrade.
Best advice ive gotten, made things a helluva lot easier and it allowed me to tackle it bit by bit, reduced frustration and kept the sanity intact.
Some points to make, for anyone else going thru it (no particular order).
Zwave devices were a little painful, having to exclude device X on old system, then quickly adding device on X on new system. Still, once i got into the cadence of it, it was fine.
Some Zwave devices were more painful than others, namely switches/relays that are buried behind lightswitch faceplates. Even though their manuals claimed they could be put into exclusion mode by flicking the lightswitch a particular no. of times, it never worked for me, had to remove the faceplates and trigger the exclusion using the button on the relays themselves.
I have an RFXTRX USB controller, getting my devices migrated was a breeze since i had all the old ID’s still on my old system, copy and paste job, thought it would be the worst part. It was easy in the end.
Hue things just all came across by themselves once i added the Hue controller, simplest part of the migration.
Have completely moved away from .item file definitions, tried to just stick to UI and so far, so good. Haven’t yet found the need to create an .items file which i’m glad about, found those tricky to keep track of and easy to get wrong.
Deleted all devices from my Alexa app and re-discovered, after switching the Skill to use my “new” email account (which is linked to my new OH 3.3 instance). Worked fine, with a bit of tinkering
Said tinkering was mainly around the Alexa metadata on the Things, e.g. trying to get an LG TV power switch to “appear” as a switch in the Alexa app, again, made much easier by the lack of using .items/.things files, just edited in UI and re-discovered in Alexa app until they appeared how i wanted them to.
Thermostat current temps appear “weirdly” in Alexa, its the correct temp but the display value is “chopped” or hidden to some extent so you only see half the value (attached a screenshot)
Thats all ive got for now, overall a reasonable experience, helped by the fact that there was no rush to get everything done in one single sitting. I’d say i spent an hour per day, over a week, to get it done (approx).
Ah, that’s a little unfortunate. If you just moved over the Z-Wave controller, then you didn’t need to exclude any of your devices. The inclusion is on the controller, so you just move it to the new server. The only tricky spot is with securely-included devices. For those to move over cleanly, you have to first copy the Network Security Key from the old server to the new one. Sorry you went through all that, and glad you didn’t have too much trouble.
Use the tags to your advantage. The more tags you add, the easier it’ll be to keep things organized.
Some folks have moved back toward items. I can see the benefits of both approaches, so I’m holding out hope that we’ll eventually have a way to make items in the UI and bulk edit them as we can with text files.