Z-Wave.me KEYFOB2, 0x60 Command class

[dolpheen]

After including the device (App.Ver. 1.4 of keyfob, 2.0.1-rc16 RaZberry) there is the next message from the log

Code: Select all

[2015-03-04 20:37:25.875] [D] [zway] RECEIVED: ( 01 0D 00 04 00 0B 07 60 0D 00 01 20 01 FF 48 )
[2015-03-04 20:37:25.877] [D] [zway] SENT ACK
[2015-03-04 20:37:25.878] [I] [zway] Got frame from device 11 to controller, but command class 0x60 is not in NIF. Wrong packet?
[2015-03-04 20:37:25.879] [D] [zway] SETDATA devices.11.data.lastReceived = 0 (0x00000000)

I saw in some posts that the remote can handle the multiinstance command classes, Is something wrong with Firmware?
Does anyone use z-wave.me KEYFOB in their automation here?

[pofs]

That must be a result of recent changes, which assume MultiChannel is in NIF. But it appears to be not true for some devices, or it is only controlled and not supported.

RC17 changes this behavior a bit, so try to update. If KFOB has MultiChannel in NIF at all, it would work.

[dolpheen]

I tried several times to include/exclude and removed battery but no luck.
The NIF is always the same

Code: Select all

[2015-03-06 09:51:05.475] [D] [zway] SETDATA devices.16.data.nodeInfoFrame = byte[10]
[2015-03-06 09:51:05.477] [D] [zway]   ( 80 70 75 86 72 85 8E 2D 77 84 )

Also in ZDDX selected (488-0115-0100-0001-03-03-43-01-04.xml ) there is a record

Code: Select all

 <commandClass id="0060" version="3" controlled="true" inNIF="false"/>

I'll try the last release.

Update
Tried the last 2.0.1-rc18 the same problem with 0x60.

[pofs]

Okay, it seems there's a stupid rule somewhere in docs, which says that controlled MultiChannel may be not present in NIF. I think we'll need to rollback this change because of that, or either look into the xml file.
Anyway, it is only present since rc14 (so you may rollback to the previous one for now), and it will be fixed soon.

[dolpheen]

Thank you for the info.
I see handling in-NIF/not-in-NIF is a challenge
I'll wait an update.