First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

Posted on
Mon Apr 12, 2021 10:43 am
InsteonDiego offline
Posts: 48
Joined: Dec 07, 2016

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

Hi Jay / Matt -

A v2 version of this device has been released. Just received mine over the weekend, here are the updated Z-wave properties:

Z-Wave Properties:
Indigo Z-Wave Version: 7.5.0
Node ID: 45
Model: Notification Sensor
Model ID: 00010003
Manufacturer: First Alert
Manufacturer ID: 0138
Protocol Version: 6.07
Application Version: 11.00
Model Definition Version: 0
Library Type: 6
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 80v1 84v2 85v1 86v1 8Ev1 55v1 59v1 5Av1 5Ev1 9Fv1 20v1 6Cv1 70v1 71v1 72v1 73v1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 6, 9, 13, 14, 17, 26
Associations: 1:[1]
Config Values: - none -

Posted on
Wed Apr 14, 2021 1:33 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

Thanks, we'll get that model ID added to the next version of Indigo.

Image

Posted on
Fri Jun 18, 2021 2:48 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

Indigo 2021.1.0 is now available and should work with your ZSMOKE/ZCOMBO device).

Image

Posted on
Mon Jan 31, 2022 12:14 am
rustyhodge offline
Posts: 54
Joined: Nov 11, 2016

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

This isn't working for me.

Running Indigo 2021.2, this does not turn on or change state in Indigo when doing a test. No data seems to be received, according to the log, aside from afterwards, it reports the battery level.

I've rsync'ed after updating to 2021.2.

I have 2 of these, and they both behave the same way.

Smoke Alarm (ZSMOKE), firmware 11.00

Indigo Z-Wave Version: 2021.2.0
Node ID: 19
Model: Smoke Alarm (ZSMOKE)
Model ID: 00010003
Manufacturer: First Alert
Manufacturer ID: 0138
Protocol Version: 6.07
Application Version: 11.00
Model Definition Version: 3
Library Type: 6
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 80v1 84v2 85v1 86v1 6Cv1 8Ev1 70v1 71v1 72v1 73v1 55v1 59v1 5Av1 5Ev1 9Fv1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 6, 7, 10, 17, 18
Associations: 1:[1]
Config Values: - none -

Posted on
Mon Jan 31, 2022 4:14 am
rustyhodge offline
Posts: 54
Joined: Nov 11, 2016

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

I'm kind of freaked out about this because there was a small fire in the adjoining suite in my building tonight. I just happened to be there, and the smoke detector alarm went off, but Indigo has nothing about it in the log. (Bad on me for not testing). But if I wasn't there, I wouldn't have gotten the alarm notification and who knows what would have happened.

Posted on
Mon Jan 31, 2022 12:26 pm
trbaldwin offline
Posts: 7
Joined: Jul 14, 2013

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

I have 2 older ZCOMBO smoke detectors on my Zwave Network and they are working just fine.
So I just bought a new one to add, but the Syncing keeps failing. Please advise.
2022-01-31 12:08:28.060 Z-Wave Syncing - started for "022 - Notification Sensor"
2022-01-31 12:08:28.096 Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 16 01 01 6F
2022-01-31 12:08:28.101 Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 40 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00 00 00 00 00 00 00 00 0E (no inbound callback)
2022-01-31 12:08:28.101 Z-Wave Debug . . getNodeNeighbors: nodeId 022, neighbors: 7, 13
2022-01-31 12:08:28.101 Z-Wave Syncing - retrieved module neighbors list: 7, 13
2022-01-31 12:08:28.101 Z-Wave Syncing - assigning return route to "022 - Notification Sensor"
2022-01-31 12:08:28.101 Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 16 01 AB
2022-01-31 12:08:28.120 Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
2022-01-31 12:08:35.033 Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 01 BC
2022-01-31 12:08:35.033 Z-Wave Debug . . assignReturnRoute: node 022, success 0
2022-01-31 12:08:35.033 Z-Wave Error Syncing - failed to assign return route
2022-01-31 12:08:35.033 Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 16 24 F3 58
2022-01-31 12:08:41.182 Z-Wave Error Syncing - failed
2022-01-31 12:08:41.182 Z-Wave Error Timeout waiting for "022 - Notification Sensor". Module might be asleep, or is unreachable.
2022-01-31 12:08:41.545 Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 16 09 71 05 00 00 00 FF 01 03 00 62
2022-01-31 12:08:41.545 Z-Wave Debug . . requestAlarmSensorStatus: node 022, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
2022-01-31 12:08:41.545 Z-Wave Debug . . requestAlarmSensorStatus: typeExt 1, valueExt 3, classSubKeyExt 7100000103
2022-01-31 12:08:41.682 Z-Wave Debug RCVD nodeInfoFrame: 01 18 00 49 84 16 12 04 07 01 5E 85 8E 59 55 86 72 5A 73 80 9F 71 84 70 6C 5E
2022-01-31 12:08:44.382 Z-Wave Syncing - started for "022 - Notification Sensor"
2022-01-31 12:08:44.434 Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 16 01 01 6F
2022-01-31 12:08:44.439 Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 40 10 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 0E (no inbound callback)
2022-01-31 12:08:44.439 Z-Wave Debug . . getNodeNeighbors: nodeId 022, neighbors: 7, 13
2022-01-31 12:08:44.439 Z-Wave Syncing - retrieved module neighbors list: 7, 13
2022-01-31 12:08:44.440 Z-Wave Syncing - assigning return route to "022 - Notification Sensor"
022-01-31 12:08:44.440 Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 16 01 AB
2022-01-31 12:08:44.458 Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
2022-01-31 12:08:51.165 Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 01 BC
2022-01-31 12:08:51.165 Z-Wave Debug . . assignReturnRoute: node 022, success 0
2022-01-31 12:08:51.165 Z-Wave Error Syncing - failed to assign return route
2022-01-31 12:08:51.166 Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 16 24 F4 5F
2022-01-31 12:08:57.254 Z-Wave Error Syncing - failed
2022-01-31 12:08:57.254 Z-Wave Error Timeout waiting for "022 - Notification Sensor". Module might be asleep, or is unreachable.
2022-01-31 12:08:58.040 Z-Wave Debug RCVD nodeInfoFrame: 01 18 00 49 84 16 12 04 07 01 5E 85 8E 59 55 86 72 5A 73 80 9F 71 84 70 6C 5E
2022-01-31 12:08:58.212 Z-Wave Debug RCVD nodeInfoFrame: 01 18 00 49 84 16 12 04 07 01 5E 85 8E 59 55 86 72 5A 73 80 9F 71 84 70 6C 5E
2022-01-31 12:08:58.247 Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 16 0A 71 05 00 00 00 FF 01 00 01 03 7F
2022-01-31 12:08:58.247 Z-Wave Debug . . requestAlarmSensorStatus: node 022, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
2022-01-31 12:08:58.247 Z-Wave Debug . . requestAlarmSensorStatus: typeExt 1, valueExt 0, classSubKeyExt 7100000100
2022-01-31 12:08:58.580 Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 16 03 80 03 64 00
2022-01-31 12:08:58.580 Z-Wave Debug . . requestBatteryLevel: node 022, level 100

I reset the interface, but still no good...
2022-01-31 12:23:32.749 Z-Wave connection reset requested
2022-01-31 12:23:33.773 Z-Wave connected to Z-Stick Gen5 (ZW090) interface on /dev/cu.usbmodem146301 (firmware 1.01, minimum SDK 6.51.06)
2022-01-31 12:23:33.969 Z-Wave found module included in controller with no matching device (missing or disabled): 022 - Notification Sensor
2022-01-31 12:23:33.973 Trigger Interface Connection Initialized

Running on Indigo Server version 7.5.0

Posted on
Mon Jan 31, 2022 3:24 pm
rustyhodge offline
Posts: 54
Joined: Nov 11, 2016

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

A followup with more info. At another location, I have another Indigo running 7.5 with a ZSMOKE and it did go "on" when I did the test.
So maybe something in the latest version broke something with some models of ZSMOKE/ZCOMBO?

Posted on
Wed Feb 02, 2022 2:37 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

