I use X10 (cheap - lights, outlets and PIR) and 1-wire (very cheap - temp and soon Humidity). Do you own your condo? meaning are you willing to run structured wiring? Cat5e/6 around

Armor Gnome,I don't use Nest but do use a Filtrete 3M-50 that I am trying to add support for (it is cheaper and not as Apple-esque).

Anderson01,What would you fit if you were just buying a normal alarm system? think of what you would want to cover then apply that to LMCE. PIR's, window/door sensors are all readily available in LMCE. Add camera's, sirens, alerts via email and phone

In general, I like the ability to use sensors for multiple things - for instance PIR's are used for security and to trigger lighting. Temp sensors help with heating system and (hopefully - when I work this out) fire alarms (if the sensor is over a certain temperature - FIRE!!!)

unfortunately, most people are just going to buy stuff that suits their pockets and buy them from places like Best Buy or they have already got their equipement before deciding they want to take it to the next level.

I know CEC is poorly supported at present but it is an optionWhat do you mean? CEC is in place on lots of HDMI equipment now but not neccesarily common codes - therefore DT's would need to be made for each device rather than each type of device (TV's, Blu-ray, PVR, Receiver).

I think support for a common, low cost 'USB-CEC injector' would be good step forward for LMCE.

========== NEW LOG SECTION ==========102/16/13 10:43:50118 (spawning-device)Starting... 1102/16/13 10:43:50118 (spawning-device)Found /usr/pluto/bin/OneWire0102/16/13 10:43:51.543TranslateSerialUSB pci0000:00/0000:00:12.0+1 result /dev/ttyUSB1 <0xb77506d0>0102/16/13 10:43:51.543Opening port: /dev/ttyUSB1 <0xb77506d0>0502/16/13 10:43:52.164Creating child 130 <0xb77506d0>0502/16/13 10:43:52.164Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77506d0>0502/16/13 10:43:52.165Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77506d0>0502/16/13 10:43:52.165Creating child 131 <0xb77506d0>0502/16/13 10:43:52.165Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77506d0>0502/16/13 10:43:52.165Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77506d0>0502/16/13 10:43:52.165Creating child 132 <0xb77506d0>0502/16/13 10:43:52.165Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77506d0>0502/16/13 10:43:52.165Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77506d0>0502/16/13 10:43:52.165Creating child 133 <0xb77506d0>0502/16/13 10:43:52.165Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77506d0>0502/16/13 10:43:52.165Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77506d0>0502/16/13 11:39:31.712Got a reload command from 0 <0xb61ffb70>0502/16/13 11:39:31.966void ClientSocket::Disconnect() on this socket: 0x80b4350 (m_Socket: 7) <0xb77506d0>Return code: 2202/16/13 11:39:31118 (spawning-device)Device requests restart... count=1/50 dev=118Sat Feb 16 11:39:32 CST 2013 Restartthen after device 132 was deleted:

========== NEW LOG SECTION ==========102/16/13 11:47:26118 (spawning-device)Starting... 1102/16/13 11:47:26118 (spawning-device)Found /usr/pluto/bin/OneWire0102/16/13 11:47:26.321TranslateSerialUSB pci0000:00/0000:00:12.0+1 result /dev/ttyUSB1 <0xb77a26d0>0102/16/13 11:47:26.321Opening port: /dev/ttyUSB1 <0xb77a26d0>0502/16/13 11:47:26.708Creating child 130 <0xb77a26d0>0502/16/13 11:47:26.709Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77a26d0>0502/16/13 11:47:26.709Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77a26d0>0502/16/13 11:47:26.709Creating child 131 <0xb77a26d0>0502/16/13 11:47:26.709Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77a26d0>0502/16/13 11:47:26.709Note: Device manager has attached a device of type 1946 that this has no custom handler for. This is normal for IR. <0xb77a26d0>0502/16/13 11:47:26.709Creating child 133 <0xb77a26d0>0502/16/13 11:47:26.709Note: Device manager has attached a device of type 1946 that this has no custom event handler for. It will not fire events. <0xb77a26d0>0502/16/13 11:47:26.709Note: 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.

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?

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

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