Print

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

[Noam]

It looks like X10 released a new update to ActiveHomePro this morning.
Here are the release notes for version 3.296:
    * Bug fix: Secure Commands not being shown in Activity Monitor
    * Filter out unknown command caused by transceiver initialization
    * Altered behavior of missing transceiver pop-up for simple video bundle
    * Fix for possible crash when opening Activity Monitor with empty history

Well, hiding some of the "garbage" some of us were seeing was good (for those that don't want to see it), but I no longer have an indicator of when my CM15A is re-initializing itself (which it was doing several times a day, with no explanation so far).

[mcguyver]

lol: i uninstalled everything and cant get past installing ahp 296 without it crashing. Even after cleaning out my reg.
I shoud have waited. lol

Update: I was able to uninstall then do a restore back to yesterday and now i am fine. That was fun. NOT.

[phongluu]

The email send out still not being fixed.
After a reboot, an email sent out by AHP still showing default sender: AHPGateway@x10.com.
Why is it not saved with my setup?

Yet, it will send out with my setup ONLY after I go to email confg. And it goes back to default setting again after AHP/computer reboot.

P.L

[anthonylavado]

@phongluu
Are you making the change in the Config while AHP is closed?

[phongluu]

I changed at My house tab>Email Config on the AHP main MENU.

I dont think we can change it while AHP close, cannt we? ...well...unless doing regedit.
Do you know a way?

Thanks,
P.L

[anthonylavado]

@phongluu
C:\Program Files\ActiveHome Pro\

I think it's called emailconfig.XML or similar. Open it with Notepad.

[phongluu]

I'm looking into the emailprp.xml, all of the email add in there is my config. Non showing AHPGateway.
Again, it's still showing AHPGateway as a sender on email after reboot.

Thanks,
P.L

[phongluu]

OK, after few hours of testing new version 3.296: there are still ton of M MTCDDVD receive RF in my Activity Moitor.
It looks like everytime the Sensor Closed feedback, it give that M MTCDDVD twice.

grrrrr

P.L

[Dan Lawrence]

With all the negative posts it sure appears to me 3.296 goes right into the bad release file of AHP with 3.236.  Makes me glad I don't use any plug-ins.  Don't need any one.

[J.B.]

Actually 3.296 is working much better than several of the last builds.
The M MTCDDVD command was also showing up in my activity monitor last night until I did a bit of testing.
This was happening with 2 MS10As and oddly enough, once I changed their security codes several times, reinstalling the sensors to AHP each time to test, eventually it stopped.
Almost seems AHP doesn't like certain security codes from devices, or something is being corrupted during updates.
It doesn't seem to cause any issues other than making navigating the log file a bit of a pain.

Either way, 3.296 has fixed several issues I had seen using the last 3.295 build, so it's a step in the right direction IMO. 

[Noam]

With all the negative posts it sure appears to me 3.296 goes right into the bad release file of AHP with 3.236.  Makes me glad I don't use any plug-ins.  Don't need any one.

Dan - Perhaps users who are having problems with 3.296 simply need to do a complete uninstall and fresh reinstall to fix the instability. ;-)

[ErikP]

This was happening with 2 MS10As and oddly enough, once I changed their security codes several times, reinstalling the sensors to AHP each time to test, eventually it stopped.

the M MTCDDVD commands are actually valid security commands which are correctly stored in your history, but the monitored security code is not functioning properly, and this causes the Activity Monitor window to parse them incorrectly.  The bug that was introducing the problem was fixed in 296, but that doesn't remove it from all affected systems.  The problem can be fixed by overwriting the monitored security code by removing your secure modules and adding them back in.  You shouldn't need to change change the codes on the devices.  When you overwrite the bad code, the next time your history is built the M MTCDDVD will be read properly for what they are and displayed as security commands in the log.  If you change the codes, then the events in your history will no longer be on a monitored security code and will not be written to your Activity Monitor.

This is working on all of the tests systems which encountered this error, but definitely let me know if you are seeing something different.

[phongluu]

I have run this version 3.296 over a night and some of my Macro trigger for some no reasons due to a Security sensor.
Looking at the log, for 1 minute, the sensor has more than 15 feedbacks: triggered, closed, M MTCDDVD.
And I'm 100% sure the sensor didnt open or close at night otherwise my DS7000 would go into alarm and wake everyone up.

Please fix this.
In addition, it would nice for someone to look into why on a Macro that using Securiy sensor a trigger then using condition (time range, day range, flag status) would NEVER work. Instead, it just can only turn on a dummy device than using that device to trigger with conditions.

Thanks,
P.L

[ErikP]

Looking at the log, for 1 minute, the sensor has more than 15 feedbacks: triggered, closed, M MTCDDVD.
And I'm 100% sure the sensor didn't open or close at night otherwise my DS7000 would go into alarm and wake everyone up.

Have you removed and re-added the secure devices?  I didn't see it happen in my testing, but its possible the same thing causing the M MTCDDVD to appear in the first place is causing extra commands to appear in the log as well.  Is anyone else seeing extra unexplained security commands in their Activity Monitor?

[J.B.]

When I was getting the M MTCDDVD show up it was along with the proper MS10A triggered command.
It stopped for me when I changed the security code on the MS10As several times while reinstalling the sensor to AHP each time.
Then I would trip the sensor to see if was still displaying M MTCDDVD.
I didn't actually delete the module from AHP as far as I remember.