Raspi3 Razby2 Fibaro Window/Door Switch and Popp Smoke Detector won't work

Setup, Configuration and Use Beginners
1

Hi there,
just started with a Raspi3 and Razby2, two Greenwave Powernodes, a Fibraro Window/Door Switch and a Popp Smoke Detector for my Home Automation. I was very happy to see, that everything was quite easy to install/configure when starting with z-way-Server, that was installed to test the Razberry. All devices were found instantly and worked fine from the first moment.

So I stopped the z-way-server, installed openhab 1.8.3 and got the two powernodes running quite easy. But now I am stuck with the Fibaro and Popp devices. Every time I start z-way-Server they are absolutely OK, but starting openhub I get some strange Messages after 5 nodes habe been found:

First, during startup (although there is no Node 255) I get:

2016-11-14 17:34:17.857 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-11-14 17:34:22.897 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-11-14 17:34:29.577 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-11-14 17:34:34.623 [WARN ] [WaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class = EnableSuc (0x52), type = Request (0x00), payload = 00 00
2016-11-14 17:34:39.690 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-11-14 17:34:46.087 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 1 attempts left!
2016-11-14 17:34:52.017 [ERROR] [WaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 0 attempts left!
2016-11-14 17:34:57.066 [WARN ] [WaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class = SetSucNodeID (0x54), type = Request (0x00), payload = 01 00 00 00 01

Then I get a first message from the smoke Detector:

2016-11-14 17:35:01.247 [INFO ] [runtime.busevents ] - S_Finn_Rauchmelder_Batterie state updated to 100
2016-11-14 17:35:01.299 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - No command class found for item = S_Finn_Rauchmelder, command class name = sensor_binary, using 0 refresh interval.
2016-11-14 17:35:01.301 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - No command class found for item = S_Finn_Rauchmelder, command class name = sensor_binary, using 0 refresh interval.
2016-11-14 17:35:01.304 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - No command class found for item = S_Finn_Rauchmelder_Sirene, command class name = switch_binary, using 0 refresh interval.
2016-11-14 17:35:01.306 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - No command class found for item = S_Finn_Rauchmelder_Sirene, command class name = switch_binary, using 0 refresh interval.

So the battery Status is obviously readm but openhab cannot handle the smoke detector itself.

I can send a command to start the siren:

2016-11-14 17:38:01.424 [INFO ] [runtime.busevents ] - S_Finn_Rauchmelder_Sirene received command ON

But it is not handled

2016-11-14 17:37:11.481 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: No command class found for item = S_Finn_Rauchmelder_Sirene. Class = switch_binary(SWITCH_BINARY), endpoint = 0. Ignoring command.

The Window/Door Switch keeps silent during Startup, but later reports:
2016-11-13 16:23:52.311 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 5: Unsupported command class SECURITY
2016-11-13 16:23:52.317 [ERROR] [ApplicationCommandMessageClass] - NODE 5: Unsupported command class SECURITY (0x98)

In my items-file I have the following entries for the devices:
Contact S_Finn_Rauchmelder “Rauchmelder Finn [%s]” (S_Finn) { zwave=“2:command=SENSOR_BINARY,respond_to_basic=true” }
Switch S_Finn_Rauchmelder_Sirene “Rauchmelder Finn Sirene” (S_Finn) { zwave=“2:command=switch_binary” }
Number S_Finn_Rauchmelder_Batterie “Rauchmelder Finn Batterie [%d %%]” (S_Finn) { zwave=“2:command=battery” }

Contact EG_Wohnzimmer_Terrassentuer “Terrassentür: [%s]” (EG_Wohnzimmer) { zwave=“5:command=SENSOR_BINARY,respond_to_basic=TRUE” }
Number EG_Wohnzimmer_Terrassentuer_Batterie “Terrassentür: Batterie [%s %%]” (EG_Wohnzimmer) { zwave=“5:command=BATTERY” }

Any ideas?

2

For the POPP Smoke I used in openHAB1:

Contact    POPP_Smoke_1_C    "Sensoralarm Smoke [%s]"    <fire>   { zwave="10:command=SENSOR_BINARY,sensor_type=2" }
Switch    POPP_Smoke_1_Sw    "Switch POPP Siren"    { zwave="10:command=switch_binary" }
Number    POPP_Smoke_1_Battery    "POPP Smoke: [%d %%]"   { zwave="10:command=BATTERY" }

Make sure the sensor is fully initialized (click the little black button on the rear once to send NIF’s) and use the latest zwave snapshot binding.

3

Hi, thank you very much for your assistance. But I tried out everything you wrote, but nothing changed. When clicking the button on the smoke detector I get an update on the battery status.

2016-11-15 13:38:55.113 [INFO ] [runtime.busevents ] - S_Finn_Rauchmelder_Batterie state updated to 100

But perhaps something else is interesting with the 1.9.0 z-wave binding:
2016-11-15 13:32:26.327 [ERROR] [CommandClassWithInitialization] - NODE org.openhab.binding.zwave.internal.protocol.ZWaveNode@bd16ca: Trying to perform secure operation but Network key is NOT set due to:
2016-11-15 13:32:26.381 [ERROR] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 5: Error instantiating command class 0x98
java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.7.0_101]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) ~[na:1.7.0_101]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[na:1.7.0_101]
at java.lang.reflect.Constructor.newInstance(Constructor.java:526) ~[na:1.7.0_101]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveCommandClass.getInstance(ZWaveCommandClass.java:247) [bundlefile:na]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveCommandClass.getInstance(ZWaveCommandClass.java:210) [bundlefile:na]
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.resolveZWaveCommandClass(ApplicationCommandMessageClass.java:156) [bundlefile:na]
at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:53) [bundlefile:na]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:231) [bundlefile:na]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:204) [bundlefile:na]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$6(ZWaveController.java:199) [bundlefile:na]
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1247) [bundlefile:na]
Caused by: java.lang.IllegalStateException: NODE 5: node wants to use security but key is not set
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveSecurityCommandClass.(ZWaveSecurityCommandClass.java:333) ~[bundlefile:na]
at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveSecurityCommandClassWithInitialization.(ZWaveSecurityCommandClassWithInitialization.java:77) ~[bundlefile:na]
… 12 common frames omitted
2016-11-15 13:32:26.401 [ERROR] [ApplicationCommandMessageClass] - NODE 5: Unsupported zwave command class SECURITY (0x98)

Node 5 is the Fibaro Window/Door Switch that cannot communicate because of a missing network key here. The Smoke Detector is also a device that displays in Z-Way-Server as a security device. Could there be a problem with the whole secure communication in mein Z-Wave Network?

BTW: Using Habadmin I recognized that the Popp smoke detector is called a garagedoor there???

With the new z-wave Binding I also get additional Infos for my powernodes like:
NODE 2: does not support SECURITY_REPORT, proceeding to next stage.

4

Solved, as far as the smoke detector was affected (have not tried the door/window Switch already) Sometimes the old “Have you tried switching it on and off again?” helps.

Although the device worked perfect under z-way-server I excluded and included it again in habadmin, and instantly it worked.

5

:slight_smile: