[SOLVED] ZWave binding not working since openhab2-2.4.0-snapshot

Thanks for testing

Bummer. Can you post your logs with and without haveged?
Would like to see the results of the new jar with vs without haveged

The 1 to 2 second delay is strange. the only change I made was to 1 line of code that should only impact the init time. Logs would hel phere as well

What chipset do you have? I think I have a NUC out in the garage, just curious if it is a .comparable CPU. Maybe I would be able to reproduce the problem

Thanks for the suggestion!

But when I checked this morning the stick was initialized. Is it supposed to take hours to initialize it? :open_mouth:

No. Initialization of the stick normally is immediate.

I’ll do it in the next few days. Thx for your response. :slight_smile:

Hi @mhilbush , I just got the exact same issue after trying to switch from 2.3 to 2.4 snapshot using docker too, and I think I found why :

root@omv:/opt/openhab# cat /proc/sys/kernel/random/entropy_avail

There’s not enough entropy on my (hp micro)server or docker, causing the timeout and the stick not beeing initialized correctly.

To fix this, I just ran another container with haveged, which you might consider including directly in the openhab docker (not sure that’s possible without running privileged) :

docker run --privileged -d harbur/haveged

Once done, I got enough entropy and the stick got initialized (I had stopped the openhab docker before adding thehavged one) :

root@omv:/opt/openhab# cat /proc/sys/kernel/random/entropy_avail

Hoping this solves other’s issue…

1 Like