Page 3 of 3
Posted: Sun Mar 06, 2011 2:36 pm
by cauer29
The Robman wrote:cauer29 wrote:once you've lived with a full state sensing system, you'll scoff at amateur solutions like toadtog.
Would you be willing to do a full write up on your state sensing system and post it in the file section?
Rob,
I finally got the writeup finished.
http://www.hifi-remote.com/forums/dload ... le_id=9531
I don't expect many positive responses here.
A.A.
Posted: Sun Mar 06, 2011 2:45 pm
by vickyg2003
Its an interesting paper. Over my head but interesting as another form of automation. I'm all about automation!
Posted: Mon Mar 07, 2011 10:36 am
by pH7_jp1
That is very interesting. Thanks for the writeup. Is this the Ocelot device?
http://www.mcmelectronics.com/product/82-4825 If so, my major problem is the cost.
As I read the info on the PF284, it sends an X10 command when the state changes on the sensed device. Is there ever a problem with dropped signals? That is, does the Ocelot ever miss the state change notification?
The simple example shows one set of rules to be enforced. For each "activity" (like watching TV, watching a DVD, listening to radio, ...) a different set of rules need to be enforced. I assume that is done by defining a different command, your house code K + a different device code, for each activity. Is that the general idea? EDIT: I went back and read the entire thread and I see this is correct.
Posted: Mon Mar 07, 2011 7:10 pm
by cauer29
pH7_jp1 wrote:That is very interesting. Thanks for the writeup. Is this the Ocelot device?
http://www.mcmelectronics.com/product/82-4825 If so, my major problem is the cost.
As I read the info on the PF284, it sends an X10 command when the state changes on the sensed device. Is there ever a problem with dropped signals? That is, does the Ocelot ever miss the state change notification?
The simple example shows one set of rules to be enforced. For each "activity" (like watching TV, watching a DVD, listening to radio, ...) a different set of rules need to be enforced. I assume that is done by defining a different command, your house code K + a different device code, for each activity. Is that the general idea? EDIT: I went back and read the entire thread and I see this is correct.
No, that's not the one. This is it:
http://www.smarthome.com/73101/Applied- ... tem/p.aspx
I think I got mine as an "open box" special or something like that for ~$100. Even then, if all you want to do is a simple 3 device setup, it's probably not worth it. I already had the Ocelot for other duties by the time I decided to use it to control AV stuff. So, it was no added cost other than the PF284s and a bit of time to design how the system would work.
There are plenty of high end "custom installer only" systems that cost upwards of 2-3K$ not even counting the custom installer fees, that work similarly to what I've built for peanuts.
As for the Ocelot missing X10 signals, I haven't noticed it. The only issue that happens occasionally is impatient users that press remote buttons before the lengthy startup macro for a given activity has finished. Fortunately, the system is designed to be self-healing. If something gets into the wrong state (ie TV or AVR on wrong input), simply pressing the remote button for the activity a second time, puts everything right with no need to go through 20 questions about what is in what state a la Harmony.
A.A.