@apella12: A file is indeed not needed anymore (as of OH3 already). The persistence configuration in the GUI is sufficient, the connection is not the issue.
Understood, I will test it like that. What surprises me though is that the system wanted to store data before any persist configuration was done. More than that, even before any connect information was provided (see the log entry in my previous post from 2023-08-30 22:58:10). It was right after the clean system setup of OH4 and after configuring the according things and items. Persistence addons installed but not configured yet.
It seems that with the below configuration, the system is behaving in a stable matter and as envisioned.
Still wonder what the âdefaultStrategiesâ does? Without having any items in the configurations part, the persistence model stayed silent and did not log anything.
Now with the items in the configuration, it uses the according strategies, which renders the âdefaultStrategiesâ further down quite useless or am I missing something?
Since itâs all asynchronous and event driven Iâm not sure there is much of another alternative. The event bus doesnât know if the persistence is configured or not, it just knows that a certain Item event occurred and the JDBC add-on cares about those events.
The JDBC add-on probably doesnât know the difference between not configured and incorrectly configured when it processes an event also so I think the behavior here is absolutely appropriate.
They were never really all that useful in the first place and are not even mentioned in the docs any more. They were just a way to save a few characters of typing. Youâs still have to define the Items but if you donât supply any strategy the defaultStrategy is applied.
Right, because youâve overridden the default add-on behaviors with your custom one and your custom one didnât identify any Items to persist so it didnât persist anything.