I'm all in on the idea of microcontroller use here. Once the firmware is flashed, it's purpose driven. That's all it does. Rock solid reliable.

In regards to the outdoor sensor, I love your approach, but I have one better (because I've done it). This of course. is only relevant if it is possible... do what you have to do on the inside of the facility. Keep the microcontroller there. Put outdoors only the sensor itself. This way, one can control all voltages/current at whatever level necessary in a safe environment, and only 3.3v or 5v at minimal current draw needs to egress the building. Only condition is, is that one adheres to the gauge and length of wire for the transmission protocol for the sensor in use (taking into consideration all environmental variables (temp, etc)).

A Raspberry Pi is great for prototyping or playing around. I spent years developing software for numerous sensors, ICs and things on a Pi. However, for critical operations such as operating a building's HVAC system, I believe it is imperative and responsible to use something suited for the task. Already, furnaces use microcontrollers for these types of things. I wouldn't deviate from the norm.

In reply to Re^7: XS Modules - why and when? by stevieb
in thread XS Modules - why and when? by Bod

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.