forum

Interview failed for all instances of my thermostat (RTCOA CT100) except instance 0, curious why I found following sequence in the log file:

[2015-04-09 21:27:49.510] [D] [zway] SENDING (cb 0xbc): ( 01 0D 00 13 02 06 60 0D 00 01 31 04 05 BC 05 )

Where the portion '60 0D 00 01' represent MultiChannel Encapsulate command for instance 1, and the portion '31 04' - SensorMultiLevel Get command. The problem here that correct sequence of MultiChannel Encapsulate command should be: '60 06 01', where bytes are: command class, command, instance.

It would be nice if this issue will be fixed.
Thank you.

'60 0D 00 01' is for MultiChannel version 2/3, '60 06 01' is for version 1.
If the device reports incorrect version of the command class, it is an issue with device itself, not with the software.

Obviously problems do concentrate on a forum like this. That being said, I am getting nervous about the sheer number of 'bad' devices that are reported on this forum.

Thank you, pofs. It explains my situation. The device reports 3rd version of MultiChannel command class. Is it possible to force the software to use specific command class version? My device is: http://pepper1.net/zwavedb/device/289. Actual versions I'm getting from the device:
BASIC (0x20) version 1
CLOCK (0x81) version 1
INDICATOR (0x87) version 1
MANUFACTURER_SPECIFIC (0x72) version 1
SENSOR_MULTILEVEL (0x31) version 2
THERMOSTAT_MODE (0x40) version 2
THERMOSTAT_OPERATING_STATE (0x42) version 2
THERMOSTAT_FAN_MODE (0x44) version 1
THERMOSTAT_FAN_STATE (0x45) version 1
THERMOSTAT_SETPOINT (0x43) version 2
VERSION (0x86) version 1
CONFIGURATION (0x70) version 1
BATTERY (0x80) version 1
ASSOCIATION (0x85) version 1
MULTI_INSTANCE (0x60) version 3

You may change it by calling But I'm not sure if it resolves the issue with your device.

Also try to re-interview Version command class and see what actually comes. There's a logic inside MultiChannel that "upgrades" its version when sees a new style command from device, even if it previously reported as v1. Could be something wrong there, but it is unlikely.

Thank you, after I changed the version to 1 the software was able to complete the interview.