http://www.rsdtotalcontrol.com/fx/pdf/Communicating_T_stat_Wireless_Overview.pdf
http://cgproducts.johnsoncontrols.com/CAT_PDF/1900624.pdf
http://cgproducts.johnsoncontrols.com/CAT_PDF/1900625.pdf
@ Pete, it does exist, but typically in doing a setup like this you need to move into a common platform protocol, typically BACnet between system components.....otherwise it's not going to be economical or practical to manufacture or install. In the case of consumer grade hardware, how scalable are these platforms? What happens when X or Y component is NLA or the format not supported? It may be a matter of time for the trickle down of the protocols and hardware to happen, it may never happen....The largest issue is usually there's either not enough conductors or the wrong type are going to the wrong location. In the case of wireless comms from the units...what protocol that is presently available gets chosen and is it the right choice? Only time will tell.
Usually TCP/IP is going tp be the easiest to leverage in a building, unless you are building your own small network using some other protocol, then it becomes what sort of protocol and what will the unit(s) be able to communicate to.
@Apu
For the same price of purchasing consumer grade items or a small premium, all these system parts can be purchased over the counter. Occupancy sensing already integrated, but could be added to. Raspberry PI for running BACnet. Whether or not you need to provide network connectivity or it already exists was not brought up as a design criteria, but most buildings have some form of network, if not, a simple standalone TCP/IP deployment would easily support a modest BACnet network with no bandwidth issues.
While you disagreed and dismissed before...something along the lines of unscrupulous HVAC/controls contractor or practices, by minimizing what sort of actions an end user performs on the system, while still allowing reasonable control within a specific bandwidth, while still allowing and maintaining scheduling abilities, the energy savings and efficiency will pay for the system itself, as it has been proven elsewhere many times over.
If you would like to forward specific design criteria , equipment installed and site information, the calculations and projections would speak for themselves. I'm sure the parish would have interest in the cost savings. I'll even do your homework and provide you a BOM for you to price and order through your friends, as you already mentioned yourself and them perform HVAC installations and service and would have access to common distribution.
No need to reinvent the wheel when it already exists....there's multiple manufacturers out there, I provided the most readily available.
http://cgproducts.johnsoncontrols.com/CAT_PDF/1900624.pdf
http://cgproducts.johnsoncontrols.com/CAT_PDF/1900625.pdf
@ Pete, it does exist, but typically in doing a setup like this you need to move into a common platform protocol, typically BACnet between system components.....otherwise it's not going to be economical or practical to manufacture or install. In the case of consumer grade hardware, how scalable are these platforms? What happens when X or Y component is NLA or the format not supported? It may be a matter of time for the trickle down of the protocols and hardware to happen, it may never happen....The largest issue is usually there's either not enough conductors or the wrong type are going to the wrong location. In the case of wireless comms from the units...what protocol that is presently available gets chosen and is it the right choice? Only time will tell.
Usually TCP/IP is going tp be the easiest to leverage in a building, unless you are building your own small network using some other protocol, then it becomes what sort of protocol and what will the unit(s) be able to communicate to.
@Apu
For the same price of purchasing consumer grade items or a small premium, all these system parts can be purchased over the counter. Occupancy sensing already integrated, but could be added to. Raspberry PI for running BACnet. Whether or not you need to provide network connectivity or it already exists was not brought up as a design criteria, but most buildings have some form of network, if not, a simple standalone TCP/IP deployment would easily support a modest BACnet network with no bandwidth issues.
While you disagreed and dismissed before...something along the lines of unscrupulous HVAC/controls contractor or practices, by minimizing what sort of actions an end user performs on the system, while still allowing reasonable control within a specific bandwidth, while still allowing and maintaining scheduling abilities, the energy savings and efficiency will pay for the system itself, as it has been proven elsewhere many times over.
If you would like to forward specific design criteria , equipment installed and site information, the calculations and projections would speak for themselves. I'm sure the parish would have interest in the cost savings. I'll even do your homework and provide you a BOM for you to price and order through your friends, as you already mentioned yourself and them perform HVAC installations and service and would have access to common distribution.
No need to reinvent the wheel when it already exists....there's multiple manufacturers out there, I provided the most readily available.