Home Automation Domotica Forum Europe, Bwired Forum

You're right, of course. It should be like this instead: IF (ra < 360) THEN ra += 360 ELSE IF (ra > 360) THEN ra -= 360 ENDIF The same goes for the "l" part: IF (l < 0) THEN l += 360 ELSE IF (l > 360) THEN l -= 360 ENDIF You said that "some parts" don't feel right, have you found...

Thanks, but all I did was translating php code to gambas code.

spierie,

Ron has added the code to the svn, just download the latest revision.

The problem was unix time versus gambas time. It is now returning the same result as timeanddate.com/worldclock/astronomy.ht ... tml?n=1382 This version is working, I'd be glad if someone else could try it out. PUBLIC FUNCTION CalcSunTimes(lon AS Float, lat AS Float, timezone AS Float, isRise AS Boo...

I've ported this php version (which is based on williams.best.vwh.net/sunrise_sunset_al ... orithm.htm : define("SUNRISE", 0); define("SUNSET", 1); class SUN { var $timezone; var $latitude; var $longitude; var $zenith; var $date; var $type; var $coords; function sin($d) { return ...

Hi, I'm using the "Dark" variable to turn on the outside lights at home. The calculation of sunset/sunrise seems to be wrong. According to DomotiGa, the sunset today is at 11:47 (which is definitely wrong). According to timeanddate.com/worldclock/astronomy.ht ... tml?n=1382 the sunset is a...

Perhaps you should fix the conversion when upgrading to 0.1.190, so that leading zero's are removed.
Also, the bDebug (as stated above) need to be fixed for future debugging.

I did a bit more testing. The Time_Cron function didn't write any debug info, since it was checking bDebug which I couldn't find anyway so I replaced it with bMainDebug. According to 2010/11/08 08:37:00 [cron] 37 08 * * * | aCron[0] 37 = aCron_Now[0] 37 so continue 2010/11/08 08:37:00 [cron] 37 08 *...

Sorry Ron, it's still not working as it should... 2010/11/07 23:00:00 [Events] 1b. Got 5 result(s). 2010/11/07 23:00:00 [Events] 2c. TimeNow trigger check Time_Cron() for event id 12 and trigger condition '30 07 * * *' returned False 2010/11/07 23:00:00 [Events] 2c. TimeNow trigger check Time_Cron()...

Seems to have done the trick, Ron.
I'll test a few more cycles later today and see if the problem is completely gone.

This is very strange. Tonight, a trigger failed again. This is the output from the debug. 2010/11/07 00:12:00 [Events] 1a. Running TimeNow query 'SELECT * FROM events, triggers WHERE events.trigger1 = triggers.id AND triggers.type = 1 AND events.enabled' 2010/11/07 00:12:00 [Events] 1b. Got 5 result...

Hi Ron, Seems like the fix you added for leading/trailing spaces fixed the problem. The triggers are working fine now. 2010/11/06 11:37:00 [Events] 1a. Running TimeNow query 'SELECT * FROM events, triggers WHERE events.trigger1 = triggers.id AND triggers.type = 1 AND events.enabled' 2010/11/06 11:37...

After upgrading to 0.1.190, all my triggers using TimeNow stopped working. All the conversions to crontab format seem okay.
The debug logs (with event debugging turned on) show nothing of interest.
Anyone else experiencing the same?

I think you've definitely got the right approach. A modular system with separate daemons is brilliant. I guess I'd probably pay for such a software, but I'd much rather contribute with code in an open source project. Have you considered releasing your software as open source (or semi open)? Php with...

Try this:
Should work...