I recently migrated from file based configuration to a UI based configuration. I’ve been enjoying a lot of the UI benefits but wanted to address one specific downside, it’s not easy to manage items, things or rules in bulk (cleanup work in tags, labels). Also modelling the semantics requires a lot of clicking in the UI.
Therefor I’ve created an Excel file that talks to the Openhab API to get a list of items, things and rules. I’ve included a bit of vba to allow changing some of the fields in the spreadsheet and make them change in Openhab as well.
Tags (as a comma seperated list)
GroupNames (as a comma seperated list)
It’s not possible to delete objects with the file. Maybe I’ll implement that later but for now I don’t like the thought of accidently cleaning up a bit to much
I wanted to share my file with the community but at the same time advise caution in using it. Even though I have tested and used it on my installation, I might have missed something important for your installation. As always, take a backup of your configuration.
You can find the file here:
Download the file, open it and accept the security warning:
Works great! It help me verify consistent naming and appropriate tags of each of the almost 1000
items. Having all items, including groups, alphabetically in a single column makes it easy to refer back and forth until you get it right. Take a look at the sample pdf here. t.pdf (398.2 KB)
I did have to bypass a number of security warnings and enable “public access” for each data query.
Configuration development for creating Excel documents is much harder than working with the UI. The hardest part is to learn algorithms and understand how it works. I wonder, what are data transformation techniques? Then I decided to take an excel course to understand the data movement system within this eco-system. You can develop an electronic reporting (ER) format configuration that has an ER format component. I didn’t need that, but I couldn’t work with the documents further without basic knowledge. So basic programming and basic knowledge are necessary for future file integration.