<?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 Breaking changes to device.command.ActivateScene in Home Automation</title>
    <link>https://www.googlenestcommunity.com/t5/Home-Automation/Breaking-changes-to-device-command-ActivateScene/m-p/672646#M51174</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To Whom It May Concern on the Google Home Dev Team:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please reverse the breaking changes that were recently made to the&amp;nbsp;&lt;A href="https://developers.home.google.com/automations/schema/reference/entity/sht_device/activate_scene_command" target="_self"&gt;ActivateSceneCommand&lt;/A&gt; function - you have ruined at least a dozen of my automations which were, until yesterday, functional for the past year. The Google Home Developer Center example script for&amp;nbsp;ActivateSceneCommand is incorrect: scenes are not devices that are assigned to rooms - they are just scenes. For context, I have been using the script editor to activate SmartThings scenes - but someone on the GH Dev Team has broken this feature.&amp;nbsp; Please promptly restore it back to working order.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;P.S.&amp;nbsp;There isn't a topic label option for Automations, so this topic does not specifically belong in the "speakers and displays" category.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Jan 2025 15:41:06 GMT</pubDate>
    <dc:creator>DWB1973</dc:creator>
    <dc:date>2025-01-27T15:41:06Z</dc:date>
    <item>
      <title>Breaking changes to device.command.ActivateScene</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Breaking-changes-to-device-command-ActivateScene/m-p/672646#M51174</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To Whom It May Concern on the Google Home Dev Team:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please reverse the breaking changes that were recently made to the&amp;nbsp;&lt;A href="https://developers.home.google.com/automations/schema/reference/entity/sht_device/activate_scene_command" target="_self"&gt;ActivateSceneCommand&lt;/A&gt; function - you have ruined at least a dozen of my automations which were, until yesterday, functional for the past year. The Google Home Developer Center example script for&amp;nbsp;ActivateSceneCommand is incorrect: scenes are not devices that are assigned to rooms - they are just scenes. For context, I have been using the script editor to activate SmartThings scenes - but someone on the GH Dev Team has broken this feature.&amp;nbsp; Please promptly restore it back to working order.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;P.S.&amp;nbsp;There isn't a topic label option for Automations, so this topic does not specifically belong in the "speakers and displays" category.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jan 2025 15:41:06 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Breaking-changes-to-device-command-ActivateScene/m-p/672646#M51174</guid>
      <dc:creator>DWB1973</dc:creator>
      <dc:date>2025-01-27T15:41:06Z</dc:date>
    </item>
  </channel>
</rss>

