It’s hard to answer that question. There are just some things that the UI and even the REST API makes a little awkward to do, mainly Item metadata. Therefore I think it might be just a tad premature to move Items to JSONDB. In my HestiaPi experience, there was no Item metadata to worry about so migration was not problem. And to be fair, Yannick has written an importer for Items already that is/will be part of the replacement for PaperUI, so I could manage Items in PaperUI, or more likely through the REST API directly in my case. But I’ve more than half a decade of legacy OH stuff to deal with and I’m not yet ready to move my Items to JSONDB.
I do know that some startup problems will go away when I do but I’m just not ready to make the move. Given that I’m not yet ready I don’t think it’s fair for me to recommend others do what I’m not willing to do.
And there are some drawbacks. It’s not as easy to search through, edit, copy and paste and that sort of stuff with JSONDB. You can’t really group or organize them in separate files or other logical organizations like you can do with separate files.
Already done. Jython Drop-in Replacement for Expire 1.x Binding. Though honestly, the simplification that comes with using Expire as Timers in Rules DSL simply doesn’t exist for Python. Put another way, it’s just as simple to define a Timer with it’s lambda in Python as it is to use Expire binding. So the link above is mainly intended as a bridge to use temporarily and not really intended to be something you would use forever, though that’s obviously an option.