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

Posted on
Sat Oct 12, 2013 10:45 am
gregjsmith offline
Posts: 946
Joined: Apr 01, 2003
Location: Rio Rancho, NM

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

dduff617 wrote:
i'm finding it hard to get much info on these units, particularly what you can do with them via z-wave.

here's what i'd like to do:

  • in a smoke detection event, tell which specific unit is triggering (not merely that some smoke or some CO detector is triggering).
  • ditto for a CO detection event, and it should be discernible from a smoke event.
  • monitor the status of batteries. i would like to at least be able to detect the onset of low battery condition (and before it starts chirping). preferably i'd like to be be able to track battery voltage over time so i could predict when low battery condition was going to occur.
  • track remaining service lifetime of the sensor, if applicable
  • monitor liveness of the units - i.e. set up a trigger for the event where indigo has not seen a status message or "heartbeat" or whatever in some period of time.
  • monitor the sensor level - i.e. periodically read the level of smoke or CO, including if it is below threshold. this might allow you to do something intelligent such as warn of the onset of an alarm condition or detect "nuisance" borderline alarms like burned toast.

do the zsmoke/zcombo support any/all of those?


You can get the battery level and on/off state. That's it.

Posted on
Sat Oct 12, 2013 5:10 pm
jay (support) offline
Site Admin
User avatar
Posts: 15620
Joined: Mar 19, 2008
Location: Austin, Texas

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

  1. Yes - you add each detector individually so you'll know which one is triggering
  2. Yes/No - there is no difference from the API standpoint which event caused the alarm so you get the alarm but you don't know which caused it
  3. Yes - they report battery level
  4. No
  5. No, other than the reported battery level
  6. No

I think you have to remember - these smoke detectors are super inexpensive for what they do offer so I wouldn't expect them to have any advanced features.

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Sun Nov 17, 2013 1:49 am
nsheldon offline
Posts: 2055
Joined: Aug 09, 2010
Location: CA

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

