I promised myself that I would get around to figuring out how HS .ini files work after getting my system mostly set up - it was not a high priority. 50 or so scripts later, the time has come, and I would like to get the advice of the HS experts here.
I have data like passwords for alarm arming/disarming and access to sensitive HSTouch screens, as well as phone numbers that HS uses for text alerts that will definitely go into the .ini file. But I also have lots-o-configuration info, all editable via HSTouch screens, that is currently stored in virtual devices, like:
Thanks in advance for any advice!
Jeff
I have data like passwords for alarm arming/disarming and access to sensitive HSTouch screens, as well as phone numbers that HS uses for text alerts that will definitely go into the .ini file. But I also have lots-o-configuration info, all editable via HSTouch screens, that is currently stored in virtual devices, like:
- Which tablets/phones can disarm the alarm system
- Which tablets/phones can control media - the screens automatically change when the source changes either by remote or Alexa (ie: DirecTV, Game, Blu-ray, etc)
- Tablet Names, which ones chime when a door/window opens, whether they default to a standard template or an LCARS template at boot-up. Blah, blah, blah...
Thanks in advance for any advice!
Jeff
Comment