all housecode remote

[bblackmoor]

I am looking for an all-housecode RF remote for X10. It does not seem
to me that this should be such a difficult thing to find, but I have
not found one. Any suggestions?

bblackmoor
2005-02-07

[Philip Lewis]

Hey X10.... listen up!

I've always wanted to see a palmpad like device.

Take 16 buttons and make the first press designate the housecode,
the second press could designate the number, and the third the
function.

The buttons would be:
************************
A 01 06% B 02 12%
C 03 18% D 04 24%
E 05 30% F 06 36%
G 07 42% H 08 48%
I 09 54% J 10 60%
K 11 66% L 12 72%
M 13 78% N 14 84%
O 15 90% P 16 96%

On Off
************************
or some such.
Three presses get you practically anywhere you want.

The switch could designate if it worked as a palmpad or the
"super" palmpad. (note that the pad would only do codes 1-8 in
"normal" mode... unless there was another switch to designate

I imagine I could have a computer emmulate this using some state
machines. (listen on a certain otherwise unused housecode for three
distinct presses, then act on the press by sending the code)

Thoughts?

--
be safe.
flip
Ich habe keine Ahnung was das bedeutet, oder vielleicht doch?

[Dan]

bblackmoor wrote:
> I am looking for an all-housecode RF remote for X10. It does not seem
> to me that this should be such a difficult thing to find, but I have
> not found one. Any suggestions?
>
> bblackmoor
> 2005-02-07
>
If you glue a little 'tab' on the dial on a palmpad, so you can change
the house code without needing any other tools, wouldn't that do the
job? I think that's as close as you are going.

[Dave Houston]

Your scheme is incompatible with existing hardware and with the RF protocol
that X-10 has used for many years. Even Leviton's All Housecode Transceiver
uses the existing protocol and works with existing 310MHz remotes like the
Palmpad.

It's simpler to add RF capability to a programmable remote (e.g. Pronto,
PDA) or design a receiver that uses the same frequency as the RF capable
remotes. Outside of North America, almost everything uses 433.92MHz so an RF
capable Pronto can be used with any of several X-10 made 230V, 433.92MHz All
Housecode Receivers. Unfortunately, in North America, X-10 uses 310MHz while
most programmable remotes use 418MHz.

One simple solution is to buy the European MR26E (433.92MHz) and tune it to
418MHz but that does require a PC (or embedded hardware) to interpret the
codes and interface with a PLC transmitter.

Philip Lewis <flip+spiced_ham@andrew.cmu.edu> wrote:

