X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: Noam on March 25, 2011, 06:42:18 AM
-
AHP version 3.310 was released today.
Here are the changes:
Version 3.310 Updated 03/25/2011
* AHP: Human readable EEPROM output (ahpeeprom_w.txt) is once again generated correctly.
* AHP: New dynamic Installer framework.
* AHP: Fix for 500 errors when accessing mobile apps resulting from unstable network connectivity.
* AHP: Registration dialog is more clear about which registration code to use when registering ActivePhone.
* AHP: Module History button in Room View now properly parses history data.
* AHP: Bright level is more correctly preserved between sessions of ActiveHome Pro.
* AHP: Fix for bright/dim commands not always sending properly when using a CM19.
* MyHouse Online: Fixes for various MyHouse Online crashes when run in Internet Explorer Protected Mode.
* MyHouse Online: MyHouse Online connection history is now stamped with local time.
You can download the new version here:
http://www.x10.com/support/support_soft1.htm
Here is a link to the revision list:
http://www.x10.com/support/rev_ahp.htm
-
I already found a few things, which I added to the Bug List.
We keep a separate thread for the Bug List, which is here: http://forums.x10.com/index.php?topic=22373.0
This is what I found so far:
1. Changing a module between "Lamps" and "Old Lamps" does not change the color of the bar at the top until you go out of the room (or AHP) and go back in.
This is a new bug in 3.310 (at least I didn't notice it in 3.306). It is a cosmetic issue, but there is no reason not to fix it in the next version.
2. "Florescent Decorator Switch" sends extended commands if defined as a "New" lamp.
This is also a new bug in 3.310. I had a number of SmartHome relay (non-dimming) switches that were defined in AHP as "Florescent Decorator" switches (WS13A-L). When 3.302 introduced SoftStart support, I noticed these didn't change their behavior, even if defined as "Lamps" instead of "Old Lamps - no SoftStart." However, in 3.310, I see that AHP now sends an Extended Dim command to turn them on. Do the newer (post 2008) WS13A-L switches turn on with an Extended command? If so, then I wonder why the change wasn't made earlier. If not, then it is a bug that needs to be corrected. When I changed them to the "Fluorescent Decorator Switch" from the "Old Lamps" list, they worked fine.
3. SDK sends extended commands for Unit codes defined as SoftStart modules in AHP.
This is another one that is new in 3.310. I found it by accident, too. I was trying to control my "Florescent Decorator Switch" (see #2 above), but it wouldn't go on. Even using the AHCMD wouldn't do it. My PalmPad could turn it on, and I could turn it off in AHP (or with AHCMD), but I could not get it to go on. I checked the Activity Monitor, and sure enough I saw the Extended Dim commands. (I discovered this together with bug #2). Once I changed the module definition in AHP, AHCMD would send the correct "On" command. It looks like there is no longer a way to specifically send "on" commands for a module that is defined in AHP as SoftStart.
Edit: I did some more testing. interestingly enough, sending an "on" to a SoftStart module now instead sends it an Extended Dim command to the level it was last at (either the current level of it is on, or the last level if it is off). I'm sure this will mess up a lot of people who use the SDK. There is no mention of this behavior change in the release notes at all (unless it has something to do with them changing the SoftStart dim level status that had been broken before).
4. Changing a module between "Lamps" and "Old Lamps" should keep the current "module type" selection, instead of defaulting to the first item in the list.
This started with 3.302, but I haven't bothered to report it. It is less of a "Bug," and more of an "Annoying feature."
Since those of us with older modules have to re-define them as "Old Lamps," It would be nice if we could do that by just changing the first drop-down, instead of having to change both. Again, it is a cosmetic thing, but still a nice thing to get fixed.
I also confirmed a few bugs were fixed. I don't have the ability to test them all, but I did mark the ones I could confirm as "fixed" in the list.
Hopefully, as more users install and test 3.310, we will get a better picture of how it is working, and get the developers working on ironing out the kinks.
-
It appears the "MyGarage" app is not displaying the status of the garage door, whether if it is closed or open. In other words, both icons: closed and open are dimmed out, so you are unable to tell that status.
-Nate
-
It appears the "MyGarage" app is not displaying the status of the garage door, whether if it is closed or open. In other words, both icons: closed and open are dimmed out, so you are unable to tell that status.
-Nate
I don't have MyGarage, so I can't test this myself.
Have to tried rebooting the PC after the upgrade, to see if that makes any difference?
Can someone else with MyGarage confirm this bug? If so, I'll add it to the bug list.
-
I noticed on the download page.
There where two files for updating AHP to 3.310.
One did just AHP. The universal one was for AHP and any other plugins that you had.
I would think anyone with installed plugins. Should try the universal installer file.
-
I noticed on the download page.
There where two files for updating AHP to 3.310.
One did just AHP. The universal one was for AHP and any other plugins that you had.
I would think anyone with installed plugins. Should try the universal installer file.
I'm not clear on that, either. The "universal updater" is a smaller file than the other one. I wonder if the other one is a full installer (like for fresh installs - you need to add the plugins afterward), and the "updater" is just that - it updates whatever you currently have installed. I used the updater (I think).
-
Another bug ... perhaps we should add that "X10 needs to provide directions on which/how to update their software."
-
Another bug ... perhaps we should add that "X10 needs to provide directions on which/how to update their software."
I don't think I would classify it as a real bug. I'll ask the developers what the difference is between the two files, but it might be a simple matter of modifying some wording on the download page.
-
I used the "Auto update" file. I then after noticing that the My Garage was not reporting the status, ran the My Garage installer, still nothing. Rebooting the PC per Noam's suggestion. Will report findings soon.
-
I used the "Auto update" file. I then after noticing that the My Garage was not reporting the status, ran the My Garage installer, still nothing. Rebooting the PC per Noam's suggestion. Will report findings soon.
If I understand correctly, you *should* only need to run the auto-updater. Separately re-installing the plugins isn't supposed to be required.
Let us know how it goes after the reboot.
-
That is what I thought too, in regards to not needing to reinstall all the apps. Just rebooted and same results - no status indication of my garage. Thinking about running all the app installers then the AHP main installer, to see if that changes anything, which I would sort of doubt. Otherwise, maybe downgrading back to 3.306.
-Nate
-
That is what I thought too, in regards to not needing to reinstall all the apps. Just rebooted and same results - no status indication of my garage. Thinking about running all the app installers then the AHP main installer, to see if that changes anything, which I would sort of doubt. Otherwise, maybe downgrading back to 3.306.
-Nate
Has anyone else with MyGarage been able to confirm this as a bug yet?
-
It appears the "MyGarage" app is not displaying the status of the garage door, whether if it is closed or open. In other words, both icons: closed and open are dimmed out, so you are unable to tell that status.
-Nate
Nate -
I just re-read your post. It wasn't clear if you had tried opening and closing the door or not.
Is the status just not showing currently, or is it also not changing when you open and close the door?
I'm wondering if the update just clears out the current status, and it won't show anything until the next open/close event. (Again, without MyGarage - or an actual garage with which to use it - I can't test it myself).
-
Okay, I got it to work. I had to re-install the "My Garage" plugin then I re-installed AHP actual installer file, not the update. Still no status indication but this time after I opened and closed the garage door from the plugin it now show the proper status. :)% Weird though, as it did not do this with the updater and the same steps. :-[ I do not know what the difference between the AHP updater and the main installer file is.
But it is working now. :)%
-Nate
-
Okay, I got it to work. I had to re-install the "My Garage" plugin then I re-installed AHP actual installer file, not the update. Still no status indication but this time after I opened and closed the garage door from the plugin it now show the proper status. :)% Weird though, as it did not do this with the updater and the same steps. :-[ I do not know what the difference between the AHP updater and the main installer file is.
But it is working now. :)%
-Nate
Nate -
Just to confirm, did you test opening and closing the garage door BEFORE you tried to reinstall the MyGarage plugin, and / or the entire AHP file?
-
Thanks Noam for sticking with me on this. >! maybe if others run into the same issues, this thread will help.
1. Update plugins manually with individual files
2. Update AHP
3. Use the "MyGarage" plugin to open/close the garage door
4. Status will properly show.
Cheers,
Nate
-
sorry Noam, I posted at about the same time you did. Yes, I opened/closed the door after installing the AHP updater file installation method but to no prevail. Hope this helps.
-
Thanks.
I'll mention this to the developers.
I'd like to hear if anyone else has seen the same issue, as well.
-
You are most welcome and Thank you Noam for all of your help.
Real quick, while we are sort of on the topic of the "my garage" plugin; has anyone had issues running the "MyGarage" mobile within Internet Explorer on mobile devices? It works in Opera and other browsers but not in IE on mobile devices. OnAlert mobile and ActivePhone work just fine in Internet Explorer on a mobile device.
-
Well I did the auto installer which was to update any plug-ins.
Now I get the registration screen for the mobile apps which I don't have nor do I want.
The installer said updates AHP and any plug-ins it should say ALL plug-ins.
Think maybe the installer should look at what is installed and only try to update those!
>!
-
Well I did the auto installer which was to update any plug-ins.
Now I get the registration screen for the mobile apps which I don't have nor do I want.
The installer said updates AHP and any plug-ins it should say ALL plug-ins.
Think maybe the installer should look at what is installed and only try to update those!
>!
I had something similar with mine.
Since I didn't have a VA11A plugged into my second PC (the one I was testing the upgrade on), I had uninstalled the iWatchout plugin a long time ago. I did this by changing the "plugin" line in the xml file to "no plugin".
Well, after the update, it was enabled again. It looks like the updated round the DLL, and added the line for it.
Did you, at any time, install any of those other plugins on that PC? If so, perhaps the installer found them and re-activated them.
I'll let the developers know about that one.
Let's wait and see if anyone else reports any installer problems before updating the Bug List.
-
I installed 3.310 and it asked me if I wanted to install plugins I had. It worked fine. Only installed items I already had. I had a fresh install of 3.306 with new computer about 2 months agoe so it seems to have worked fine.
I initally installed some plugins I did not have activated at first a couple months ago and I kept getting the screen that I had to click on to get it to close the registration screen so I reinstalled the entire computer and did not install items I did not have registration codes for so this update seems to work fine.
Thanks
Randy
-
initally installed some plugins I did not have activated at first a couple months ago
Ok looks like this may have been the case with this PC!
As I had lines commented out in the XML file and the installer rewrote them!
I had thought it was the XP machine that this was done on! B:(
-
Quick explanation about the new installer framework.
This is an advanced topic so if some of this doesn't make sense to you, you likely don't need to worry about any of this :)
The universal update installer is the base installer which all of the other installers use. For this reason it is slightly smaller than the others since it contains no data about what to install, it gets all of that from the ahp_plugin.xml file in the specified install directory.
The text parsing it does is very basic, it simply looks for the 6 character identifier of the plugin. For this reason if you had commented out a line, the installer will update that plugin's files and rewrite the plugin entry to the file. It was never intended that the user should edit this file, so it assumes it hasn't been tampered with. If you want to disable a plugin I recommend you delete the entry line completely. This way the upgrade installer won't attempt to restore it.
The update installer will always install the AHP base program files.
The specific installers, are really just a self extracting file which contains the universal update installer, and a small text config file to override the default behavior. When the universal upgrade installer runs it checks for the presence of of this config file, and if found installs the specified plugins ignoring the ahp_plugin.xml file.
Currently to rebuild your installation you need to run each plugin's installer separately to install all the files and write all the plugin entries. I am working with IT to deploy an updated software page which will dynamically generate a custom AHP installer with a custom config file specifying the plugins you select. We are also working to roll this out to the new order system so if you place an order for an AHP plugin, the email generated will contain a custom installer which will install all of the plugins purchased by your account. Once this is complete, you can still run the universal update installer for quick updates, but doing a clean install for any plugin configuration will simply mean checking a few boxes then downloading and running a single installer. New users who purchase a bundle of software should also have a significantly easier time by being able to just run one installer to get up and running.
The self extracting exe's should place the universal installer and the config file side by side in your system's default temp directory.
-
Currently to rebuild your installation you need to run each plugin's installer separately to install all the files and write all the plugin entries. I am working with IT to deploy an updated software page which will dynamically generate a custom AHP installer with a custom config file specifying the plugins you select. We are also working to roll this out to the new order system so if you place an order for an AHP plugin, the email generated will contain a custom installer which will install all of the plugins purchased by your account. Once this is complete, you can still run the universal update installer for quick updates, but doing a clean install for any plugin configuration will simply mean checking a few boxes then downloading and running a single installer. New users who purchase a bundle of software should also have a significantly easier time by being able to just run one installer to get up and running.
The self extracting exe's should place the universal installer and the config file side by side in your system's default temp directory.
Why not just have the installer open up a box, where you can check off the plugins you want to install?
Other programs (MS Office comes to mind) make it easy to add or remove components, by re-running the install, and selecting or deselecting options.
Since you would need a key to activate each plugin, I don't see the harm in doing this.
It would also make it easier for novice users to remove a plugin they no longer want to use.
-
I'll add that to the list of suggestions :)
-
Since version 3.311 was released this morning, I'm making this thread "non-sticky."