I'm currently developing an application that triggers a schedule update with a UISwitch. Unfortunately, I often get the following error: "Error Domain=com.philips.hue.sdk Code=92 \"The operation couldn\U2019t be completed. (com.philips.hue.sdk error 92.)\""
I realized that I systematically get the error when I tap the switch approximately just before the heartbeat occurs. I feel that there are interferences between the heartbeat and the calls the the PHBridgeSendAPI method calls.
In the first thing, I would expect that the SDK manages all this. It should queue all the bridge activities one after the other. Is it a bug or I miss something?
I also tried many things to get around the issue:
I tried to stop the heartbeat with [UIAppDelegate.phHueSDK disableLocalConnection] before calling updateScheduleWithSchedule and restart it with [UIAppDelegate.phHueSDK enableLocalConnection] in the completion handler of [BridgeSendAPI updateScheduleWithSchedule... but I got the same result.
I tried with [UIAppDelegate.phHueSDK disableCacheUpdateLocalHeartbeat:YES] and ...NO with the same result.
I tried to add some delay with [NSThread sleepForTimeInterval:1.0f] and [[NSRunLoop currentRunLoop] runUntilDate:[NSDate dateWithTimeIntervalSinceNow:1]] after the call to [UIAppDelegate.phHueSDK disableLocalConnection] and before the call to [UIAppDelegate.phHueSDK enableLocalConnection] with the same result. I tried many length of delay.
I also tried to move things around like calling [UIAppDelegate.phHueSDK disableLocalConnection] before initializing PHBridgeSendAPI *myBridgeSendAPI but without any effect.
The only way I found to get rid of the error is to stop the heartbeat. Unfortunately, I need it.
Hi,
I'm currently developing an application that triggers a schedule update with a UISwitch. Unfortunately, I often get the following error: "Error Domain=com.philips.hue.sdk Code=92 \"The operation couldn\U2019t be completed. (com.philips.hue.sdk error 92.)\""
I realized that I systematically get the error when I tap the switch approximately just before the heartbeat occurs. I feel that there are interferences between the heartbeat and the calls the the PHBridgeSendAPI method calls.
In the first thing, I would expect that the SDK manages all this. It should queue all the bridge activities one after the other. Is it a bug or I miss something?
I also tried many things to get around the issue:
[UIAppDelegate.phHueSDK disableLocalConnection]
before callingupdateScheduleWithSchedule
and restart it with[UIAppDelegate.phHueSDK enableLocalConnection]
in the completion handler of[BridgeSendAPI updateScheduleWithSchedule...
but I got the same result.[UIAppDelegate.phHueSDK disableCacheUpdateLocalHeartbeat:YES]
and ...NO
with the same result.[NSThread sleepForTimeInterval:1.0f]
and[[NSRunLoop currentRunLoop] runUntilDate:[NSDate dateWithTimeIntervalSinceNow:1]]
after the call to[UIAppDelegate.phHueSDK disableLocalConnection]
and before the call to[UIAppDelegate.phHueSDK enableLocalConnection]
with the same result. I tried many length of delay.[UIAppDelegate.phHueSDK disableLocalConnection]
before initializingPHBridgeSendAPI *myBridgeSendAPI
but without any effect.The only way I found to get rid of the error is to stop the heartbeat. Unfortunately, I need it.
Can anybody help me with this?
My method code is below.
Thank you.