Maybe the Zwave device it’s self needs reset or a bit more time for everything to come back?
Possibly… Will shutdown it all once more and see.
@jr555se: Since openhab-cli clean-cache does not work with docker you may want to keep this command handy, as I had to dig a bit to find it.
sudo rm -rf /var/lib/openhab2/cache/* && sudo rm -rf /var/lib/openhab2/tmp/*
Very helpful to use anytime OH starts acting weird or you see strange logs. It’s my first step in troubleshooting and for my system it’s usually the only needed.
1 Like
If you still cannot control the devices I would delete one of them from OH then rediscover it. Maybe that is all that’s needed for control but I would test with just one and do the rest if it works.
1 Like
yeah, I seem to be able to control now. Takes long time though so I think the mesh needs a reset which will happen tonight.
So, to recap all that was needed was to remove the reference to the old rest-doc in the addons file “/home/openhab/userdata/config/org/openhab”
then clean the cache and tmp directories which for me is:
“/home/openhab/userdata/tmp/” and “/home/openhab/userdata/cache/”
Hoping noone else gets my issues but just in case… 
Thank you @H102 and @Bruce_Osborne my family is happy now when its up again. Looking fwd to use the new and updated rule engine.
//JR
1 Like
Just to add a little bit if info. When you start a new container, it checks to see if the version of OH running is different than the version indicated in userdata/etc/version.properties. If they differ, the script will back up userdata and perform a clear the cache automatically before stressing OH. For a normal upgrade, manually clearing the cache would be redundant. However, because if the REST API issue, a separate clear the cache was necessary to deal with that. But it’s not usually required.
1 Like
This would be the complete solution (for those using Docker) for others that do not want to read all post.