To answer my own question, I took the following steps to create a 2.5.6 jar for the wemo binding:
- Download the docker repository from https://github.com/openhab/openhab-docker.
- Copy the files from the folder 2.5.6/debian (3 files total, including a Dockerfile) to my server.
- ssh into the server and
cd
to the location of the copied files. -
docker build --tag openhab:2.5.6 .
to create a new image. - Create a new container using the new image (I did this with a stack within Portainer, but you can use whatever you would normally use). You’ll likely need to shut down any running OH container first to avoid a port conflict. As soon as the container is fully loaded you can stop it again.
- Navigate to the config folder for the new container and then to userdata\tmp\mvn\org\openhab\addons\bundles\org.openhab.binding.wemo\2.5.6-SNAPSHOT (this is Windows notation because I copied and pasted File Explorer via Samba).
- Grab the 2.5.6 jar file from there (there were two, I used the one with the specific date instead of the generic “SNAPSHOT” filename, but it looks like they might be identical.
- Start your real OH installation.
- Disable your 2.5.5 Wemo binding (I did this in my addons.cfg file, but do it wherever you added the Wemo binding in the first place, e.g., PaperUI).
- Place the 2.5.6 jar in the addons folder of your real OH installation.
It’s only been running for a couple minutes, so I’ll try to report back on whether the connection to my Wemo devices is more stable.