First Alert ZCOMBO Not Reporting

PeteC · April 16, 2020, 4:37pm

I have a First Alert Smoke/CO detector that is not reporting smoke detections. I introduced smoke into the detector and the alarm sounded but nothing was reported in the OpenHAB log file. The LogView below is filtered for node 20.
The entries from 20:08:41.385 through 21:02… were updates I did to the HABPanel. I have no idea what the entries at 8:45…were for.
At about 11:00 I introduced smoke and caused an audible alarm but nothing appeared in the openhab.log (I was watching it in real time).
At 11:06 I did a wake up by holding the Test button and removing then inserting the battery tray.
I’m not sure if the raw openhab.log file is important but I included it below also.
I am also suspicious that I haven’t set up my items correctly. The things page for node 20 shows 5 channels, four of which are shown to be “switch” but I don’t think that is right and likely beyond this present problem.

2020-04-16 11:02:58.611 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-04-16 11:02:58.614 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2020-04-16 11:02:58.616 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-04-16 11:02:58.618 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-04-16 11:02:58.621 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-04-16 11:06:24.196 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 49 84 14 0A 04 A1 00 20 80 70 85 71 72 86 49
2020-04-16 11:06:24.200 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationUpdate[73], type=Request[0], dest=20, 

callback=132, payload=84 14 0A 04 A1 00 20 80 70 85 71 72 86
2020-04-16 11:06:24.202 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationUpdate[73], type=Request[0], dest=20, callback=132, payload=84 14 0A 

04 A1 00 20 80 70 85 71 72 86
2020-04-16 11:06:24.204 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-04-16 11:06:24.206 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 0
2020-04-16 11:06:24.208 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: null
2020-04-16 11:06:24.210 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=ApplicationUpdate[73], type=Request[0], dest=20, callback=132, payload=84 14 0A 

04 A1 00 20 80 70 85 71 72 86
2020-04-16 11:06:24.212 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 20: Application update request. Node information received. Transaction null
2020-04-16 11:06:24.214 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Creating new instance of command class COMMAND_CLASS_BATTERY
2020-04-16 11:06:24.219 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Command class COMMAND_CLASS_BATTERY, endpoint 0 created
2020-04-16 11:06:24.221 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 20: Application update is adding command class COMMAND_CLASS_BATTERY.
2020-04-16 11:06:24.223 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: Adding command class COMMAND_CLASS_BATTERY to the list of supported command classes.
2020-04-16 11:06:24.225 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Creating new instance of command class COMMAND_CLASS_CONFIGURATION
2020-04-16 11:06:24.229 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Command class COMMAND_CLASS_CONFIGURATION, endpoint 0 created
2020-04-16 11:06:24.231 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 20: Application update is adding command class COMMAND_CLASS_CONFIGURATION.
2020-04-16 11:06:24.232 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: Adding command class COMMAND_CLASS_CONFIGURATION to the list of supported command classes.
2020-04-16 11:06:24.234 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Creating new instance of command class COMMAND_CLASS_ASSOCIATION
2020-04-16 11:06:24.238 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Command class COMMAND_CLASS_ASSOCIATION, endpoint 0 created
2020-04-16 11:06:24.240 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 20: Application update is adding command class COMMAND_CLASS_ASSOCIATION.
2020-04-16 11:06:24.242 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: Adding command class COMMAND_CLASS_ASSOCIATION to the list of supported command classes.
2020-04-16 11:06:24.244 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Creating new instance of command class COMMAND_CLASS_ALARM
2020-04-16 11:06:24.248 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Command class COMMAND_CLASS_ALARM, endpoint 0 created
2020-04-16 11:06:24.251 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 20: Application update is adding command class COMMAND_CLASS_ALARM.
2020-04-16 11:06:24.252 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: Adding command class COMMAND_CLASS_ALARM to the list of supported command classes.
2020-04-16 11:06:24.254 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Creating new instance of command class COMMAND_CLASS_MANUFACTURER_SPECIFIC
2020-04-16 11:06:24.258 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Command class COMMAND_CLASS_MANUFACTURER_SPECIFIC, endpoint 0 created
2020-04-16 11:06:24.260 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 20: Application update is adding command class COMMAND_CLASS_MANUFACTURER_SPECIFIC.
2020-04-16 11:06:24.262 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: Adding command class COMMAND_CLASS_MANUFACTURER_SPECIFIC to the list of supported command classes.
2020-04-16 11:06:24.264 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Creating new instance of command class COMMAND_CLASS_VERSION
2020-04-16 11:06:24.269 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Command class COMMAND_CLASS_VERSION, endpoint 0 created
2020-04-16 11:06:24.271 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 20: Application update is adding command class COMMAND_CLASS_VERSION.
2020-04-16 11:06:24.273 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: Adding command class COMMAND_CLASS_VERSION to the list of supported command classes.
2020-04-16 11:06:24.275 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 20: Application update - no transaction.
2020-04-16 11:06:24.278 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-04-16 11:06:24.279 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-04-16 11:06:24.528 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-04-16 11:06:24.533 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: Is awake with 1 messages in the queue
2020-04-16 11:06:24.536 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: COMMAND_CLASS_WAKE_UP not found - setting AWAKE
2020-04-16 11:06:24.538 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: Start sleep timer at 5000ms
2020-04-16 11:06:24.539 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2020-04-16 11:06:24.551 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 20: Node Status event - Node is AWAKE
2020-04-16 11:06:27.040 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2020-04-16 11:06:29.540 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: WakeupTimerTask 1 Messages waiting, state REQUEST_NIF
2020-04-16 11:06:29.542 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: No more messages, go back to sleep