>Hey X10.... listen up!
>
>I've always wanted to see a palmpad like device.
>
>Take 16 buttons and make the first press designate the housecode,
>the second press could designate the number, and the third the
>function.
>
>The buttons would be:
>************************
>A 01 06% B 02 12%
>C 03 18% D 04 24%
>E 05 30% F 06 36%
>G 07 42% H 08 48%
>I 09 54% J 10 60%
>K 11 66% L 12 72%
>M 13 78% N 14 84%
>O 15 90% P 16 96%
>
>On Off
>************************
>or some such.
>Three presses get you practically anywhere you want.
>
>The switch could designate if it worked as a palmpad or the
>"super" palmpad. (note that the pad would only do codes 1-8 in
>"normal" mode... unless there was another switch to designate
>
>I imagine I could have a computer emmulate this using some state
>machines. (listen on a certain otherwise unused housecode for three
>distinct presses, then act on the press by sending the code)
>
>Thoughts?

[Ian Shef]

nobody@whocares.com (Dave Houston) wrote in
news:4208fd0f.76434632@nntp.fuse.net:

> Your scheme is incompatible with existing hardware and with the RF
> protocol that X-10 has used for many years. Even Leviton's All Housecode
> Transceiver uses the existing protocol and works with existing 310MHz
> remotes like the Palmpad.
<SNIP>

I don't think that Philip said anything about the RF protocol. He appears
to have expressed an opinion on the user interface. Presumably, the brains
of the transmitter would use the information from the button presses (after
the third button press) to send the appropriate stream of data via RF to
the receiver.

It's not the user interface that I would have chosen, but never mind that.

>
> Philip Lewis <flip+spiced_ham@andrew.cmu.edu> wrote:
>
>>Hey X10.... listen up!
>>
>>I've always wanted to see a palmpad like device.
>>
>>Take 16 buttons and make the first press designate the housecode,
>>the second press could designate the number, and the third the
>>function.
>>
>>The buttons would be:
>>************************
>>A 01 06% B 02 12%
>>C 03 18% D 04 24%
>>E 05 30% F 06 36%
>>G 07 42% H 08 48%
>>I 09 54% J 10 60%
>>K 11 66% L 12 72%
>>M 13 78% N 14 84%
>>O 15 90% P 16 96%
>>
>>On Off
>>************************
>>or some such.
>>Three presses get you practically anywhere you want.
>>
>>The switch could designate if it worked as a palmpad or the
>>"super" palmpad. (note that the pad would only do codes 1-8 in
>>"normal" mode... unless there was another switch to designate
>>
>>I imagine I could have a computer emmulate this using some state
>>machines. (listen on a certain otherwise unused housecode for three
>>distinct presses, then act on the press by sending the code)
>>
>>Thoughts?
>
>



--
Ian Shef 805/F6 * These are my personal opinions
Raytheon Company * and not those of my employer.
PO Box 11337 *
Tucson, AZ 85734-1337 *

[Dave Houston]

Ian Shef <invalid@avoiding.spam> wrote:

>nobody@whocares.com (Dave Houston) wrote in
>news:4208fd0f.76434632@nntp.fuse.net:
>
>> Your scheme is incompatible with existing hardware and with the RF
>> protocol that X-10 has used for many years. Even Leviton's All Housecode
>> Transceiver uses the existing protocol and works with existing 310MHz
>> remotes like the Palmpad.
><SNIP>
>
>I don't think that Philip said anything about the RF protocol. He appears
>to have expressed an opinion on the user interface. Presumably, the brains
>of the transmitter would use the information from the button presses (after
>the third button press) to send the appropriate stream of data via RF to
>the receiver.

In which case the current Palmpad works just fine with a knob added to
select the housecode.

However, the rightmost column appears to be the dim level and that would
require a change to the protocol.

[Don]

Don't know if they are still available but I bought some little knobs that
fit on the house code dial and made it really easy to set the HC to
anything. Forgot where I got them and what they were called. I still have
a couple dozen in the parts cabinet. They work on the Palmpad and
maxi-controller. They came in both Red and Black. Maybe someone knows
more about them. It has been almost a couple years since I originally
bought them.

Don


"Dan" <haguru@gmail.com> wrote in message
news:Xg6Od.339$Eq6.31@twister.nyroc.rr.com...
> bblackmoor wrote:
>> I am looking for an all-housecode RF remote for X10. It does not seem
>> to me that this should be such a difficult thing to find, but I have
>> not found one. Any suggestions?
>>
>> bblackmoor
>> 2005-02-07
>>
> If you glue a little 'tab' on the dial on a palmpad, so you can change the
> house code without needing any other tools, wouldn't that do the job? I
> think that's as close as you are going.

[Mitch]

Reading your email just jogged my memory...

It's Home Controls that sells those things. I went to their site.

They call them X10 Code Clickers (product id DECC, DECCR and DECCB).
You can find them at

http://www.homecontrols.com/cgi-bin/hci.pl?pgm=co_disp&func=displ&strfnbr=2&prrfnbr=365&sesent=0,0

Mitch

Don wrote:
> Don't know if they are still available but I bought some little knobs that
> fit on the house code dial and made it really easy to set the HC to
> anything. Forgot where I got them and what they were called. I still have
> a couple dozen in the parts cabinet. They work on the Palmpad and
> maxi-controller. They came in both Red and Black. Maybe someone knows
> more about them. It has been almost a couple years since I originally
> bought them.
>
> Don
>
>
> "Dan" <haguru@gmail.com> wrote in message
> news:Xg6Od.339$Eq6.31@twister.nyroc.rr.com...
>
>>bblackmoor wrote:
>>
>>>I am looking for an all-housecode RF remote for X10. It does not seem
>>>to me that this should be such a difficult thing to find, but I have
>>>not found one. Any suggestions?
>>>
>>>bblackmoor
>>>2005-02-07
>>>
>>
>>If you glue a little 'tab' on the dial on a palmpad, so you can change the
>>house code without needing any other tools, wouldn't that do the job? I
>>think that's as close as you are going.
>
>
>
>

[Philip Lewis]

Ian Shef <invalid@avoiding.spam> writes:
>Presumably, the brains of the transmitter would [...] send the
>appropriate stream of data via RF to the receiver.
Exactly!

Dave Houston writes:
>In which case the current Palmpad works just fine with a knob added to
>select the housecode.
much less convenient in my opinion... I could do the button thing by
feel. I suppose i could do the knob thing by feel as well, but i can
count down three buttons easier than i can tell 22 from 44 degrees ;).
(actually perhaps it isn't that hard... but still)
I do use palmpads for multi housecode, but i usually have to whip out
my pocket knife or find a drywall screw. (which fits the slot
perfectly. ;)

>However, the rightmost column appears to be the dim level
Actually the dim level is based on button number. Perhaps that wasn't
clear for folks reading in a proportional font.

If buttons are numbered left->right top->bottom, absolute dime level
is Number * 6%. with "on" and "off" being sent by pressing the current
"brighten" and "dim" buttons.

(so 1on = 6%, 1off = 12%, 2on = 18% [...] 8off=96%)
My interface spec does not have relative dim.

>and that would require a change to the protocol.
I thought you could send absolute dim commands? (it's been a *long* time
since i looked at the specs) Is the RF signal capability different
than the powerline signal capability?

Ian Shef <invalid@avoiding.spam> writes:
>It's not the user interface that I would have chosen, but never mind that.
I'd be interested in hearing other interface designs given the current
palm pad configuration. How would you use it to control the entire x10
space? My scheme gives constant access to all 256 codes, and a
pleathora of dim levels. One that does it more efficiently does not
come to mind. Perhaps something where it acts like a palmpad, but
changing the housecode requires another button? (a button which
doesn't exist on current palmpads... but could replace the dial
wheel... press that button and then use my button scheme to choose
housecode) That's at least a little easier than the clicker
solution... but it still doesn't address upper or lower 8 which isn't
immediately available without sliding the bottom switch....

The palmpad has the capability of sending all housecodes, and it is
cheap. (esp when you get the 6 for $20 deal :) Programmable remotes
are cool, but not that cheap... and they have the disadvantages Dave
mentions of being improperly tuned for off the shelf receivers in this
country. If i were a "Tinker God" like Dave, it might be
easy... but i still havn't got around to building his AHT with the
basic chip i bought.... and it's been at least a year. :(
Heck, i havn't even put in my capacitor coupler. (I suffer from
perfectionist procrastination. If i can't do something "right" I tend
to put it off. Often "right" means figuring out a frugal and elegant
solution)

Thanks for responding!

--
be safe.
flip
Ich habe keine Ahnung was das bedeutet, oder vielleicht doch?
Remove origin of the word spam from address to reply (leave "+")

[Philip Lewis]

"Don" <kyham@k9soa.net> writes:
>anything. Forgot where I got them and what they were called. I still have
according to one of the forums, Homeautomation.com has them.... called
"clickers" and they are about 40 cents each, but shipping is high.

you also run into the possibility that the dial was not meant to
change frequently, and might wear out.

--
be safe.
flip
Ich habe keine Ahnung was das bedeutet, oder vielleicht doch?
Remove origin of the word spam from address to reply (leave "+")

[Dave Houston]

Philip Lewis <flip+spiced_ham@andrew.cmu.edu> wrote:

>(so 1on = 6%, 1off = 12%, 2on = 18% [...] 8off=96%)
>My interface spec does not have relative dim.
>
>>and that would require a change to the protocol.
>I thought you could send absolute dim commands? (it's been a *long* time
>since i looked at the specs) Is the RF signal capability different
>than the powerline signal capability?

The RF protocol allows for a single dim/bright command. The various
"transceivers" react to it differently - most send a 12% step to the
powerline, the RR501 tends to send 18% (due to a bug in its firmware). The
protocol is explained here...

ftp://ftp.x10.com/pub/manuals/cm17a_protocol.txt

[Dan]

Those are pretty cool. I found 2 more sources when doing a search for
these, but not sure how much shipping and handling is, as I was in a hurry:

http://www.pacificcable.com/X10_Misc.html
http://shop.store.yahoo.com/elights/codeclickers.html

Don wrote:
> Don't know if they are still available but I bought some little knobs that
> fit on the house code dial and made it really easy to set the HC to
> anything. Forgot where I got them and what they were called. I still have
> a couple dozen in the parts cabinet. They work on the Palmpad and
> maxi-controller. They came in both Red and Black. Maybe someone knows
> more about them. It has been almost a couple years since I originally
> bought them.
>
> Don
>
>
> "Dan" <haguru@gmail.com> wrote in message
> news:Xg6Od.339$Eq6.31@twister.nyroc.rr.com...
>
>>bblackmoor wrote:
>>
>>>I am looking for an all-housecode RF remote for X10. It does not seem
>>>to me that this should be such a difficult thing to find, but I have
>>>not found one. Any suggestions?
>>>
>>>bblackmoor
>>>2005-02-07
>>>
>>
>>If you glue a little 'tab' on the dial on a palmpad, so you can change the
>>house code without needing any other tools, wouldn't that do the job? I
>>think that's as close as you are going.
>
>
>
>

[Don]

Well I have been using them on both the PalmPad and Maxi controllers for
over 3 years and haven't had a problem yet. Then again I don't change code
every day. Basically I have a PalmPad that covers the 2/3 rooms close by.
Each room has it's own HC. For the way I use them, it makes it easier and
less changing codes.

As soon as you mentioned Code Clickers I remembered them. I think I got
mine from the person that originally made them up then went on to have
others market them for him. Been a LONG time ago.


--
Don K9SOA

www.k9soa.net
Home of JEANNIE
The House That Listens
My voice controlled automated home
as seen on HGTV and
in Home Automation and Kentucky Living magazines


"Dan" <haguru@gmail.com> wrote in message
news:AooOd.1682$Eq6.1655@twister.nyroc.rr.com...
> Those are pretty cool. I found 2 more sources when doing a search for
> these, but not sure how much shipping and handling is, as I was in a
> hurry:
>
> http://www.pacificcable.com/X10_Misc.html
> http://shop.store.yahoo.com/elights/codeclickers.html
>
> Don wrote:
>> Don't know if they are still available but I bought some little knobs
>> that fit on the house code dial and made it really easy to set the HC to
>> anything. Forgot where I got them and what they were called. I still
>> have a couple dozen in the parts cabinet. They work on the Palmpad and
>> maxi-controller. They came in both Red and Black. Maybe someone knows
>> more about them. It has been almost a couple years since I originally
>> bought them.
>>
>> Don
>>
>>
>> "Dan" <haguru@gmail.com> wrote in message
>> news:Xg6Od.339$Eq6.31@twister.nyroc.rr.com...
>>
>>>bblackmoor wrote:
>>>
>>>>I am looking for an all-housecode RF remote for X10. It does not seem
>>>>to me that this should be such a difficult thing to find, but I have
>>>>not found one. Any suggestions?
>>>>
>>>>bblackmoor
>>>>2005-02-07
>>>>
>>>
>>>If you glue a little 'tab' on the dial on a palmpad, so you can change
>>>the house code without needing any other tools, wouldn't that do the job?
>>>I think that's as close as you are going.
>>
>>
>>

[Philip Lewis]

Dave Houston writes:
>The RF protocol allows for a single dim/bright command. The various
>"transceivers" react to it differently - most send a 12% step to the
Damn... i guess it was too much to ask for the RF protocol to be the
same as the line protocol. :)

