Alarm CC & sensor tampering

[Vincentoo]

Hello,

Is the Alarm CC now fully supported?
With my sensor device (SM 103 Everspring door sensor), that supports Alarm CC to indicate tampering, it gives this:
[2013-11-26 15:37:42.250] RECEIVED: ( 01 0A 00 04 00 02 04 71 05 01 11 93 )
[2013-11-26 15:37:42.250] SENT ACK
[2013-11-26 15:37:42.251] Got frame from device 2 to controller, but command class 0x71 for device is not registered - instantiating it as not supported
[2013-11-26 15:37:42.251] SETDATA devices.2.instances.0.commandClasses.113.data = Empty
[2013-11-26 15:37:42.251] SETDATA devices.2.instances.0.commandClasses.113.data.version = Empty
[2013-11-26 15:37:42.251] SETDATA devices.2.instances.0.commandClasses.113.data.version = 1 (0x00000001)
[2013-11-26 15:37:42.252] SETDATA devices.2.instances.0.commandClasses.113.data.security = Empty
[2013-11-26 15:37:42.252] SETDATA devices.2.instances.0.commandClasses.113.data.security = False
[2013-11-26 15:37:42.252] SETDATA devices.2.instances.0.commandClasses.113.data.interviewDone = Empty
[2013-11-26 15:37:42.252] SETDATA devices.2.instances.0.commandClasses.113.data.interviewCounter = Empty
[2013-11-26 15:37:42.252] SETDATA devices.2.instances.0.commandClasses.113.data.interviewDone = False
[2013-11-26 15:37:42.252] SETDATA devices.2.instances.0.commandClasses.113.data.interviewCounter = 10 (0x0000000a)
[2013-11-26 15:37:42.252] SETDATA devices.2.instances.0.commandClasses.113.data.V1supported = Empty
[2013-11-26 15:37:42.253] SETDATA devices.2.instances.0.commandClasses.113.data.typeMask = Empty
[2013-11-26 15:37:42.253] SETDATA devices.2.instances.0.commandClasses.113.data.V1event = Empty
[2013-11-26 15:37:42.253] SETDATA devices.2.instances.0.commandClasses.113.data.V1event.type = Empty
[2013-11-26 15:37:42.253] SETDATA devices.2.instances.0.commandClasses.113.data.V1event.level = Empty
[2013-11-26 15:37:42.253] SETDATA devices.2.data.lastReceived = 0 (0x00000000)
[2013-11-26 15:37:42.254] SETDATA devices.2.instances.0.commandClasses.113.data.V1event.type = 1 (0x00000001)
[2013-11-26 15:37:42.254] SETDATA devices.2.instances.0.commandClasses.113.data.V1event.level = 17 (0x00000011)
[2013-11-26 15:37:42.254] SETDATA devices.2.instances.0.commandClasses.113.data.V1event = Empty

Using code (C), I seem to be unable to get a data holder on "V1event.level"...
What is wrong?

Regards,

V.

[Vincentoo]

Bump this old thread I posted just before the old forum went down
I would love to get an answer on that one...

[Vincentoo]

After some research, it seems that the Everspring SM103 does not report supporting the ALARM command class during the interview. The ZWave device database (http://www.pepper1.net/zwavedb/device/25) also indicates that. But still, the device supports the Alarm CC.
Is there a way to make sure ZWay is enabling full support for this command class and have the data model including it for this device?

[PoltoS]

It will have data created after first command arrived from the device. So, you can get it in C cathing this creation. Also we will add saving of "controlled" CCs, so it will survive restart.

[Vincentoo]

Is this something already working in one of the latest versions (e.g. 1.5.0-rc1)?
Just tried and:
- There is no Alarm CC data for my device after the device sent it in the UI.
- There is also no data in the data updates (when doing a POST on http://ip:8083/ZWaveAPI/Data/1393433863).
Or is it only working when working with the C API?

[PoltoS]

"Controlled" CCs and all non-interviewed features are not exposed to the outside (in /ZWaveAPI/Data/ and hence in the UI) and are not saved on the disc right now. But you can access them via /ZWaveAPI/Run/devices[n].instances[0].Alarm.data