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.

72 string port = TranslateSerialUSB(DATA_Get_COM_Port_on_PC());[…]78 if (OW_init(port.c_str())==0) {[…]the "port" string would need to be assigned with other owfs device options to achieve the wanted behaviour. So one could probably add a device parameter for a specific owfs init string. If that is set it would take precedence over COM_Port_on_PC.

A quick hack in the database to test if I'm right could look like this:update Device_DeviceData set IK_DeviceData='usb' where FK_DeviceData=37 and FK_Device=<id of your OneWire device>;

Hari,How do I test/get this? sqlCVS update and or apt-get update?Sorry newbie question's Also I may have broke the 1wire template 2161, By making changes to device data section!Is there a way to get it back to original?

I can now report success (adapter registered)THANK YOU HariI did need to make changes to my device template 2161 though to get it to work:Comm Method was saying 'RS232' so changed to 'Please select'Under Device data - 37 com port on pc (string) - Default value - was still saying 'dev/ttyS0' so just deleted value and saved template then reload.....Thats it, it just worked

Sorry Thom was nearly ready to put DS9490R in post to you!

Wish I could code, tried programing a pic chip once in C+ gave up after 2weeks & used pic basic instead took 1day.