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:

Code:

========== 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:

Code:

========== 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.

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?

It is the JSON template I was asking about a few weeks ago in the IRC.  I have struggled with it and havent really got very far. Aviator had it working, cant find him though

I think you have miss understood what 'embedded' means.  'Embedded' means their is a physical device inside the TV that would need controlling - A TV tuner (sometimes called 'Tuner' or 'TV' in your input selection), another example is a Radio tuner for an AV reciever.  everything else should be 'external' (I think it is 'external', I will have to check at home). 

Once you have done this and created a template for your set top box, you should be able to configure them via the setup wizard and check them via the screen where you can see a graphical representation of the pipes to check it.

once the Device Template is corrected it should work as you have specified in your scenarios.

you are correct LMCE doesn't know if the TV is on or not - discrete codes or a two way comms method would fix this

Yes, it is cold in my basement!!

I was trying to set up an event that warns me if the temp drops below 9 deg C but that will be another thread.....

I had already done all the things you suggest. I did a couple of reboots after due to some other reasons then all of a sudden the sensor showed up.  not sure I understand it but it is working.  See below

I rebooted, 9 hours ago.  still no sensor.  I checked the sensor was connected properly earlier using the maxim graphing tool.

Perhaps I should reboot then, it has been months since I rebooted!

I can now report success Grin (adapter registered)

did any sensors show up?

It would be nice to get that one to work but I have struggled.  Probably get some of that back if you throw it on Ebay

I think there may be a problem with the DS9490R with LMCE.  Take a look at:

http://forum.linuxmce.org/index.php/topic,11328.150.html

page 11 you will see I had the same issue with the DS9490R which I then replaced with the http://www.ibuttonlink.com/linkusb.aspx

I dont know what I did but my last update was less than a week ago

Not sure it is working, right now I dont have a temp sensor plugged in.  I took my test one to work to graph how cold it is in my office - LOL

Extra stuff can be taken care of with 'respond to events'

http://wiki.linuxmce.org/index.php/Make_LinuxMCE_do_something_when_I_start_media
http://wiki.linuxmce.org/index.php/Respond_To_Events_By_Email

I don't think there is any difference between how it will run on and Intel or AMD processor.  I have an AMD core and a Media Director that is Intel Atom and both run fine.  There is a device template for CM11 and CM15 but I am not sure about CM19.  I would plug it in and see what happens.  The CM15 is plug and play.  There is more hardware support in 10.04 and L3MCE has done a load of work getting video and sound to work well, you will also find the install process much cleaner than in 0810.