Socket Rocket Problem - Request Feedback

[fingerae]

I am a long time X10 user and am very familiar with the home automation modules and remotes.  I have recently installed several Socket Rocket modules around my house.  I have run into a unique problem.

Step 1:  Unit code 8 is currently on and unit code 9 is currently off (both controlled by Socket Rocket modules)
Step 2:  Using a Palm Pad remote control, turn unit code 8 off.
Step 3:  Unit code 9 turns on automatically.

If unit code 8 is currently off, the Palm Pad unit code 8 off button can be pushed, and unit code 9 will not turn on.

After further testing and trying different Socket Rocket modules and unit codes, I have found that this problem occurs any time adjacent unit codes are used with Socket Rocket modules in each one.  For example, if lamp A is on unit code 1 and lamp B is on unit code 2, lamp A is on and lamp B is off, the off button is pressed on the Palm Pad remote on unit code 1, then lamp B will turn on.  Is this a common problem with the Socket Rocket modules?

Please help!  It's in my bedroom, and that is a rude awakening at night.

Thanks.

[JimC]

This is a strange problem. A couple of questions.
1 Are you running AHP
2 Do you have any motion sensors on the same house code?

Jim

[HA Dave]

I am just thinking out loud here... (actually, I am just typing as I think). Could you have a busted/damaged/defective palmpad? Do you have another remote you could try?

[dave w]

fingerae

Sounds like your Palm Pad is trying to act like Scan Pad camera remote. Is the Palm Pad new?