Openhab 2 - "no matching features" error

I confess I’m getting a bit frustrated with the transition to openhab2.

It had been mostly working (except persistence), but with the last few days’ packages I’m getting a series of errors on startup:

2016-12-11 12:01:28.763 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-powermax': No matching features for openhab-binding-powermax/0.0.0
2016-12-11 12:01:28.764 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-weather': No matching features for openhab-binding-weather/0.0.0
2016-12-11 12:01:28.764 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed retrieving features: null
2016-12-11 12:01:28.865 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-powermax': No matching features for openhab-binding-powermax/0.0.0
2016-12-11 12:01:28.866 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-weather': No matching features for openhab-binding-weather/0.0.0
2016-12-11 12:01:34.930 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed retrieving features: null
2016-12-11 12:01:36.330 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed retrieving features: null
2016-12-11 12:01:37.511 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed retrieving features: null

Would it make sense to hold off on further attempts openhab2 for at least a few months, in the hope things become easier?

No! openHAB2 works fine and is pretty stable (I migrated two month ago and did not regret it).
BUT: there were several breaking changes in the last days, yours seems to be related to the change of id’s:

In short: if you have configured any 1.9 addons through addons.cfg, you need to change the id’s now with a suffix “1”, f.e. weather is now weather1 and so on …

As @sihui says, it is a good idea to subscribe to https://community.openhab.org/c/openhab-2/news-important-changes, so that you do not miss any important changes. I think most bigger refactorings are through now, it should be fairly safe to go to a recent OH2 now.

Many thanks for your help - that has indeed fixed it. As @kai suggests, I’ll follow the ‘important changes’ board going forward

Dan

1 Like