Hi @chris, if you search in the log for node 39 you see the warnings and what happens if I try to move the blinds. You see as well my rules trying to recover for blinds not moving (my qubinos have a firmware bug, so I need to program around this), but nothing works. Typically this error shows:
2017-06-30 23:38:37.062 [INFO ] [.eclipse.smarthome.model.script.FILE] - --> CLOSE slates for Blinds_FF_LivingRoom_Side1_Lam
2017-06-30 23:38:37.070 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 39: Command received zwave:device:b11c1630:node39:switch_binary2 --> OFF
2017-06-30 23:38:37.074 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 39: No command converter set for command zwave:device:b11c1630:node39:switch_binary2 type OnOffType
2017-06-30 23:38:37.804 [INFO ] [.eclipse.smarthome.model.script.FILE] - --> OPEN slates for Blinds_FF_LivingRoom_Side1_Lam
2017-06-30 23:38:37.810 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 39: Command received zwave:device:b11c1630:node39:switch_binary2 --> ON
2017-06-30 23:38:37.811 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 39: No command converter set for command zwave:device:b11c1630:node39:switch_binary2 type OnOffType
I can’t see any problem in the startup phase, it seems to setup the corresponding command classes. something broken in my installation ?
I don’t really see any problem. I suspect the most likely issue is that you’ve done something wrong with creating the binding that you’ve created, so I’ll update the binding properly tomorrow and you can try that.
I am as well seeing frequent fails of nodes no longer communicating, which I didn’t have before. I have different nodes getting marked as failed in the controller. The system with by modified 2.1.0-snapshot.jar seems to be very unstable.
Let me know when I can wget the new 2.1.0-snapshot.jar, or will I be able to pull it via the paper UI ?
So what I did was not correct with the JAR, it seems. Thanks for the new version, this is very good.
I still have failed nodes, I leave it running for some time and see if I can recover them without a rest. Problem is that it is not the same nodes failing all the time, it is different ones… hmmm… could this connected to the security updates ?
Well it seems now we have problems with the ZMNHCD with version S5. There are no 1st and 2nd endpoints in the binding now, the version seems 4 in the XML. I do not use additional endpoints it is only rollersutter, not blinds. However i cannot get values from the optional temperature sensors now. Using Zwave binding:
225 | Active | 80 | 2.2.0.201706290942 | ZWave Binding
And, habmin and paperui sees the module as version:
This is the same point that we are talking about - you are still running a version that has not yet had the fix - I will probably do an update tonight.
This binding hasn’t been changed. The one I changed was the development version.
226 | Active | 80 | 2.1.0.201706302351 | ZWave Binding
Endpoints are back.But now i have two problems:
As i see the database has 2 versions for ZMNHCD. Version up to 4.0, and version higher than 4.0. Although my modules are of version S5, habmin still sees them as “Version S1 for for version up to 4.0”.
Temperature sensor still not updating the value, they still insist on showing the same values as it was working some versions ago.
My devices are version S5, so i guess they should get the device database “All After 4.1”. In XML it says:
<version>4</version>
So i am not sure if openhab-habmin picks the correct database item.
Looking at the logs the device never sends the temperature. The values are coming from persistence. When i check out from domoticz software, it gets the values as expected. So i guess there’s nothing wrong with the devices.
You’re looking at the wrong information. What does HABmin or PaperUI say the version is.
Then you need to solve this problem first. I would guess that there’s a configuration value to set when the device sends the data? If the device isn’t sending the temperature, then the binding won’t display it. Polling should return the data as well of course, but without some data to look at I can’t do anything to help.
