Since in the past I always had troubles and hours of work fixing my installation after an update I would like to ask if this would be the correct workflow on a synology running the openhab docker image. I am on 2.5.0 and would like upgrade to latest stable (2.5.3?) to see if some of my websocket errors are solved.
My things are created by paperui only.
Used addons are defined in \conf\services\addons.cfg (package is set to minimal) same as other services like mail, pushover, etc.
Items are defined in \conf\items\demo.items
My workflow to update the docker image would be:
- Stop running the openhab container
- Delete openhab.log in userdata
- Delete tmp and cache folder under userdata
- Delete openhab container or should I just delete content of the openhab container?
- Delete the openhab/openhab:latest image
- Download/register openhab/openhab:latest image
- Configure the downloaded image by mapping userdata, addons and conf folder to my lokal folders and network settings to use my local network settings
- Start the image and pray
Does this look like a correct approach or is there more to consider e.g. deleting like org.ops4j.pax.logging.cfg to ensure I get the latest intended loglevels?
Do I have to consider some extra steps for addons which need configuration so I don’t have to configure them again after an update like pushover action, amazon echo control, harmony hub, homematic, hue, mail, netatmo, openhab cloud connector, rrd4j persistence.
Thanks for any hints where I could finetune the docker update process