| Author |
|
sparky
Newbie
Joined: April 25 2006
Online Status: Offline
Posts: 11
|
| Posted: April 25 2006 at 22:00 | IP Logged
|
|
|
Just got into PowerHome recently and registered tonight hoping this would go away: Even though I set up appropriate values in the Explorer:Setup:Sun screen, I'm finding that when I create a timed event with "sunset" timing, the value shown for the "start time" column is 23:59:59, and if I add an absolute offset (like 30 minutes), the "start time" column reads 23:29:59. It was working fine over the past week while I was using a demo version of PowerHome. How do I get the real sunset value??
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 25 2006 at 22:33 | IP Logged
|
|
|
Sparky,
Let me know the version of PowerHome youre running and what values you're using for the Latitude and Longitude in the Sun configuration so I can duplicate it here.
Let me know and Im sure we can get it working.
Dave.
|
| Back to Top |
|
| |
Dean
Senior Member
Joined: August 21 2003
Location: United States
Online Status: Offline
Posts: 109
|
| Posted: April 25 2006 at 22:33 | IP Logged
|
|
|
I'm still using the following Macro to calculate Sunset and sunrise. There may be an easier way to do this with newer versions of PowerHome, I've been using this method for years.
string(datetime(today(),relativetime(00:00:00,[SUNSET])))
string(datetime(today(),relativetime(00:00:00,[SUNRISE])))
I have a daily timed event that runs at 1 minute after midnight that calculates sunset and sunrise and then creates two macros that run at sunrise and sunset.
|
| Back to Top |
|
| |
sparky
Newbie
Joined: April 25 2006
Online Status: Offline
Posts: 11
|
| Posted: April 26 2006 at 19:47 | IP Logged
|
|
|
My version is 1.03.4.7
I've tried a variety of combinations using city / state, various positive / negative longitude (wasn't sure negative longitude was correct, but I guess it is).
Anyway I'm currently having the problem with the following settings: <blank> state, <blank> city, 41.78 latitude, -70.5 longitude, -5 hours past GMT, and observe DST is on (checked). The "reference time" is showing 23:59:59. I also just tried changing the "sunset" timing to "sunrise", and the "reference time" shows up as tomorrow at 15:44:08.
One more - just tried changing the latitude and longitude to many different values, and the sunrise reference time is still 15:44:08.
Should changes in the "Sun" window take effect immediately?
Thanks...
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 26 2006 at 22:30 | IP Logged
|
|
|
Dean,
Your method still works. Later versions of PowerHome have the ability to select sunrise and sunset built into the timed events screen along with other enhancements. Check it out and see if any of it is useful for you  .
Sparky,
Checked out your settings on my end and had no problems. For the above longitude and latitude, the sunrise time for tomorrow will be 05:44:08 and sunset will be 19:37:54.
Your problem may just be a misunderstanding in how PowerHome works. First, any changes made to the Setup section of the Explorer will not take effect until PowerHome is either reinitialized or restarted. So if you change the longitude and latitude, you wont be able to create new timed events based upon these values until a reinit or restart.
Second, even with a reinit or restart, the timed event reference and start time will not change once a timed event is created. Even though the timed event screen now includes the ability to specify sunrise, sunset, etc. for the timing, PowerHome is still just storing the resulting calculation as a datetime in it's database. The calculation is ONLY done at the time the timed event is created.
Sooo, once you've got your longitude and latitude set properly (and reinit or restarted  ), you need to manually change the existing timed event (or create a new one) in order for the sunrise/sunset calculation to be performed. If you're changing an existing timed event, just change the "Timing" column from sunset to sunrise and back to sunset and you'll get the proper sunrise calculation.
This will continue to work for recurring timed events because once a timed event is executed, PowerHome will automatically calculate the next time for the next day.
If you want to set a timed event for a future date using sunrise or sunset, then just change the "Reference Time" date to the appropriate date value. Tab off of the reference time field and you'll see the time value update appropriately for that date.
Let me know if this takes care of your problem or not.
Dave.
|
| Back to Top |
|
| |
sparky
Newbie
Joined: April 25 2006
Online Status: Offline
Posts: 11
|
| Posted: April 26 2006 at 22:56 | IP Logged
|
|
|
That's it! Thanks - I changed the lat/long values appropriately, reinitailized, and changed my timers from sunset to sunrise and back to sunset to recreate them. I now get the proper values. I suppose I must have set the lat/long to something bizarre on the last reinit and then any new timers or changes to old timers were giving me the strange sunset times.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 26 2006 at 23:25 | IP Logged
|
|
|
Great. Glad to hear it's working now. Let me know if you have any other problems or questions.
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome Bug Reports
Topic: Sunset time is way off
