<?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 timer stops listening mid command in Speakers and Displays</title>
    <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/timer-stops-listening-mid-command/m-p/775250#M128523</link>
    <description>&lt;P&gt;Timers no longer work properly. This behavior has been for a few weeks now. This affects all speakers in my house (home mini, nest hub). I found a way to get around the problem but it the problem persists. Surely I am not the only one that is annoyed by the requirement to use math to calculate the verbiage required to set a simple timer.&lt;/P&gt;&lt;P&gt;-- commands that don't work anymore&lt;/P&gt;&lt;P&gt;me: set timer 1 hour and 30 minutes. Reply: Alright, 1 hour, starting now&lt;/P&gt;&lt;P&gt;me: set timer 1 hour 30 minutes. Reply: Alright, 1 hour starting now&lt;/P&gt;&lt;P&gt;me: set timer 1 and a half hours. Reply: I don't understand&lt;/P&gt;&lt;P&gt;--commands that work now:&lt;/P&gt;&lt;P&gt;me: set timer 90 minutes. Reply: Alright, 1 hour and 30 minutes, starting now&lt;/P&gt;&lt;P&gt;me:&amp;nbsp; set timer to 1 hour and 30 minutes. Reply: Alright, 1 hour starting now.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; me again (frowning again): add 30 minutes to my timer. Reply: Alright, 30 minutes added to your 1 hour timer&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Dec 2025 20:07:44 GMT</pubDate>
    <dc:creator>nolats44</dc:creator>
    <dc:date>2025-12-22T20:07:44Z</dc:date>
    <item>
      <title>timer stops listening mid command</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/timer-stops-listening-mid-command/m-p/775250#M128523</link>
      <description>&lt;P&gt;Timers no longer work properly. This behavior has been for a few weeks now. This affects all speakers in my house (home mini, nest hub). I found a way to get around the problem but it the problem persists. Surely I am not the only one that is annoyed by the requirement to use math to calculate the verbiage required to set a simple timer.&lt;/P&gt;&lt;P&gt;-- commands that don't work anymore&lt;/P&gt;&lt;P&gt;me: set timer 1 hour and 30 minutes. Reply: Alright, 1 hour, starting now&lt;/P&gt;&lt;P&gt;me: set timer 1 hour 30 minutes. Reply: Alright, 1 hour starting now&lt;/P&gt;&lt;P&gt;me: set timer 1 and a half hours. Reply: I don't understand&lt;/P&gt;&lt;P&gt;--commands that work now:&lt;/P&gt;&lt;P&gt;me: set timer 90 minutes. Reply: Alright, 1 hour and 30 minutes, starting now&lt;/P&gt;&lt;P&gt;me:&amp;nbsp; set timer to 1 hour and 30 minutes. Reply: Alright, 1 hour starting now.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; me again (frowning again): add 30 minutes to my timer. Reply: Alright, 30 minutes added to your 1 hour timer&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Dec 2025 20:07:44 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/timer-stops-listening-mid-command/m-p/775250#M128523</guid>
      <dc:creator>nolats44</dc:creator>
      <dc:date>2025-12-22T20:07:44Z</dc:date>
    </item>
    <item>
      <title>Re: timer stops listening mid command</title>
      <link>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/timer-stops-listening-mid-command/m-p/775292#M128529</link>
      <description>&lt;P&gt;Rebooting the speaker is what I do&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Dec 2025 23:18:11 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Speakers-and-Displays/timer-stops-listening-mid-command/m-p/775292#M128529</guid>
      <dc:creator>SmartHomeH-TAGS</dc:creator>
      <dc:date>2025-12-22T23:18:11Z</dc:date>
    </item>
  </channel>
</rss>

