Version 2.2.8 was just submitted to Google Play to fix a few issues people have reported.
Although issues can happen time to time, and we don’t always pick them up until it’s publicly released. Even when issues do come up, we then need to troubleshoot to find why it’s happening and most of the time we can’t reproduce the same issue on our devices.
This new update fixes the following reported issues:
Starting Service Issue
A few people reported that the loading screen got stuck on a message that showed ‘Starting Service’.
This issue was caused by an Google API that for some reason stopped working. (Thanks Google)
This issue was not picked up by our development devices due to them having our master Google Play account signed in to them.
Many have reported that ever since version 2.2.6 they could no longer connect to there panels.
This issue was due to the app connecting to the M1XEP (Ethernet Module) with the secure port but with no username or password.
Whenever connecting over the internet you should use the secure port with a username and password. Without a username or password enabled is like having the front door unlocked, but not open.
In version 2.2.6 the connection driver was re-written, and it required the secure port to have an username and password enabled. We never thought that people would use the secure port without a username and password!
Version 2.2.7 had a quick fix to fix this issue, but we forgot a section in the code which only half fixed the issue. Version 2.2.8 should hopefully fix the issue completely.
If you run into any issues, then please contact our support and we will run some troubleshooting with you to fix the issue you have.
Although some left negative feedback (we hope you can change that now we pushed out this update), we thank for the rest of you being patient while we look into the issue and fix it for you.