Domoticz

Woody wrote: ↑Friday 06 March 2020 20:40 Most recent stable build: 4.10717, Aurora theme, zero changes.

I have a darksky dev Secret Key for the API. darksky.net shows that the key is stil valid and I am well under my 1,000 requests a day.

I have a number of weather "devices" which are darksky and they work and update fine and there are no errors in the log file relating to any of them.

However, approx 4 days ago, when I select the forecast page (that has been working fine until now) http://xx.xx.xx.xx:8081/#/Forecast I simply get a page that says darksky.net refused to connect.

This is browser and client machine agnostic - so it is not something that has changed locally, and if I go to the dedicated darksky web page directly - https://darksky.net/forecast/xx.xx,xx,xx/ukxx/en the forecast page loads fine for my correct location.

There is no weird AV involved and while I have PiHole, it is not blocking - so does anyone have any bright ideas?

Woody wrote: ↑Friday 06 March 2020 20:40 However, approx 4 days ago, when I select the forecast page (that has been working fine until now) http://xx.xx.xx.xx:8081/#/Forecast I simply get a page that says darksky.net refused to connect.

This content cannot be displayed in a frame
There is content, but the publisher does not allow it to be displayed in a frame.
This will better protect the information you may enter on this site.
Try this
Open this in a new window
Report this problem

wizworks wrote: ↑Tuesday 10 March 2020 4:02 I think this is because Domoticz makes a call to the API over port 80 (HTTP) and not port 443 (HTTPS). When I curled:

curl http://api.darksky.net/forecast/api.key ... 4,-71.3329
{"code":400,"error":"this call requires HTTPS"}

Where do we change the API call from HTTP to HTTPS? It seems Darksky stopped answering HTTP requests.

wizworks wrote: ↑Tuesday 17 March 2020 2:44 *bump* we need a fix, or at least someone to point out the script object to modify to allow Domoticz to call this API over HTTPS... please help.