This page last changed on Aug 17, 2014 by amensing67.

i have bought a ebox and aeon Labs Stick 2 fot z-wave integration. Stick is successful integrated with a z-wave smoke detector. (zensys-tools)

but when I plugin into the ebox, i donĀ“t see any device in the professional designer. I have try to discover the device, but nothing happens.

Any idea where could be the problem.

Andreas

LOGS:
INFO 2014-08-17 18:32:04,505 (Z-Wave): Reader thread asked to start
INFO 2014-08-17 18:32:04,533 (Z-Wave): Writer thread asked to start
INFO 2014-08-17 18:32:04,539 (Z-Wave): Writer thread starting
DEBUG 2014-08-17 18:32:04,545 (Z-Wave): sending: 01 08 00 54 00 01 01 01 01 a3
DEBUG 2014-08-17 18:32:04,548 (Z-Wave): Message lock exists. Frame waiting: 01 03 00 02 fe
DEBUG 2014-08-17 18:32:04,551 (Z-Wave): received: 06 01 04 01 54 00 ae
DEBUG 2014-08-17 18:32:04,563 (Z-Wave): Controller registered as SUC/SIS
DEBUG 2014-08-17 18:32:04,599 (Z-Wave): sending: 06
DEBUG 2014-08-17 18:32:04,601 (Z-Wave): sending: 01 03 00 02 fe
DEBUG 2014-08-17 18:32:04,604 (Z-Wave): received: 06
DEBUG 2014-08-17 18:32:04,655 (Z-Wave): received: 01 25 01 02 05 08 1d 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 01 da
DEBUG 2014-08-17 18:32:04,656 (Z-Wave): sending: 06
DEBUG 2014-08-17 18:32:04,657 (Z-Wave): Node id: 1 discovered
DEBUG 2014-08-17 18:32:04,657 (Z-Wave): Node id: 5 discovered
DEBUG 2014-08-17 18:32:04,662 (Z-Wave): sending: 01 04 00 41 01 bb
DEBUG 2014-08-17 18:32:04,664 (Z-Wave): Message lock exists. Frame waiting: 01 04 00 41 05 bf
DEBUG 2014-08-17 18:32:04,670 (Z-Wave): received: 06 01 09 01 41 92 16 00 02 02 01 33
DEBUG 2014-08-17 18:32:04,715 (Z-Wave): sending: 06
DEBUG 2014-08-17 18:32:04,717 (Z-Wave): sending: 01 04 00 41 05 bf
DEBUG 2014-08-17 18:32:04,721 (Z-Wave): received: 06 01 09 01 41 52 9c 00 04 a1 07 da
DEBUG 2014-08-17 18:32:04,722 (Z-Wave): sending: 06
ERROR 2014-08-17 18:32:04,742 (Z-Wave): Could not create device class for node: 5
java.lang.InstantiationException
at sun.reflect.InstantiationExceptionConstructorAccessorImpl.newInstance(InstantiationExceptionConstructorAccessorImpl.java:48)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at org.openremote.controller.protocol.zwave.model.Controller.createDevice(Controller.java:147)
at org.openremote.controller.protocol.zwave.model.Controller.handleResponseMessage(Controller.java:96)
at org.openremote.controller.protocol.zwave.model.ZWaveNode.handleZWaveResponseEvent(ZWaveNode.java:159)
at org.openremote.controller.protocol.zwave.ZWaveGateway.fireZWaveResponseEvent(ZWaveGateway.java:93)
at org.openremote.controller.protocol.zwave.ZWaveGatewayRxtx$ZWaveReaderThread.run(ZWaveGatewayRxtx.java:288)

ERROR 2014-08-17 18:32:04,742 (Z-Wave): Could not create device class for node: 5

It seems that the current Z-Wave protocol implementation fails to create a device class for the Z-Wave smoke detector. Actually I don't know why this happens. It should create internally a binary sensor device class or a generic device class according to the generic Z-Wave device class type of the smoke detector.

Note that we are currently working on a complete rewrite of the Z-Wave protocol implementation (see aeotec 4 in 1 multi sensor).

Posted by rhitz at Aug 18, 2014 08:00
Document generated by Confluence on Jun 05, 2016 09:38