HG dimming lights for no reason

[bkenobi]

I have 3 exterior lights that are connected with 3 different types of X10 modules (all dimming though).  In HG, I have the "turn on to 100%" module turned on and each of the lights is set to a dimmer.  I can control the lights via an in-wall transmitter (XPT), the web interface, or the Android app correctly.  I also have a second CM15A hooked up to a Windows machine running AHP with nothing configured (simply for logging activity).

Last night, when the lights were turned on via the XPT, the lights turned on to a very low level.  The lights were at 100% on their last usage (we don't dim these lights).  When I went back and reviewed the activity log, it did indicate that commands were sent to dim the lights to 22% for one and some other value for the others.  This was also confirmed when looking at the AHP activity log.  I don't have a repeatable test to see what's going on in that one case, so I'm not sure what to look at other than the couple activity logs and the "100% when turned on" code.

[bkenobi]

I did a little more digging and it looks like the logs indicate that HG thinks it sent the right thing, but AHP disagrees.  These are the lines HG shows in the log:

Code: [Select]

"2014-07-06T22:38:45.9098000-07:00 HomeAutomation.X10 A2 - Status.Level 1"
"2014-07-06T22:38:45.9109930-07:00 HomeAutomation.HomeGenie.Automation 84 Automation Program X10 Auto Bright BBQ light<br>A2 set to 100%"
"2014-07-06T22:38:45.9133850-07:00 HomeAutomation.X10 A2 - Status.Level 1"
"2014-07-06T22:38:49.5708940-07:00 HomeAutomation.X10 A4 - Status.Level 1"
"2014-07-06T22:38:49.5720690-07:00 HomeAutomation.HomeGenie.Automation 84 Automation Program X10 Auto Bright Kennel light<br>A4 set to 100%"
"2014-07-06T22:38:49.5746780-07:00 HomeAutomation.X10 A4 - Status.Level 1"
The attached pictrue shows what AHP saw as input.  I think the M3 was sent correctly as A3 (the light turned on), but it was garbled before HG or AHP saw it.  The problem lies with A2 and A4 in that they were dimmed to 44% and 5% for some reason instead of turning on to 100%.  HG thinks it sent 100%, but the lights did not see that command nor did AHP.  So, either it did send the command and it got misinterpreted as 44%/5% dim or it was actually sent incorrectly.

Any thoughts?

[bkenobi]

I found a way to break HG!  Well, not exactly broken, but not responding as expected.  I have 2 issues.

1) When a Control.Level command is sent, HG thinks the lights were turned on. 

Code: [Select]

Modules.WithName("BBQ light").Command("Control.Level").Set("100");This does not send the correct command to turn on X10 modules though.  It sends a command such as:

Code: [Select]

A2
A BRIGHT 100%This does NOT turn the light on and only does anything if the module were already on (it ignores the command otherwise...for X10 anyway).

2) When a Control.Level is sent, it can send a spurious dim level after sending an intended one.  I have used the attached very simple code (1005-test.hgx) to generate the AHP log.  I simply told the light to turn on to 5% (which appeared to be more like 50%) and then 100%.  This worked, but it then appears to have dimmed it to 94% according to AHP.  I can't tell the difference in light level, but since it did the same last night at lower levels, I believe it's actually sending the command.