The file should be placed in usr/share/openhab2/addons.
Before adding the file I recommend making a backup. If you’ve never backed up OH, an easy way is to use openhab-cli.
The command is sudo openhab-cli backup or sudo openhab-cli backup --full if you prefer the bigger file (The smaller file should work just as well). The backup location is var/lib/openhab2/backups and you will want to move that file from the OH server to another device/PC (you can use something like Filezilla).
If the backup is ever needed, start with a fresh install of OH, then place the backup file into var/lib/openhab2/backups. Next use sudo systemctl stop openhab2 to stop the running OH service, then sudo openhab-cli restore /var/lib/openhab2/backups/your_backup_files_name.zip to restore and lastly sudo systemctl start openhab2
The Metoblue binding may work fine without needing to upgrade OH from 2.4 to 2.5 but if you still have issues then I would consider giving OH 2.5 a chance and with a backup you can easily go back to 2.4.
@H102 thanks for your patience
i will try it tonight.
i have done the configuration in the Paper UI - when saved should there not be a *.cfg file at the end?
i have done a things, items and added to the sitemap but no cfg file created for the basic information.
A file that ends with .cfg ( and located at etc/openhab2/services/) is something that’s configured for a specific binding. Take the mqtt binding for example, if you have not installed the mqtt binding, then you will not have a mqtt.cfg file located at ect/openhab2/services. OH automatically creates this file when a binding gets installed so creating a .cfg manually should not be needed.
If you’ve done all configuration via PaperUI then you shouldn’t need to worry about .cfg files as OH will handle this for you. If doing a binding configuration using files, not PaperUI, is when the .cfg is used.
I’m not the best at explaining things (reason for all the examples in previous replies) so hope the above explanation makes some sense. Here’s a snapshot using VScode for creating/editing OH files.
Notice the zigbee.items near the top and alexa.things at the bottom that’s part of my Items/Things files that I (not OH via PaperUI) created. In the middle, you can see the services file that holds all the OH service/bindings configuration files.
Good catch, finding that each item needed a unique name. This is true for all OH items, not just for this binding. Guess that’s what happens when I copy and paste to much. I edited the post above so if anyone else is having issues they won’t make the same mistake.
If you have everything configured via PaperUI and it works then no need to add anything extra. The .cfg file is automatically created by OH and you shouldn’t need to manually create this file.