Thanks for the clarification!

hmmm... perhaps i'll read the *RF* spec and rethink my "dream"
device. ;)

--
be safe.
flip
Ich habe keine Ahnung was das bedeutet, oder vielleicht doch?
Remove origin of the word spam from address to reply (leave "+")

[Ian Shef]

Philip Lewis <flip+spiced_ham@andrew.cmu.edu> wrote in
news:qvjk6pie81s.fsf@unix42.andrew.cmu.edu:

> Ian Shef <invalid@avoiding.spam> writes:
>>It's not the user interface that I would have chosen, but never mind
that.
> I'd be interested in hearing other interface designs given the current
> palm pad configuration.

First, I have to admit that I don't know the configuration of a Palmpad.
Perhaps it is better that I am unbiased.

I don't want equal and independent access to 256 devices. Who can remember
that many codes? I would have to hang a sign on every light, fan, and
other controlled device providing its address to make use of that scheme.
I want to operate at a higher level of abstraction.

I just want access to a few independent functions, and the ability to send
out commands to a controller that will implement whatever scenes or
scenarios that I have programmed into it.

Thus, I would have a remote (for example) with 16 buttons and a 17th (and
maybe 18th) shift button. Any button (or shifted button) can be programmed
to send an ON or OFF command to any specific unit on any housecode.
Perhaps even permit it to send ALL LIGHTS ON or ALL OFF or DIM or BRIGHTEN
or any other X10 operations.

