You mean in the detail of a thing with the list of channels in PaperUI? It’s an advanced channel, and will be shown when clicking Show More. But I’m guessing you already tried that?
Damn it - you’re right.
I knew that once, but that’s what’s happening, when you don’t use PaperUI for a long time
Thanks for pointing me into the right direction!
Unfortunately since a few versions openhab is getting more and more unstable for me: Startups are sometimes randomly failing (the Webinterface is loading forever and bindings aren’t loaded after a few hours), bindings stop to work or don’t load/startup properly (execute binding for example needs a bundle:restart at least once) and not even to mention the loading of rules without the underlying system being ready (which causes all kinds of weird errors, delaying the loading gets around it though). I haven’t seen anything suspicious in the logs though, so that’s making it hard to post issues on all of these.
Are you sure there is not something network or permission related causing issues? NFS can be tricky at times.
I would shy away from having rootfs network mounted unless absolutely necessary as a temporary workaround until a permanent solution is deployed.
This is a way better solution than SD cards and is a lot more reliable. If there would be network issues there would be “NFS Server x.x.x.x not responding, still trying” in dmesg, but it isn’t. There is also no permission issue as I have openhab running as root as its a dedicated device just for openhab.
I might need to mention that my installation is quite big with more than 600 items, loading those also takes a while and I think that is a contributing factor to my rule issues (which is still no excuse that the fundamental underlying environment isn’t setup when rules are executed and it then never recovers from that situation).
I meant NFS mount permission issues since the filesystem is on a different server. I was a UNIX systems admin for years using NFS but not for a root filesystem.
I know, but this filesystem was setup from the client itself and that wouldn’t explain why it starts working after a bundle:restart and why the startup fails and after a service restart it succeeds. Also as root is mapped to root by NFS there shouldn’t be any issues. Also this started to appear with the recent builds, this setup was working fine for more than 3 years (if not more) before that, and on a different hardware another 4 years before (starting with openhab1 back then).
However, I’ll try to copy all my configs over and try to run it on a virtual machine, but giving it limited CPU power to come close to the real setup, just to rule this one out.
What is missing? The warning message on installation specifically states cpu load is no longer available.
I just installed M3 last night and a quick check looks good.
Which MQTT binding? Some people still prefer the v1 binding.
CPU load is no longer in the binding according to the warning when installed. I gather that a change in an upstream library removed that.
MQTT v1 is also available in the current OH. I do not use MQTT though