I wonder, is it possible (and desirable) to have multiple items configuration files?
F ex a
gives the idea that OH2 only works with mapDB, yet I have been working with a file for items, sitemap etc…
Am I wrong, should I stop working with the files and somehow do the configuration in a different way?
so far I like the files as I can have them in a source control system to see (and revert) my changes.
yet I do worry about speed.
What is the preferred way to go:
one feel per type
as many files as I want, that makes no different in speed and configuration use.
I used a file per technology in my OH1 setup, but if you want to let people control their room, then maybe split per room. Or, split per technology for the stuff you don’t want the kids messing with, and then per room for the stuff they can control…
It’s a case of whatever works best for you and your system
I have split the items in technology, too, but to be honest, I have a few items that don’t fit in these files, because they are bound to more than one binding. For items, it couldn’t care less, because any changing of any items file will cause a complete jump to uninitialized items (yes, all items!).
In question of rules, this is different, each rule file will only get a “system started” trigger, if the file itself is touched, this is important to know for splitting rule files. As a second point, you have to keep in mind, that vars and vals outside of rules are per file, but please avoid the same vars in different files, this will confuse openHAB.