Paper UI Control stays empty

Yes, you’re right, my mistake. In PaperUI Control there are items, not things. And at the top of the page these items are seperated by two sub-menu-tabs “mqtt” and “other”. At least it was this way last time it worked :-\

No. Since I started with mqtt it said there are validation issues. But the items appeared anyway and I could switch the items. Now nothing appears anymore.

No, see my answer to @rossko57
The Tabs are your location (@ somewhere) definitions. Other means there is no location defined.

This is correct. But: it worked a few hours ago. And the mqqt things are bound to items:

Switch itmStecker01 “Stecker01 [MAP(hideState.map):%s]” (Zwischenstecker) {channel=“mqtt:topic:Stecker01:switch”}
Number itmStecker01_Spannung “Stecker01 Spannung [%.0f V]” (Zwischenstecker) {channel=“mqtt:topic:Stecker01:voltage”}
Number itmStecker01_Leistung “Stecker01 Verbrauch [%.0f W]” (Zwischenstecker,Strom) {channel=“mqtt:topic:Stecker01:power”}
String itmStecker01_Link “Stecker01 Verbindung [MAP(NWLink.map):%s]” (Zwischenstecker, Funkempfang) {channel=“mqtt:topic:Stecker01:Link”}

The whole control page does not appear anymore. The other items (e.g. homematic) are gone, too.

Do you not think that could be a little clue as to why your MQTT Things do not behave as expected?
This is the error message that was denied.

2 Likes

Still: Your thing definitions are incorrect, that’s what your earlier posted log does show as an error.

I changed the mqtt.things file to a short form and changed the definition in a way that no issues are reported anymore.
It didn’t help.

But I found out, that the things seem to be rendered fine, but there must be a problem with the items.
E.g. VSCode shows all things, but the item section renders until eternity and shows nothing.

So I again did a sudo openhab-cli clean-chache and restarted.

The items and things appeared in VSCode again, but all items were not assigned to a group. The items group appeared, but had no items in them.
The openhab.log showed many errors about unknown items for REST value assignments.
The IO-Error did not appear.
After I let the system com to rest for a few moments I rebooted again.
After this boot everything was back to the beginning: no items under paperUI-Control page.
VSCode shows things but no items.

So my conclusion is, there went something wrong with the “internal item database”.
I already reduced myitems.items to a few items.
But that had no effect.

How can I do some kind of “rebuild item database from scratch”?

Is it possible, that maybe an update to 2.5.4 yesterday can be the problem?

You may need to restart OH a few times for everything to start working correctly. Takes me 2-3 restart when upgrading. Just make sure to watch the logs so you know when OH has fully started between each restart.

sudo systemctl restart openhab2

After 7 restarts and waiting each time for 20 min until the logs calmed down to normal event routine I must say: no luck. The items still do not appear in VSCode nor in PaperUI.

Given what has gone before …
Are your Items defined in xxx.items files?
Do you see any messages about loading these files in your openhab.log? May we see them too?

Thank you very much for your patience and support!
Yes, all items are defined by myitems.items. There was no item defined via the openhab GUIs.

This is what’s in openhab.log after sudo systemctl restart openhab2

