After 2.5 upgrade, saved habmin2 charts no longer load

Apps & Services HABmin
1

I updated to OH2.5 yesterday and noticed that habmin2 was throwing errors (%%KEY_NOT_FOUND%% on load). After some searching here and elsewhere I figured the easiest fix was to back up my habmin2 userdata and reinstall habmin2. This seemed to work in as much as I was able to create and save a new chart. However, when I reloaded the page (just a simple page refresh) I had the same %%KEY_NOT_FOUND%% error. I can’t see anything obvious in the server logs, and the console logs are equally unhelpful, but I may simply be looking in the wrong places.

Other than removing the mail action & rest docs from my addons.cfg I’ve made no changes - so persistence, etc. are all as they were under 2.4. Does this problem either ring any bells for anyone, or can anyone point me at debug actions that might help track it down?

Versions:

  • running on MacOS El Capitan (old machine, can’t run newer versions)
  • Java 1.8.0_121
  • mysql 5.7.15
  • HABmin splash screen says “Version: 2.0.0, 2019-12-15T18:44:50”
  • installed as a system service, but running via CLI right now while I try to debug

Cheers,
Waider.

2

Ok, so I’m getting a server error from http://server:8080/rest/habmin/charts

{
    "error": {
        "message": "org.openhab.ui.habmin.internal.services.chart.ChartListBean",
        "http-code": 500,
        "exception": {
            "class": "com.thoughtworks.xstream.mapper.CannotResolveClassException",
            "message": "org.openhab.ui.habmin.internal.services.chart.ChartListBean",
            "localized-message": "org.openhab.ui.habmin.internal.services.chart.ChartListBean"
        }
    }
}

Looking at the git logs for habmin2, it looks like it’s to all intents and purposes abandoned? The only updates in the last year or more have been administrative checkins to ensure basic compatibility with new versions.

3

I guess I was right about the “abandoned” status: https://github.com/openhab/openhab-webui/pull/154

I guess this is a “won’t fix” issue so I may as well close the topic.