I just had a very friendly call with Aleš Humar from Qubino support. He said that all Qubino devices support reporting back manually changed states (e.g. switching/dimming via button input). If it is not working, then there is a problem with multichannel association with lifeline groups or association with lifeline group, depending on the product. He said that this normally should be set correctly during inclusion. In some cases/gateways, it may have to be set manually.
As said earlier, all association fields are blank on my setup. I tried to set them manually (see screenshot), but this does not seem to have any effect:
Looking at the logs of my ZMNHAD 1 Relay, I don’t see the previously reported errors that I am seeing in the logs for the ZMNHSD Din Dimmer. Instead, I am seeing these errors:
10:35:32.623 [WARN ] [ng.zwave.internal.protocol.ZWaveNode] - NODE 29: Unsupported multi instance command version: 0.
I am only seeing this error on one of my ZMNHAD Flush 1 relays, the other ZMNHAD’s don’t show such errors in the logs. Therefore I suppose this is not the root cause either.
After analyzing the complete log file which I posted earlier using Excel, I see that all of my Qubino devices are affected by the “Transaction not completed: node address inconsistent.” error:
- ZMNHAD Flush 1 relay
- ZMNHBD Flush 2 relays
- ZMNHCD Flush Shutter
- ZMNHSD DIN Rail Dimmer
The only other ZWave device I have, a Aeon Labs ZW100 MultiSensor 6, is not affected. It also does not have any problems with updates like the Qubinos. Interestingly, this is the only device I have which has “OpenHAB Controller” set in the field “Association Group 1” (not sure how that setting got there). I will be adding a Sensative Strip shortly, so I will have some more input in a few days.
In summary, I am pretty clueless atm regarding how to get status reporting to work on these Qubino devices with OH2. I have tried both inclusion via Controller (Aeon ZStick Gen5) and via Habmin, have included many devices so far, nothing makes a difference. None work as expected with regards to status reporting with OH2. My guess is that the problem has something to do with the association groups (like Aleš from Qubino says), but is not user fixable at this point, perhaps due to some specifics of the Qubino devices (multichannel?) which are not fully supported by the binding. I hope @chris will be able to bring some light into this.