No announcement yet.

Co-mingling Nest Protect with conventional wired smoke detectors

  • Filter
  • Time
  • Show
Clear All
new posts

  • Co-mingling Nest Protect with conventional wired smoke detectors

    I have wired smoke detectors on each of three floors of our house (3) and one in every bedroom (5). I was thinking of replacing the smoke detectors on the three floors with the Nest and using the plugin for HS3. I was also thinking of keeping the existing wired detectors in the bedrooms - for now - mostly for cost reasons. As the Nest Protect communicates with the other Nests wirelessly, then the existing detectors will continue to communicate with each other on the wired channel.

    I recognize that if the smoke is in the hallway, then the Nests will pick it up and the bedroom detectors will not go off until one of them senses it. But I will use the plugin to set off the fire alarm, etc.

    Does anyone see an issue with this configuration? Thanks.
    Last edited by simonmason; November 6th, 2016, 09:42 AM. Reason: Fixing incorrect title

  • #2
    I don't have an answer but I have wondered the same thing, so I'm following this thread. You might want to fix the subject though ;-)

    Sent from my XT1650 using Tapatalk


    • #3
      I fixed the title. Thanks.

      I am guessing that doing this is not to code as not all smoke detectors would trigger in the event of smoke. However, buying 8 nest detectors at once is quite an expense.


      • #4
        If you have Kidde or FireX interconnected Smoke and CO detectors then you can easily intergrade them into your HomeSeer HS3 system. I wrote a HowTo guide that you can find here.

        This way you can keep your existing Smoke and CO detectors while switching over to Nest Protect. All of you're existing devices will be viewed as a single device while the Nests will be shown as individual devices.

        The other reason to do this is when you have areas you can't use Standard Smoke detectors and have to use Heat Detectors. These places include attics and garages. This will allow you to keep those areas covered.

        It's too bad that Nest didn't design the Protect so it would work with existing Smoke and CO detector built by companies like Kidde. Then existing detectors would correctly sound along with the Nest plus the Nest could tell you that the existing one triggered. As it is I believe that it's a safety issue when you mix Nest Protect along with existing devices.

        Nest could easily fix this by offering a small device which would connect to the existing interconnect and they relay their status back to the Next Protect.

        Since I don't have any Protects yet I've been wondering how they communicate with each other. If they do it via WiFi only then I see a big safety issue if your WiFi router or access point fails. If that happens you won't know in a bedroom if you have smoke detected in the family room. Not Good!

        If Kidde ever added Z-Wave or WiFi, if we could connect to it, to their wired detectors and kept the existing interconnect system I'd buy them over Nest in a heart beat.
        Last edited by Timon; January 3rd, 2018, 01:13 PM.
        John (N6BER), Joyce, Lucas (Golden Ret mix), Bella (Great Pyrenees) and Lance (GP).

        HomeSeer Version: HS3 Standard Edition
        Linux version: Linux auto 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
        Number of Devices: 347
        Number of Events: 535
        Available Threads: 399
        HSTouch Enabled: True

        Enabled Plug-Ins AirplaySpeak BLBackup EasyTrigger
        1.3.6927.42284: LiftMaster MyQ mcsMQTT PHLocation Pushover 3P Z-Wave


        • #5
          Nest protects use a proprietary wireless network to communicate with each other. The Wi-Fi just lets them communicate with the thermostat and cloud.

          If you dig through the FAQ at the Nest site, you'll see there explanation for choosing the wireless interconnection instead of a wired interconnection is so the individual protects could identify themselves to the others and sound the appropriate "smoke detected in X room" alarm. The wired protects use the wiring only for power and not for interconnection. The good thing about the wired connectors is they send motion updates to the cloud and thermostat immediately - which increases home/away reaction time - whereas the battery only protects push the info on a schedule (maybe once a day) that only create habitation patterns but not real-time motion tracking.

          I think you already identified the biggest problem - smoke/fire detected by the Nests won't alert you in the non-Nest rooms and vice-versa.

          I have 9 battery operated Protects and a Nest Thermostat (old house - no existing wired smokes). As my never ending remodeling saga continues I will likely run wire to the detector locations so I can change them to wired models when these expire in 7-10 years.

          I cannot imagine what will be available by then - hopefully an Echo/Google Home-like device that also does all your environmental (motion, temp, RH, light, glass break, other audio etc.) monitoring plus paging, whole-house music, night lights, Wi-Fi mesh, and so forth.
          Last edited by jrfuda; January 3rd, 2018, 02:16 PM. Reason: typos
          Hardware: i5-6400T w/16GB RAM & SSD w/HS3Pro, Z-Net, Harmony Hub x2, Echo Dot x2, Ocelot
          Plugins: Z-wave, HSTouch, BLBackup, Harmony, GTS CPUXA, UltraMon3, Nest
          HSTouch: Multiple Android Devices; 5 x ToteVision MD-1001 10.1" Win 7 Tablets
          Devices: Cooper RF9501 x4, RF9517 x6, RF9534 x1, RF9540-N x7, RF9542 x1, RF9542-Z x2, RFHDSCG x1, RFWC5 x5; Intermatic HA02 x6; FortrezZ MIMOLite x3; Leviton VRPD3-1LW x4, VRR15-1LZ x6; Nest Tstat & 9x Protects; Dragon PD-100 x3, PA-100 x3