Back to file-based openhab configurations in the age of AI?

[thefathefa]

Hello everyone,

Interesting discussion and interesting activities on-going !

I’m trying to understand if there is a way to enjoy the benefits of versioning .items, .rules etc… files (e.g. with GitHub) while being in the Main UI world?

Jsondb deltas do not seem to be very easy to read…

So what would be the solution? Generate the YAML version of jsondb, and use that to snapshot the config in GitHub?

I’m pretty sure many of you are already doing this (versioning of config, in a readable way, with deltas between x and y versions etc…) one way or the other and I am interested in understanding what you are doing…

I like what @andre showed in this topic:

OpenClaw to manage OpenHAB config

Yeah am doing that too and it works well. The only real difference here is you can relatively safely make config changes in a pretty hands off manner. I’ve written about it here and shared the skill I’m using here in case others would like to try it out too. My Openclaw and Openhab run on different VMs, so there’s some mucking about creating a restricted user on your openhab server, but after that it’s pretty neat being able to adjust your openhab configs from a telegram chat (while knowing yo…

But a key point there is that he is using file based config.
Even if I would let AI use REST API to update the config (and so possibly would not be able to use the approval solution he has put in place), I would like to be able to a posteriori track what AI did, in a user friendly way…

Am I making sense?