Sysmonitor and darksky stopped working after .36

Archive HASSbian
1

I installed update then system monitor and dark sky stopped working!

1 Like
2

me too facing the same problem
22:03:02 homeassistant.components.sensor.darksky: Unable to connect to Dark Sky. 403 Client Error: Forbidden for url:

3

Thanks for the reply I thought it was just me. I installed system monitor early this morning and darksky yesterday night. I saw the updated this morning and both sysmonitor and darksky disappeared.

4

Both work fine here.

5

Any Ideas I updated per instructions! was working before update

6

Nope sorry, having some other trouble myself after upgrading (local mp3 files can’t be streamed to my Chromecasts which was working fine before the upgrade)

7

I’m still on 0.35.3. Have same issue with Darden every night.

8

updates to radar (“weather underground”) by the camera component stopped getting updates. I thought at first it was was nic problem but i am still getting updates from weather underground local conditions.

9

Check the issues in GitHub; we’ve been discussing an issue with precip values with one of the engineers from DarkSky who has been saying that they have been trying to rack down some issues they’ve been having with the Forecast API. This may be related.

10

Sure will its at least a start

11

You have any news on a fix for dark sky?

12

Nothing reported in the issue at github. I haven’t looked at their site to see if they have identified anything though.

13

I am getting the 403/Forbidden errors for the Darksky component too. Happens throughout the day and I can’t associate it with anything else happening. When it happens I get no results for any of the darksky components. Some time later it starts working again and I get results\values.

Running a fresh install on Raspbian Jessie Lite.

14

Ahhhhh, so I logged into my Darksky account on their website and saw that for some reason I was calling 1000 API lookups a day (the daily max). I have since added update_inverval into my config and removed some of the monitored_conditions.

1 Like
15

I can confirm that the error was due to having too many calls to the Darksky API.
I believe I started getting this after adding in the minutely/hourly/daily_summary fields, potentially these get called separately from the other calls so you get multiple API calls per 2 minute refresh.