Wesley,
Go to the network devices in the mobile app, then navigate to the specific touchscreen settings and “save” the data again. This should resolve the polling issue. We are addressing a bug that prevents the touchscreen from syncing when it is first onboarded. Saving the settings again seems to resolve this. You will need to do this for each screen’s settings. This bug will be fixed in a future update.
Regarding the issue of having to enter the code more than once to arm the system, I believe it is due to an active trouble condition on the control. On the keypad, trouble conditions must be acknowledged before proceeding, but in the mobile applications, this is not as clear. What is happening is that the first PIN entry clears the trouble beep, while the second PIN entry performs the intended function.
This requirement has been corrected in an internal firmware update that will be released before we move the touchscreen out of beta. That firmware includes numerous other updates and changes that need to be thoroughly tested before publication. In this new firmware, mobile applications will no longer require a PIN entry to silence trouble conditions before arming. When an arming command is sent from an application, the system will arm even if a trouble condition is present. Trouble alerts are restored after arming/disarming, so this can feel like it is always an issue.
Since the touchscreen does not currently support sound, you may not be aware that it is beeping. If a trouble condition persists, it will continue to cause issues with the touchscreen unless you silence it from the troubles page (bell icon at the top) before arming.
Let me know if you need further clarification!