Page 1 of 1

SceneActivation not registered

Posted: 12 May 2014 00:54
by Squar0L
Hello,

Just upgraded to 1.7RC and adjusting my scripts. I found that the scene activation command (2B) is no longer accepted by Razberry - please see the trace below. It worked on 1.4.1. The device #5 is a Leviton scene controller. Is it a defect or something else?

Code: Select all

[2014-05-11 21:34:52.893] RECEIVED: ( 01 15 00 49 84 05 0F 02 01 00 85 2D 7C 77 82 73 86 72 91 EF 2B 2C F1 )
[2014-05-11 21:34:52.894] SENT ACK
[2014-05-11 21:34:52.895] Node info received: 5
[2014-05-11 21:34:52.896] SETDATA devices.5.data.basicType = 2 (0x00000002)
[2014-05-11 21:34:52.897] SETDATA devices.5.data.genericType = 1 (0x00000001)
[2014-05-11 21:34:52.898] SETDATA devices.5.data.specificType = 0 (0x00000000)
[2014-05-11 21:34:52.902] SETDATA devices.5.data.deviceTypeString = ""
[2014-05-11 21:34:52.904] SETDATA devices.5.data.nodeInfoFrame = byte[12]
  ( 85 2D 7C 77 82 73 86 72 91 EF 2B 2C )
[2014-05-11 21:34:52.905] SETDATA devices.5.data.lastReceived = 0 (0x00000000)
[2014-05-11 21:34:53.290] RECEIVED: ( 01 0A 00 04 08 05 04 2B 01 02 00 D0 )
[2014-05-11 21:34:53.291] SENT ACK
[2014-05-11 21:34:53.292] Got frame from device 5 to controller, but command class 0x2b for device is not registered - instantiating it as not supported

Re: SceneActivation not registered

Posted: 12 May 2014 03:35
by pofs
If you're sure it was supported before, try re-including your device.
Probably NIF information was corrupted somehow, and device doesn't know it supports this CC.

Also, there's nothing wrong for such a command class to be not supported. Device just controls it (sends SceneActivation Set commands), but doesn't support it itself (cannot receive and handle SceneActivation Set). It might be perfectly fine, if anything else (besides this line) works okay.

Re: SceneActivation not registered

Posted: 12 May 2014 20:00
by PoltoS
@psof is right, this CC was never supported by Leviton. If you look in the NIF you posted (85 2D 7C 77 82 73 86 72 91 EF 2B 2C F1) 2B is behnd EF - this means it is controlled by the device. So, Z-Way creates them on the fly. After first time Z-Way got such a packet, it will memorize this.

It is a good idea to create them on NIF reception - will add it as a feature request.