Classic UI has stopped working

My classic UI has stopped working … this is what I get …


Problem accessing /classicui/app. Reason:

    Server Error

Caused by:

java.lang.NoSuchMethodError: org.eclipse.smarthome.ui.items.ItemUIRegistry.getChildren(Lorg/eclipse/smarthome/model/sitemap/Sitemap;)Lorg/eclipse/emf/common/util/EList;
	at org.eclipse.smarthome.ui.classic.internal.servlet.WebAppServlet.service(
	at org.eclipse.jetty.servlet.ServletHolder.handle(
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(
	at org.eclipse.jetty.servlet.ServletHandler.doScope(
	at org.eclipse.jetty.server.session.SessionHandler.doScope(
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
	at org.eclipse.jetty.server.Server.handle(
	at org.eclipse.jetty.server.HttpChannel.handle(
	at org.eclipse.jetty.server.HttpConnection.onFillable(
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
	at org.eclipse.jetty.util.thread.QueuedThreadPool$

I have tried removing classic UI using paper UI and re-added it… but no differens…
Help is appreciated!

Did you try:

  • To restart OpenHAB;
  • To undo a recent change you have made to your sitemap? Maybe there are syntax-errors in your whatever.sitemap that you need to look in to.

Tried restart … have also tried undoing last change…no difference…

My sitemaps do work in the android app! Its just when using Classic UI that I get this error …


I had similar problems; there is a new nightly available which seems to resolve my problems. Recommend to give it a try => #928.

ok! I will try that out… thanks

That actually worked! Thanks …

Cant understand why it suddenly broke in the first place though…

Hi I am facing the same issue. I assume there was a build for 2.1.0-snapshot-amd64, would it be possible to trigger a build for 2.1.0-snapshot-arm64 too?