I did a basic setup of a zwave USAB stick with one Devolo temperature and humidity sensor yesterday. I am running openHAB 2.2.0-SNAPSHOT in a docker container on my Synology.
After a nightly reboot the controller gets back online but the sensor stays offline until I set it manually into inclusion mode. Once done it goes quickly online.
There are two reasons why I cannot configure it through Paper UI:
As I am running a docker container the configuration is not persistent when done through GUI and I prefer to have it all in the things configuration file to understand whats happening.
When I tried to configure the sensor detected as zwave thing through Paper UI for test purposes, I found that it does not update but the browser receives a small, black notification box in the bottom right showing a “HTTP 500: Server Error” and the properties get not updated …
Hence I prefer setting this via config file but do not know how?
thank you for you quick reply. I kindly appreciate your attention.
Ok, understood. I am suspecting that the configuration done via Paper UI ist stored somewhere in the userdata directory tree and when I mount this from the outside of the container then this configuration should be stored persistently as well …
But then I have the issue that when updating the configuration the HTTP 500 Server Error appears in the Paper UI?
Or do you have an idea how I can force the sensor to go online when openHAB boots up?
Yes, it’s stored in the json database folder. However, if you are using things files to configure the thing, then you can’t use PaperUI to configure that thing - the system doesn’t allow it.
I dont know the docker container, but I would have expected it to map out to an external folder for the userdata - otherwise many things probably won’t work. My guess is that your problem is simply that you can’t configure things in a text file, and also then try and configure them in the UI.
You can manually wake it by pressing a button, but really you need to configure the wakeup period. This should be done automatically by the binding when the device is first initialised, so in general you shouldn’t need to change it unless the default time is somehow ‘wrong’.
However, do you really mean “Online” (ie is the device showing offline)? It should always be online after a restart - but it will also show that it’s initialising until after the device has woken up following a binding restart. If it’s offline, then maybe there’s another problem?
I get this status info in the karaf console after the restart:
openhab> smarthome:things list
zwave:serial_zstick:abcd1234 (Type=Bridge, Status=ONLINE, Label=zwave_usbstick, Bridge=null)
zwave:device:abcd1234:node2 (Type=Thing, Status=OFFLINE: Node not found in Z-Wave network, Label=WZ_TEMP_HUMI, Bridge=zwave:serial_zstick:abcd1234)
Then I started the inclusion on the device and after some seconds it was ONLINE.
So even when the node2 is ONLINE, the Paper UI update fails …
found a corresponding entry in openhab.log:
13:40:04.976 [ERROR] [est.core.internal.thing.ThingResource] - Exception during HTTP PUT request for update config at 'things/zwave:device:abcd1234:node2/config' for thing 'zwave:device:abcd1234:node2': null
I removed the Zwave.things and items file and reconfigured Z-wave USB Controller and the Devolo device via Paper UI but I got still the same HTTP 500 Error with the same PUT error in the Google Chrome console log.