X10 Community Forum
🖥️ActiveHome Pro => ActiveHome Pro General => Software Problems & Bugs => Topic started by: andyd on April 04, 2005, 08:23:13 AM
-
Saturday midnight my timed event worked on
schedule. Sunday morning my timed event was
1 hour early. Sunday midnight again 1 hour
early. Ah yes - daylight savings change.
Trouble is I'm in Arizona and we don't do
daylight savings time. My computer is set
to MST and the interface configuration
reports MST is set and shows the correct
time.
Why were my events an hour off?
I just reset the time so maybe it will work
right until the next time change?
Andy D
-
More info -
OS Windows ME
Time zone GMT-7 Arizona
automatic DST checked but grey as not
applicable to this time zone.
It seems AHP is using the auto DST flag even
though it is not appropriate for the
selected time zone.
Andy D
-
AndyD: It could be that we aren't using all
the information Windows is giving us. I'll
look into it.
-
X10 Pro
As I said in another thread, I too live in AZ
and saw the same behavior as AndyD. All
timed events now trigger one hour early.
This is with a dianostic unti
-
Based on the format of the data sent to the
cm15a to set the time, there is no provision
for "use DST" or "Don't use DST".
So, unless there's a change in the protocol,
DST changes will probably be an issue for
anyone living in a place that doesn't observe
DST. That's only 6 million people in AZ and
Indiana, and HI (in the US), and included the
5th largest city in the US!
If this data is indeed being passed to the
cm15a, which command is it in X10pro? (I'm
talking at the USB level)
-
And in Canada you have the 979,000 people
in Saskatchewan. ;)
-
To all who have DST problems.
Yes You are all right and X10 schould
incorporate an otpion, ie. a checker box to
select DST - on or off, as on the old CM11
S/W.
X10 is referencing in the Main Forum to a
user in Germany, its me:
Yes DST change worked perfect 26/27th of
March - dusk/dawn times were still perfect.
I must admid that I updated the CM15A in the
morning after the GMT Timechange to set the
CM15A Clock. So I cannot confirm that my
CM15A did it automatically.
-
The AHPro S/W shouldn’t need to have a
check box to select DST as there is one in
Windows that can be used. I gather that
was their intent, but something isn’t
working properly.
AndyD: What happens if you select (GMT-
07:00) Mountain Time (US&Canada) instead
and then uncheck the DST box? I suspect
that AHPro is seeing the checkmark in the
box even though it is disabled. This is a
bug which should be fixed, but a work
around would be useful I am sure.
-
It may be interesting that the hardware
configuration time zone shows Mountain, when
the PC time zone is GMT-7 Arizona. Perhaps
the interface does not recognize these as
different time zones.
-
Roger H. I did that after I had connected
and removed the interface so maybe I'll find
out if it works in October, or whenever the
next time change is.
It seems the problem is fixed as soon as the
interface is connected as it resyncs to the
actual PC time. I assume the problem only
happens if the interface is disconnected at
the DST roll over. My timed events are
correct now.
Andy D
-
I'm pretty sure the problem is that we're
storing DST change dates for Arizona when we
shouldn't be. We'll fix this soon. Too late
for the change, but at least it will be right
in October.
-
It's obvious, the problem is as plain as
the nose on your face. All you dummy's
that live in a "non-DST" area need to move
if you want to continue using the X10 AHP
solution.......... Move to a more
sophisticated location that is cool with
changing time to accomodate more outdoor
living...... What's an hour ???? !!!!!!
-
Max: LOL. This whole DST topic made me
realize that changing to DST is completely
useless for people who live in (and near)
the Tropics (and Arctic). If the sun rises
at 6:00am and sets at 6:00pm all year long,
why bother changing your clock in the
summer. Cuba probably has it right to be
on DST all year long (having the sun rise
and set at 7:00 makes more sense).
Similarly in the Arctic who cares what time
it is if the sun is up all day long in the
summer and set all day long in winter. Now
I am not sure if that is why Arizona does
not switch to DST, but it is interesting.
-
DST changes used to be beneficial, though
I'd vote to just stop changing or change to
DST then leave it there, lot of work with
little or no benefit. Till this happens
though, X10 should clean up AHP, seems
silly that they did not catch this one.....
-
One thing that should be happening is to
let the operating system take care of any
time changes. AHP should only have to deal
with getting the time into the CM15A - a
seperate clock should not have to be
maintained within the program - let windows
worry about the clock - makes things a lot
less difficult and time consuming.
-
Donald: For most applications you can let
Windows worry about the clock and
timezone. Unfortunately, as far as I know
Windows does not calculate the “Dawn”
and “Dusk” times. The “Dawn” and “Dusk”
times are dependent on not only latitude
and longitude, but also on the time zone
and if DST is being used. As a result AHP
needs to get this information from Windows.
As far as the clock itself, the AHP
software on the PC does use the clock from
Windows. However, the CM15a can run
disconnected from the PC thus needs to have
its own clock. This clock should adjust
for DST (if needed) otherwise a light that
turns off at 10:00 in the winter will
suddenly start turning off at 11:00 in the
summer.
-
The only thing though is that if you are
getting your time from the OS then you
don't need to worry about DST since this
has already been taken care of. I don't
know how Windows takes care of the time -
Does it adjust the hardware clock directly
or does the hardware clock get adjusted
only when a request is made? If the
hardware clock is already adjusted when the
time change comes into effect then you
don't need to make any adjustments within
your program. If Windows makes the
adjustments when a time request is made and
your program is setup to read the hardware
clock directly then you are going to run
into problems. That is why I made the
suggestion that you let Windows take care
of the grunt work and you just request the
time from it - no adjustments needed.
-
Donald: So you are suggesting that:
a) Forcing people who don’t keep their
CM15a connected to their computer connect
their CM15A to their computer after
switching to and from DST to reset the
clock, and
b) Not supporting Dawn and Dusk during DST?
-
We're going to fix this bug, it's pretty
simple. The CM15A adjusts the clock for
daylight savings time on its own when not
connected to the computer, and we just need
to be sure to tell it not to do that when the
customer isn't in an area that uses DST.
-
I know this topic is old but the whole inconvenience is getting old. I’ve contacted the technical support people somewhere like 4 times… that’s 2 years. Each time I was told to go clear the unit’s memory and make sure that my PC is in the correct time zone. This morning while on HOLD, I looked at the Knowledgebase. It appears that it is a CM15A Software/Firmware problem.
It looks like people who live in areas that do not have daylight savings time are getting the runaround. We need a firm answer on what is being done to rectify this problem. We also need the name and contact information of the person who will be the focal point for getting this issue resolved. If the answer is a new hardware unit, I believe those of us who live in the non-daylight savings time regions, and are having problems running our units are entitled to either a new unit or a discount on the superseding unit.
There, I’ve said how I feel, now let's get this thing resolved. Two+ years is too long.
-
[Oh BTW, I’m using ActiveHome Pro Ver 3.204. The software was updated on 7/2006. I checked this morning and there are any new software updates.
-
I'm pretty sure the problem is that we're
storing DST change dates for Arizona when we
shouldn't be. We'll fix this soon. Too late
for the change, but at least it will be right
in October.
"SOON"? It's been 2 years and approx 6 months.
-
DST changes used to be beneficial, though
I'd vote to just stop changing or change to
DST then leave it there, lot of work with
little or no benefit. Till this happens
though, X10 should clean up AHP, seems
silly that they did not catch this one.....
I think we should leave the clocks in standard time. When spring and fall come around just change the start and stop time of the employees. Well get up and hour early in the spring and reset in fall. This who daylight savings thing has caused many problem with program scheduling and other meetings.
That’s my 2 cents worth.
-
The AHPro S/W shouldn’t need to have a
check box to select DST as there is one in
Windows that can be used. I gather that
was their intent, but something isn’t
working properly.
Yep. That’s where it went wrong. Somebody didn’t COMPLETELY test the changes. I say put the DST check box back.[/b]
-
If the answer is a new hardware unit, I believe those of us who live in the non-daylight savings time regions, and are having problems running our units are entitled to either a new unit or a discount on the superseding unit.
Well, to be fair, that is more the responsibility of your congressman/woman, and not X10. Write to him/her and explain just how much trouble they caused you.
My old VCR changed time this past weekend, and BTW, it sync's with my local PBS station (which apparently hasn't updated its own broadcast equipment yet).
-
Here’s how the Smarthome people step up to the plate. This morning I received an email from Eric Boyd prioritysupport@x10.com that points to this article. http://kbase.x10.com/wiki/DST_in_AHP (http://kbase.x10.com/wiki/DST_in_AHP)
The article is as follows.
How is time kept on the computer interface? Will it lose time if it isn't connected to the PC?
How does ActiveHome Pro know when Daylight Savings Time is?
Answer
Since there are enough places in the US that do not use Daylight Savings Time anyhow, AHP copies the time, date, and Daylight Savings Time settings from your computer. ActiveHome Pro is designed to keep time when running by itself. If you have Windows Update turned on, that should keep your Daylight Savings Time information in sync with whatever changes are made. If your CM15A has been running by itself for a very long time, you may want to hook it back up to the PC and run Tools-Download Timers and Macros to make sure it has the correct dates for Daylight Savings Time.
Just for the record I’ve cleared and refreshed the memory numerous times, I run Windows update weekly and the problem remains. So now after approx 2.5 years after they said they had a problem, they are changing their tune. What a cop out.
-
If the answer is a new hardware unit, I believe those of us who live in the non-daylight savings time regions, and are having problems running our units are entitled to either a new unit or a discount on the superseding unit.
Well, to be fair, that is more the responsibility of your congressman/woman, and not X10. Write to him/her and explain just how much trouble they caused you.
My old VCR changed time this past weekend, and BTW, it sync's with my local PBS station (which apparently hasn't updated its own broadcast equipment yet).
I agree with who's responsibility it is for the invocation of daylight savings time.
Frankly I'm not concerned with your VCR. I'm really only concerned with the CM15A attempting to adjust the clock when it should not.
-
Okay, so here’s what I just did just to show that I’ll willing to work on this problem..... some more. I know it appeared that my old PC didn’t have the latest DST date as it changed this week. So maybe my old PC didn’t get that update or it came in after I reset the CM15A.
Even if my old PC did not have the latest Windows updates I see no reason for the DST flag to be activated, as I’m not in a DST region.
1. Updated Windows on my newer machine.
2. Reset my Windows XP region to Tucson.
3. Pulled the batteries out of my CM15A.
4. Reinstalled the batteries in the CM15A.
5. Ran AHP and cleared the CM15A memory. I know, removing the batteries should have done this. Humor me.
6. Set my preferences to another time zone, and then back to Tucson.
7. Updated the interface.
8. Downloaded Timers and Macros.
9. Saved the file.
10. Closed AHP.
11. Removed the CM15A from the PC and plugged it in the wall.
I’ll now wait to see when the OFFICIAL daylight savings changes in the USA, if it affects my CM15A unit.
ONLY TIME WILL TELL. No pun.
-
<snip>
5. Ran AHP and cleared the CM15A memory. I know, removing the batteries should have done this. Humor me.
<snip>
FYI: The CM15A has non-volatile memory; unplugging and removing the batteries will not clear it.
-
<snip>
5. Ran AHP and cleared the CM15A memory. I know, removing the batteries should have done this. Humor me.
<snip>
FYI: The CM15A has non-volatile memory; unplugging and removing the batteries will not clear it.
WOW NVS who would have thought that? THANKS. Anyway, that's what technical support has told me NUMEROUS times in the past.
-
<snip>
5. Ran AHP and cleared the CM15A memory. I know, removing the batteries should have done this. Humor me.
<snip>
FYI: The CM15A has non-volatile memory; unplugging and removing the batteries will not clear it.
WOW NVS who would have thought that? THANKS. Anyway, that's what technical support has told me NUMEROUS times in the past.
The batteries just keep the clock running in the event of a power failure. The CM15A will run fine without batteries so long as the AC power isn't interrupted.
-
Charles,
Thanks for the input. I guess when all else fails I use a bigger hammere to resolve problems.
just a little related subject to the NVS. I've had times when the PC didn't recognize that I connected the CM15A. Technical support had me
1) Unplug the unit from the PC.
2) Removed the batteries.
3) Install the batteries again.
4) Connect the unit to the PC and the PC found the unit.
Do you have any ideas of what was going on during thesee operations?
-
just a little related subject to the NVS. I've had times when the PC didn't recognize that I connected the CM15A. Technical support had me
1) Unplug the unit from the PC.
2) Removed the batteries.
3) Install the batteries again.
4) Connect the unit to the PC and the PC found the unit.
Do you have any ideas of what was going on during thesee operations?
The user program is stored in NVM. The microcontroller, which is also the USB interface, has a small amount of internal RAM used for software and device control. When you remove all power, this is the memory that gets cleared and resets the CM15A.
-
Okay it looks like somebody update the old KB article.
Here's what it now looks like:
Since there are enough places in the US that do not use Daylight Savings Time anyhow, AHP copies the time, date, and Daylight Savings Time settings from your computer. ActiveHome Pro is designed to keep time when running by itself, but this does not work correctly with Daylight Savings Time right now. Currently, ActiveHome Pro applies old, out-of-date DST adjustments when it is NOT connected to the PC.
If you have Windows Update turned on and keep the CM15A connected all the time, that should keep your Daylight Savings Time information in sync with whatever changes are made. If your CM15A runs by itself, you will need to hook it back up to the PC and run Tools-Download Timers and Macros to make sure it has the correct dates for Daylight Savings Time. Do this four times a year- on the old and the new DST days. If you do not have DST in your area, you will need to update the unit twice a year- it does not ignore DST correctly either.
We are taking steps to correct these errors. We hope to have it resolved in time to Spring Forward. If you have any questions about this please email ahpsupport@x10.com.
I underlined the part that affects non-DST regions.
-
Thanks tucsonuser!
I'm just hoping the code is not hardwired into the CM15A.
Let's hope it can be done with just a software update or a field firmware update to the CM15A.
-
WELL, I'm back. I just checked for an update and it STILL says I have the latest (3.204) version. Are we EVER going to get an update for this problem?????
-
Can you belive this? WTF are they doing to us. 3 years and no answer. Are these people working out of a garage in Indina some where? After amost 3 years they now jerk us around for another 6 months. I have used X10 sutuff for maybe 20 years plus. When I get my next house I will seriously consider never using it again!!!!!!
Since there are enough places in the US that do not use Daylight Savings Time anyhow, AHP copies the time, date, and Daylight Savings Time settings from your computer. ActiveHome Pro is designed to keep time when running by itself, but this does not work correctly with Daylight Savings Time right now. Currently, ActiveHome Pro applies old, out-of-date DST adjustments when it is NOT connected to the PC.
If you have Windows Update turned on and keep the CM15A connected all the time, that should keep your Daylight Savings Time information in sync with whatever changes are made. If your CM15A runs by itself, you will need to hook it back up to the PC and run Tools-Download Timers and Macros to make sure it has the correct dates for Daylight Savings Time. Do this four times a year- on the old and the new DST days. If you do not have DST in your area, you will need to update the unit twice a year- it does not ignore DST correctly either.
We are taking steps to correct these errors. We hope to have it resolved in time to Fall Back in 2008. If you have any questions about this please email ahpsupport@x10.com.
Taking steps....BULL. Look back and see where they changed the target timeframe. I just cannot believe that these people really care about this problem. Someone has to be held accountable for the update. Am I upset, you bet your @ss I am.
I just sent an email to Eric Boyd [prioritysupport@x10.com], the person I contacted way back in 2006
-
I was just updating XP on my PC, and noticed that Microsoft has yet another DST update. ::)
Seems nobody can get it right. ;D
-
There are actually 2 problems going on here. One is that Daylight savings time has changed. The other is that AHP doesn't recognize that some states or cities no not have DST. It was simpler in the past when we checked the DST on/off box.
The second on is what I’ve be waiting to have fixed for close to 3 years. HOW SAD.
-
There are actually 2 problems going on here. One is that Daylight savings time has changed. The other is that AHP doesn't recognize that some states or cities no not have DST. It was simpler in the past when we checked the DST on/off box.
The second on is what I’ve be waiting to have fixed for close to 3 years. HOW SAD.
AHP is supposed to get its calendar info from Windows, and Win XP has a check box for DST. What happens if you turn it off there?
-
Charles,
I just looked in Control Panel and I don’t find a check box for DST. I find that I’m currently set for “MST”. Just for the record my PCs both keep the proper time, and don’t jump forward/fall back when we go across the DST Spring and Fall dates.
I really sure this is a AHP problem as it did not happen with the previous version that used the serial port and I believe had a check box for DST.
Thanks
-
Don't forget that rather odd DST correction that happen to several of us one weekend this past December (12/16). That doesn't fit anyone's rules, old or new.
-
Charles,
I just looked in Control Panel and I don’t find a check box for DST. I find that I’m currently set for “MST”. Just for the record my PCs both keep the proper time, and don’t jump forward/fall back when we go across the DST Spring and Fall dates.
I really sure this is a AHP problem as it did not happen with the previous version that used the serial port and I believe had a check box for DST.
Thanks
Right click on the clock in the task bar and select "Adjust date and time". In the timezone tab there's a box for "Automatically adjust for DST". My recollection (which may be faulty) is that this turned off DST in AHP.
-
Any word yet on leap year support? I mean, w/o a PC being needed to correct the CM15A.
-
My guess, between Slim and None. Leap years come every four years, so that's very low priority.
-
Well, sorry, I meant current/existing support for leap years.
I am almost afraid to plug my PC into the CM15A, to see if the CM15A thinks today is 2/29 or 3/1. ::)
I hate to think that it will be executing date based timer events and macros, off by one day, for the rest of the year. :o
-
Leap years come every four years...
Not every four years. ;)
-
Any word yet on leap year support?
Why would you worry about that? We won't have an extra day for YEARS.
-
Leap years come every four years (2008, 2012, 2016, etc.) except century years unless divisible by 400. 2000 was a Leap Year, but 1900 was not.
-
Not every four years. ;)
It is difficult to worry about the exceptions when those exceptions will not occur anytime during our life times. ;D
-
Not every four years. ;)
It is difficult to worry about the exceptions when those exceptions will not occur anytime during our life times. ;D
Very true. Remember, in 2000 we got to see something that hadn't happened for 400 years - a leap day (February 29) in a century year.
-
... in 2000 we got to see something that hadn't happened for 400 years - a leap day (February 29) in a century year.
...and baring some major medical development, no one living now or their great grandkids will see again!
-
Now, back o the original OP's problem.
Does a CM15 that is not connected 24/7 show February 29 or March 1 on a leap year?
-
Daylight saving in UK takes place last weekend October, however, the DST table in AHP shows time change scheduled to take place first weekend October.
I've got my local UK city entered in the 'location' field.
So what can I do? How can I get the DST table updated?
AHP version 3.227
I only connect the interface to the PC when making edits...
On my previous CM11, I could set the DST dates myself.
-
Guess What?
My AHP just updated today with a fix for the DST Bug!
-
Guess What?
My AHP just updated today with a fix for the DST Bug!
If you mean for the folks that don't have the CM15 plugged in to the PC 24/7, where did the firmware upgrade come form?
-
Just upgraded to AHP v227. DST settings are improved now :)
Only one problem remaining: switching back to winter time is scheduled on the first weekend of October, whereas in reality this happens on the LAST weekend of October (in Europe) :-\
-
Guess What?
My AHP just updated today with a fix for the DST Bug!
If you mean for the folks that don't have the CM15 plugged in to the PC 24/7, where did the firmware upgrade come form?
The Reverend from Ohio yields to the Gentleman with a valid point!
-
Daylight saving in UK takes place last weekend October, however, the DST table in AHP shows time change scheduled to take place first weekend October (AHP version 3.227)
Does version 3.228 now show DST changeover (at Fall) as last weekend October (European Cities)?
Could someone please confirm.
Thanks...
-
@dash: don't know where you got 3.228, I'm on 3.227
In Tools - Hardware configuration, if you choose "daily", I see the hour changing back to winter time on the first weekend of October (I'm in Europe). This is wrong.
HOWEVER !!!!
when I look into the file C:\Documents and Settings\All Users\Application Data\Active Home Professional\ahpeeprom_w.txt, which is the file that will be sent to the CM15A (after "translation" to binary), I see
0x0004: 0x01 00000001 dusk/dawn resolution: each entry represents 1 day(s)
0x0005: 0x01 00000001 b7: day msb; daylight savings turn forward - first Su
0x0006: 0x5a 01011010 after day 90 (31-mar)
0x0007: 0x81 10000001 b7: day msb; daylight savings turn backward - first Su
0x0008: 0x2c 00101100 after day 300 (27-oct)
Seems to me that this is the last Sunday of October, which is correct...
-
Where did you get 3.227? X10 Europe? The 3.228 version of Active Home Pro is for US/Canada use only.
-
I downloaded from www.marmitek.be (I'm in Belgium).
Thanks for making clear to me that 227 correction: 3.228 is not for Europe.
On www.activehomepro.eu the current version is 224 - strange.
-
The various X10 companies in England and the Continent have different versions of their software, thus the various numbers. X10USA's current version is 3.228, they sell only in the USA and Canada. The electric systems are 100/220 60HZ. The CM15A usb interface is for that electric system.
-
@dash: don't know where you got 3.228, I'm on 3.227
In Tools - Hardware configuration, if you choose "daily", I see the hour changing back to winter time on the first weekend of October (I'm in Europe). This is wrong.
HOWEVER !!!!
when I look into the file C:\Documents and Settings\All Users\Application Data\Active Home Professional\ahpeeprom_w.txt, which is the file that will be sent to the CM15A (after "translation" to binary), I see
0x0004: 0x01 00000001 dusk/dawn resolution: each entry represents 1 day(s)
0x0005: 0x01 00000001 b7: day msb; daylight savings turn forward - first Su
0x0006: 0x5a 01011010 after day 90 (31-mar)
0x0007: 0x81 10000001 b7: day msb; daylight savings turn backward - first Su
0x0008: 0x2c 00101100 after day 300 (27-oct)
Seems to me that this is the last Sunday of October, which is correct...
Hi Jacardito
I'm on 3.227 in UK (was previously hoping to get a copy of 3.228 in the hope that DST switchover dates were resolved in this version, but now realise that this is for US/Canada only).
However, you seem to be suggesting that, despite Tools/Hardware showing switchover on 1st Sunday, switchover on version 3.227 will actually occur on last Sunday as required. Have you managed to verify?
Dave
-
As posted before 3.228 is for the USA and Canada ONLY It's made for the CM15A, which is 60HZ/120Volts. It may or may not work with UK version of the interface.
-
As posted before 3.228 is for the USA and Canada ONLY It's made for the CM15A, which is 60HZ/120Volts. It may or may not work with UK version of the interface.
Sorry Dan, I've now edited my previous post to read better.
I realise that 3.228 is US/Canada version. Hoping for confirmation from Jakardito that 3.227 will behave correctly on DST changeovers.
Dave
-
Version 3.229 now available in Europe.
Nothing changed to rectify incorrect behaviour of DST in October - still scheduled 1st weekend instead of last weekend.
The programming data is now listed here...
C:\Documents and Settings\All Users\Application Data\X10 Settings\X10Active.xml
When set with a UK home city, and dusk/dawn resoluition set to daily...
There are 90 items having DST = "0" at the beginning of the list which I guess takes us close to the end of March (if each line of data corresponds to a day of the year).
However, there are also 90 items having DST = "0" if you count backwards from the end of the list which takes us close to the beginning of October, NOT the end of October as required.
Roll on 3.230 !!
-
Version 3.232 seems to have fixed the DST issues (correct dates showing in Tools/Hardware Configuration dusk/dawn resolution set to daily).
Anyone else using this version please confirm.
Thanks
Dave
-
Version 3.236
CM15A connected to PC all the time
Time Zone is showing as "GMT Standard Time - GMT-00:00"
In UK daylight saving starts last weekend in March
I thought I'd check Tools/Hardware Configuration to confirm that X10 was going to change the DST on the correct day.
There's something wrong. X10 is not scheduled to change times at any point throughout the year (it behaved fine in October at which point I was already running 3.236)
In C:\Documents and Settings\All Users\Application Data\X10 Settings\X10Active.xml all lines are followed by a 0, i.e. no account is being taken of DST
Any ideas?
Dave
-
You are in England, your DST does not begin until March 29!!!!
Ours in the US began last Sunday at 2:00 AM
What O/S does your PC run?
-
PC is running XP SP3
So where have DST schedules gone?
They were definitely present and correct before October's change.
I've chosen my home town (which is available in the drop-down), so am now at a loss as to what's going on.
Any suggestions as to how I might restore correct DST schedule?
-
Windows time is US/Canada unless you have the British/European version of Windows. Which version of XP are you using?
-
Dan
Windows XP Home version 2002 was supplied OEM with a UK purchased PC
The problem lies here...
C:\Documents and Settings\All Users\Application Data\X10 Settings\X10Active.xml
All lines are currently followed by a 0
Around half those lines should be followed by a 1 to account for DST
Everything was correct in October before the last DST shift (with AHP 2.236 already running on the PC).
The database has changed/corrupted for some inexplicable reason...
Do you think this might have happened at the end of the year when the calendar would have been updated?
-
No idea as looking at my C:\Documents and Settings\All Users\Application Data\X10 Settings\X10Active.xml everything is followed by a 0 and My DST date changes are correct. My CM15A is connected 24/7/365 (366 in Leap years). Has your XP Home been updated by MS upgrades?
-
It fixed itself when the daylight saving time changed (CM15a always connected to PC).
I wonder if it will stay fixed....
Just noticed that 3.238 is available from Marmitek in Europe
Release notes...
V238:
- GUI: Lat/Lon bug fix, 230V countries outside Europe added
-Macro Designer, advanced Functions, X10 Function Command, added all direct functions.
Still open: Change of Summer/Wintertime problem.
That last line bothers me - looks like there is an ongoing, unresolved issue with DST switching
Dave
-
i do not see any more responses to this thread
i am currently using AHP v 3.240
i inspected the date table in the hw config and i can tell you the time jumps + 1 hour when we enter summertime and jumps back -1 hour when we enter winter time.
as far as i can see the cm15 should work on it's own without being connected to a pc.
this should probably mean that the rtc is not adjusted(otherwise there is no need for the +1 hour jump.
i do not know how this affects modules which turn on at a specific time but all dusk/dawn related timers should work.
DST will en next month overhere so i can tell you if it works within a month
i live in the netherlands fyi
-
You need to go to X10 Europe for any updates. US/Canada versions of AHP will not work.