[2.3.0 snapshot 1250] ClassicUI essentially blank

Add-ons UIs
,
1

All it displays is this…

<root><part><destination mode="replace" zone="timeout" create="false"/><data/></part></root>

No errors. BasicUI displays properly, and 1247 displayed properly too. Clearing the sitemap to dsiplay a single item did not help. Is anyone else seeing this?

2

@Kai, I don’t see any recent changes here that would have caused this, so I must be looking in the wrong place. I’d open an issue, but I’m not sure where to create it. There was another thread that started too, so others are experiencing this.

3

I checked with #1251 windows and openHABianPi and have the same problem.
I think it’s a issue and the correct place for that is https://github.com/eclipse/smarthome/issues

4

I think you’re right. My ESH version shows as 0.10.0.201804051647, so the changes listed in Cloudbees must not show ESH updates. I’m looking through the recent commits right now to see if I can identify which change caused it.

5

I couldn’t find anything. There were some commits for BasicUI, but they didn’t seem to be related.

1 Like
6

I get this error

2018-04-06 23:22:54.455 [ERROR] [clipse.smarthome.io.transport.serial] - Component descriptor entry 'OSGI-INF/*.xml' not found
7

Do you get this error every time you go to ClassicUI? I ask because I don’t see how the two could be related.

8

I can confirm the issue and have created a fix. I hope this will be available in the openHAB distro by Sunday night.

1 Like
9

#1252 fixed the ClassicUI-problem.

I still get

2018-04-08 15:03:46.007 [INFO ] [er.internal.HomeBuilderDashboardTile] - Started Home Builder at /homebuilder
2018-04-08 15:03:47.955 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.178.3:8080
2018-04-08 15:03:47.978 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.178.3:8443
2018-04-08 15:04:19.271 [ERROR] [clipse.smarthome.io.transport.serial] - Component descriptor entry 'OSGI-INF/*.xml' not found
10

You can ignore that. Will be fixed soon as well, but it is completely unrelated (see here).