rustyhodge wrote:
A followup with more info. At another location, I have another Indigo running 7.5 with a ZSMOKE and it did go "on" when I did the test.
So maybe something in the latest version broke something with some models of ZSMOKE/ZCOMBO?

Although we didn't change Indigo's definition for that device, we did add support for a newer version of the ZSMOKE between 7.5 and the latest version. Can you use the Write Device Details button for both your working and not working modules so we can compare both the model ID and firmware versions?

And have you tried to capture what commands are being sent when it trips with Indigo's Z-Wave debug logging enabled (via Interfaces->Z-Wave->Configure... menu item)? I'd expect it to send something, even if Indigo isn't properly catching and updating the device state.

Image

Posted on
Wed Feb 02, 2022 2:42 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

trbaldwin wrote:
I have 2 older ZCOMBO smoke detectors on my Zwave Network and they are working just fine. So I just bought a new one to add, but the Syncing keeps failing.

I don't believe the problem you are seeing is related to rustyhodge's issue. A couple of notes on this one. First, the Z-Wave Controller is failing to get a return route defined back from the module. This almost always happens if there is a range issue (or marginal hardware). The other issue, once the first one is resolved, is that you might need the Indigo 2021.1.0 or higher if the newer one you bought is using the new model ID, as we didn't add support (a device definition) for that one until v2021.1.0. Note that is unrelated to the return route not being assigned though – it shouldn't be having an issue on that unless there is a range problem regardless of what version of Indigo you are running.

Image

Posted on
Thu Feb 03, 2022 9:10 pm
rustyhodge offline
Posts: 54
Joined: Nov 11, 2016

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

I am not able to get to the other location that isn't working for another week to do a test, I will do that with the debug on the see what it is sending.

After getting the data, I realize the one that works in the ZCOMBO and the 2 at the other location that don't work are the ZSMOKE. Hope that helps.

On Indigo 7.5. This works, and a test will turn the device on (and off again after the test concludes).

Indigo Z-Wave Version: 7.5.0
Node ID: 62
Model: Smoke / Carbon Monoxide Alarm (ZCOMBO)
Model ID: 00010002
Manufacturer: First Alert
Manufacturer ID: 0138
Protocol Version: 3.52
Application Version: 0.05
Model Definition Version: 3
Library Type: 6
Class Name: Sensor Alarm
Class Hierarchy: 04 : A1 : 00
Command Class Base: 71
Command Versions: 20v1 80v1 72v1 85v1 86v1 71v1 70v1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming
Neighbors: 4, 5, 7, 10, 18, 23, 25, 33, 36, 37, 39, 40, 41, 42, 43, 45, 57, 58
Associations: 1:[1]
Config Values: - none -


On This install at another location, it doesn't work. Just realized these are the ZSMOKE not ZCOMBO.


Feb 3, 2022 at 7:04:17 PM
Z-Wave Indigo Device "Smoke Detector (Downstairs)" Z-Wave Properties:
Indigo Z-Wave Version: 2021.2.0
Node ID: 19
Model: Smoke Alarm (ZSMOKE)
Model ID: 00010003
Manufacturer: First Alert
Manufacturer ID: 0138
Protocol Version: 6.07
Application Version: 11.00
Model Definition Version: 3
Library Type: 6
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 80v1 84v2 85v1 86v1 6Cv1 8Ev1 70v1 71v1 72v1 73v1 55v1 59v1 5Av1 5Ev1 9Fv1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 6, 7, 10, 17, 18
Associations: 1:[1]
Config Values: - none -




Feb 3, 2022 at 7:03:51 PM
Z-Wave Indigo Device "Smoke Detector (Upstairs)" Z-Wave Properties:
Indigo Z-Wave Version: 2021.2.0
Node ID: 11
Model: Smoke Alarm (ZSMOKE)
Model ID: 00010003
Manufacturer: First Alert
Manufacturer ID: 0138
Protocol Version: 6.07
Application Version: 11.00
Model Definition Version: 3
Library Type: 6
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 80v1 84v2 85v1 86v1 6Cv1 8Ev1 70v1 71v1 72v1 73v1 55v1 59v1 5Av1 5Ev1 9Fv1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 6, 10
Associations: 1:[1]
Config Values: - none -

