Hello All,
I'm not a Homeseer user (yet), but I'd like to get some opinion on the generic topic of web based front ends to Home Automation systems-
How many people are doing this?
Consider it the main interface?
If so, how do you overcome some of the issues associated with this method?
For example, web browsing is, by design, a user driven process where the user requests data and the server provides it on demand.
Home automation info however, in my experience, is more server driven - Some event occurs that would trigger a change in the browser display - outside of a user requesting it.
Some systems deal with this by using java applets, some simply refresh the browser on fixed intervals. How does Homeseer web interface update information related to typical automated items?
I'm not a Homeseer user (yet), but I'd like to get some opinion on the generic topic of web based front ends to Home Automation systems-
How many people are doing this?
Consider it the main interface?
If so, how do you overcome some of the issues associated with this method?
For example, web browsing is, by design, a user driven process where the user requests data and the server provides it on demand.
Home automation info however, in my experience, is more server driven - Some event occurs that would trigger a change in the browser display - outside of a user requesting it.
Some systems deal with this by using java applets, some simply refresh the browser on fixed intervals. How does Homeseer web interface update information related to typical automated items?
Comment