When using Indigo Touch to control my Indigo Server (using either wifi @ home or WiFi/3G/Edge out on the road), I find that that Touch doesn't always update device status with the Server correctly.

The server is setup using Prism.

Is it possible that my setup is incorrect?

Thank you for any assistance,

Christopher

CGD wrote:When using Indigo Touch to control my Indigo Server (using either wifi @ home or WiFi/3G/Edge out on the road), I find that that Touch doesn't always update device status with the Server correctly.

The server is setup using Prism.

Is it possible that my setup is incorrect?

Thank you for any assistance,

Christopher

We've had no other reports of this behavior - you say it happens both when you're on the local network and through Prism? There isn't any configuration that would change that behavior. Perhaps if you delete and reinstall Indigo Touch? When you see that Touch is out of sync, does the Mac client show something different? Does the log show anything interesting?

We've had no other reports of this behavior - you say it happens both when you're on the local network and through Prism? There isn't any configuration that would change that behavior. Perhaps if you delete and reinstall Indigo Touch? When you see that Touch is out of sync, does the Mac client show something different? Does the log show anything interesting?[/quote]

Jay,

I did as suggested and deleted Indigo Touch (and also turned the iphone off and on) then reinstalled Indigo Touch.

Still have a problem where not all commands are accepted and devices are not updated in Indigo Touch.

Here is an example of the log;
Nov 10, 2009 9:12:21 PM
Webserver - Indigo Touch client connected from 10.0.1.8
Action Group - TurnOffLights
Error - "Master Bedroom Lamp" off; send failed (no acknowledgement)
Sent INSTEON - "Dining Room Lamp" off
Error - "Living Room Lamp" off; send failed (no acknowledgement)
Sent INSTEON - "Media Room Lamp" off

Extra information in case it helps;
1. We setup a headless mini to run Indigo Server.
2. We have two iPhones using Indigo Touch.
3. Sometimes on the choose a server page in Indigo Touch we get "Home Server" and "Home Server (2)" appearing along with "Demo Server". Home Server (2) is a copy of Home Server which we did not add.

Thanks,

Christopher

CGD wrote:Error - "Master Bedroom Lamp" off; send failed (no acknowledgement)
Sent INSTEON - "Dining Room Lamp" off
Error - "Living Room Lamp" off; send failed (no acknowledgement)
Sent INSTEON - "Media Room Lamp" off

These errors are indicating that you're experiencing some signal noise issues. Check out the signal troubleshooting page for common causes and solutions to signal issues.

Are you sure that after these errors, the Indigo Mac client is showing that "Master Bedroom Lamp" and "Living Room Lamp" are off but Indigo Touch is showing that they're on? They should always be in sync, even if they both don't represent the true state of the device (because of the errors above).

CGD wrote:3. Sometimes on the choose a server page in Indigo Touch we get "Home Server" and "Home Server (2)" appearing along with "Demo Server". Home Server (2) is a copy of Home Server which we did not add.

Also, this implies that you have 2 different copies of Indigo running. Have you installed Indigo on more than one Mac? It's probably starting up Indigo automatically on both Macs when you log in so that's why you're seeing 2 copies of the server.

[quote="jay"][quote="CGD"]3. Sometimes on the choose a server page in Indigo Touch we get "Home Server" and "Home Server (2)" appearing along with "Demo Server". Home Server (2) is a copy of Home Server which we did not add.[/quote]

Also, this implies that you have 2 different copies of Indigo running. Have you installed Indigo on more than one Mac? It's probably starting up Indigo automatically on both Macs when you log in so that's why you're seeing 2 copies of the server.[/quote]

Just the one copy running.

If you have had Indigo installed on another Mac, IndigoSERVER might still be running without you knowledge.

If statement above is true, run Activitymonitor on the Mac you´ve previously had Indigo on and find and end process; Indigo Server.

Jay,

You were correct about the second server. I had removed Indigo from one computer and installed it on another but two processes which I believe were installed by Indigo are still running and stopping them doesn't help (as they just restart). The processes are Indigo Server and Python (not sure about this one). How can I remove these?

"Are you sure that after these errors, the Indigo Mac client is showing that "Master Bedroom Lamp" and "Living Room Lamp" are off but Indigo Touch is showing that they're on? They should always be in sync, even if they both don't represent the true state of the device (because of the errors above)." They are not always in sync.

Christopher

CGD wrote:You were correct about the second server. I had removed Indigo from one computer and installed it on another but two processes which I believe were installed by Indigo are still running and stopping them doesn't help (as they just restart). The processes are Indigo Server and Python (not sure about this one). How can I remove these?

Delete the "/Library/Application Support/Perceptive Automation/Indigo 4" folder and reboot.

CGD wrote:"Are you sure that after these errors, the Indigo Mac client is showing that "Master Bedroom Lamp" and "Living Room Lamp" are off but Indigo Touch is showing that they're on? They should always be in sync, even if they both don't represent the true state of the device (because of the errors above)." They are not always in sync.

Hmmm. Haven't seen this happen before. OK, so, when they are out of sync, which one is right - the Mac client or Touch? And if you quit Touch then relaunch it, do the states get updated so they show correctly? Also, is it the states on control pages or the built-in lists or both that are wrong?

Jay,

Sorry about the delay. I really haven't had time to check more into this or see if I have an appliance affecting the insteon.

What I observed was the Touch being out of sync with the Client. However that could be a delay from the touch to the client and back. That also may have changed with the recent server update.

Christopher