Over the last few weeks I have spent quite a few days of reading on the forum about OH3, migrating to it from OH2, how to, what to watch out for, and what not.
(Actually I am dabbling in it / contemplating since Jan 2022)
I see that some have changed their mind on how they went about migrating from OH2 to OH3, compared to how they did the same thing later, either redoing the migration, or spending a lot of time creating items via the UI, while others are using files (without the groups).
Others build models… and it just does not sink in, what it is actually used for.
It somehow can build what used to be sitemap, saying somewhere else you do not need a sitemap, why do I need a model to build one.
I am interested in some long-timer OH users, who may started out on v1, moved to v2, who may have, like I, never used the new things 2.5 offered. So yes, ‘things’ … never mind…
… anyway: looking back, with what you know today, how would you migrate to OH3?
I planning to move from a rPi3 to a rPi4 with 4GB memory.
Why? I see no choice, if wanting a supported uniform solution… and use some new bindings, such as ZigBee, Modbus, ComfoAir, myEnergi, etc. and not wanting to use a bridge. (Just get it over with.)
I have 1,475 items, 142 rules, and 167 groups, if this helps to imagine the task at hand. Most controllers are Arduinos communicating via MQTT.
While the automation is barely visible, a lot of thing are happening; however, I am using one HabPanel (I think; forgot how it all works); use the sitemap for mostly admin; never made to grafana, I’d like to use (much nicer), and there are these things called cards and yml which seems interesting.
Voice control (self-hosted) is something I’d like to eventually add as well.
Taking all the above into account, what would be the most suitable way to migrate?
What did I figure out so far?
Install openhabian, which I have. works
I would create things via the UI, as well as groups.
Remove groups from the .items files and keep them as text files.
I would keep rules in text file if this is a good idea. (but can’t argue pro or against it)… and fix any code incompatibilities.
And then expect all would work.
I can see three options:
- migrate quick and dirty; keep mostly text files and sort out rules.
- do one better by creating things, groups via UI
- build all new in OH3 (I reckon I die before I finish); so not really an option, unless there is some quick import thingy.
What is the “doing head in” part?
When I read the concepts, these make sense; but when I want to apply these I get lost. Point, equipment, model, semantics, …
Any hints appreciated.