HomeGenie Forum
General Category => Troubleshooting and Support => Topic started by: naps1saps on August 21, 2014, 03:56:01 AM
-
Ok so I'm at it again. I refuse to give up on the FA smoke alarm since it's carried in Lowes home improvement stores all across America. There is no reason we shouldn't get this device to work with HG since it is so openly available for purchase.
It never shows up as a smoke alarm, always as generic and never works with HG. I can get specific id, supported classes, variable value, and battery level but not the basic value. It always says timed out.
Manufacturer Specific = 0138:0001:0001
Supported Classes
Basic, Battery, Configuration, Association, Alarm
Here is the log. Got battery value, variable value, then basic value:
[18:49:02.875733] SPO < 01 09 00 13 12 02 80 02 05 06 74
[18:49:02.906933] SPI > 06 01 04 01 13 01 E8
[18:49:02.906933] SPO < 06
[18:49:02.969333] SPI > 01 05 00 13 06 00 EF
[18:49:02.969333] SPO < 06
[18:49:03.031733] SPI > 01 09 00 04 00 12 03 80 03 64 04
[18:49:03.031733] SPO < 06
[18:49:08.769443] SPO < 01 0A 00 13 12 03 70 05 01 05 07 81
[18:49:08.831843] SPI > 06 01 04 01 13 01 E8
[18:49:08.831843] SPO < 06
[18:49:08.894243] SPI > 01 05 00 13 07 00 EE
[18:49:08.894243] SPO < 06
[18:49:08.956643] SPI > 01 0B 00 04 00 12 05 70 06 01 01 00 91
[18:49:08.956643] SPO < 06
[18:49:13.870652] SPO < 01 09 00 13 12 02 20 02 05 08 DA
[18:49:13.886252] SPI > 06
[18:49:13.886252] SPO < 06
[18:49:13.886252] SPI > 01 04 01 13 01 E8
[18:49:13.948652] SPI > 01 05 00 13 08 00 E1
[18:49:13.948652] SPO < 06
-
bump
-
http://products.z-wavealliance.org/products/863 (http://products.z-wavealliance.org/products/863)
I'm sure this info would help but I don't know what to do with it to modify the source code. Anyone know what I'm looking for?
-
I just saw some $20 door sensors on lowes.com and one reviewer complained that Lowes is using a proprietary variation of Zigbee protocol and these door sensors wouldn't work with any other system. Maybe same issue with the fire alarm?
-
The Lowes Iris branded equipment uses x10 I think and I'm pretty sure its proprietary. The GE, First Alert, and Utilitech branded equipment is open zwave. On one forum for micasaverde they said the smoke alarm uses non standard commands but still conforms to the open zwave standard. The manual even says you can use it with 3rd party zwave receivers and some people have gotten it to work with other base stations. Just need to crack the code to communicate with it.
-
You sure about Iris using X10? I just performed a search and from what I see it uses WiFi/Zigbee/Z-wave. If it does use X10, I'd like to see a reference since that's the protocol I'm using. It's nice to know other compatible equipment!
-
Yeah looks like the other stuff is zigbee. Not sure how you pair zigbee stuff since there are no buttons to speak of.
-
Looks like InControl has this device supported and someone got it to work with OpenRemote I tried both of these systems and they are way too complicated for me. I don't have hours to sit down and try to figure out what is going on and try to get a simple if this triggers then sound alarm scene. With home genie I can install, add, and click check boxes for the simple security system in about 30 min no research required. You have a fantastic extremely simple system Gene. Just wish you had more time and wish I understood what I was looking for in the code to change it. :
Here is the thread if at helpful
http://www.openremote.org/display/forums/First+Alert+-+ZCOMBO+-+strange+data (http://www.openremote.org/display/forums/First+Alert+-+ZCOMBO+-+strange+data)
-
I tried updating the pepper1 db json file (now that I know where to get it and convert it ^_^) but it did not fix anything. I am using the configuration for the zcombo 0002 because they did not have zsmoke 0001 available. I think there is a problem in the coding. Anyone have any idea what to look for to fix it? I see no communication in the console when I use the test button. On the other systems, this sends a test alert via zwave.
-
Tried the smoke alarm again and HG is seeing the status change when testing the alarm!
security sensor is checked...
New problem:
security alarm is not triggered when armed and fire alarm is tested
sirens do not go off when fire alarm is tested
Any ideas Gene? The fire alarm is already detected as a sensor by default and when the value changes to 255, it should trigger the alarm since it is a sensor class same as my motion sensors.
-
Which HG version are you using?
-
1.1 beta r497
-
My two devices seem to be included with HG (r505) but not ever getting any status from them (according to the widget). I tried waking them up with the button while inserting battery as well but now HG doesn't show the pepper db info/picture. I read somewhere that the test button does not send zwave. Only way to test is to use smoke. Also read that CO does not send a zwave message!!! No idea how to confirm this one though.
-
CO is produced by your car so you could hold it near the tail pipe?
-
The test button does send zwave trigger at least for the smoke only alarm. The basic status changes value and HG was seeing the change when I'd press the test button.
As far as setup, I would do pair mode until I got all the values in hg.
-
I tried the car exhaust idea just now on my two First Alert zwave alarms. The first didnt alarm at all near the tail pipe and then I noticed I mistakenly bought a smoke alarm only :( I grabbed the other I had bought which definitely was CO and smoke. It did alarm, but for smoke according to the LED on it. Tried again little bit later and no alarm.
Nothing happened in HG either time :-( Nothing on the widget, nothing in the event log for node 9 or 14.
-
I exchanged my zsmoke for another zcombo and then found this on FirstAlert website...
[color=rgb(181, 18, 27) !important]Can I test my carbon monoxide alarm in any other way besides pressing the test button? ([url]http://www.firstalert.com/component/flexicontent/34/13#[/url])[/color]
Pressing the test/silence button is the only proper way to test the CO alarm. NEVER use vehicle exhaust or some other source of combustion fumes. Exhaust causes permanent damage and voids your warranty
[/size][/font]
.
-
<sarcasm> Well duh. You don't want to put carbon monoxide in a carbon monoxide detector as that will cause it to do its job. Pffft. Everyone knows that! </sarcasm>