Omnistat Schedue programming

[cantrels]

I'm wondering, is there any means to adjust the schedule programming for the Omnistat thermostat schedule (the four temperature points by weekday) via a software interface? My background is with the NEST thermostat, that had a web-accessible interface for setting schedule times by date.
 
While it's certainly a breeze (no pun intended) to control the thermostat in real-time remotely via software (even off-site), I'm interested in the ability to be able to modify or set the schedule times and temps without having to walk over and adjust the settings at the thermostat itself.
 
I was looking at Haiku for this, but my understanding is each time/day would require a different user setting, which would take 56 of them (2 temps x 4 times x 7 days), and that requires too many user settings.
 
Thanks in advance for any assistance.

 

[Desert_AIP]

Is this a standalone system or integrated with an HAI panel?
 
You can change setpoints via HAI programming in PCAccess and be as finite as you desire with respect to time of day, date and setpoint among other items.
You can directly input numbers without using user settings.
 
Even with user settings, is it not possible for you to reuse the registers? 
Do you actually have 56 different temperature setpoints?  Or are there overlaps?
So a user setting of 70 degrees should be able to be used anytime you want to set to 70, etc.
Or are you modifying the user setting itself?
If that is the case, why not have a standing setpoint and use the user setting to modify it if desired?

 

[cantrels]

This is an integrated thermostat, it's not standalone. And you make a good point, if you have commonality in your schedule settings, you could use a fixed setpoint (i.e. one setting for 81 degrees, and use it 7 times for the "morning away" setting for each day). That would certainly reduce the overall settings needed.
 
I guess my question was more from a design standpoint, what were people doing to maintain the 4 setpoints per day schedule, rather than treating each possible setpoint as a different code interaction. 
 
I'll look into PC Access, and thanks for the feedback.

 

[Desert_AIP]

I use the occupancy settings, day, night, away, vacation and make time of day modifications to them.
 
I have a timed transition from night mode to day mode so that the day time temperatures automatically start at a user setting called "wakeup time".
I have a similar user setting called "bedtime" to change the setpoints to the night settings even if the security system isn;t armed in night mode.
 
I also have a timed increase in setpoints to rewarm the house approximately an hour prior to arrival. 
The system is armed in away mode, which has more severe setbacks, and the setpoints are changed to the day setpoints an hour before we retun from work.
 
After playing with the timed programming of the T-stat, I changed to the occupancy mode.
It seems more intuitive, especially when using the "auto" mode of the HVAC system.