Holding the first two buttons for three seconds puts the unit into a
programming mode (LED illuminates on the unit). Press the button, or shift
plus the button that I want to program. Then press a button for the
housecode, press a button for the unit, press a button for the command.
LED blinks a couple of times to acknowledge and turns off.

When I press the button that I just programmed, it sends the command that I
programmed into it. Maybe we will set this up so that a button can even
send a series of commands. Oh, and I want the programming saved in a
nonvolatile memory, so it remains even if the battery dies. How about a
USB or RS-232 or ethernet connector so that I can connect this to my
computer, both to save the programming that I loaded, and to upload
programming that is saved on the computer or even(!) that I created on the
computer.

Now I can label each button for the function it commands.

Two shift buttons gives me {unshifted, shift1, shift2, shift1+shift2] four
possible states for each of the 16 buttons. 64 commands are a large
number, and with the right layout on the remote I might even manage to
label this much next to the buttons.

Maybe there are buttons with labels like "Dim TV Light", but there are far
more buttons with labels like: "Breakfast", "Leave House", "Arrive Home",
"Heat Spa", "Night Security", "Security Alert", "Evening", etc. that
operate (possibly via a controller) whole groups of devices.

16 buttons is convenient because it allows programming of house codes and
unit codes with a single button press, but six or eight buttons might be
sufficient, especially if I can connect to a PC for programming.

