OH2 First Alert Smoke Detector

Add-ons Bindings
1

I can’t get this to include with OH2.
I’ve followed the instructions and it never works
I go to things - search for things
Remove battery cover hold button push battery in release button

no idea but it never shows up in OH

ave:eco_dwzwave2_00_000
2016-11-30 18:58:39.323 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
2016-11-30 18:58:39.323 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:false.
2016-11-30 18:58:39.324 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-11-30 18:58:39.324 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-11-30 18:58:39.326 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 81 01 30
2016-11-30 18:58:39.328 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 81 01 30
2016-11-30 18:58:39.338 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A 01 01 00 00 B2
2016-11-30 18:58:39.344 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-11-30 18:58:39.346 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 4A 01 01 00 00 B2
2016-11-30 18:58:39.347 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 4A 01 01 00 00 B2
2016-11-30 18:58:39.348 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00
2016-11-30 18:58:39.351 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Learn ready.
2016-11-30 18:58:39.351 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInclusionEvent
2016-11-30 18:58:39.354 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=81 01
2016-11-30 18:58:39.355 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00
2016-11-30 18:58:39.356 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false transaction complete!
2016-11-30 18:58:39.356 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2016-11-30 18:58:39.357 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 25ms/4817ms.
2016-11-30 18:59:38.783 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2016-11-30 19:00:02.495 [ERROR] [o.myopenhab.internal.MyOpenHABClient] - Socket.IO error: io.socket.engineio.client.EngineIOException: websocket error
2016-11-30 19:00:02.504 [INFO ] [o.myopenhab.internal.MyOpenHABClient] - Disconnected from my.openHAB service (UUID = xxxxx, base URL = http://localhost:8080)
2016-11-30 19:00:19.530 [INFO ] [o.myopenhab.internal.MyOpenHABClient] - Connected to my.openHAB service (UUID = xxxxx, base URL = http://localhost:8080)
2016-11-30 19:01:02.834 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2016-11-30 19:01:35.616 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2016-11-30 19:04:15.204 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!

2

When you slide the battery tray back in, are you holding the button until it beeps?

3

Yes I am

4

Okay, try removing it first then. Some devices like to be un-included before they can be included. Set the controller to remove instead of include, and perform the same process on the device, then try to include again. Hopefully that will do the trick.

Good luck!

5

Naa doesn’t work i see this in the log:
Using the build from 2 nights ago

2016-12-06 16:58:58.972 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2016-12-06 16:59:31.768 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 0: Polling aborted due to exception
java.lang.NullPointerException
at org.openhab.binding.zwave.handler.ZWaveThingHandler$1.run(ZWaveThingHandler.java:360)[181:org.openhab.binding.zwave:2.0.0.201612051634]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_91]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_91]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_91]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_91]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_91]

6

ok i got it to pair…24th times a charm?

How long does it take to recognize it?
Is there a way to wake this so it shows up as a smoke alarm?

Thanks

7

It’s been Unknown for about 24 hours now…no idea how to get it to recognize it.

8

I give up on this thing in OH2…i start up OZW…i wake it…the controller recognizes what this is…shows config and versions, etc…i start up OH2…the node is still unknown…no idea why.

9

2016-12-07 18:35:59.168 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Initialising Thing Node…
2016-12-07 18:35:59.193 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Initialising Thing Node…
2016-12-07 18:36:09.326 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Initialising Thing Node…
2016-12-07 18:36:09.350 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Initialising Thing Node…
2016-12-07 18:36:13.377 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2016-12-07 18:36:13.481 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2016-12-07 18:36:16.561 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising Thing Node…
2016-12-07 18:36:16.584 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising Thing Node…
2016-12-07 18:37:22.504 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2016-12-07 18:37:22.616 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2016-12-07 18:38:11.367 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2016-12-07 18:38:11.415 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2016-12-07 18:38:11.419 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:controller:node38’ to inbox.
2016-12-07 18:39:27.022 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
2016-12-07 18:39:27.120 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0

