I've since upgraded the phone to iOS 6 and now after sending a finite number of commands to the panel, the panel seems to stop responding. The display in the mobile link changes appropriately, i.e. it shows me that I have added "arm stay" or "disarm" etc. to the command queue, but the command never reaches the panel. I am not sure whether the command fails to reach the Eyez-On server from the mobile link, or the command fails to reach the panel from the Eyez-On server. Since I can restore operation (see below) I would guess that the link between the 2DS and the Eyez-On server is not failing, and something has changed in the browser and/or its interaction with the mobile link.
I can restore operation by doing the following on the phone (running iOS 6):
- - If Safari is open in the foreground, press the home button to get out of Safari.
- Double click the home button to display the running apps.
- Scroll left/right to find Safari.
- Press and hold the Safari icon to show the red X in the corner of the icon.
- Press the red X to close Safari.
- Press the home button to get out of app-management (wiggly) mode.
- Go into phone settings (gear icon).
- Enter Safari settings.
- Clear history.
- Clear cookies and data.
- Enter Advanced settings for Safari.
- Enter Website Data settings.
- Clear all website data.
- Exit phone settings.
- Restart Safari.
- Reload mobile link for 2DS, log in etc. to get to the interface for the alarm panel.
- Access to controlling the alarm panel is now restored.
When I say the panel stops responding, I mean after I enter a command, I wait several minutes, 5-10 minutes, and there is no response from the panel. I seem to remember that the polling interval for the 2DS is about 2 minutes -- the 2DS looks at the Eyez-On server every 2 minutes. This info is from doing some troubleshooting with one of the Envisalink engineers earlier, and using Wireshark.
Is there really something that has changed between iOS 5.x and iOS 6 that is interfering with the control of the alarm panel using the 2DS? Is anyone else seeing similar behaviour? The only thing that has changed on my end is the upgrade to iOS 6.
Since I can restore operation by resetting Safari, I don't think the 2DS needs rebooting.
I pre-ordered an iPhone 5, and will be running iOS 6 on it too. Hopefully I/we can get this problem solved.
Kevin