I recently got a Z-Stick to start building a Z-Wave network. My first Z-Wave device is a First Alert ZCOMBO. It paired and synced just fine with Indigo 6.0.4 a few weeks ago when I got it. I've upgraded to Indigo 6.0.5 and am running Mac OS X 10.9 with Server 3.0.1. Earlier this week, my wife was cooking and caused a lot of smoke in the area where I placed the ZCOMBO. It sounded an alarm, but Indigo didn't even log the event. I used the ZCOMBO's test feature twice and Indigo received the Z-Wave on and off messages each time. So for a more controlled test, I intentionally burned a piece of paper towel in a porcelain bowl right beneath the ZCOMBO and caused it to sound. Again, no message shown in Indigo. Once the alarm stopped sounding, I enabled debug logging in the Z-Wave interface control and forced the alarm to activate again (with another piece of paper towel). Indigo is definitely receiving the message, but doing nothing with it. Below is the Z-Wave debug log. Perhaps the ZCOMBO is sending a different message for an actual alarm as opposed to a test alarm.
Code: Select all
2013-11-16 22:03:44   Z-Wave Debug   stopping node status polling
2013-11-16 22:03:44   Z-Wave Debug   stopped zwave packet parser thread
2013-11-16 22:03:44   Z-Wave   connection reset requested
2013-11-16 22:03:44   Z-Wave Debug   starting serial connection loop
2013-11-16 22:03:44   Z-Wave Debug   starting zwave packet parser thread
2013-11-16 22:03:44   Z-Wave Debug   SENT getVersion: 01 03 00 15 E9
2013-11-16 22:03:44   Z-Wave Debug   RCVD getVersion: 01 10 01 15 5A 2D 57 61 76 65 20 32 2E 37 38 00 01 9B
2013-11-16 22:03:44   Z-Wave Debug   . .  getVersion: Z-Wave 2.78 static controller
2013-11-16 22:03:44   Z-Wave Debug   SENT getHomeID: 01 03 00 20 DC
2013-11-16 22:03:44   Z-Wave Debug   RCVD getHomeID: 01 08 01 20 01 6A 25 7F 01 E6
2013-11-16 22:03:44   Z-Wave Debug   . .  getHomeID: 23733631, nodeID: 001
2013-11-16 22:03:44   Z-Wave Debug   SENT getInterfaceFeatures: 01 03 00 05 F9
2013-11-16 22:03:44   Z-Wave Debug   RCVD getInterfaceFeatures: 01 04 01 05 08 F7
2013-11-16 22:03:44   Z-Wave Debug   . .  getInterfaceFeatures: 08
2013-11-16 22:03:44   Z-Wave Debug   SENT getInterfaceApiCapabilities: 01 03 00 07 FB
2013-11-16 22:03:44   Z-Wave Debug   RCVD getInterfaceApiCapabilities: 01 2B 01 07 03 07 00 86 00 02 00 01 FE 80 FE 88 0F 00 00 00 FB 97 7F 82 07 00 00 80 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C2
2013-11-16 22:03:44   Z-Wave Debug   . .  getInterfaceApiCapabilities: serialApi 3.07, manufactureId 0086, productType 0002, productId 0001
2013-11-16 22:03:44   Z-Wave   connected to Z-Stick S2 interface on /dev/cu.SLAB_USBtoUART (firmware 3.07)
2013-11-16 22:03:44   Z-Wave Debug   SENT getInitialNodeData: 01 03 00 02 FE
2013-11-16 22:03:44   Z-Wave Debug   RCVD getInitialNodeData: 01 25 01 02 05 00 1D 05 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 C6
2013-11-16 22:03:44   Z-Wave Debug   . .  getInitialNodeData: [1, 3]
2013-11-16 22:03:44   Z-Wave Debug   SENT getNodeProtocolInfo: 01 04 00 41 01 BB
2013-11-16 22:03:44   Z-Wave Debug   RCVD getNodeProtocolInfo: 01 09 01 41 92 16 00 02 02 01 33
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:       node 001, class name: Static Computer Controller
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:            class hierarchy: Static Controller : Static Controller : Static Computer Controller (02 : 02 : 01)
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:         base class command: 00
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:   supported class commands: 20
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:                   features: beaming
2013-11-16 22:03:44   Z-Wave Debug   SENT getNodeProtocolInfo: 01 04 00 41 03 B9
2013-11-16 22:03:44   Z-Wave Debug   RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 00 04 A1 00 DC
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:       node 003, class name: Sensor Alarm
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:            class hierarchy: Routing Slave : Sensor Alarm : -- (04 : A1 : 00)
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:         base class command: 71
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:   supported class commands: 20 71 72
2013-11-16 22:03:44   Z-Wave Debug   . .  getNodeProtocolInfo:                   features: routing, beaming
2013-11-16 22:03:45   Z-Wave Debug   overriding node 003 type from zwCustomType to zwOnOffSensorType
2013-11-16 22:03:45   Z-Wave Debug   starting node status polling
2013-11-16 22:07:47   Z-Wave Debug   RCVD requestAlarmSensorStatus: 01 0A 00 04 00 03 04 71 05 01 FF 7C
2013-11-16 22:07:47   Z-Wave Debug   . .  requestAlarmSensorStatus: node 003, endpoint None, cmdClass 71, type 1, value 255
2013-11-16 22:08:25   Z-Wave Debug   RCVD requestAlarmSensorStatus: 01 0A 00 04 00 03 04 71 05 01 00 83
2013-11-16 22:08:25   Z-Wave Debug   . .  requestAlarmSensorStatus: node 003, endpoint None, cmdClass 71, type 1, value 0
2013-11-16 22:10:29   Z-Wave   connection reset requested

Any suggestions?

Posted on
Sun Nov 17, 2013 8:55 am
matt (support) offline
Site Admin
User avatar
Posts: 19212
Joined: Jan 27, 2003
Location: Texas

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

Good catch -- it is indeed sending out different messages. We'll have this fixed in v6.0.6. Thanks!

Image

Posted on
Sun Nov 17, 2013 12:33 pm
nsheldon offline
Posts: 2055
Joined: Aug 09, 2010
Location: CA

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

Cool. Thanks!

