Post by kenneth558 on Dec 2, 2017 2:28:11 GMT
I'm trying to understand the architectural concepts of OpenHAB2 from the perspective of employing an Arduino as an interfacing hub. Complete thermostat code is also in the Arduino. The Arduino sketch will also accept commands from host (Ubuntu CLI) to read pin levels and change them. I'm trying to categorize the Arduino, pins, and thermostat functionality optimally. I have am a total newby with OpenHAB and am having a difficult time figuring out delineating and assigning Hub, Thing, Item, and that sort of whatnot. OpenHAB forum folks aren't explaining things at my level and neither is Eclipse SmartHome forum. I'll bet the right people are on this forum. Here are links to my postings in the other forums so that I don't waste space over again describing my system: my OpenHAB forum post, my Eclipse SmartHome forum post.
I should confess that I prefer avoiding MQTT feeling it is an unnecessary level of complexity and potential unreliability in upgrade changes. CLI scripts-to-STDOUT and scripts-to-serial are doing just fine.
If I could get started in the right direction (what physical device or software functionality is is best configured as what conceptual object), I'm sure I'll get the details figured out fine after that. Lord bless and Thank you for any help!!!
[ADDITION 12/2/17] Methinks a fair approach to my project is tobegin proceed with a diagram of functional pathway and just decide where to delineate and which functional aspects need to be spelled out. I'm coming to suspect, whether correct or not is unknown, that an important point to make in a beginner's learning curve is that the functional elements are that the order in which they are connected is somewhat inflexible - any connection pathway can only have zero or one Item, and that Item must be the terminus of the pathway, if present. The pathway can branch out but not mesh back together, and the branch points can be Things or [whatnots or other whatnots]. (Etc. Etc. as I get farther along...)
IOW, I'll approach this by making a tree diagram of virtual functional pathways and see if I can get all functionalities accounted for and accommodated. That is in contrast to coming from a direction of "a [such and such device] is a [virtual object]. Period." because the documentation confusingly in one place describes a light bulb as a Thing and in another placed as an Item.
I should confess that I prefer avoiding MQTT feeling it is an unnecessary level of complexity and potential unreliability in upgrade changes. CLI scripts-to-STDOUT and scripts-to-serial are doing just fine.
If I could get started in the right direction (what physical device or software functionality is is best configured as what conceptual object), I'm sure I'll get the details figured out fine after that. Lord bless and Thank you for any help!!!
[ADDITION 12/2/17] Methinks a fair approach to my project is to
IOW, I'll approach this by making a tree diagram of virtual functional pathways and see if I can get all functionalities accounted for and accommodated. That is in contrast to coming from a direction of "a [such and such device] is a [virtual object]. Period." because the documentation confusingly in one place describes a light bulb as a Thing and in another placed as an Item.