PeteC · April 18, 2020, 3:35pm

So I have been pondering this situation and can conceive of two ways this can happen.
(1) The device is not sending any message for Smoke (or heartbeat or Test).
(2) The device sends a message but it doesn’t get through my Aeotec dongle to the log.

Has anyone experienced either situation?

chris · April 18, 2020, 3:37pm

If you get a debug log it should be easy enough to at least work out which of these cases is the right one. I’m not sure I understand the log you’ve provided - it looks like it’s been filtered and is missing the important bits.

PeteC · April 18, 2020, 3:47pm

Chris,
The version of the log from your LogView was filtered to show just the node in question. The code fenced version should have everything from before I started the test sequence.
I also have the unfiltered LogView but it is quite long and I don’t know how to upload that.
Thanks,
Pete

chris · April 18, 2020, 4:03pm

Unfiltered logs are normally best, but if this is everything, then I guess the device isn’t sending anything. You should take a look at the association configuration settings.

If you want to pist full logs (always best) then use something like Dropbox or Github or one of the many other systems out there that provide file hosting and just post the link here…

PeteC · April 18, 2020, 4:27pm

I uploaded the openhab.log to google drive. Link here:
openhab log.
Just in case it might be useful.
I am researching “association configuration settings”. I was not familiar with the term or process.

chris · April 18, 2020, 4:31pm

PeteC · April 18, 2020, 4:33pm

Yep, on that very page right now.
Learning all I can.

PeteC · April 18, 2020, 4:51pm

Below is the “Properties” from the PaperUI, Configuration, Things, Node 020.
Do I have to do lot more wake ups? The one reported, "2020-04-16T16:06:24Z " is the one I performed as shown in the LogView at 11:06:24.196.
Or is there something else I should be looking at?

dbReference 	238
defaultAssociations 	1
manufacturerId 	0138
manufacturerRef 	0001:0002,000C:0001
modelId 	ZCOMBO
vendor 	BRK Brands, Inc.
zwave_beaming 	true
zwave_class_basic 	BASIC_TYPE_ROUTING_SLAVE
zwave_class_generic 	GENERIC_TYPE_SENSOR_ALARM
zwave_class_specific 	SPECIFIC_TYPE_NOT_USED
zwave_deviceid 	2
zwave_devicetype 	1
zwave_frequent 	false
zwave_lastwakeup 	2020-04-16T16:06:24Z 
zwave_listening 	false
zwave_manufacturer 	312
zwave_neighbours 	
zwave_nodeid 	20
zwave_routing 	true
zwave_secure 	false
zwave_version 	0.0

PeteC · May 15, 2020, 7:48pm

Just an update. I haven’t figured this out yet but I am experimenting with OpenZWave. I hope I can unravel some of the layers and get right at the device.

I am also experimenting with PC Controller.

system · June 26, 2020, 11:48am

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.