I have OH1 talking to my MyTotalControl perfectly for my thermostat. See post if interested.
It’s a bit late for the OP but for others reading this thread later:
If all you need is temperature for a lot of zones, an excellent and CHEAP solution is to use a 1Wire busmaster device such as the Embedded Data Systems “OW-SERVER-ENET-2,” combined with a string of Dallas Semiconductor DS18B20 temperature sensors. The latter are available in bulk on eBay, with leads and stainless steel housings I have 20 currently, strung together using Cat5e cable in a loose bus configuration.
The chain of data flow goes:
DS18B20 sensor --> Cat 5E bus cable --> EDS OW-SERVER-ENET-2 Hardware device --> LAN/TCP IP --> owserver 3.1p4 daemon** running on my OH server, publishing on a localhost:4304 port --> OH OneWire binding polls the owserver daemon via TCPIP --> sensor data updated in OH Items.
I have been running this setup for about a month and it is rock solid. You have to be able & willing to string cable, but in trade for that you avoid hassles with wireless interference, Zwave configuration, replacing batteries, etc. I haven’t verified it yet but I believe in my configuration the OW-SERVER-ENET-2 1Wire busmaster device will support up to about 100 1-wire sensors. (The EDS marketing material and specs say it supports “up to 22 devices” – but that can be circumvented by accessing the device through the low-level direct TCP socket interface. Which the OWFS “owserver” daemon I run happens to do. Thru the low-level interface the device is said to support up to 100 sensors, tho I have not yet exceeded 20.)
There are also humidity & other 1Wire sensors available but they are considerably more expensive.
When purchased thru eBay the sensors come unlabeled (with no IDs visible,) so they have to be hooked up to the bus-master device one by one to map the internal hardware IDs with an external physical label (which you create & stick on to the wire.) During that process I also took the time to do a rough 1-point calibration using a known reference; I found that nearly all sensors were within +/- 1ºF of the reference, with just one or two stragglers at +/- 1.5ºF.
**Nota bene!: EDS chose an unfortunate part # for their busmaster device. “OW-SERVER-ENET-2” is their arbitrary model name for a physical product. “owserver” is the name of a pre-existing software daemon that is part of the “OWFS” project. owserver daemon handles onewire-protocol processing on Linux and other platforms. There is no direct connection between the EDS hardware product & the OWFS / owserver software project!
OWFS owserver software churns Onewire-format sensor data into other, simpler formats & publishes it in various forms for consumption elsewhere, e.g. in OpenHAB.
Also note: I had problems getting owserver daemon working reliably when I ran other versions than 3.1p4. YMMV but if you have problems connecting “owserver” to the “OW-SERVER-ENET-2” device, be sure to try 3.1p4 version of the owserver software.
Project costs:
Embedded Data Systems “OW-SERVER-ENET-2” hardware device, $100
Twenty (20) DS18B20 sensors, with 3’ cables and stainless housings, $50 total
About 150’ of Cat5e cable, ~$30
A box of 3M ScotchLok UR moisture-resistance butt splice connectors, $15
About $10 per zone for 20 zones. The DS18B20 is a popular sensor, wouldn’t be surprised if it’s at the heart of many a $50-$150 “smart wireless” thermostat unit.