Well looks like I dumped that email. however what caused from my questioning the RF send was his add of the Cm19 code to HG.as Originaly the cm19 could see and send RF but the CM15 could only see it and react to it.
I asked if there was away to add the RF send code that the Cm19 used to the Cm15 as from my experience they sent the same code.
I believe you helped with the add of the Cm19 to HG as well, And if I remember correctly Gene had no cm19 to test perhaps the cm19 code uses the dashes and when he combine the send into the Cm15 code it wasn't changed for spaces it is easier to just add one line of code to respond to both dashes or spaces then to change all X10 codes.
Possibly if you go through the cm19 issues you may find a clue, to me it is irrelevant. HG works. Could it use a total rebuild sure most things can benefit from that.
Dumped the email?? Shame seeing as this is the basis for this confusion. I'll drop Gene a message on the subject for clarification.
Yes I suppose you could say I "helped with the add of the CM19" as I was the one that requested it in the first place.
The fact that something appears to work doesn't mean it actually works as it is supposed to and doesn't future proof it in any way.
I'm now going to have to trawl through the CM19 driver code to see exactly what method was used to define the Hex codes. Thankfully i have the assistance of another experienced HG coder to do this. In the meantime maybe Gene can verify this if or when he replies. I do know that he now has a CM19 to help with this verification.
I want to get to the bottom of this. Nothing worse than heresay and loose ends when it comes to a project. I'll leave the rest of the HG troubleshooting to you on the X10 Forum. The users here are of a very delicate disposition and I wouldn't want to upset them any further
You can assume the role of the 24/7 support bot