Posted on
Thu Jan 23, 2014 7:56 pm
toille27 offline
User avatar
Posts: 233
Joined: Jul 18, 2011
Location: Doylestown PA

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

I didn't read anything about inclusion of this device on here so wanted to clarify since it took me a while to figure it out...

I am used to pushing the z-stick first and then pushing the button on the device (at the new device location) to pair them up prior to returning to the computer to return the z-stick in the usb port and add the device in indigo. My understanding was that pairing the device at its final resting place allows the new device to find its neighboring nodes and improve the z-wave network.

With the zsmoke it appears you have to push the button on the z-stick first then hold the test button on the zsmoke as you slide the battery tray in. You will see the z-stick do its flash thing and then you have 30 seconds to run to the computer plug the z-stick back in and then add and sync the device in indigo. It only stays awake for 30 seconds (it beeps once when it leaves the awake state) which makes pairing the device in its final resting place a little difficult.

I had to resort to pairing the smoke next to the computer to utilize the 30 second awake window. Was I missing something and is there a way to wake it back up after returning the z-stick to the usb connection to sync the zsmoke?

Posted on
Wed Feb 05, 2014 7:18 am
DaveL17 offline
User avatar
Posts: 4920
Joined: Aug 20, 2013
Location: Chicago, IL, USA

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

toille27 wrote:
It only stays awake for 30 seconds (it beeps once when it leaves the awake state) which makes pairing the device in its final resting place a little difficult.

In my experience, this is completely common with battery operated Z-Wave devices. In fact, the Aeon Multisensor, for example, behaves differently depending on whether it is being run off battery power or external USB power.

Dave

I came here to drink milk and kick ass....and I've just finished my milk.

[My Plugins] - [My Forums]

Posted on
Sun Feb 23, 2014 8:36 am
DaveL17 offline
User avatar
Posts: 4920
Joined: Aug 20, 2013
Location: Chicago, IL, USA

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

Just finished installing three ZCOMBO units. The first two went off without a hitch, but the third required me to exclude it before it would include.

Code: Select all
address : 32
allowOnStateChange : True
allowSensorValueChange : False
batteryLevel : 100
buttonGroupCount : 0
configured : True
description :
deviceTypeId : zwOnOffSensorType
displayStateId : onOffState
displayStateValRaw : False
displayStateValUi : off
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState :
folderId : 55846995
globalProps : MetaProps : (dict)
     com.perceptiveautomation.indigoplugin.zwave : (dict)
          AllowOnStateChange : true (bool)
          SupportsBatteryLevel : true (bool)
          SupportsEnergyMeter : false (bool)
          SupportsEnergyMeterCurPower : false (bool)
          SupportsEnergyMeterReset : false (bool)
          SupportsOnState : true (bool)
          SupportsSensorValue : false (bool)
          SupportsStatusRequest : false (bool)
          address : 32 (integer)
          userPollAfterActivity : true (bool)
          userPollInterval : 0 (integer)
          userPollingEnabled : true (bool)
          userWakeInterval : 60 (integer)
          zwAppVersMajor : 0 (integer)
          zwAppVersMinor : 5 (integer)
          zwAssociationsMap : (dict)
               g1 : (list)
                    Item : 1 (integer)
          zwAssociationsMapStr : 1:[1] (string)
          zwClassCmdBase : 113 (integer)
          zwClassCmdMap : (dict)
               c112 : 1 (integer)
               c113 : 1 (integer)
               c114 : 1 (integer)
               c128 : 1 (integer)
               c133 : 1 (integer)
               c134 : 1 (integer)
               c32 : 1 (integer)
          zwClassCmdMapStr : 20v1 80v1 85v1 86v1 70v1 71v1 72v1 (string)
          zwClassIds : (list)
               Item : 4 (integer)
               Item : 161 (integer)
               Item : 0 (integer)
          zwClassInstanceCountMap : (dict)
          zwClassInstanceCountMapStr : - none - (string)
          zwClassName : Sensor Alarm (string)
          zwConfigVals : (dict)
          zwConfigValsStr : - none - (string)
          zwDevSubIndex : 0 (integer)
          zwEndpointClassMap : (dict)
          zwEndpointClassMapStr : - none - (string)
          zwEndpointDevTypeMap : (dict)
          zwEndpointDevTypeMapStr : - none - (string)
          zwFeatureListStr : routing, battery, beaming (string)
          zwLibType : 6 (integer)
          zwManufactureId : 312 (integer)
          zwManufactureName : First Alert (string)
          zwMeterSubTypeFlags : 0 (integer)
          zwMeterSupportsReset : false (bool)
          zwMeterType : 0 (integer)
          zwModelDefnVers : 3 (integer)
          zwModelId : 65538 (integer)
          zwModelName : Smoke / Carbon Monoxide Alarm (ZCOMBO) (string)
          zwNodeNeighbors : (list)
               Item : 1 (integer)
               Item : 3 (integer)
               Item : 7 (integer)
               Item : 8 (integer)
               Item : 9 (integer)
               Item : 13 (integer)
               Item : 14 (integer)
               Item : 16 (integer)
               Item : 17 (integer)
               Item : 18 (integer)
               Item : 21 (integer)
               Item : 23 (integer)
               Item : 27 (integer)
               Item : 28 (integer)
               Item : 29 (integer)
          zwNodeNeighborsStr : 1, 3, 7, 8, 9, 13, 14, 16, 17, 18, 21, 23, 27, 28, 29 (string)
          zwProtoVersMajor : 3 (integer)
          zwProtoVersMinor : 52 (integer)
          zwShowMainUI : true (bool)
          zwShowPollingUI : false (bool)
          zwShowWakeIntervalUI : false (bool)
          zwWakeInterval : 0 (integer)
