A pull-down action chart instructs you in what to do if the CO alarm goes off. There are no complicated displays or settings to navigate-a single button silences the alarm and tests the CO detector. Simply plug the alarm into a 120-volt wall outlet, and the CO detector will start to monitor your space for carbon monoxide. The First Alert CO600A Carbon Monoxide Alarm is easy to set up. The CO detector lasts approximately five years. A low-battery light and alarm alert you when battery power is running low, and an end-of-life timer lets you know when the device should be replaced. This carbon monoxide detector features an 85-decibel siren that is designed to wake even the soundest of sleepers. Placing carbon monoxide detectors on every floor of the home and in each sleeping room is an important way to protect your family from danger. Carbon monoxide can't be seen, smelled, or tasted in the air, and it is the leading cause of accidental poisoning deaths in America. When CO is detected, the carbon monoxide detector sounds an alarm to warn you of the threat. The First Alert CO600A Plug-In Carbon Monoxide Alarm uses an advanced electrochemical CO sensor to detect elevated carbon monoxide levels. When carbon monoxide levels become elevated, a loud 85-decibel alarm alerts you to the threat. This carbon monoxide detector plugs into any wall outlet. Scroll down to the bottom, and you should see three entries for your First Alert device: the root device, the alarm type, and the alarm level.The First Alert CO600A Plug-In Carbon Monoxide Alarm utilizes an electrochemical carbon monoxide sensor that lasts for up to five years to detect carbon monoxide. storage/core.entity_registry so we can tweak a few items. Go into your Home Assistant directory and type vi. I know this is supposed to be done in the UI, but I’m happy making changes directly in the file. Step 2: clean up the names in Home Assistant You’ll then need to wait for z-wave to come back up again. Now, because the naming convention isn’t always the best with z-wave, you’ll want to take a few more steps to clean this up a bit. You’ll want to change that Node id="16" at the beginning to match the number for the previous step, otherwise this isn’t going to work. Edit the zwcfg_xyz123.xml file and add the following with your other nodes: Ĭauses the device to send double alarm messages. See the “Node:X” value that’s listed in the nodes while you’re in the z-wave configuration panel? You’ll need the number associated with the First Aler. At this point you’ll need to manually edit the zwcfg_xyz123.xml file and plug in some details. Apparently the z-wave component isn’t sure what to do with these. If you’re like me and want to know what it’s doing, you can tail the OZW_Log.txt file to see what’s happening.Īfter it’s added, you’ll see it in the list of devices, but the nodes will show up as unknown. You should hear a beep after a few seconds. Wait about 2 seconds and let go of the button. Pull the battery tray, hold down the test button, and plug the tray back in while holding the button. To include them, go into the z-wave configuration panel and select Add Node Secure. Figuring out why nothing seemed to work was a whole other problem. Note: First Alerts Smoke / CO Warranty begins. If your alarm is more than 10 years old, its time for a replacement. Check your alarms manual for the exact warranty period. This can vary slightly based on the model you own. It’ll beep one and you should see it removed from SmartThings. After an alarm is turned on for the first time, it should last approximately 7-10 years in normal operating conditions. ![]() Select General Exclusion from the SmartThings app, pull the battery tray on the detector, hold down the test button, and plug the tray back in while you’re holding down the button. I pulled this from a few different sources and didn’t really document the process, so I apologize to anyone I might have grabbed bits and pieces from without giving them credit. ![]() The last item to move was the First Alert detectors: they also happened to be the biggest pain in the ass. I didn’t have any major problems with SmartThings, but got tired of dealing with the hacky MQTT bridge that didn’t always seem to work as expected. I’ve been in the process of moving everything z-wave from SmartThings over to Home Assistant. Type: Docker, so this might be slightly different in HASS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |