Print

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

[X10 Pro]

I know there are a few of you who have been waiting for this for a while. This release adds support for the new Sentinel dome camera, and includes fixes for a number of outstanding bugs:

• Added support for new Sentinel dome camera.
• Added Vanguard-style draw/zoom (with Vanguard and Sentinel cameras).
• Fixed room and house "All Lights On" commands so they don't sends On commands to all modules.
• Fixed crash occurring after opening a module note and then switching rooms.
• Fixed problem with incorrect status display for modules on monitored house code.
• Fixed video recording problem where system performance couldn't match specified frame rate.
• Timestamp on pictures saved during Standard Time not changed when viewed during Daylight Savings.
• Fixed video timestamp to display local time, not GMT.
• Made deleting a module with an associated timer set the "Need Download" icon correctly.

   
You can get the update directly from:

   http://software.x10.com/pub/applications/activehome/ahp_updt.exe

You can roll back to the previous release version with:

   http://software.x10.com/pub/applications/activehome/ahp_updt_203.exe

[Dan Lawrence]

Thank you!!!!

Tonight was the first time the status of A1 and A3 were correctly shown. Both lights were on when the timer ran and the status of both was unchanged.

[steven r]

Thanks!

I'll download it soon and let you know if the bug I found about the monitored HC setting is still there. (It wasn't listed in the fixes above.)

Tested and the bug is still there. See my post on May 13, 2006 of the bug here.

[JimC]

I installed the new update last night and all seemed to go well. I woke up this morning to find all of my macros that have delays in them running fast. One example is a macro that is triggered by a motion sensor which starts a macro that turns on a light and after 30 minutes turns it back off. It is now turning of in 10 minutes or less. I did not have time to get into it this morning as I needed to get to work. When I get home tonight I will remove power to the CM15A and reload the program and see if that helps.

 I will keep you informed.

 

[Chris S.]

My problem with the AHP right now is primarily with Iwitness and the recording features.
So I was very much looking forward to this update.

I had posted a fairly detailed bug report for v3.203 concerning recording video initiated by a macro,
and AHP crashing, or video cut short, and also sent my *.ahx file request by x10 Pro.
Reference Post: http://www.x10community.com/forums/index.php?topic=8245.45


I installed the v3.204, and ran some tests for macro initiated video recording, and AHP would shutdown
each time during the record process. Not crash, but just shutdown.

I did not want to get into any extensive testing with a detailed report (no time),
so I reverted back to the 3.203 version.

I use AHP primarily for module control, macros and timers, I only have one camera,
so I think at this point I'll hold off indefinitely on adding any more cameras until
there is a release that corrects the Iwitness module.

Currently looking at some alternative camera solutions for my needs which
provide a higher degree of reliability.

I'll post some detailed info concerning my 3.204 problems at a later date,
when I get a bit of time to spare.

[JimC]

Dumping the memory in the CM15A seems to have taken care of my "delay"  problem.

[JimC]

Seems like ever since the update the problem in my original post is a reoccurring one. Delays in macros are running fast. 30 minute delays execute in less than 10 minutes. Dumping the interface memory and reloading the program takes care of the problem but it reoccurs, sometimes in a couple of hours and other times in a day or two. All timers seem to be running correctly. The problem only seems to be with delays used in macros.
 
I did not have this problem before installing the most recent update.

 

[EdMaxx]

When I try to install the latest 3.204 update, I get an error message:

This software requires an additional 8400K bytes free on the F: drive to install.  Please remove any unnecessary files and try again.

I used to have an F: drive, but no longer have it.  It acts like it's trying to install from a non-existent F: drive.

[steven r]

When I try to install the latest 3.204 update, I get an error message:

This software requires an additional 8400K bytes free on the F: drive to install.  Please remove any unnecessary files and try again.

I used to have an F: drive, but no longer have it.  It acts like it's trying to install from a non-existent F: drive.

I have a similar problem when I try to update iTunes on my laptop. Somehow from a previous incarnation my laptop thinks it has a F drive also. I suspect the registry is screwed up somehow. Unfortunately I have no idea how to repair the registry. I have to plug in a flash drive to fool it into thinking I have a F drive everytime I update.

[Dan Lawrence]

When I try to install the latest 3.204 update, I get an error message:

This software requires an additional 8400K bytes free on the F: drive to install.  Please remove any unnecessary files and try again.

I used to have an F: drive, but no longer have it.  It acts like it's trying to install from a non-existent F: drive.

PM X10Pro with your very strange problem. X10Pro is "the boss" here, he will not ignore your private message

Sounds to me it's time to back up everything you feel should be backed up, reformat the C:\ Drive and re-install the O/S and all applications you want. Sounds like the registry is corrupted so badly, Windows can't even restore it to good condition.

[EdMaxx]

When I try to install the latest 3.204 update, I get an error message:

This software requires an additional 8400K bytes free on the F: drive to install.  Please remove any unnecessary files and try again.

I used to have an F: drive, but no longer have it.  It acts like it's trying to install from a non-existent F: drive.

PM X10Pro with your very strange problem. X10Pro is "the boss" here, he will not ignore your private message

Sounds to me it's time to back up everything you feel should be backed up, reformat the C:\ Drive and re-install the O/S and all applications you want. Sounds like the registry is corrupted so badly, Windows can't even restore it to good condition.

That's okay.  I just renamed my backup drive E: to F: and it let me install it.

[Dan Lawrence]

Good. As to the backup/reformat game, been there, done that, don't wanna do it again. 

[Tuicemen]

BUG:   This took me a while to notice as I've been on holidays and when not I was not paying close attention to my flags!
 I noticed my macros that trigger a phantom switch which in turn triggers another macro to set a flag no longer works! Today  I did a little digging to see if I'd mistakenly added another macro which switches this off  ( I sometimes do strange things trying to help others) . Thats not the case. If I select the phantom switch to turn on /off the flag it works. I've worded the problem macro so it directly sets the flag to see if that fixes my flag problem! I'm not sure if all my macros can be edited to do this.now we'll wait until tomorrow to see if everything fires off as intended!    Was this intetional in order to fix something else?

[Tuicemen]

Well seems my modification worked? my question now is: Has anyone else noticed that their macros fired from another macro no longer work? Or is it just if flags are involved?
Originaly X10Pro stated "macros were not designed to trigger other macros " So we users came up with the Phantom module work arround to allow this! Now this work arround no longer works (for me).

[steven r]

...Has anyone else noticed that their macros fired from another macro no longer work? Or is it just if flags are involved?...

The good news / bad news (Good for me. Bad for you.) is that mine still appear to be still calling macros ok.
While some of my calling macros set and test for flags, I don't believe any of my called macros use any flags, however.
If I have some time I'll try to set up a test but it will be awhile till I can do it.
Have you tried building a new macro calling a macro test? Clearing memory and reloading the CM15A?