Strategic questions about HomeVision

[Julian Driver <Julian@xxxxxxx>]

We have been messing about with HV for a couple of weeks now, and are
successfully making it do the sorts of things we want it to do (control
heating, lighting at this stage). The big question before we go any
further is "What is the best overall structure for the files, so as to
work efficiently, but also be maintainable?"

On the one hand do people have lots of files which they download as the
need arises e.g.. Weekend, workday, away for hols, home for hols etc. Or
do they use flags or extensively use macros?

One of the problems we have encountered is that as we experiment with
the software we leave a trail of dead ends in our wake which are
difficult to delete in certain cases (scheduled or periodic events for
example, where only the last is easy to delete). It is also very complex
to keep tabs on what is happening as we cannot sort scheduled or
periodic events. How do other users cope with this?

Perhaps the answer is to use other software to set up HV. Has anybody
else tried this, if so what? (my other pet dislike of the HV s/w is the
logging, as a non programmer I find hex cumbersome, a CSV file would be
much friendlier!)
--
Julian Driver

------------------------------------------------------------------------
A shopper’s dream come true! Find practically anything on earth at eBay!
Come and browse the more than 2 million items up for bid at any time.
You never know what you might find at eBay!
http://clickhere.egroups.com/click/1140

-- Create a poll/survey for your group!
-- http://www.egroups.com/vote?listname=ukha_d&m=1