id : 1866995668
lastChanged : 2014-02-23 07:28:16
model : Smoke / Carbon Monoxide Alarm (ZCOMBO)
name : Sensor - Upstairs Smoke Detector
onState : False
pluginId : com.perceptiveautomation.indigoplugin.zwave
pluginProps : emptyDict : (dict)
protocol : ZWave
remoteDisplay : True
sensorValue : None
states : States : (dict)
     batteryLevel : 100 (integer)
     batteryLevel.ui : 100% (string)
     onOffState : off (on/off bool)
subModel : Smoke Sensor
supportsAllLightsOnOff : False
supportsAllOff : False
supportsStatusRequest : False
version : 0

I use a Z-stick (and I did them one at a time) so it was pretty easy to get them included in Indigo before they timed out. The sync went very fast. I started with the one closest to my Indigo computer and then the next closest. We'll see how they do when the batteries need replacing.

I came here to drink milk and kick ass....and I've just finished my milk.

[My Plugins] - [My Forums]

Posted on
Fri Apr 11, 2014 9:04 pm
dduff617 offline
Posts: 478
Joined: Jul 05, 2006

some basic questions

time for me to replace some smoke detectors and i'm considering ZSMOKE and ZCOMBO units. looking to check my understanding of how these work.

my current detectors are interconnected (aka "hardwired") such that if one goes off, they all go off. i was surprised to see info on the web that indicates the ZSMOKE detectors don't work this way. it seems that each alarm only sounds if/when smoke is detected; if my basement detector goes off, my bedroom units stay quiet (unless/until they also detect smoke or CO). do i have that right?

if so, i'm a bit surprised by this, since First Alert seems to sell two other major types of detectors ("hardwired" and "One Link"), both of which provide interconnected operation. i'm fuzzy about this: i believe the law in my state (MA) requires smoke detectors to be either hardwired/interconnected or what they call "system type" (which i assume includes gear like One Link), but it sounds like ZSmoke/ZCombo would not qualify.

specific questions:
  • when one ZSMOKE or ZCOMBO unit detects smoke, do other units remain silent?
  • is it possible to trigger a ZSMOKE unit from indigo? - i.e., to cause it's alarm to sound? in that case, i could create my own "connected" system of detectors.
  • recommendations or suggestions? Nest? OneLink? or just use hardwired detectors with a relay+IOLinc or smoke bridge to connect to indigo?

