› Alarm Engine Support Forum › Touchscreen Beta Issues
- This topic has 10 replies, 3 voices, and was last updated February 10, 2025 at 5:08 pm by Wesley Perry.
-
AuthorPosts
-
January 30, 2025 at 6:52 pm #8758JOHN WADE
Mike, you may already be aware of these. When changing alarm status from the touchscreen stay/away/disarm, the conventional keypads immediately show the change but the touchscreen does not until you navigate away from the home screen and then come back. It appears that the touchscreen does not poll the panel after a user or system initiated status change.
Additionally, if on the home screen and you touch the large status shield indicator, the touchscreen seems to get confused, then pops up a dialog box offering status change options, then reboots.
Finally, when entering credentials to link the touchscreen, it will say invalid credentials, but then re-entering the same data results in a connection.
January 30, 2025 at 7:09 pm #8760Michael BurrellJohn,
One of the items we are working on is making the set up a little cleaner. The issue you are seeing I believe is due to the settings it in the Network Devices not being configured. Connect with the mobile app and navigate to Network Devices. Then click on the touchscreen and view the settings.
It should look similar to this:
In the screen shot, I have two areas. Just confirm that you have the area selected in the blue box. You can also Name it if you like. The other settings in this area are not active yet, we are still working to implement these.
Once you save the settings, power cycle the touchscreen and it will reconnect with the proper Area selection. This will allow the broadcasts to be displayed as they come in.
Again, please note it is still a work in progress as we are continuing to finalize the settings, sounds, sleep options, quite time, screen saver, etc. I will ping this thread when we release the next build.
FYI, if you want to get to the touch screen settings (display, Wifi, Etc) they are hidden in the beta builds since we do not have the login information set up yet from the main menu. To access them, touch and hold on the time and date in the top right, this will give you the touch screen settings. If you tap the time and date you get the installer update page. This is where future updates will appear.
Thanks,
Mike
February 10, 2025 at 12:23 pm #8790Wesley PerryI wanted to note that i also have the same status poling issue on the E27 T7S’. When you arm/stay/disarm the touchscreens do not show the change unless i go to another page flip via the menu and come back. Goes for all 3 (2 poe, 1 wifi). If i fix 1, i need to do the same on all the others to show the accurate status. This seems somewhat crucial do have working properly.
I also have to type in my code twice 90% of the time before it takes on a arm/stay/disarm.
Hopefully that info helps diagnose some beta issues
February 10, 2025 at 1:35 pm #8791Michael BurrellWesley,
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!
February 10, 2025 at 2:26 pm #8792Michael Burrell@Wesley – I also should note that our most recent beta build for the 7TS is 0.13.006. If you do not have this update, please let me know your serial number and I will be sure you have it.
February 10, 2025 at 3:15 pm #8793Wesley PerryThis is great info. I am on 0.13.006 so I will try your save method and see how it works. EDIT : The polling is fixed with that recommendation to re save panels in app.
Also great info on the double code entry, My system is not fully finished but i disabled the zones I am working on. So i am surprised on the double entry but I will keep playing with it and when me system is fully operational ill recheck it all.
Last questions, for my info. I see you said they do not support sound yet? Does that mean the chime on screens are not working yet? Will the 7″ screen support sound going forward? Such as entry chimes or tripping zones?
Thank you for the response! Its appreciated
February 10, 2025 at 3:26 pm #8794Michael BurrellWesley,
Let me know if the save method works, we are still in the mist of digging into this and it seems that it resolves it most of the time but we have some that didn’t have the issue at all. Feels like it is timing related.
Correct, there are no sounds implemented in the touchscreen for E27 as of yet. We are working on this as part of final stages to get this released. Here are all the items that are being worked on at the moment for this application on the touch screen: Sounds (chimes, alarms, entry/exit delays), Sleep Mode, Screen Saver Mode (Screen off when idle), Silent Entry/Exit, Quite Time, Pin to Lock or Unlock screen (this might not make release), Hide Automation Menu, Enable Emergency Alarms, error handling (being able to properly recover from different situations). I am sure I am missing some things, but this is what we are pushing to complete in order to release this offering.
If you have any additional questions, I am happy to assist.
Thanks,
Mike
February 10, 2025 at 3:28 pm #8795JOHN WADEMike, will the touchscreens automatically update to the latest firmware versions?
February 10, 2025 at 4:02 pm #8798Wesley PerryAll that sounds great mike. And yes the Save function fixed my polling issue on all panels. Do i have to do that often? Or just when i make adjustments?
February 10, 2025 at 4:20 pm #8800Michael BurrellWesley – You only have to do that after the first onboarding of the device after you “link” it. If you were to delete it and add it back, I assume it would require a save again. During linking it is getting the connection, but does not know what Area it is associated with so it does not respond to the broadcasts from the control with area specific data. Like arming, zones opening, etc. When you go to the page, it requests the data. So that is why it works “partially”. We believe the is a timing or conflict issue when it is linking that doesn’t apply the defaults properly. Engineering is looking at a fix for it.
John – It does not auto update. Click on the “time/date” on the home page. This will show the update at the top of the page if there is one for it. This is not the final method, just what we have in place during the development.
February 10, 2025 at 5:08 pm #8801Wesley PerryMike, Thanks again for the help today. Cant wait for full release, I sell the heck out of elk M1 and starting to push e27. Keep up the good work!
-
AuthorPosts
- You must be logged in to reply to this topic.