Print

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

[Tuicemen]

I believe 3.228 was when the "Check for update" stopped working!
It is listed as a known bug!
 

[Noam]

I believe 3.228 was when the "Check for update" stopped working!
It is listed as a known bug!
 

Correct! 3.204, released on 7/10/2006, was the last version where the "check for update" actually worked.
3.228, which was released on 5/9/2008, was unable to find the next version, 3.236, which was released on 9/5/2008.

So, the "check for update" function has been broken for nearly 3 years (since 2008).

[Dan Lawrence]

Sounds familiar as I used 3.228 from its issue to 3.296 and 296 had the same thing as does 3.306.  Seems a bit strange that nobody at X10 programming has never caught on in three years.

[Noam]

I actually asked one of the developers about this a few months back.
He told me that AHP goes out and checks for a certain file on X10's servers, to determine if there is an update or not.
Apparently, that file isn't getting updated properly (or the format of it changed, or something).
It is on their list to fix it (or so they say), but there is no way to know when (or if) it will ever get fixed.

EDIT: It looks like it makes a call to "http://software.x10.com/cgi-bin/checkfornewrelease.cgi", with a HEX value after the question mark. I'm guessing that hex value has something to do with the current version number.
However, that file doesn't exist, and you get dumped to the homepage.

I'm willing to bet that's a big part of the problem with the "check for updates" function not working.

[Noam]

I actually asked one of the developers about this a few months back.
He told me that AHP goes out and checks for a certain file on X10's servers, to determine if there is an update or not.
Apparently, that file isn't getting updated properly (or the format of it changed, or something).
It is on their list to fix it (or so they say), but there is no way to know when (or if) it will ever get fixed.

EDIT: It looks like it makes a call to "http://software.x10.com/cgi-bin/checkfornewrelease.cgi", with a HEX value after the question mark. I'm guessing that hex value has something to do with the current version number.
However, that file doesn't exist, and you get dumped to the homepage.

I'm willing to bet that's a big part of the problem with the "check for updates" function not working.

The only problem with my theory is that it seems that the function worked in 3.204, even after it didn't work in later versions (one could still install 3.204, and upgrade to 3.228, but couldn't go further).

I suppose I could take the time to roll back to 3.204, and then try to sniff again, and see if the request is different. It is just a bit of a pain to do, that's all.

[Dan Lawrence]

I suspect not.  The programmers that built 3.228 are long gone and I also suspect that every version after 3.228 were built on the "bones" of 3.228.  The only "changes" in 3.305 and 3.306 are the Lamps (Soft-Start) and Older Lamps (No SoftStart). 

[Noam]

Well, I got an e-mail from the developers yesterday about this.
They said that the problem is entirely on the back-end, and would not require any changes to AHP to correct.
They told me they were actively working on it yesterday, but I didn't get any ETA on when it would be fixed.

In the meantime, it isn't too hard for those of us who frequent the forums to find out about new updates. I usually post them as soon as I find out about them. (The developers sometimes give me a heads-up before the updates are posted to the server).