....or I can dream about what could be accomplished with an affordable touch
screen display...


--
Ian Shef 805/F6 * These are my personal opinions
Raytheon Company * and not those of my employer.
PO Box 11337 *
Tucson, AZ 85734-1337 *

[Philip Lewis]

Ian Shef <invalid@avoiding.spam> writes:
>First, I have to admit that I don't know the configuration of a Palmpad.
>Perhaps it is better that I am unbiased.
Ha, I *will* bias you.
There is a dial, which indicates house code

There is a switch near the bottom front of the unit to select which
group of 8 codes the palmpad controls

There are two columns of 9 buttons

The top 8 pairs of buttons represent on (left) and off (right) for
unit codes 1-8 or 9-16 (as determined by a manual switch on the
bottom)

The bottom two buttons of each column will send a dim or brighten
command to the house code as determined by the dial



>I don't want equal and independent access to 256 devices.
>Who can remember that many codes?
Well, not to say that i can, but i can remember that the living room
is "A", bathroom is "B" etc... (not that that's my configuration)

>I want to operate at a higher level of abstraction.
I've not gone far enough into it to have that sort of thing... Our
system is really simple. We mostly have lights on X10... with no real
conditionals. (that might change if i get a "house basestation"
computer built from the pleathora of carcasses i have laying about)
We typically use about 4 by switch, the rest are on motion based
control and come on as needed. (there are also switches for those
lights... but they are hardly ever used)

>Thus, I would have a remote (for example) with 16 buttons and a 17th (and
>maybe 18th) shift button. Any button (or shifted button) can be programmed
>to send an ON or OFF command to any specific unit on any housecode.
[...]
>Perhaps even permit it to send ALL LIGHTS ON or ALL OFF or DIM or BRIGHTEN
>or any other X10 operations.
[...Rest of description...]
>...or I can dream about what could be accomplished with an affordable touch
>screen display...

Much of your description can be done if you have a computer interface.
All you do is set up macros. (you do lose the signal space of half the
units of any given house code for each "uniquely configured" palmpad.)

Programming from the palmpad is not available with the computer
control program.... only at the computer. Also, if you want
conditionals (IF it's dark THEN turn on the light) you'll need
hardware that X10 doesn't sell directly. (or can the new CM17a (?)
unit do that?)

Also shift-buttoning is not currently available... but could certainly
be done.

Your design sounds nifty, but the premise i was going on was a single
transmitter which could easily send all 256 codes.
You were going for the "ultimate X10 remote"

Having different goals naturally led us to different designs.

Given the specs to which Dave gave the link, i think my interface
design would only change slightly:

IF (First press)=(top 16 buttons)
THEN
Change house code of pad to First_press
Get(second_press, (5 second timeout))
IF (Second_press = (top 16 buttons) )
THEN
Change unit code of device to Second_press
Get(third_press, (5 second timeout))
ELSE
IF First_press = DIM
THEN
Send OFF on stored house/unit-code
ELSE
Send ON on stored house/unit-code
ENDIF
ENDIF
ELSE
IF First_press = DIM
THEN
Send DIM on stored housecode
ELSE
Send BRIGHT on stored housecode
ENDIF
ENDIF

(ummm this is a quick runthrough i think it covers what i have in
mind)


--
be safe.
flip
Ich habe keine Ahnung was das bedeutet, oder vielleicht doch?
Remove origin of the word spam from address to reply (leave "+")

[Just Another Joe]

Yes, it's an almost two-year old thread, but interesting!

See reply at bottom.


On 10 Feb 2005 15:29:43 -0500, Philip Lewis
<flip+spiced_ham@andrew.cmu.edu> wrote in message
<qvjll9wduq0.fsf@unix42.andrew.cmu.edu>:

> Ian Shef <invalid@avoiding.spam> writes:
> >First, I have to admit that I don't know the configuration of a Palmpad.
> >Perhaps it is better that I am unbiased.
> Ha, I *will* bias you.
> There is a dial, which indicates house code
>
> There is a switch near the bottom front of the unit to select which
> group of 8 codes the palmpad controls
>
> There are two columns of 9 buttons
>
> The top 8 pairs of buttons represent on (left) and off (right) for
> unit codes 1-8 or 9-16 (as determined by a manual switch on the
> bottom)
>
> The bottom two buttons of each column will send a dim or brighten
> command to the house code as determined by the dial
>
>
>
> >I don't want equal and independent access to 256 devices.
> >Who can remember that many codes?
> Well, not to say that i can, but i can remember that the living room
> is "A", bathroom is "B" etc... (not that that's my configuration)
>
> >I want to operate at a higher level of abstraction.
> I've not gone far enough into it to have that sort of thing... Our
> system is really simple. We mostly have lights on X10... with no real
> conditionals. (that might change if i get a "house basestation"
> computer built from the pleathora of carcasses i have laying about)
> We typically use about 4 by switch, the rest are on motion based
> control and come on as needed. (there are also switches for those
> lights... but they are hardly ever used)
>
> >Thus, I would have a remote (for example) with 16 buttons and a 17th (and
> >maybe 18th) shift button. Any button (or shifted button) can be programmed
> >to send an ON or OFF command to any specific unit on any housecode.
> [...]
> >Perhaps even permit it to send ALL LIGHTS ON or ALL OFF or DIM or BRIGHTEN
> >or any other X10 operations.
> [...Rest of description...]
> >...or I can dream about what could be accomplished with an affordable touch
> >screen display...
>
> Much of your description can be done if you have a computer interface.
> All you do is set up macros. (you do lose the signal space of half the
> units of any given house code for each "uniquely configured" palmpad.)
>
> Programming from the palmpad is not available with the computer
> control program.... only at the computer. Also, if you want
> conditionals (IF it's dark THEN turn on the light) you'll need
> hardware that X10 doesn't sell directly. (or can the new CM17a (?)
> unit do that?)
>
> Also shift-buttoning is not currently available... but could certainly
> be done.
>
> Your design sounds nifty, but the premise i was going on was a single
> transmitter which could easily send all 256 codes.
> You were going for the "ultimate X10 remote"
>
> Having different goals naturally led us to different designs.
>
> Given the specs to which Dave gave the link, i think my interface
> design would only change slightly:
>
> IF (First press)=(top 16 buttons)
> THEN
> Change house code of pad to First_press
> Get(second_press, (5 second timeout))
> IF (Second_press = (top 16 buttons) )
> THEN
> Change unit code of device to Second_press
> Get(third_press, (5 second timeout))
> ELSE
> IF First_press = DIM
> THEN
> Send OFF on stored house/unit-code
> ELSE
> Send ON on stored house/unit-code
> ENDIF
> ENDIF
> ELSE
> IF First_press = DIM
> THEN
> Send DIM on stored housecode
> ELSE
> Send BRIGHT on stored housecode
> ENDIF
> ENDIF
>
> (ummm this is a quick runthrough i think it covers what i have in
> mind)

I've been doing something very similar to this for over three years,
using standard palmpads and an Ocelot. The palmpads are on a dedicated
house code, distinct from the house code(s) of the controlled devices.
Every palmpad command goes to the Ocelot, which interprets it and sends
appropriate PLC commands, which may be individual device commands or
entire macros. For the controlled devices, I use seven distinct house
codes, so that 'All Off' can be used to quickly turn off a specific
group of units. It works like this:

The palmpad's eight on/off pairs, together with the group slider switch
at the bottom, address 16 units, exactly like the usual operation. The
'bright' button functions as a 'shift up' command, giving access to
another 16 units by first pressing 'bright' and then pressing a
unit-on/off button. The 'dim' button functions as 'shift down,' giving
access to 16 more units, for a total of 48. So, 1on/1off addresses the
first unit, shift-up followed by 2on/2off address the 18th unit,
shift-down followed by 3on/3off address the 35th unit, and so on.

With the slider in the '1-8' position, the unshifted eight button pairs
address my most frequently used eight devices. In the '9-16' position,
the unshifted eight 'on' and eight 'off' buttons each activate a macro,
which are my 16 most frequently used macros. Less frequently used
devices/macros are addressed with shift-up and shift-down.

In addition, I have three ceiling fans with lights, each with three
speeds plus 'off,' which are operated by RF controlled from the Ocelot.
Each fan's light is controlled in the usual way by one of the 48
available units of the palmpad, while its speed is controlled by four
consecutive palmpad buttons, eg. 1, 2, 3, 4 or 9, 10, 11, 12
representing 'high,' 'medium,' 'low,' and 'off,' when preceded by
'bright,' 'bright,' or as I like to think of it, 'shift-up,' 'shift-up.'
The base digit (the first of the four consecutive) is the same as the
unit number which operates that fan's light, making it easy to remember.
So, for example, if unit 5on/5off controls the lights of the kitchen
fan, then shift-up, shift-up, 5/6/7/8 will control the kitchen fan's
speed. It doesn't matter whether 5on or 5off is pressed; both are
interpreted as 'high' for convenience, and so on. Of course, the fan's
lights and speeds can be controlled within macros as well.

Finally, shift-down-shift-down-number (eg. 'dim,' 'dim,' 4[on or off])
will send an 'All Off' command for the house code 1-8 represented by the
number. The numbers can represent any house codes one likes, and don't
have to represent A, B, C, D, E, F, G, H. Since I'm using only seven
house codes for devices, the numbers 9-16 are interpreted as 1-8 for
convenience, so it doesn't matter which position the slider switch is
in. If one's devices are grouped appropriately by house code, then for
example, dim-dim-5[on or off] can be used to quickly turn off all the
master bedroom/ensuite/closet lights, or maybe dim-dim-14(6)[on or off]
turns off all the lights in the basement.

While I've spoken of palmpads throughout, this also works with all my
maxi-controllers and mini-controllers. With the plug-in controllers,
there is no need to press 'on' or 'off' when doing such actions as fan
speed or group-off. Simply pressing bright-bright-7 (without pressing
'on' or 'off') will set a fan's speed to low, or dim-dim-11(3) will do
group 3's 'All Off' without having to press 'on' or 'off.' I don't use
the plug-in controllers' 'All Lights On' and 'All Off' buttons, since
there is nothing equivalent available on the palmpads.

Similar programming services sticky-switches, though they are on
differing house codes, so can be interpreted differently according to
room.

The one thing that this scheme does not afford, is direct manual
dimming, since the bright/dim buttons are used as shift keys. So, while
one can't hold the bright or dim button to manually adjust a lamp level,
it can still be accomplished by use of scenes, either using scene
enabled switches/modules, or by Ocelot control.

This has served me well for over three years, with the only downside
that I've experienced being the extra delay of the added signal hop.
But, I'm always interested in new and better ways of doing things, and
would like to hear what others are doing.

--
Just Another Joe Remove .windows to reply.
Why be politically correct, when you can be right?