PoltoS wrote:The device just have a broken firmware. Having Version inside channels for example is just bad (means not allowed). The device announce it but do not answer, so interview will never finish
It may well be that I'm misunderstanding the Z-Wave spec, but Chapter 3.52 Version Command Class, version 1 in the Z-Wave Command Class Specification, N-Z
In a Multi Channel device, the Version Command Class MUST be supported by the Root Device, while the Version Command Class SHOULD NOT be supported by individual End Points.
There may be cases where a given Command Class is not implemented by the Root Device of a Multi Channel device. However, the Root Device MUST respond to Version requests for any Command Class implemented by the Multi Channel device; also in cases where the actual Command Class is only provided by an End Point.
The terms MUST and SHOULD NOT are described in the top of the document (Chapter 2.3) to correspond to the definitions in IETF RFC 2119
, which defines SHOULD NOT like this:
4. SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
So it appears to me that Fibaro may well be involved in some bad practice here, but having Version CCs inside channels does not seem to be illegal according to the spec. As I said, I might be mistaken, but if so it would be great if you could elaborate and point to the relevant part of the spec.