Question on running Shortcuts via Indigo

[norcoscia]

I’m having a very strange problem running Shortcuts from Indigo.

I issue the shortcut to run from the indigo command line (via trigger) but it does not work - if I wait an hour or so and issue the command again it works and then works fine until the next day. Since I don’t know how to look at what indigo is doing I don’t know how to figure this out.

[MODERATOR NOTE]: moved to the appropriate forum.

[jay (support)]

We need some context:

1. How exactly are you running the shortcut?
2. What is the exact definition of the shortcut?

[DaveL17]

3. Any conditions you have associated with the trigger.

[norcoscia]

Like I mentioned it works after an hour but not the first time each day ?

[berkinet]

Try adding this to the end of your command:

Code: Select all

 >> /tmp/debug.txt 2>&1

Then look at /tmp/debug.text to see if you captured any output.

[norcoscia]

I’m not sure what that is supposed to do but I just did it - did not work - if I wait an hour or so and try again it will work and then work all day, log output below - no change from what I usually see…

May 16, 2023 at 6:03:38 AM
Received INSTEON "Hall Bath Light" on
Received INSTEON "Hall Bath Fan" on
Trigger Hall Bath Music On Soro


Edit - I went and asked my wife (she was a programmer (I’m a hardware guy)) - it does not look like any file was created - so maybe the whole thing including my original command is not getting run for some reason?

[jay (support)]

Are you sure that your Mac's clock is set appropriately? Also, confirm that you have your times set correctly in the conditions tab.

[norcoscia]

Just checked the clock and it is correct - times in action are also OK.

Funny, I just tried it again since it has been about a hour since my first test today and it did not work - tried 3 more times and it did not work (log looked good as normal). Then I removed the
>> /tmp/debug.txt 2>&1 stuff. Went and tried it and it worked perfect — this makes zero sense to me

[ryanbuckner]

Remove the time check condition and run it again, just to rule that out.

[norcoscia]

I’ll do that but Ill have to wait for tomorrow since it started to work now - I have many other triggers like that so that is not likely going to work…

[ryanbuckner]

Not sure what your shortcut does, I would recommend duplicating your Indigo trigger and using it to troubleshoot. (remove conditions, etc..) You'll need to determine if it's the trigger, the conditions, the shortcut, or the device causing the lag.

[norcoscia]

Really hard to troubleshoot - could be some weird OS issue or shortcut issue - so strange that once it starts working it works great until the next day….

[jay (support)]

Just to confirm: when it doesn't work, you DO see the following in your event log?

Code: Select all

Trigger             Hall Bath Music On Soro

If that's the case, then it narrows down the issue since the trigger is firing correctly. It will not log if the conditions were not met, so if it is logging it's getting past the conditions. One way to confirm that is to add another action to the trigger that just logs a message - "shortcut trigger is firing actions" or somesuch.

Assuming the trigger is firing correctly, then either the run shell script action isn't working or the shortcut is failing. You never posted an image of the shortcut definition, so hard to know if there's something in there that may be an issue.

[norcoscia]

The shortcut always works when I run it from within the shortcuts application and the log always looks the same (same messages when it works or does not work). The shortcut uses Soro (which is a way to control Sonos via shortcuts).

I found something in the Soro guide that mentioned directly addressing a Sonos speaker (via IP). I set it up that way but I will not know until tomorrow since once it works it works for the rest of the day.

I have been trying to find a replacement for the Sonos Plug-in since It is not looking good for that to get converted to P3. I hope this works….

[jay (support)]

Ok, well, if you are getting consistent logging then the issue has to be somewhere in the shortcut (or the things used in the shortcut).