I'm seeing a delay, or non-response in some cases, between when a profile is activated and when IC responds. I general keep my apps closed on my phone, so I find that IC will respond more consistently after I open the IC phone app. Though even if I leave it open the tasker profile doesn't always activate the scene or device it's supposed to. Plus it kinda defeats the convenience if I have to open and wait for the IC app to load before triggering autovoice. I noticed a similar issue with IC app scene widgets. Some times I hit the widget and it doesn't do anything. Anyway to improve the response time? Would it be possible to keep the IC app running in the background without killing the battery?
Anyone else seeing this?
Tasker Plugin Response Time
- 75 Views
- Last Post 09 August 2014
tnamey
posted this
15 January 2014
Ryan-Scott
posted this
15 January 2014
I'm seeing a delay, or non-response in some cases, between when a profile is activated and when IC responds. I general keep my apps closed on my phone, so I find that IC will respond more consistently after I open the IC phone app. Though even if I leave it open the tasker profile doesn't always activate the scene or device it's supposed to. Plus it kinda defeats the convenience if I have to open and wait for the IC app to load before triggering autovoice. I noticed a similar issue with IC app scene widgets. Some times I hit the widget and it doesn't do anything. Anyway to improve the response time? Would it be possible to keep the IC app running in the background without killing the battery?
Anyone else seeing this?
I don't see the delay on my end... for what it's worth, you shouldn't need to open InControl prior to it working either, though if you do, it should still be OK.
Do you use Cloud or direct connect? How long does it normally take before you see your list of devices show up when you open the app up the first time?
tnamey
posted this
15 January 2014
I have my phone setup using the cloud and a tablet using direct. I have the issue on both. Cloud usually takes around 5 seconds to load the devices after it's running. Direct is a little quicker. I'll be honest I have to hit the refresh button every once and a while because only some devices will show up from the start.
Sometimes I'll activate a Tasker profile and only see the "scene activated" text when I bring up the IC app 30+ seconds later.
monkey-magic
posted this
15 January 2014
I must admit I get similar results but it isn't consistent. I feel mostly when IC app is connected and showing the devices Tasker works fine. If IC is closed it doesn't always respond. I think it's similar to when I open IC not all devices are there and sometimes it takes a few seconds to update/refresh. That seems be when Tasker doesn't work, those seconds when IC isn't connected.
I'm on direct connect, I find that a bit quicker, esp when I'm on the home WiFi.
Josh
Plasmon
posted this
09 August 2014
On my side, I've realize that tasker isn't able to interact or really slow if InControl app is still running in the background.
My quick solution was to kill InControl just before activating the scene from tasker.
1 - kill App; InControl HA
2 - InControl Action ; Activate scene ... or Power ...
Maybe it depends on the version, but in your case you could do the opposite in tasker :
1 - Launch App; InControl HA
2 - InControl Action ; Activate scene ... or Power ...
App versions : Version 3.0.27
InControl Free edition : 3.114.5252.25392
Regards