Posted on
Tue Feb 15, 2022 7:31 pm
rustyhodge offline
Posts: 54
Joined: Nov 11, 2016

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

I found a technical spec for these online:
https://s7d9.scene7.com/is/content/Newe ... 5B2%5D.pdf

Based on that and testing the raw packet I sent, I've found these. I've only been able to test the Test On and Test Cleared but I ordered some "canned smoke" detector test spray to confirm the differences in the actual alarm vs test.

#Test On
17.9 seconds ago from 019 - Smoke Detector (Downstairs):
raw packet bytes: 0x01 0x0F 0x00 0x04 0x00 0x13 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x03 0x00 0x67
suggested match bytes: ? ? ? ? ? ? 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x03 0x00 ?

#Smoke Detected??? Need to confirm.
17.9 seconds ago from 019 - Smoke Detector (Downstairs):
raw packet bytes: 0x01 0x0F 0x00 0x04 0x00 0x13 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x02 0x00 0x67
suggested match bytes: ? ? ? ? ? ? 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x02 0x00 ?



# Test Over ?
1.2 seconds ago from 019 - Smoke Detector (Downstairs):
raw packet bytes: 0x01 0x10 0x00 0x04 0x00 0x13 0x0A 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x00 0x01 0x03 0x7A
suggested match bytes: ? ? ? ? ? ? 0x0A 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x00 0x01 0x03 ?


#Smoke Cleared??? Need to confirm.
raw packet bytes: 0x01 0x10 0x00 0x04 0x00 0x13 0x0A 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x00 0x01 0x02 0x7A
suggested match bytes: ? ? ? ? ? ? 0x0A 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x00 0x01 0x02 ?


#Smoke Silenced by pressing button??? Need to confirm.
raw packet bytes: 0x01 0x10 0x00 0x04 0x00 0x13 0x0A 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x00 0x01 0x02 0x7A
suggested match bytes: ? ? ? ? ? ? 0x0A 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x06 0x01 0x02 ?

Posted on
Wed Feb 23, 2022 7:40 pm
rustyhodge offline
Posts: 54
Joined: Nov 11, 2016

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

How would I go about detecting the heartbeat of these detectors?

From the docs:
Heartbeat
On every power up event and at an interval of approximately every 1 hour, the ZCOMBO will send the following Z-Wave message content to the Z-Wave Controller. If the S2 security is enabled, the message will be encapsulated inside the SuperVision Command Class.

Command Class
Notification (0x71)

Notification Type
System(0x09)

Notification Event
0x05

Posted on
Wed Feb 23, 2022 9:01 pm
rustyhodge offline
Posts: 54
Joined: Nov 11, 2016

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

Found this in the debug log after a while:

Code: Select all
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 19 09 71 05 00 00 00 FF 09 05 00 63
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 025, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 9, valueExt 5, classSubKeyExt 7100000905


So I'm guessing this is the raw packet match I'm looking for?

? ? ? ? ? ? 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x09 0x05 0x00 ?

Which I believe is:
First 4 bytes are home ID, next 2 are device ID, then the command sequence, at the end is a checksum.

I'll let you know later if it manages to trigger on that as they only go off once an hour or so.

Posted on
Thu Feb 24, 2022 5:43 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

The next version of Indigo will update the device state correctly, but in the mean time for the raw triggers I would use:

Test On Match Bytes:
* 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x03 *

Smoke Detected Match Bytes:
* 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x02 *

Cleared/Silenced/Test Over Match Bytes (I wouldn't try to break these out individually):
* 0x71 0x05 0x00 0x00 0x00 0xFF 0x01 0x00 *

Heartbeat Detected Match Bytes:
* 0x71 0x05 0x00 0x00 0x00 0xFF 0x09 0x05 *

Image

Posted on
Tue May 10, 2022 3:27 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: First Alert Wireless Smoke & Fire Alarm (ZSMOKE/ZCOMBO)

Indigo 2022.1.0 is now available and should support your First Alert Smoke / Carbon Monoxide Alarm (ZCOMBO) module.

Image

Who is online

Users browsing this forum: No registered users and 3 guests