Well, here is what I found out:
I upated through apt-get and had to switch the mechanism to the new repository at bintray first. Before I had:
195 | Active | 80 | 2.0.0.201701071314 | ZWave Binding
And after the update/upgrade:
195 | Active | 80 | 2.0.0.201701071702 | ZWave Binding
So only a slighty newer build. But gladly your changes were implemented in the newer build (at least I think so).
Initialisation went well and I also got the xml files soon afterwards. I got a wakeup timestamp in Habmin and no DYNAMIC VALUES message.
Nevertheless I got a minor issue: During the re-addition of one of the two sensors (node 8), I got the following log message:
2017-01-09 18:01:59.706 [ERROR] [curityCommandClassWithInitialization] - NODE 8: SECURITY_ERROR Invalid state! Secure inclusion has not completed and we are not in inclusion mode. Aborting
2017-01-09 18:02:00.095 [ERROR] [curityCommandClassWithInitialization] - NODE 8: SECURITY_ERROR Invalid state! Secure inclusion has not completed and we are not in inclusion mode. Aborting
2017-01-09 18:02:01.082 [ERROR] [curityCommandClassWithInitialization] - NODE 8: SECURITY_ERROR Invalid state! Secure inclusion has not completed and we are not in inclusion mode. Aborting
This is somehow irritating, because I deactivated secure inclusion for the controller some weeks ago. And the messages didn’t appear for the other sensor (node 13). Does the sensor kind of remembers the initially inclusion method and maybe at that time secure inclusion was still active? Is this something to be concerned about?