<?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: Heads up: Philips Hue Change Impacting Scripted Automations! in Home Automation</title>
    <link>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/593518#M44361</link>
    <description>&lt;P&gt;If you don't have Nest automations programmed to read data from Philips Hue motion sensors, then you probably don't care.&amp;nbsp;&amp;nbsp;&lt;A href="https://labs.meethue.com/formulas/huelabs/temperature-monitor" target="_blank"&gt;https://labs.meethue.com/formulas/huelabs/temperature-monitor&lt;/A&gt;&amp;nbsp; Sounds like Hue developers changed a variable name.&lt;/P&gt;</description>
    <pubDate>Tue, 06 Feb 2024 23:49:39 GMT</pubDate>
    <dc:creator>Wherdgo</dc:creator>
    <dc:date>2024-02-06T23:49:39Z</dc:date>
    <item>
      <title>Heads up: Philips Hue Change Impacting Scripted Automations!</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/592951#M44340</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hey everyone,&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;We wanted to keep you in the loop about some recent changes related to Philips Hue sensors that might impact your scripted automations. Philips Hue has updated their sensor device configuration to use the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;I&gt;TemperatureSetting&lt;/I&gt;&lt;/STRONG&gt;&lt;SPAN&gt; trait (previously this used &lt;/SPAN&gt;&lt;STRONG&gt;&lt;I&gt;TemperatureControl&lt;/I&gt;&lt;/STRONG&gt;&lt;SPAN&gt;).&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Scripted automations containing the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;I&gt;TemperatureControl&lt;/I&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp; trait might start to fail when the Philips Hue changes go live. To get your scripted automations working again, you’ll need to update your scripts to use the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;I&gt;TemperatureSetting&lt;/I&gt;&lt;/STRONG&gt;&lt;SPAN&gt; trait instead. After you update your script to use &lt;/SPAN&gt;&lt;STRONG&gt;&lt;I&gt;TemperatureSetting&lt;/I&gt;&lt;/STRONG&gt;&lt;SPAN&gt;, you’ll be able to use ambient temperature as a starter or condition again. We recommend using autocomplete to help you make these changes so your script validates and can be run.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;We apologize for the inconvenience, please use the comments below to provide feedback and keep us aware of anything else you are encountering with your scripts once these changes are live.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Thank you,&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;The Google Nest Team&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Feb 2024 21:15:12 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/592951#M44340</guid>
      <dc:creator>GoogleNestTeam</dc:creator>
      <dc:date>2024-02-05T21:15:12Z</dc:date>
    </item>
    <item>
      <title>Re: Heads up: Philips Hue Change Impacting Scripted Automations!</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/593407#M44357</link>
      <description>&lt;P&gt;I don't think I have Temperaturesetting on my device , so can you please explain what it is?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Feb 2024 19:30:32 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/593407#M44357</guid>
      <dc:creator>JeremyJoe82</dc:creator>
      <dc:date>2024-02-06T19:30:32Z</dc:date>
    </item>
    <item>
      <title>Re: Heads up: Philips Hue Change Impacting Scripted Automations!</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/593518#M44361</link>
      <description>&lt;P&gt;If you don't have Nest automations programmed to read data from Philips Hue motion sensors, then you probably don't care.&amp;nbsp;&amp;nbsp;&lt;A href="https://labs.meethue.com/formulas/huelabs/temperature-monitor" target="_blank"&gt;https://labs.meethue.com/formulas/huelabs/temperature-monitor&lt;/A&gt;&amp;nbsp; Sounds like Hue developers changed a variable name.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Feb 2024 23:49:39 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/593518#M44361</guid>
      <dc:creator>Wherdgo</dc:creator>
      <dc:date>2024-02-06T23:49:39Z</dc:date>
    </item>
    <item>
      <title>Re: Heads up: Philips Hue Change Impacting Scripted Automations!</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/594413#M44453</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/509925"&gt;@JeremyJoe82&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/340797"&gt;@Wherdgo&lt;/a&gt;&amp;nbsp;is correct. If you haven't intentionally created a scripted automation using either of these traits, then the changes most likely won't impact you.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Feb 2024 21:34:08 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/594413#M44453</guid>
      <dc:creator>kelanfromgoogle</dc:creator>
      <dc:date>2024-02-08T21:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: Heads up: Philips Hue Change Impacting Scripted Automations!</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/595387#M44560</link>
      <description>&lt;P&gt;okay no problem, fix it as possible&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 11 Feb 2024 21:48:19 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/595387#M44560</guid>
      <dc:creator>davidlily343</dc:creator>
      <dc:date>2024-02-11T21:48:19Z</dc:date>
    </item>
    <item>
      <title>Re: Heads up: Philips Hue Change Impacting Scripted Automations!</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/595388#M44561</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Don't worry,&lt;/SPAN&gt;&lt;SPAN&gt; it's an easy fix:&lt;/SPAN&gt;&lt;SPAN&gt; just swap "TemperatureControl" to "TemperatureSetting" in your scripts.&lt;/SPAN&gt;&lt;SPAN&gt; Autocomplete can help you out too!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 11 Feb 2024 21:55:09 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Heads-up-Philips-Hue-Change-Impacting-Scripted-Automations/m-p/595388#M44561</guid>
      <dc:creator>davidlily343</dc:creator>
      <dc:date>2024-02-11T21:55:09Z</dc:date>
    </item>
  </channel>
</rss>

