Nope. I cleared the cache, did shutdowns of the machine, restarts of openHAB, and reloads of the binding but nothing happens. What seems strange to me (after having a look at the source code) is that although I set DEBUG log level for the binding, none of the related error/warning messages show up (e.g. that the whitelist file could not be read).
Also tried both linux and dos EOL format, restarted openhab, cleared the cache but nothing helps. Even after went back back to version 2.5.1 nothing works. For now I’ve deactivated the things and hoping for a better documentation how to specify commands in the whiltelist…
I’m running openhab on a Raspberry Pi 3 with DietPi, manualley installed in /opt/openhab2
I am using OpenHAB 2.5.1 and have this issue and nothing helps so far. How do I downgrade the binding to 2.5.1 as well?
What is the general way to a) downgrade a binding and b) where do I find the corresponding .jar file? I looked at ci.openhab.org but the CI server there didn’t really show me any artifacts I could use.
I have no idea what the reason for inability of reading the file could be. Permissions are set to OpenHAB user and the usual 755 and there’s nothing special about it. When I set permissions to 777 the warning is gone, but the non-executability info still stays.
I saw the same warning message in the log whenever I copied my amended whitelist file over during my setup of it while OH was running. Even with this warning message the entered whitelist commands did work however.
During a fresh startup of OH this warning didn’t appear for me.
It would be nice, if the maintainers could add some debug logging to the process of reading and processing the whitelist, so one can understand what’s going on. In my case, the above warning only means that the whitelist is obviously in the right place but I have no idea what prevents it from being properly processed.
Are you sure it’s not being processed properly, since I got the same warning message, but the newly entered whitelist commands were exectuted correctly in spite of the warning - which means the modified whitelist file was recognised and processed.
Have you tried any of the commands after seeing this log warning?
You can uninstall the original through Paper UI, I think. Then you take the 2.5.1 exec binding jar and drop it in the addons directory. After that you should be able to configure it through PaperUI, I think. I haven’t had the chance to try any of this yet…