If, like me, you’re stuck with “invalid” addresses due to having an older system with a MyHomeServer1 installed, it is possible to get yourself back up and running in the short term by reverting just the OpenWebNet bundle of your openhab installation. This won’t fix things longer term, but at least it buys some breathing space for the problems to be worked out.
Important note: if you added any new OpenWebNet things of the newly supported types (i.e. light groups, etc), remove those before following the steps below!
If you have the openhab-cli tool installed, run the command bundle:list. Look for the number in the first column that matches your OpenWebNet addon. For me, it looked like this:
304 │ Active │ 80 │ 4.3.5 │ openHAB Add-ons :: Bundles :: OpenWebNet (BTicino/Legrand) Binding
Using the number from above, you can then run bundle:upgrade to switch to using the version of the addon that was distributed with openhab 4.1 (the built jar files are kept for a while):
bundle:upgrade <<your number here>> https://openhab.jfrog.io/artifactory/libs-release/org/openhab/addons/bundles/org.openhab.binding.openwebnet/4.1.3/org.openhab.binding.openwebnet-4.1.3.jar
Running bundle:list again (maybe after giving openhab a moment to finish restarting the “new” addon) should show you running the 4.1.3 version:
304 │ Active │ 80 │ 4.1.3 │ openHAB Add-ons :: Bundles :: OpenWebNet (BTicino/Legrand) Binding
This works with my system that is running openhab 4.4 flawlessly, but obviously isn’t officially supported in the same way as running a addon version that matches your openhab version.