<?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: Triggers marked incompatible? in Home Automation</title>
    <link>https://www.googlenestcommunity.com/t5/Home-Automation/Triggers-marked-incompatible/m-p/794456#M63078</link>
    <description>&lt;P&gt;It sounds like the issue might be related to how &lt;STRONG&gt;Homey exposes device capabilities to Google Home&lt;/STRONG&gt;, because when devices are synced through another hub (like virtual switches or Shelly devices), Google Home sometimes recognizes them only as controllable devices rather than valid automation triggers. That’s why they appear as “incompatible” even though they worked fine in SmartThings. Re-syncing the integration or checking the device capability settings in Homey may help, and you can also see a similar discussion here:&amp;nbsp;&lt;A href="https://www.googlenestcommunity.com/t5/Home-Automation/On-Off-or-motion-sensor-trigger-unreliable/td-p/468645" target="_self"&gt;https://www.googlenestcommunity.com/t5/&lt;/A&gt;&lt;A href="https://www.gorillabow.com/" target="_self"&gt;visit&lt;/A&gt;&lt;A href="https://www.googlenestcommunity.com/t5/Home-Automation/On-Off-or-motion-sensor-trigger-unreliable/td-p/468645" target="_self"&gt;-Home-Automation/On-Off-or-motion-sensor-trigger-unreliable/td-p/468645&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 01 Mar 2026 18:49:10 GMT</pubDate>
    <dc:creator>johndeos</dc:creator>
    <dc:date>2026-03-01T18:49:10Z</dc:date>
    <item>
      <title>Triggers marked incompatible?</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Triggers-marked-incompatible/m-p/794277#M63055</link>
      <description>&lt;P&gt;Just switched from Smartthings to Homey and got all synced up.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Problem is that all triggers I want to use are marked as incompatible.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Virtual sockets (ie on/off switches) worked fine with ST but not for homey.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tried other synced devices like Shelly, same thing. "choose a compatible trigger?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How are nothing compatible?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIA&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Br Per&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 28 Feb 2026 13:15:30 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Triggers-marked-incompatible/m-p/794277#M63055</guid>
      <dc:creator>Thyg0d</dc:creator>
      <dc:date>2026-02-28T13:15:30Z</dc:date>
    </item>
    <item>
      <title>Re: Triggers marked incompatible?</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Triggers-marked-incompatible/m-p/794284#M63059</link>
      <description>&lt;P&gt;Just to clarify the triggers are the ones when you create an automation in Google Home.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 28 Feb 2026 14:48:32 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Triggers-marked-incompatible/m-p/794284#M63059</guid>
      <dc:creator>Thyg0d</dc:creator>
      <dc:date>2026-02-28T14:48:32Z</dc:date>
    </item>
    <item>
      <title>Re: Triggers marked incompatible?</title>
      <link>https://www.googlenestcommunity.com/t5/Home-Automation/Triggers-marked-incompatible/m-p/794456#M63078</link>
      <description>&lt;P&gt;It sounds like the issue might be related to how &lt;STRONG&gt;Homey exposes device capabilities to Google Home&lt;/STRONG&gt;, because when devices are synced through another hub (like virtual switches or Shelly devices), Google Home sometimes recognizes them only as controllable devices rather than valid automation triggers. That’s why they appear as “incompatible” even though they worked fine in SmartThings. Re-syncing the integration or checking the device capability settings in Homey may help, and you can also see a similar discussion here:&amp;nbsp;&lt;A href="https://www.googlenestcommunity.com/t5/Home-Automation/On-Off-or-motion-sensor-trigger-unreliable/td-p/468645" target="_self"&gt;https://www.googlenestcommunity.com/t5/&lt;/A&gt;&lt;A href="https://www.gorillabow.com/" target="_self"&gt;visit&lt;/A&gt;&lt;A href="https://www.googlenestcommunity.com/t5/Home-Automation/On-Off-or-motion-sensor-trigger-unreliable/td-p/468645" target="_self"&gt;-Home-Automation/On-Off-or-motion-sensor-trigger-unreliable/td-p/468645&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 01 Mar 2026 18:49:10 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Home-Automation/Triggers-marked-incompatible/m-p/794456#M63078</guid>
      <dc:creator>johndeos</dc:creator>
      <dc:date>2026-03-01T18:49:10Z</dc:date>
    </item>
  </channel>
</rss>

