RE: [EPODS] Development - FIXED!!!!

[andy.powell@xxxxxxx]

>erm what benefit would this approach be over the web page view of
homeseer ?

Well, full screen house status (Pictures maybe) , Automatic alerts/alarms
integration with my mp3 player (extra interface in the application) my own
layout


>or even a custom web page developed through the homeseer COM object ?

Although I've :

1. Written my own webserver that communicates with
Homeseer with no problems
2. Got PWS working with Homeseer with no problems
3. been able to tell if the machine I'm connecting
with is an EPODS or PC/Linux box etc

it isn't the best or quickest way to get data - it's fine for remote
access but we're talking local access - You expect a web browser to take a
little time to get the info. *I* expect my EPODS to be as quick as a
screen refresh (or there abouts). The data transfer has got to be quicker.
Images would stored locally (EPODS) and you could probably expect
something like (and these are rough figures - I haven't worked out the
full data structure yet):

Header : 10 bytes
Body     : 512 bytes
Checksum: 8 bytes

the Homeseer logo by comparison is 13kb!

It's clear that a lot more thought needs to go into the development but
HTTP is pretty slow...

A.







"Henderson, Darren" <Darren.Henderson@xxxxxxx>
23/01/2001 16:25
Please respond to ukha_d


To:     "'ukha_d@xxxxxxx'" <ukha_d@xxxxxxx>
cc:
Subject:        RE: [ukha_d] [EPODS] Development - FIXED!!!!

erm what benefit would this approach be over the web page view of homeseer
?

or even a custom web page developed through the homeseer COM object ?

Darren

> -----Original Message-----
> From: andy.powell@xxxxxxx
> [mailto:andy.powell@xxxxxxx]
> Sent: 23 January 2001 15:12
> To: ukha_d@xxxxxxx
> Subject: Re: [ukha_d] [EPODS] Development - FIXED!!!!
>
>
> Vince,
>
> Nice n simple  - I already have an app that talks to Homeseer
> so I can
> incorporate that into the WSOCK app on the PC side...
>
> I've been having a think about this and this is what I've come up with
>
>
> 1. Server side app polls Homeseer once every 2-3 seconds and
> stores data
> in its memory (arrays??) unless a specific command is
> received from the
> EPODS (on/off/brite/dim etc)
>
> 2. EPODS polls the server every 4-5 seconds to get status of
> changed items
> unless it sends an on/off/bright/dim. If a command is sent
> then all the
> changed data is refreshed.
>
> 3. The icons/images should be stored locally (storage card)
> on the epods
> to reduce dataflow. It sohuld be pretty easy to update them
> using active
> sync other the network.
>
> 4. Security shouldn't be an issue with wireless encryption. (probably
> should use 128 bit)
>
> The  times about are rough - I haven't tested to see what effect this
> would have on the server (load) but it's done like this
> because you may
> well have more than 1 epods on the network!!  :-))
>
> The WSOCK app seems to send data in blocks of 8192 bytes
> which should be
> more than enough to hold all the info needed (unless you want
> text strings
> sent)
> It seems to work out at about 8192 bytes /5sec with a serial
> cable PPP
> link so this should improve when going wireless.
>
>
> A.
>
>
>
>
>
> "vince" <vince@xxxxxxx>
> 23/01/2001 15:49
> Please respond to ukha_d
>
>
>         To:     ukha_d@xxxxxxx
>         cc:
>         Subject:        Re: [ukha_d] [EPODS] Development - FIXED!!!!
>
> > Look at the WSOCK example - there is a (Full) Vb version
> and a Version
> > for
> > the EPODS - could be the start of a Client server Home Automation
> > Interface from EPODS!!!
> >
> > A.
>
> Andy,
>
> Played with that last night, had the Pod talking to my
> desktop. Now if
> only Homeseer had a socket interface.
>
> Vince
>
>
>
> ______________________________________________________________
> __________
> This message has been checked for all known viruses, by Star
> Internet,
> delivered through the MessageLabs Virus Control Centre.
> For further information visit:
> http://www.star.net.uk/stats.asp
>
>
>
>
>
>
>
>
>
> *********************** DISCLAIMER **************************
> This message is intended only for use by the person
> to whom it is addressed. It may contain information
> that is privileged and confidential. Its content does
> not constitute a formal commitment by Lombard Odier.
> If you are not the intended recipient of this message,
> kindly notify the sender immediately and destroy this
> message. Thank you.
> *************************************************************
>
>
>
*****************************************************************

Privileged/Confidential Information and/or Copyright Material may
be contained in this e-mail. The information and Material is
intended for the use of the intended addressee. If you are not
the intended addressee, or the person responsible for delivering
it to the intended addressee, you may not copy or deliver it to
anyone else or use it in any unauthorised manner. To do so is
prohibited and may be unlawful. If you receive this e-mail by
mistake, advise the sender immediately by using the reply
facility in your e-mail software.


Thank you.
Information Technology Department
Belfast City Hospital Trust

*****************************************************************