<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Alexa+ (Alexa Plus) breaks TRIGGERcmd custom actions in new routines, while existing routines still work]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I've been using TRIGGERcmd with Alexa for a long time to execute commands on my Windows PC through Alexa routines. Everything worked perfectly until Alexa+ was introduced.</p>
<p dir="auto">My setup uses a single TRIGGERcmd command named <code>parametro</code>, which executes a batch file (<code>alexa_actions.bat</code>) and accepts parameters to determine which action to perform.</p>
<p dir="auto">For example, this is the custom action I use in my Alexa routines:</p>
<p dir="auto"><strong>Spanish (my actual configuration):</strong></p>
<pre><code>preguntarle a Ejecuta Comando ejecutar "parametro" con parametro modojuego
</code></pre>
<p dir="auto"><strong>English equivalent:</strong></p>
<pre><code>ask Trigger Command to run "parametro" with parameter modojuego
</code></pre>
<p dir="auto">The parameter <code>modojuego</code> is passed to my batch file as <code>%1</code>, which then executes the corresponding action.</p>
<h3>The issue</h3>
<p dir="auto">All my existing Alexa routines created before Alexa+ <strong>continue to work perfectly</strong>, including those that pass parameters to TRIGGERcmd.</p>
<p dir="auto">However, when I create a new routine using the exact same custom action, Alexa+ fails to execute it.</p>
<p dir="auto">I've tested the following:</p>
<ol>
<li>Creating a new routine using the same Spanish command structure as before.</li>
<li>Copying and pasting the exact custom action from an existing, fully functional routine into a new one.</li>
<li>Trying alternative Spanish phrasing.</li>
<li>Trying the English command syntax.</li>
<li>Invoking the TRIGGERcmd skill directly by voice, without using a routine.</li>
</ol>
<p dir="auto"><strong>All these attempts fail</strong>, while the original routines continue working normally.</p>
<p dir="auto">Alexa responds with messages such as:</p>
<ul>
<li>"I can't execute that command. There seems to be an error with the request."</li>
<li>"I can't help you with that right now."</li>
<li>"This request is not available."</li>
</ul>
<h3>Expected behavior</h3>
<p dir="auto">New Alexa routines should be able to invoke TRIGGERcmd and pass parameters just like existing routines.</p>
<h3>Actual behavior</h3>
<p dir="auto">Only routines created before Alexa+ continue to execute successfully. New routines fail even when their custom actions are identical to those in working routines.</p>
<p dir="auto">This suggests that Alexa+ may be handling third-party skill invocations differently, while preserving compatibility with previously created routines.</p>
<h3>Question</h3>
<p dir="auto">Is this a known compatibility issue with Alexa+? Is there any workaround that would allow me to continue using the original TRIGGERcmd skill with parameters in new Alexa routines?</p>
<p dir="auto">I'd prefer to keep my current setup rather than migrate to the Smart Home skill, since I use a single command with multiple parameters to control different PC actions.</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://www.triggercmd.com/forum/topic/3396/alexa-alexa-plus-breaks-triggercmd-custom-actions-in-new-routines-while-existing-routines-still-work</link><generator>RSS for Node</generator><lastBuildDate>Mon, 16 Nov 2026 23:46:25 GMT</lastBuildDate><atom:link href="https://www.triggercmd.com/forum/topic/3396.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 16 Nov 2026 21:37:48 GMT</pubDate><ttl>60</ttl></channel></rss>