I am running Openhabian on an RPi having updated from 2.5. Actually I am running two Openhab installations side by side because I have had issues and a number of my systems are mission-critical to a happy wife!
One particular problem I am having is my old 2.5 setup mostly used .items files. My heating system has 23 radiator valves and thermostats each with several endpoints, set temperature, valve state, battery level, mode etc etc. I can set them up fine using a .items file with the addition of the modern metadata to link them to the new semantic model so I have House (UI) → Downstairs (UI) → Living room (UI) → Radiator (file - Equipment group) → Set temperature (file - Point).
All that works… until it doesn’t. Every so often, the living room just forgets that the equipment lives there. The thermostats etc still appear, just under the root of the model instead of in the room. The Living_room_radiator item has a clear (Living_room) parent group in the .items file and each underlying point item is a member of the Living_room_radiator equipment group. Living_room is set up as a location in the semantic model using the UI. The Living _room_radiator is an equipment group defined in the .items file.
I forget now how I do it but with a little fiddling about restarting Openhab it will correct itself without me making any adjustments to the .items file, so it is not the file that is at fault. Just reloading the items file doesn’t however fix things.
I know there are warnings that items defined in files and UI based items don’t necesarily play nicely but Openhab 3 has been around for a while now. Is this something that is fixable? I really don’t want to have to create the best part of 200 items through the UI (a laborious process) and moreover if/when I change my configuration as my setup improves, modifying many items in the same way with a bit of copying and pasting in the files is a lot easier than making changes through the UI.
Or are there workarounds that can make the UI more palatable that I’m missing?