Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

After being derailed for a couple of weeks on other tasks, I started working on this again.  The serial input has been converted to interrupt driven, so that should prevent loss of communication from the computer unless the actual message is corrupted.  I have been testing this with a terminal emulator, but it will need to be tested with an actual Smartenit Harmony.

It presently supports receiving and transmitting X10 commands as well as the Reset and Get Version commands in case they are needed by the Harmony.  It will ignore and issue the LED serial error if it receives any other command.

Also, there is no double buffering, and it will not accept another send X10 command until the pending send X10 command has completed transmitting.

Note that it will support X10 only.  And converting pre-set dim to extended has not yet been implemented.

Jeff

The 2412U uses two Hex commands to send the X10 address and then the X10 function.
Send X10 A4  (adddress)
02 63 6A 00

Send X10 A On (function)
02 63 62 80

I get the wrong light coming on or off a couple of times a week. My most common is A8 ON and A4 comes on with it. I have always chocked it up to noise. How many LED bulbs have you added in the last few years. 

Just a thought... turn the code wheels on those modules back and forth a few times to scrape off any oxidation that could cause an error.

I really doubt this was the issue (bad wheel connections) as two modules responded incorrectly to the command.  I've seen no issues when commanding either from the WM100.  This happened when I asked Alexa (via the P2) to turn on a light in the bedroom.  Also, when I realized what had just happened, all I did was send two separate commands from my WM100 to turn the pump off and bedroom light on and those responded correctly.  I really think the P2/PLM sent the wrong device address and I just happened to have a module on that code.  I don't think it was an Alexa issue either as for those times it would not control my house, I was using the Smartenit app.  Now was the PLM sending codes but not the right ones?  I don't have a signal meter to know.

Is there a 3 way light switch that one can use and be sure it will not have the problem most switches do of ignoring commands that are sent to the switch from a macro ??

I will check in the Insteon Modem Developers Guide and see what the send X10 shows. I know it is a strange arrangement that didn't make too much sense to me either.

Just a thought... turn the code wheels on those modules back and forth a few times to scrape off any oxidation that could cause an error.

E8 = 0001 1101
D10 =1010 1111

Both House and Unit codes are different so I don't think that's the problem. I suspect that the problem may be with the PLM firmware version as I've never had an issue with mine which are older.  Since the PLM can't be updated perhaps Al will have a f/w upgrade for the P2 to solve it.

Thanks.  Never did understand their "binary count" logic.  I hope they can make a work around for the P2.

E8 = 0001 1101
D10 =1010 1111

Both House and Unit codes are different so I don't think that's the problem. I suspect that the problem may be with the PLM firmware version as I've never had an issue with mine which are older.  Since the PLM can't be updated perhaps Al will have a f/w upgrade for the P2 to solve it.

Well of course when I say it has been working flawlessly, it goes south yesterday.  But here is the interesting part.  I use it for Alexa control mostly, and I asked her to turn on the bedroom lamps (code D10).  Instead I noticed that my sprinkler pump (code E8) activated from that request.  I believe it has happened another time as the sprinkler pump was running a couple days back and was not supposed to be on.  I have also had some unexplained activations of other devices.  So for those in the know, is there a similarity between E8 and D10 (one bit difference in packet?) that might point at something?