2020-05-08 21:01:11.248 [INFO ] [openhab.ui.paper.internal.PaperUIApp] - Stopped Paper UI 2020-05-08 21:01:11.327 [INFO ] [panel.internal.HABPanelDashboardTile] - Stopped HABPanel 2020-05-08 21:01:11.386 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Stopped HABmin servlet 2020-05-08 21:01:11.455 [INFO ] [assic.internal.servlet.WebAppServlet] - Stopped Classic UI 2020-05-08 21:01:11.580 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI 2020-05-08 21:01:21.644 [INFO ] [.dashboard.internal.DashboardService] - Stopped Dashboard 2020-05-08 21:01:42.382 [ERROR] [ersey.server.ServerRuntime$Responder] - An I/O error has occurred while writing a response message entity to the container output stream. [.. rest of IO Error Message removed by wbuh to keep it readable..] 2020-05-08 21:01:54.491 [ERROR] [e.internal.engine.RuleTriggerManager] - Error while starting the scheduler service: The Scheduler cannot be restarted after shutdown() has been called. 2020-05-08 21:02:18.737 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'Europe/Berlin'. 2020-05-08 21:02:18.779 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Location set to 'xx.xxxxx,xxxxxx.xxxxxx'. 2020-05-08 21:02:18.784 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Locale set to 'de_DE'. 2020-05-08 21:02:18.786 [INFO ] [.core.internal.i18n.I18nProviderImpl] - Measurement system set to 'SIUnits'. 2020-05-08 21:02:28.277 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'myItems.items' 2020-05-08 21:02:29.942 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rrd4j.persist' 2020-05-08 21:02:30.004 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'influxdb.persist' 2020-05-08 21:02:31.167 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'default.sitemap' 2020-05-08 21:02:31.843 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'openweathermap.things' 2020-05-08 21:02:31.878 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'mythings.things' 2020-05-08 21:02:48.794 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'holiday.script' 2020-05-08 21:02:50.598 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'wasserzaehler.rules' 2020-05-08 21:02:51.066 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'LichtUmkleide.rules' 2020-05-08 21:02:54.639 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'funkempfang.rules' 2020-05-08 21:02:58.427 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'Verschluss.rules' 2020-05-08 21:02:59.779 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'ventilator.rules' 2020-05-08 21:03:04.155 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'batteriemeldungen.rules' 2020-05-08 21:03:05.068 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'fernbedienungen.rules' 2020-05-08 21:03:08.291 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rollos.rules' 2020-05-08 21:03:11.175 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'aussenbeleuchtungAutomatik.rules' 2020-05-08 21:03:13.540 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'aussenbeleuchtung.rules' 2020-05-08 21:03:14.423 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'wwz.rules' 2020-05-08 21:03:18.172 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'temperatursalden.rules' 2020-05-08 21:03:19.864 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'helligkeit.rules' 2020-05-08 21:03:21.331 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'regensensor.rules' 2020-05-08 21:03:21.529 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'holiday.rules' 2020-05-08 21:03:21.964 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'LichtSchlafzimmer.rules' 2020-05-08 21:03:22.626 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'rollosAutomatik.rules' 2020-05-08 21:03:24.826 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'tasterSchlafen.rules' 2020-05-08 21:03:25.492 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'sprinkler.rules' 2020-05-08 21:03:26.976 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'sabotage.rules' 2020-05-08 21:03:29.756 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007 2020-05-08 21:03:33.598 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.178.202:8080 2020-05-08 21:03:33.602 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.178.202:8443 2020-05-08 21:03:39.820 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'WIRED' on gateway 'c76327ef' not available, disabling support 2020-05-08 21:03:39.826 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'HMIP' on gateway 'c76327ef' not available, disabling support 2020-05-08 21:03:39.831 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'CUXD' on gateway 'c76327ef' not available, disabling support 2020-05-08 21:03:39.840 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'GROUP' on gateway 'c76327ef' not available, disabling support 2020-05-08 21:03:39.966 [INFO ] [ommunicator.AbstractHomematicGateway] - HmGatewayInfo[id=HOMEGEAR,type=Homegear,firmware=0.7.45-3101,address=VBC7495691,rf=true,wired=false,hmip=false,cuxd=false,group=false] 2020-05-08 21:03:43.882 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'setInterface2.php' contains invalid characters, new Datapoint name 'setInterface2_php' 2020-05-08 21:03:43.885 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'listDevices.php' contains invalid characters, new Datapoint name 'listDevices_php' 2020-05-08 21:03:43.888 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'HM-XMLRPC-Client/Client.php' contains invalid characters, new Datapoint name 'HM-XMLRPC-Client_Client_php' 2020-05-08 21:03:43.890 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'setInterface.php' contains invalid characters, new Datapoint name 'setInterface_php' 2020-05-08 21:03:43.892 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'BackupHomegear.sh' contains invalid characters, new Datapoint name 'BackupHomegear_sh' 2020-05-08 21:03:43.894 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Connect.php' contains invalid characters, new Datapoint name 'Connect_php' 2020-05-08 21:03:43.896 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'RestoreHomegear.sh' contains invalid characters, new Datapoint name 'RestoreHomegear_sh' 2020-05-08 21:03:43.898 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Test.php' contains invalid characters, new Datapoint name 'Test_php' 2020-05-08 21:03:43.900 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'GetID.php' contains invalid characters, new Datapoint name 'GetID_php' 2020-05-08 21:03:43.902 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'ReadMe.txt' contains invalid characters, new Datapoint name 'ReadMe_txt' 2020-05-08 21:03:43.911 [INFO ] [rnal.type.HomematicTypeGeneratorImpl] - Multiple firmware versions for device type 'HM-LC-Sw1-Pl-2' found (1.C, 2.4, 1.9). Make sure, all devices of the same type have the same firmware version, otherwise you MAY have channel and/or datapoint errors in the logfile 2020-05-08 21:03:43.913 [INFO ] [rnal.type.HomematicTypeGeneratorImpl] - Multiple firmware versions for device type 'HM-ES-PMSw1-Pl' found (2.5, 1.6). Make sure, all devices of the same type have the same firmware version, otherwise you MAY have channel and/or datapoint errors in the logfile 2020-05-08 21:03:43.915 [INFO ] [rnal.type.HomematicTypeGeneratorImpl] - Multiple firmware versions for device type 'HM-LC-Bl1PBU-FM' found (2.1, 2.B, 2.2, 2.3). Make sure, all devices of the same type have the same firmware version, otherwise you MAY have channel and/or datapoint errors in the logfile 2020-05-08 21:03:43.917 [INFO ] [rnal.type.HomematicTypeGeneratorImpl] - Multiple firmware versions for device type 'HM-Sec-RHS' found (2.0, 2.1, 2.4). Make sure, all devices of the same type have the same firmware version, otherwise you MAY have channel and/or datapoint errors in the logfile 2020-05-08 21:03:43.918 [INFO ] [rnal.type.HomematicTypeGeneratorImpl] - Multiple firmware versions for device type 'HM-LC-Sw4-DR' found (1.C, 2.4, 1.9). Make sure, all devices of the same type have the same firmware version, otherwise you MAY have channel and/or datapoint errors in the logfile 2020-05-08 21:03:43.920 [INFO ] [rnal.type.HomematicTypeGeneratorImpl] - Multiple firmware versions for device type 'HM-LC-Sw2-FM' found (1.C, 2.8, 1.9). Make sure, all devices of the same type have the same firmware version, otherwise you MAY have channel and/or datapoint errors in the logfile 2020-05-08 21:03:53.591 [INFO ] [o.internal.handler.AstroThingHandler] - Scheduled Positional job astro:moon:home every 60 seconds 2020-05-08 21:03:53.839 [INFO ] [o.internal.handler.AstroThingHandler] - Scheduled Positional job astro:moon:home every 60 seconds 2020-05-08 21:04:08.137 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'openweathermap:uvindex:api:local' to inbox. 2020-05-08 21:04:08.145 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'openweathermap:weather-and-forecast:api:local' to inbox. 2020-05-08 21:04:11.016 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin 2020-05-08 21:04:11.322 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel 2020-05-08 21:04:11.560 [INFO ] [openhab.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui 2020-05-08 21:04:18.342 [WARN ] [rm.AbstractFileTransformationService] - Could not transform '1.0' with the file 'szene_aussenbel.map' : Target value not found in map for '1.0' 2020-05-08 21:04:18.410 [ERROR] [ersey.server.ServerRuntime$Responder] - An I/O error has occurred while writing a response message entity to the container output stream. [.. rest of IO Error Message removed by wbuh to keep it readable..] 2020-05-08 21:04:35.559 [INFO ] [rthome.model.script.ventilator.rules] - Ventilatorautomatik initialisiert 2020-05-08 21:04:39.226 [INFO ] [rthome.model.script.Verschluss.rules] - Verschlussdaten OG aktualisiert (offen: 0, gekippt: 0, geschlossen: 3, unklar: 0) 2020-05-08 21:04:39.229 [INFO ] [.smarthome.model.script.rollos.rules] - Initialisiert und normalisiert

Maybe this is better to read:
There seem to be no issues with loading myitems.items.

Is it an idea to change some kind of log-level to find out why the items are not loaded?

Yup, agreed.

Do you have REST API interactive “docs”? I’d try interrogating an Item from your items file to see what that says about it.
In fact you can do it anyway -
http://yourOpenhabHostorIP:8080/rest/items/yourItemName

I’m suspecting your Items exist and PaperUI is messing up. Or maybe its the links messed up, not the Items, after Things disaster.

Yes, I have. In fact I have a NodeRed instance communicating with Openhab all the time. It still works without problems.
I can do a REST call like
http://192.168.178.202:8080/rest/items/itmLicht_Flur/state
and it returns “OFF”.

What’s not working:
http://192.168.178.202:8080/rest/items
This returns
grafik

But I’m not shure if it’s intended to be used this way when you have a larger number of items.
On the other side: calling http://192.168.178.202:8080/rest/things works flawless!

The (end of) the raw data of the items request is
grafik

To put it in a nutshell: what I know at this moment

  • paperUI works, but the control tab remains empty
  • VSCode gets things from openhab, but no items / the items tab remains empty
  • there is a recurring java error as long as a browser or VSCode tries to access openhab (the items in openhab?)
  • openhab2 is running, the rules are executed, values are updated, persistance works, the basicUI works
  • communication via REST API works
  • items get updated if values are changed by homematic, NodeRed or openhab rules
  • sudo openhab-cli clean-chache cleans the cache (sarcasm: unbelievable!) but does not help (even after multiple restarts sigh)
  • uninstall and reinstall of paperUI via Habmin did no change at all
  • all my items are defined in myitems.items, there were no items defined or linked via paperUI
  • there are no mqtt things defined in my system to exclude this source of an error at the moment (I’m pretty shure now, they played no role at the moment I found this error)
  • reducing the number of items to only one item did not help
  • there was an update of openhab from 2.5.3 to 2.5.4 between last time I checked paperUI and now

It seems to me, that the service that is maintaining the items is some kind of broken. But I do not know how to fix it?

Conclusion: I need help!

Good investigation.

Inability to list all Items from REST API seems to be the key symptom.
That will mess up list based functions in PaperUI, VSCode, etc.

I recall years ago some having trouble with a great many Items due to the transfer timing out or something. It got fixed, but there remains the possibility that you have a bad setting in jersey or something, that just cuts it short.

Seems more likely there is something invalid in openHABs JSONDB though. (Yes, that is still the primary source even if you use xxx.items files)
Did you note if it always fails at the same point in the listing, for a clue?
FDK_Wohnen_TV_Garten_Error looks like a suspect at first glance.

Else I think you’d stop OH, copy the Items JSONDB and run it through a validator. It could still have corrupt OH-upsetting content even if valid JSON structure, but again you might get a clue.

If you really define all from xxx.files, I think it will be possible to bin the Items part of JSONDB complete, but will defer to advice on that. @rlkoshak ?

This is what I suspected!
I gave it a try again to reduce my myitems.items file to only one item to find out what’s happening.
openhab.log said the myitems.items was refreshed.
And afterward:

So there is definitly something in the dark (db) that does not belong there!

The point it fails depends on the number of items. I added a few new items and the position changed.

Yes, if you only use .items files you can delete the org.eclipse.smarthome.items.Item.json and org.eclipse.smarthome.core.thing.link.ItemChannelLink.json. Technically, if you’ve never used PaperUI to create Items or link them to Channel than neither of these files should exist in the first place of if they exist they would contain just [ ] as the file contents. Just make sure to stop openHAB first before deleting the files.

Definitely get the link file too. Sometimes an Item get’s removed but the link remains which confuses OH, leaving the Item in a zombie state, deleted but still in the list.

As time passes by…
At least I got to the point to delete the json files
grafik

When I reduce my myitems.items file to only one, only this one appears. The obsolete items are gone. So far, so good. Thank’s to you guys for the hint.

But the error with rendering / reading the items via REST API still happens sigh:
grafik

Any ideas how to find out, what’s going wrong?

Do you use any Scale Transformation on any of your items? I had exactly same behaviour after upgrading to 2.5.6 with an item exceeding the range of what was defined inside scale.map and had NaN defined for this.

See my issue: https://github.com/openhab/openhab-addons/issues/8011

What I’m missing at your issue: https://github.com/openhab/openhab-addons/issues/8123 is the full stacktrace of the exception in log. You only posted the top level Exception but there should be more interesting Root Exceptions with prefix “Caused by” at this stack trace. Can you please add this one to your issue as well, so I can do further investigation.

Thanks
Johannes

1 Like

Yes! You found it!
I’m so thankful for your support.
I had only one(!) scale for one of my 552 items. And abvioulsy this item broke it all.

The item was a simple calculated number
Number sysVar_Helligkeit "Helligkeit [SCALE(helligkeit.scale):%s]" (Umwelt, Systemzustand)

With
NaN=unbekannt
[0…33]=dunkel
[34…50]=dämmrig
[51…255]=hell

Now I have to find out, what’s the value that kicks the system out of operation / range.

Again: Big THANK YOU!

As you asked for the complete error message:

2020-07-14 17:46:03.157 [ERROR] [ersey.server.ServerRuntime$Responder] - An I/O error has occurred while writing a response message entity to the container output stream.
org.glassfish.jersey.server.internal.process.MappableException: java.lang.NullPointerException
	at org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:92) ~[?:?]
	at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:162) ~[bundleFile:?]
	at org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1130) ~[bundleFile:?]
	at org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:711) [bundleFile:?]
	at org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:444) [bundleFile:?]
	at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:434) [bundleFile:?]
	at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:329) [bundleFile:?]
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) [bundleFile:?]
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) [bundleFile:?]
	at org.glassfish.jersey.internal.Errors.process(Errors.java:315) [bundleFile:?]
	at org.glassfish.jersey.internal.Errors.process(Errors.java:297) [bundleFile:?]
	at org.glassfish.jersey.internal.Errors.process(Errors.java:267) [bundleFile:?]
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) [bundleFile:?]
	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) [bundleFile:?]
	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) [bundleFile:?]
	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) [bundleFile:?]
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) [bundleFile:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) [bundleFile:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) [bundleFile:?]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) [bundleFile:?]
	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) [bundleFile:?]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:852) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:544) [bundleFile:9.4.20.v20190813]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) [bundleFile:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:536) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1581) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1307) [bundleFile:9.4.20.v20190813]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) [bundleFile:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:482) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1549) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1204) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [bundleFile:9.4.20.v20190813]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) [bundleFile:?]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.Server.handle(Server.java:494) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:374) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:268) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:367) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:782) [bundleFile:9.4.20.v20190813]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:918) [bundleFile:9.4.20.v20190813]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]