10

2016-12-07 19:01:15.790 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Checking zwave:yale_yrd220_00_000
2016-12-07 19:01:15.791 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Checking zwave:yale_yrd220_00_000
2016-12-07 19:01:15.792 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Checking zwave:yale_yrd220_00_000
2016-12-07 19:01:15.792 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Checking zwave:devolo_mt02648_00_000
2016-12-07 19:01:15.794 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2016-12-07 19:01:15.797 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:controller:node38’ to inbox.
2016-12-07 19:01:15.798 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
2016-12-07 19:01:15.800 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:false.
2016-12-07 19:01:15.801 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-12-07 19:01:15.801 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-12-07 19:01:15.803 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 81 01 30
2016-12-07 19:01:15.804 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 81 01 30
2016-12-07 19:01:16.579 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A 01 01 00 00 B2
2016-12-07 19:01:16.581 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-12-07 19:01:16.583 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 4A 01 01 00 00 B2
2016-12-07 19:01:16.584 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 4A 01 01 00 00 B2
2016-12-07 19:01:16.585 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00
2016-12-07 19:01:16.586 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Learn ready.
2016-12-07 19:01:16.586 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInclusionEvent
2016-12-07 19:01:16.589 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=81 01
2016-12-07 19:01:16.590 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00
2016-12-07 19:01:16.591 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false transaction complete!
2016-12-07 19:01:16.592 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2016-12-07 19:01:16.594 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 21ms/2568ms.
2016-12-07 19:01:40.023 [DEBUG] [ve.internal.protocol.ZWaveController] - Stopping inclusion timer.
2016-12-07 19:01:40.024 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
2016-12-07 19:01:40.025 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-12-07 19:01:40.025 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-12-07 19:01:40.026 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller end inclusion
2016-12-07 19:01:40.027 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 01 B4
2016-12-07 19:01:40.028 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 01 B4
2016-12-07 19:01:40.086 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A 01 06 26 00 93
2016-12-07 19:01:40.087 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-12-07 19:01:40.089 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 4A 01 06 26 00 93
2016-12-07 19:01:40.089 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 4A 01 06 26 00 93
2016-12-07 19:01:40.090 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 06 26 00
2016-12-07 19:01:40.091 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Done.
2016-12-07 19:01:40.091 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInclusionEvent
2016-12-07 19:01:40.093 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device already known.
2016-12-07 19:01:40.095 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 38: Newly included node already initialising at DETAILS
2016-12-07 19:01:40.096 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=05 01
2016-12-07 19:01:40.098 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 06 26 00
2016-12-07 19:01:40.099 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false transaction complete!
2016-12-07 19:01:40.099 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2016-12-07 19:01:40.100 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 72ms/2568ms.

11

Man, this crap gets deep.
I excluded it and included it with the zstick manually.
I deleted Node 38 from paper ui(unknown in inbox)
search for devices now i got unknown node 38 and node 39
holy help please

12

Node 38 is likely in a odd state now where you will have to delete it from the controller. It seems it did not exclude cleanly. You can also try to remove the node38.xml file in userdata/zwave and restart, but I am guessing it is still in the controller. This won’t hurt anything, but is annoying. You have to get the controller to come to the realization that it is failed, and this is tougher to do on a battery device.

Once included, it should eventually wake up, but this is a special device that does weird things to prolong the battery life. It does not accept changing the wake up time from the controller, and instead has a fixed wake that appears to be more than a day. This mean that once you include it, if you just let it sit, it may not ever fully appear. It will be marked as dead before proper initialization. To get around this, you can wake it up. It took me about 3 times of waking it before it initialized. You wake it by doing the same process you did to include it with the battery door. Just don’t put the controller in include or exclude mode. Just keep doing it until it initializes. Once you do it one time, it is not so bad, but that first one was a learning experience.

13

I ended up getting a new one. I have no problems including it. So, chalk it up to a manufacturers defect on this one.