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
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
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-chachecleans 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!