DateTime Rule Trigger in OH3

[dathbe]

@rossko57

Not really, you have the right approach. Always more than one way to do things though.
How often are you editing this rule, exactly?
Presuming you’re editing other stuff really, can you extract it to a separate rule file that won’t get edited often? (You may need to take shared global variables into account here.)

I think this is the answer. I do have a separate rules file for all my pool rules, but I think separating those that have timers into their own rules files will mostly solve this because, as you suggest, I’m not editing THIS rule that often. I will have to consider global variables, but for the most part I store my globals as persistent items, so that shouldn’t be too hard.

@rossko57

What happens when you edit a Thing is pretty much dependent on the binding it belongs to. Some accept dynamic changes more gracefully than other. It is usually possible to restart only the affected binding, if needed.

Tell us more about ignoring Item edits.

I think this may have been an issue with trying to run an OH2 and OH3 container side-by-side. I just realized I couldn’t get to my OH3 karaf console to check logs (because both containers were listening on 8101). When I stop my OH2 container, the items and things files seem to reload as expected. Now on to figuring out how I can get my karaf consoles running side-by-side.

Edit: I answered my own question. I had found this post: OpenHAB3 Docker Test Instance on Synology , which explains how to change the karaf port. But when I did that it would not accept my karaf password. Somehow restarting everything fixed that, so it seems to be working for now.