beelzerob
Senior Member
My cousin installed a wood burning water boiler to heat their house, and it works great! It's also filled the house with smoke at least once, and has signs it had at least 1 flue fire. So, while he takes care of all of the other safety related repairs and projects, he's asked me to design a system to help him monitor the system's vital signs and to appropriately warn the family if needed.
Because I've only known CQC to this point, I'm kind of at a loss to think outside that all-in-one box. He's always balked at CQC's price (and even with the current sale, I can't get him to accept the yearly fee, even though I understand the reason for it), and that's probably ok, because he's not looking to control his media or distributed audio or lights....really, it's just a system to monitor temps and sensors and to notify...maybe some relays to control water valves, too. So, maybe that means some kind of home automation panel would work ok?? Or maybe it's Premise or Girder running on a PC?? Or build the control from scratch with java services and server pages?? Again, since I only know CQC (and I know it can do all those things with ease), I'm not sure what the capabilities of other stuff is out there.
Here's the basic list of requirements at this point:
We're both software engineers, so if coding or device drivers are required to make some of this work, that won't be a problem. It'd be fun to write as much as possible in java. However, I'm more concerned just about stability than anything else, and so if we had to use a PC, that's adding some potential unreliability into the system (though I use one for CQC, and can't complain about its reliability). Mainly the idea that a PC has more moving parts than most things, so that's more that can go wrong. But maybe a thin client would be able to handle whatever software controls this system, so that would be a tad more stable.
Or if there's an automation panel that could handle all this (and more), and that may be even better. I know the Elk can do MOST of what's on the list, but all of it? And would the Elk be even more overkill than CQC would be?
Thanks for the help guys!
Because I've only known CQC to this point, I'm kind of at a loss to think outside that all-in-one box. He's always balked at CQC's price (and even with the current sale, I can't get him to accept the yearly fee, even though I understand the reason for it), and that's probably ok, because he's not looking to control his media or distributed audio or lights....really, it's just a system to monitor temps and sensors and to notify...maybe some relays to control water valves, too. So, maybe that means some kind of home automation panel would work ok?? Or maybe it's Premise or Girder running on a PC?? Or build the control from scratch with java services and server pages?? Again, since I only know CQC (and I know it can do all those things with ease), I'm not sure what the capabilities of other stuff is out there.
Here's the basic list of requirements at this point:
- Water temps
- Water detector
- Heat Detector (digital input)
- Smoke detector (will probably use GE ESL350CX to get the tandem line of his existing smokes)
- CO detector
- Flue temp measurement (external, surface temp measurement, probably up to 400 deg)
- Web-based status readout, so it's accessible from any PC's in the house AND outside the house (from work)
- External alerting capability (whether annoying noise or voice/TTS)
- Email notifications
- Phone notifications
- Relay control (water valves, most likely)
- Extensibility, ease of adding more and varied sensors
We're both software engineers, so if coding or device drivers are required to make some of this work, that won't be a problem. It'd be fun to write as much as possible in java. However, I'm more concerned just about stability than anything else, and so if we had to use a PC, that's adding some potential unreliability into the system (though I use one for CQC, and can't complain about its reliability). Mainly the idea that a PC has more moving parts than most things, so that's more that can go wrong. But maybe a thin client would be able to handle whatever software controls this system, so that would be a tad more stable.
Or if there's an automation panel that could handle all this (and more), and that may be even better. I know the Elk can do MOST of what's on the list, but all of it? And would the Elk be even more overkill than CQC would be?
Thanks for the help guys!