Print

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

[Noam]

I'm running AHP 3.306 on Windows 7 64-Bit.
I noticed what I thought at first was a fluke, but now I realize seems to be repeatable.
Every time my PC reboots, AHP sends duplicates of every command. It isn't just that the lines are repeated in the Activity Monitor, but that the sequences (like when macros run) actually run through a second time.
I have several timers that are set to run at the same time, and I see the whole sequence of them run through a second time.
If I open AHP, and then close it (without making any changes), then it no longer sends the double commands (at least not until the next reboot).
I first noticed this a few weeks back, but I didn't realize it happens every time my PC reboots.
Edit: I just did some more testing. Stopping and restarting the x10nets service causes the duplicate commands to happen again. Opening and closing AHP fixes it again.

Has anyone else seen this with their own systems? I just reported it to the developers, but I don't want to add it to the "bug list" yet if I'm the only one having this problem.

[Tuicemen]

Is AHP set to open on windows startup?
Are the x10 events actualy firing or only showing in the activity monitor?
I'll try to reproduce. 

[Noam]

AHP is NOT set to open at Windows startup.
From the looks of it (watching from a second Pc that has its own CM15A), the commands ARE being sent twice.
My simple test is a macro I have (M14), that activates a chime module (M15). I don't keep the chime plugged into the wall most of the time, though.
Right after booting up, if I use AHCMD to send an "M14 On", I'll see the "M14 On," followed by TWO sets of "M15 On," when looking from the other PC.
If I open and close AHP, then I only see ONE "M15 On" after the "M14 On."

If I stop and restart the X10nets service, and re-run the test, it behaves the same. Two sets before AHP is opened, one set after.

If you are able to duplicate this behavior, I think we can classify it as a "bug." If I'm the only one, then I think it is still a "quirk" until we can determine the cause.

[Noam]

More information -
I tested this on one of my XP SP3 systems, and I get the same results!
I hadn't noticed it before, because I mainly use them for monitoring, and sending commands using the SDK. There are no stored timers or macros. I created a macro (same thing - just runs a simple command), and I was able to duplicate the behavior.
Since this is a separate PC, (located at work, not at home), running a different AHX file, I'd say that I was able to independently duplicate the results. Anyone else?

[Tuicemen]

This may explain why sometimes PCC was producing duplicate sound alerts!
Man I was going nuts trying to sort that out!
I can duplicated this on my Win 7 64 bit machine!

[Noam]

This may explain why sometimes PCC was producing duplicate sound alerts!
Man I was going nuts trying to sort that out!
I can duplicated this on my Win 7 64 bit machine!

Thanks for testing. I'm going to add it to the Bug List.

[Dan Lawrence]

This is interesting.  I'm running 3.306 on a XP SP3 machine and after a reboot, there are no duplicate commands being sent, just the usual lack of X10Nets.exe not running so AHP does not show proper status of modules.   Nothing like what Noam is experiencing.

[Noam]

This is interesting.  I'm running 3.306 on a XP SP3 machine and after a reboot, there are no duplicate commands being sent, just the usual lack of X10Nets.exe not running so AHP does not show proper status of modules.   Nothing like what Noam is experiencing.

Dan -
X10nets not running at startup is NOT considered "usual," by the way.

If your X10nets service is not running, then you probably won't be able to experience the problem (or monitor events, etc).

[Brian H]

On my XP setup when AHP got installed. The x10nets was set to auto start and I believe starts at boot time.
Even if i reset it to manual. It starts when I first run AHP.

[Dan Lawrence]

This is interesting.  I'm running 3.306 on a XP SP3 machine and after a reboot, there are no duplicate commands being sent, just the usual lack of X10Nets.exe not running so AHP does not show proper status of modules.   Nothing like what Noam is experiencing.

Dan -
X10nets not running at startup is NOT considered "usual," by the way.

If your X10nets service is not running, then you probably won't be able to experience the problem (or monitor events, etc).

My x10Nets runs like it always does at windows start up. When windows shuts down I always get the message x10Nets is being shut down, so when the reboot is done and windows reloads, AHP does not see proper module status even though all x10 controlled lights are still on.  It's done that since AHP came along in 2005.

[Noam]

My x10Nets runs like it always does at windows start up. When windows shuts down I always get the message x10Nets is being shut down, so when the reboot is done and windows reloads, AHP does not see proper module status even though all x10 controlled lights are still on.  It's done that since AHP came along in 2005.

Dan -
It sounds like your x10nets service is not configured properly.
What OS are you using?
How is the service set to start? What user is it set to run as?

[Tuicemen]

AHP never did show correct module status on a restart with or without x10nets running!
AHP attempts to try but rarely gets it right!

However X10nets should restart.
If X10Nets isn't restarting then there definitely is a issue there Dan!
Do you have to manually restart the X10Nets?

[Dan Lawrence]

AHP never did show correct module status on a restart with or without x10nets running!
AHP attempts to try but rarely gets it right!

However X10nets should restart.
If X10Nets isn't restarting then there definitely is a issue there Dan!
Do you have to manually restart the X10Nets?

X10Nets starts promptly on a reboot, it's on the shutdown that X10Nets gets shut down.  You are correct when you said "AHP never did show correct module status on a restart with or without x10nets running!".   

[Dan Lawrence]

My x10Nets runs like it always does at windows start up. When windows shuts down I always get the message x10Nets is being shut down, so when the reboot is done and windows reloads, AHP does not see proper module status even though all x10 controlled lights are still on.  It's done that since AHP came along in 2005.

Dan -
It sounds like your x10nets service is not configured properly.
What OS are you using?
How is the service set to start? What user is it set to run as?

See my reply to Tuicemen below.