New Furnace Room Light adventure

[Steve Hume]

I have a floor lamp that is now standing near the Furnace so that I  
can see when in that area. Until tonight, I was using the old  
fashioned switch on the Lamp. Now of course I have stirred up some  
trouble.

Trouble #1)
I found an LM14 in the parts bin and when I plugged it between the  
lamp and the wall socket. The lamp didn't come on??? The logs  
revealed a zillion
Sun, Jan 7, 2007 7:24:01 PM Interface error: (Powerline reception error)
Sun, Jan 7, 2007 7:24:01 PM Interface error: (Powerline reception error)
Sun, Jan 7, 2007 7:24:01 PM Interface error: (Powerline reception error)
Sun, Jan 7, 2007 7:24:01 PM Interface error: (Powerline reception error)
Sun, Jan 7, 2007 7:24:01 PM Interface error: (Powerline reception error)
Sun, Jan 7, 2007 7:24:02 PM Interface error: (Powerline reception error)

with things otherwise functioning. I tried new unit codes to no avail  
and sent the LM14 back to the parts bin. This time with the label  
"bad??" on it.

Trouble #2)
I opened one of the 2-way appliance modules that I bought during a  
fall sales deal; PAM22 is the unit type. I went to add the new unit  
to XTension and found that I could not check smart box without  
setting the dimmable box! But Appliance modules are not dimmable and  
I have not determined whether they are smart, although it did send this
Sun, Jan 7, 2007 7:33:00 PM Received extended code for Furnace Light  
Command = 55 Data = 16
Sun, Jan 7, 2007 7:33:00 PM Setting value of Furnace Light to 16
when I plugged in the PAM22 with no lamp plugged into it.
Shouldn't XTension allow non-dimmable smart units?

Trouble #3)
For now I have it set to dimmable and smart. There does not seem to  
be any local sense behavior, as all turning of the lamp switches does  
not make the lamp come on locally. The relay clicks only when I  
command it from XTension. Not sure what the use of being smart is if  
local sense does not work?
Some signs of smartness:
Sun, Jan 7, 2007 7:45:36 PM Sending OFF for Furnace Light
Sun, Jan 7, 2007 7:45:37 PM ack: OFF for K7 from powerline interface
Sun, Jan 7, 2007 7:45:39 PM Received extended code for Furnace Light  
Command = 56 Data = 192
Sun, Jan 7, 2007 7:45:39 PM Setting value of Furnace Light to 0

and
Sun, Jan 7, 2007 7:46:20 PM Sending ON for Furnace Light
Sun, Jan 7, 2007 7:46:21 PM Sending ON for Furnace Light
Sun, Jan 7, 2007 7:46:22 PM ack: ON for K7 from powerline interface
Sun, Jan 7, 2007 7:46:23 PM ack: ON for K7 from powerline interface
Sun, Jan 7, 2007 7:46:25 PM Received extended code for Furnace Light  
Command = 56 Data = 255
Sun, Jan 7, 2007 7:46:25 PM Setting value of Furnace Light to 100

Trouble #4) (X-10 UI confusion)
I have an X-10 motion sensor screwed to a shelf near the furnace.  
This will be the sensor that will start the turning on of the light.  
All the transmission tests did not pass and I decided that new  
batteries were in order. Of course, I can't remember which type it is  
MS12 MS13?? So I have to just try to reprogram it by guess.  
Thankfully the XTension Log window was nearby. Why did I use code  
K10! I copied some nice scripts from another unit. It would have been  
nice to cut/paste/drag some unit properties too, but no big deal  
manually entering them. Everything working. Save and archive database.

Trouble #4)
The server needed a restart for other application maintenance. I noticed
Sun, Jan 7, 2007 8:07:57 PM Missed Event: Furnace Light (#1)
in the logs. I had always thought that XTension was noticing this and  
correcting things by executing the missed event at startup. The light  
had stayed on and was correctly shown as on by XTension. My turn off  
event had been missed. How do others deal with this? Does XTension  
call any unit handlers when reporting missed events on them so that  
they can be dealt with?

That's enough trouble for tonight.

Steve Hume