Lighting Schedular failing

[trevethan]

I've been unsuccessfully attempting to resolve an issue with the Lighting Scheduler. It's almost working but is failing at a certain point. Here is what I did and is working:

• Created two schedules, one for on & one for off, using the web interface at scheduler.php

• Created a cron job using my local IP as per the documentation:

  • • • • • lynx -dump http://10.0.0.5/tcp/runSchedule.php

• In config.inc.php I have included the following: define("SAVE_SCHEDULE", 1); as well as setting up the timezone, latitude, and longitude parameters. (One of my tasks is set to happen at "sunset", which is working perfectly.)

• I'm also allowing external API access, external URL, and external port (443), but I'm not requiring a password at this point.

• Checking the Action Logs shows the on and off tasks being initiated at the proper times, however the "Result:" in the task log is empty.

For example:
2022-10-11 18:07:02 Running Task - http:/10.0.0.5/tcp/api.php?fx=toggle&type=device&uid=216427469384146938&val=1 - Result:

However, if I paste the URL from the log into a browser the lights turn on and off correctly by changing the val attribute to 0 or 1.

Examining runSchedule.php I see the task is built at line 128, then the curl commands begin and finally the log display is created at line 138. So it seems that the result from curl_exec($ch); is not returning anything.

In a nutshell, the cron is running correctly and scheduler.php is looping through each task which is then correctly generated, but the curl process appears to be failing at that point. (Curl is definitely installed on my server.)

Any help would be greatly appreciated!

Thanks,
John T

[trevethan]

I found the error, it was very subtle and I finally caught it.

In config.inc.php, for the define("LOCAL_URL", parameter I left out a single forward slash in my local URL. I had it as http:/10.0.0.5/ rather than http://10.0.0.5/

Now the Scheduler works and I finally have the Sunrise and Sunset options available so I won't need to routinely change the times as I had been when using the fixed values in Scenes.

[sktaylortrash]

Oh, that's great you found it. I hadn't had a chance to dig into what might be causing your issue