Posted on
Sat Apr 12, 2014 7:43 am
jay (support) offline
Site Admin
User avatar
Posts: 15620
Joined: Mar 19, 2008
Location: Austin, Texas

Re: some basic questions

dduff617 wrote:
specific questions:
  • when one ZSMOKE or ZCOMBO unit detects smoke, do other units remain silent?


Yes - they are not connected. I believe this is because the Z-Wave radio sleeps until it's needed to send out the command so they can't respond to Z-Wave commands (unless you explicitly manually wake them up).

dduff617 wrote:
  • is it possible to trigger a ZSMOKE unit from indigo? - i.e., to cause it's alarm to sound? in that case, i could create my own "connected" system of detectors.


No, for the reason above.

dduff617 wrote:
  • recommendations or suggestions? Nest? OneLink? or just use hardwired detectors with a relay+IOLinc or smoke bridge to connect to indigo?


I use them anyway. I just created a Device Group which goes on when any of them go on. When the group goes on, I turn on all the lights in the house and start a spoken announcement. When I integrate my alarm system I'll probably set the alarm off. In the interim I may just get a Z-Wave siren. I have one in my travel trailer (though it's not the same model) and have to set it to it's lowest sound setting because it's so loud - I can probably put one in a central part of the house and I think it'll wake everyone up.

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Sat Apr 12, 2014 9:19 pm
dduff617 offline
Posts: 478
Joined: Jul 05, 2006

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

thanks for the info, jay. helps me with the decision.

Posted on
Tue Jul 15, 2014 8:45 am
TheTechnoPilot offline
Posts: 46
Joined: Mar 31, 2014
Location: Montreal, QC, Canada

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

DaveL17 wrote:
Just finished installing three ZCOMBO units. The first two went off without a hitch, but the third required me to exclude it before it would include...


I picked one of these up while I was down in California and was having a hell of a time trying to get it to pair with my Z Stick before reading this! Thanks for the tip to try excluding first before inclusion. It is weird that so many of these need this to be done.

Cheers,
Sean "TheTechnoPilot"

Android's Tasker, to a person who does home automation...is like walking up to a Crack Treatment facility with a truck full of 3lb bags of crack. Then for each person that walks in and out smack them in the face with an open bag.

Posted on
Tue Jul 15, 2014 8:58 am
DaveL17 offline
User avatar
Posts: 4920
Joined: Aug 20, 2013
Location: Chicago, IL, USA

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

Anymore, I think it's best to do with all new devices.

Glad I could help!


Posted with Tapatalk 2.

I came here to drink milk and kick ass....and I've just finished my milk.

[My Plugins] - [My Forums]

Posted on
Fri Nov 14, 2014 5:25 pm
markf424 offline
Posts: 58
Joined: Dec 25, 2013

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

Has anyone else had issues with false alarms on the ZSMOKE devices? I have three ZSMOKE and two ZCOMBO units in the house. All three ZSMOKE units have had false alarms (full alarms, not battery alerts) over the few months I've owned them. The ZCOMBO have not as of yet. It's an issue because of course the alarms have been in the middle of the night.. and in the kids' rooms... etc.

I'm considering replacing them with ZCOMBOs, but was curious if anyone had any other data points. Possible I got a bad batch - I bought them all at once.

Posted on
Fri Nov 14, 2014 5:59 pm
nsheldon offline
Posts: 2055
Joined: Aug 09, 2010
Location: CA

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

I have 2 ZSMOKEs and 1 ZCOMBO and haven't encountered any issues (yet). The oldest ZSMOKE is about 4 months old. The ZCOMBO is about a year old.

I did, however, have another non-z-wave FirstAlert speaking smoke/CO2 alarm in the hallway that would occasionally enter test mode and start to yell at us to evacuate (of course, in the middle of the night) even though the batteries seemed fine. That happened 2 or 3 times over the last month or two. The last time was last week and I'd had enough. I removed it and am going to replace it with a ZCOMBO, but maybe it's an issue with some FirstAlert detectors in general. Hard to say as I certainly don't have enough sample smoke detectors to make that assumption yet. Just a thought.

Who is online

Users browsing this forum: No registered users and 1 guest