Actually, if you're able to make the C++ 1-wire device template more flexible, to accommodate more of the OWFS supported devices, that may solve the problem. Right now it's hard-coded to expect a serial type device, which rules out all the network, i2c, and other types of OWFS bus masters <http://owfs.org/index.php?page=bus-masters>
In my case, I'd like to be able to use my Raspberry Pi as a networked OWFS control node. I have some quick and dirty bash scripts running that do owreads into a variable, and then do a messagesend to a manually created device on the core. Works well enough for proof-of-concept, and I can see the little Thermometer icon on the floor plans.
Just a thought...