IFTTT -> Hue recently slow

[milhouse6]

I've had Sighthound sending IFTTT triggers for Philips Hue lights for a long time now and it has been working perfectly. See someone on the porch, flash the living room lights. Immediate and reliable responses. But recently (past 6-8 weeks) the lights are very slow to respond, i.e. anywhere from 2-5 minutes. I know Sighthound is processing as promptly as ever, because sounds and mobile notifications come through immediately. And Hue commands from local apps are still responding promptly as well. I was assuming it was a temporary glitch but I guess it's time to report the problem. Anyone have an explanation for the sudden change or suggestions how to fix? Or an alternate method (maybe there's a local command line app we could run to flash a group)?

TIA

[Devin]

Hello milhouse6,

I'd be happy to check your logs to see if IFTTT triggers are being sent out in a timely manner if you could submit a bug report by going to Help > Report a Problem. It sounds like Sighthound probably isn't the problem but it's always good to eliminate possible causes. If you send a bug report be sure to link to this forum post so we know it is you.

Regards,

-Devin

[milhouse6]

Thanks Devin. IFTTT continues to be slow so I thought I'd switch to local triggering with WinHue, but I'm not having much luck there either. : (

With Sighthound 3.0 build 15984 on Windows 10
I've created a batch script:

Code: Select all

C:\Program Files (x86)\WinHue 3\whc.exe" -ip:192.168.x.x -l:3 -alert:lselect
exit

Running cmd.exe -k START path/to/batch.bat works when I click test, but does NOT trigger on event detection. Other triggers (i.e. mobile app notification) do execute.

Here's what else I've tried:

• Trying to run whc.exe directly doesn't seem to pass any arguments along when I click test -- it just flashes a command window briefly.
• have tried both .bat and .cmd (both work with test, neither execute on event)
• Doesn't work after having used a .bat->.exe converter as another forum post recommended (works when I click test using cmd /k start path/to.exe but not as path/to.exe - same behaviour as .bat)
• MS-DOS 8.3 naming changes nothing

There must be something simple I'm missing. TIA