<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Google Home Scripting Nest Protect in Nest Protect</title>
    <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643761#M10675</link>
    <description>&lt;P&gt;This is correct. Unfortunately, there isn't a way to integrate it into google home yet and it is not matter enabled either which means its only stuck using nest app for now, whilst they work on integration not much can be done. Plus, I doubt nest protect can be automated due to it being a smoke detector and any form of automation could defeat its purpose/cause it not to work. Also, a MAC address is a hardware device number used to identify a piece of hardware its being used to connect to the internet, so I doubt a mac address can be changed either.&lt;/P&gt;</description>
    <pubDate>Fri, 13 Sep 2024 08:50:32 GMT</pubDate>
    <dc:creator>code_</dc:creator>
    <dc:date>2024-09-13T08:50:32Z</dc:date>
    <item>
      <title>Google Home Scripting Nest Protect</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/642314#M10642</link>
      <description>&lt;P&gt;I have reluctantly been using the home script tool to try to get some automations from the Nest Protects as opposed to simple presence sensing. &amp;nbsp;I have not been able to find an accurate, verifiable source to determine what 'device types" and "states" can be used, and actually work in a script.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also could Google have found a less obtuse way of naming unique devices other than the 802.15 MAC as is used in the Google Home Presence sensing?&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2024 02:21:00 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/642314#M10642</guid>
      <dc:creator>justsam</dc:creator>
      <dc:date>2024-09-06T02:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: Google Home Scripting Nest Protect</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/642428#M10644</link>
      <description>&lt;P&gt;You're wasting your time as until Google integrates the Nest Protect into Google home, you'll not be able to access any of it's sensors for use in routines. Google has been saying "Working on it" for years but so far nothing so I've actually given up hope that this will ever happen.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2024 15:36:09 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/642428#M10644</guid>
      <dc:creator>GBD</dc:creator>
      <dc:date>2024-09-06T15:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: Google Home Scripting Nest Protect</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643761#M10675</link>
      <description>&lt;P&gt;This is correct. Unfortunately, there isn't a way to integrate it into google home yet and it is not matter enabled either which means its only stuck using nest app for now, whilst they work on integration not much can be done. Plus, I doubt nest protect can be automated due to it being a smoke detector and any form of automation could defeat its purpose/cause it not to work. Also, a MAC address is a hardware device number used to identify a piece of hardware its being used to connect to the internet, so I doubt a mac address can be changed either.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 08:50:32 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643761#M10675</guid>
      <dc:creator>code_</dc:creator>
      <dc:date>2024-09-13T08:50:32Z</dc:date>
    </item>
    <item>
      <title>Re: Google Home Scripting Nest Protect</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643762#M10676</link>
      <description>&lt;P&gt;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/522561"&gt;@moralesvicente&lt;/a&gt;&amp;nbsp;Are you able to explain more on this? I feel you may know more on scripting for Nest protect.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 08:53:28 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643762#M10676</guid>
      <dc:creator>code_</dc:creator>
      <dc:date>2024-09-13T08:53:28Z</dc:date>
    </item>
    <item>
      <title>Re: Google Home Scripting Nest Protect</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643859#M10679</link>
      <description>&lt;P&gt;Thanks for the tag!&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;While I can't comment on the technical aspects, I can confirm that Nest Protect support is on our agenda for the Google Home app. We're currently working on integrating more Nest devices into the Home app, and you can learn more in the FAQ of&amp;nbsp;&lt;A href="https://goo.gle/4d4twxg" target="_blank" rel="noopener"&gt;this blog post&lt;/A&gt;.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have any other questions please let me know!&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Daniel&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 23:30:27 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643859#M10679</guid>
      <dc:creator>moralesvicente</dc:creator>
      <dc:date>2024-09-13T23:30:27Z</dc:date>
    </item>
    <item>
      <title>Re: Google Home Scripting Nest Protect</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643893#M10681</link>
      <description>&lt;P&gt;Probably best to review this video. &amp;nbsp;I use the AI Script Writing Tool as it seems to know all the capabilities and parameters of device types that I have not found in a succinct document. &amp;nbsp;Trying to find all the available variables for Nest Protect is an example of trying by hit or miss to see what works or will validate. &amp;nbsp;There are example scripts at their web site. &amp;nbsp;Watch video first.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.youtube.com/watch?v=Jk9z-TpY-q8" target="_blank"&gt;https://www.youtube.com/watch?v=Jk9z-TpY-q8&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 22:07:58 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643893#M10681</guid>
      <dc:creator>justsam</dc:creator>
      <dc:date>2024-09-13T22:07:58Z</dc:date>
    </item>
    <item>
      <title>Re: Google Home Scripting Nest Protect</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643899#M10683</link>
      <description>&lt;P&gt;I reviewed the FAQ and heard/read no mention of Nest Protect. &amp;nbsp;Seemed to be more focused on cameras and legacy cameras. &amp;nbsp;Would be delighted if more done with Nest Protect.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 22:18:31 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643899#M10683</guid>
      <dc:creator>justsam</dc:creator>
      <dc:date>2024-09-13T22:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: Google Home Scripting Nest Protect</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643914#M10684</link>
      <description>&lt;P&gt;Hey folks,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We're always looking for ways to improve.&amp;nbsp; Would you be interested in sharing your&lt;A href="https://goo.gle/43SS7Sr" target="_blank"&gt; feedback&lt;/A&gt; with us?&amp;nbsp;Let us know how we can improve your experience.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 23:27:00 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/643914#M10684</guid>
      <dc:creator>moralesvicente</dc:creator>
      <dc:date>2024-09-13T23:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: Google Home Scripting Nest Protect</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/644123#M10687</link>
      <description>&lt;P&gt;In response to my own post, I have now been able to use my Nest Cameras and Nest Protects as simple motion detect starters. &amp;nbsp;You must use "device event" and not "device state". &amp;nbsp;For what ever reason the AI Script writer wants them to be "device state" devices and they do not support that, at least for now. &amp;nbsp;Clearly the Scripting would be much easier if there was a clear definition of what all the proper parameters are for each device, proper syntax, etc. &amp;nbsp; The context sensitive drop downs are a big help. &amp;nbsp;It is a good start, so I am much happier with Google Nest than in the past. Now instead of using an external motion detector, I can make use of the existing 15 I suddenly have access to. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 15 Sep 2024 00:48:20 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Protect/Google-Home-Scripting-Nest-Protect/m-p/644123#M10687</guid>
      <dc:creator>justsam</dc:creator>
      <dc:date>2024-09-15T00:48:20Z</dc:date>
    </item>
  </channel>
</rss>

