So I have 4 Temperature sensors installed in my 1-Wire network.
2 days back 1 was accidentally unplugged. Since then the temperature has remained constant at the temp that was being reported - even after a reload and reboot. what is the correct process for getting this to work again?
you could check if the right USB port was recognized in the devicetemplate.
other than that, 1wire has always been a misterious thing - suddenly one day they get recognized and nobody knows why ???
was the serial number recognized already?
the one sensor that was disconnected was still appearing in the log on reboot - this is after the device was physically disconnected and shows that it is connected properly:
========== NEW LOG SECTION ==========
1 02/16/13 10:43:50 118 (spawning-device) Starting... 1
1 02/16/13 10:43:50 118 (spawning-device) Found /usr/pluto/bin/OneWire
01 02/16/13 10:43:51.543 TranslateSerialUSB pci0000:00/0000:00:12.0+1 result /dev/ttyUSB1 <0xb77506d0>
01 02/16/13 10:43:51.543 Opening port: /dev/ttyUSB1 <0xb77506d0>
05 02/16/13 10:43:52.164 Creating child 130 <0xb77506d0>
05 02/16/13 10:43:52.164 Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77506d0>
05 02/16/13 10:43:52.165 Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77506d0>
05 02/16/13 10:43:52.165 Creating child 131 <0xb77506d0>
05 02/16/13 10:43:52.165 Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77506d0>
05 02/16/13 10:43:52.165 Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77506d0>
05 02/16/13 10:43:52.165 Creating child 132 <0xb77506d0>
05 02/16/13 10:43:52.165 Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77506d0>
05 02/16/13 10:43:52.165 Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77506d0>
05 02/16/13 10:43:52.165 Creating child 133 <0xb77506d0>
05 02/16/13 10:43:52.165 Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77506d0>
05 02/16/13 10:43:52.165 Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77506d0>
05 02/16/13 11:39:31.712 Got a reload command from 0 <0xb61ffb70>
05 02/16/13 11:39:31.966 void ClientSocket::Disconnect() on this socket: 0x80b4350 (m_Socket: 7) <0xb77506d0>
Return code: 2
2 02/16/13 11:39:31 118 (spawning-device) Device requests restart... count=1/50 dev=118
Sat Feb 16 11:39:32 CST 2013 Restart
then after device 132 was deleted:
========== NEW LOG SECTION ==========
1 02/16/13 11:47:26 118 (spawning-device) Starting... 1
1 02/16/13 11:47:26 118 (spawning-device) Found /usr/pluto/bin/OneWire
01 02/16/13 11:47:26.321 TranslateSerialUSB pci0000:00/0000:00:12.0+1 result /dev/ttyUSB1 <0xb77a26d0>
01 02/16/13 11:47:26.321 Opening port: /dev/ttyUSB1 <0xb77a26d0>
05 02/16/13 11:47:26.708 Creating child 130 <0xb77a26d0>
05 02/16/13 11:47:26.709 Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77a26d0>
05 02/16/13 11:47:26.709 Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77a26d0>
05 02/16/13 11:47:26.709 Creating child 131 <0xb77a26d0>
05 02/16/13 11:47:26.709 Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77a26d0>
05 02/16/13 11:47:26.709 Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77a26d0>
05 02/16/13 11:47:26.709 Creating child 133 <0xb77a26d0>
05 02/16/13 11:47:26.709 Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77a26d0>
05 02/16/13 11:47:26.709 Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77a26d0>
it seems like it doesn't find the device. When I installed them less than a week ago they were discovered almost immediately.
the OneWire DCE device uses the OWFS client API. If you can see the devices in OWFS, they will appear in LinuxMCE.