Caused by: java.lang.NullPointerException
	at org.openhab.transform.scale.internal.ScaleTransformationService.lambda$0(ScaleTransformationService.java:132) ~[?:?]
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) ~[?:1.8.0_181]
	at java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1812) ~[?:1.8.0_181]
	at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) ~[?:1.8.0_181]
	at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) ~[?:1.8.0_181]
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) ~[?:1.8.0_181]
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) ~[?:1.8.0_181]
	at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152) ~[?:1.8.0_181]
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0_181]
	at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464) ~[?:1.8.0_181]
	at org.openhab.transform.scale.internal.ScaleTransformationService.getScaleResult(ScaleTransformationService.java:132) ~[?:?]
	at org.openhab.transform.scale.internal.ScaleTransformationService.formatResult(ScaleTransformationService.java:126) ~[?:?]
	at org.openhab.transform.scale.internal.ScaleTransformationService.internalTransform(ScaleTransformationService.java:105) ~[?:?]
	at org.openhab.transform.scale.internal.ScaleTransformationService.internalTransform(ScaleTransformationService.java:1) ~[?:?]
	at org.eclipse.smarthome.core.transform.AbstractFileTransformationService.transform(AbstractFileTransformationService.java:138) ~[?:?]
	at org.eclipse.smarthome.core.transform.TransformationHelper.transform(TransformationHelper.java:125) ~[?:?]
	at org.eclipse.smarthome.core.transform.TransformationHelper.transform(TransformationHelper.java:100) ~[?:?]
	at org.eclipse.smarthome.io.rest.core.item.EnrichedItemDTOMapper.considerTransformation(EnrichedItemDTOMapper.java:124) ~[?:?]
	at org.eclipse.smarthome.io.rest.core.item.EnrichedItemDTOMapper.map(EnrichedItemDTOMapper.java:67) ~[?:?]
	at org.eclipse.smarthome.io.rest.core.item.EnrichedItemDTOMapper.map(EnrichedItemDTOMapper.java:61) ~[?:?]
	at org.eclipse.smarthome.io.rest.core.internal.item.ItemResource.lambda$0(ItemResource.java:230) ~[?:?]
	at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0_181]
	at java.util.HashMap$KeySpliterator.tryAdvance(HashMap.java:1574) ~[?:1.8.0_181]
	at java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(StreamSpliterators.java:294) ~[?:1.8.0_181]
	at java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(StreamSpliterators.java:206) ~[?:1.8.0_181]
	at java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(StreamSpliterators.java:169) ~[?:1.8.0_181]
	at java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:300) ~[?:1.8.0_181]
	at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681) ~[?:1.8.0_181]
	at org.eclipse.smarthome.io.rest.Stream2JSONInputStream.fillBuffer(Stream2JSONInputStream.java:93) ~[?:?]
	at org.eclipse.smarthome.io.rest.Stream2JSONInputStream.read(Stream2JSONInputStream.java:69) ~[?:?]
	at java.io.InputStream.read(InputStream.java:179) ~[?:1.8.0_181]
	at java.io.InputStream.read(InputStream.java:101) ~[?:1.8.0_181]
	at org.glassfish.jersey.message.internal.ReaderWriter.writeTo(ReaderWriter.java:115) ~[bundleFile:?]
	at org.glassfish.jersey.message.internal.AbstractMessageReaderWriterProvider.writeTo(AbstractMessageReaderWriterProvider.java:79) ~[bundleFile:?]
	at org.glassfish.jersey.message.internal.InputStreamProvider.writeTo(InputStreamProvider.java:105) ~[bundleFile:?]
	at org.glassfish.jersey.message.internal.InputStreamProvider.writeTo(InputStreamProvider.java:60) ~[bundleFile:?]
	at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.invokeWriteTo(WriterInterceptorExecutor.java:265) ~[bundleFile:?]
	at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.aroundWriteTo(WriterInterceptorExecutor.java:250) ~[bundleFile:?]
	at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:162) ~[bundleFile:?]
	at org.glassfish.jersey.server.internal.JsonWithPaddingInterceptor.aroundWriteTo(JsonWithPaddingInterceptor.java:106) ~[?:?]
	at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:162) ~[bundleFile:?]
	at org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:86) ~[?:?]
	... 53 more

I’m glad I could help you. I marked your issue on github as duplicate of my issue. And I started a pull request to fix this issues: