forum

Posted: **14 Jan 2015 12:12**

[2015-01-14 07:03:34.818] [D] [zway] RECEIVED: ( 01 31 00 04 00 0D 2B 56 01 91 01 0F FF 04 02 2D 05 07 D0 02 05 08 28 1D 00 B4 00 B4 00 B4 00 B4 00 B4 00 B4 00 B4 00 B4 00 B4 00 B4 00 B4 00 B4 A0 E9 51 )
[2015-01-14 07:03:34.818] [D] [zway] SENT ACK
[2015-01-14 07:03:34.818] [D] [zway] SETDATA devices.13.data.lastReceived = 0 (0x00000000)
[2015-01-14 07:03:34.819] [I] [zway] Node 13:0 CC CRC16: Received command, but CC 0x91 isn't registered. Creating it as not supported
[2015-01-14 07:03:34.819] [E] [zway] Trying to create command for unknown CC 0x91
[2015-01-14 07:03:34.819] [W] [zway] Command Class 0x91 is not supported (requested for node 13:0)
[2015-01-14 07:03:34.819] [E] [zway] Error returned from _zway_cc_call_handler(zway, command, controller->id, 0, data[4], &data[5]): Bad arguments (-1)

What is CC 0x91 - some sort of manufacture specific stuff? Can I access this info from JSON-API somehow?

A guess is that this is the "black box" recording the device does.

Posted: **15 Jan 2015 03:04**

It is manufacturer proprietary command class.

It is not supported by z-way, so you cannot access it with JSON API.
We can add it, but it won't help you much, because the actual data format is unknown.

Posted: **18 Jan 2015 01:48**

I was hoping Fibaro could tell me about the format, but they don't give it out unless you're a "z-wave device developer".

I'll let you know if I get anything useful out of the data, then I might want it in the JSON API.

forum

0x91 from fibaro smoke detector

0x91 from fibaro smoke detector

Re: 0x91 from fibaro smoke detector

Re: 0x91 from fibaro smoke detector