Problem with Forecast.io after release 19 it keeps reconnecting rapidly (multiple times per second)

ronvl · May 14, 2016, 6:43pm

Does anybody have the same problem as me that after upgrading to 19.4 it keeps connecting every second and I can’t seem to slow it down.

  - platform: forecast
    api_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    scan_interval: 900
    monitored_conditions:
      - hourly_summary
      - minutely_summary


May 14 20:43:12 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:43:13 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:01 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:02 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:03 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:04 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:05 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:05 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:06 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:07 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:08 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:08 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:09 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:10 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:11 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:11 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:12 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io
May 14 20:40:13 raspberrypi hass[919]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.forecast.io

please advise

Thanks

Ron

rpitera · May 14, 2016, 7:37pm

Just checked again to be sure, but not seeing that on my end. I’m on a Windows 10 installation though.

ronvl · May 14, 2016, 8:43pm

Good point I’m running it on a Raspberry Pi 3… was working perfectly under 18 though…

rpitera · May 15, 2016, 12:21am

Have you tried setting the scan interval higher, just to test? I’d be curious if there was any difference if you doubled the scan interval to 1800…also, beyond the speed up, is it actually grabbing any data?

ronvl · May 15, 2016, 9:21am

Under 18 I didn’t had the scan interval configured as it was not going over the 1000 free connections in a day. I added it to see if it makes a different but it doesn’t. I’ve tried several values but no difference at all.

Yes it is grabbing data and updating the history.

Also tried to change the monitored_conditions from 10 to one and various combinations to see if that makes a difference but no difference in its behavior.

With the way it currently operates the 1000 free connects are done in 1 to 1.5 hours :-s so had to comment weather forecast out in the config.

rpitera · May 15, 2016, 12:11pm

Really weird. You may want to bring this up in Gitter chat so a higher level dev can comment. There are surely more RaspPi users here than Windows users so I am sure if it was a common issue it would have shown up here in the forums. I’ll keep looking though and see if I can find anything.

kwetiaw · May 20, 2016, 3:10am

Im on Raspberry Pi 3 as well and have the same issue, it’s just littering my log file

16-05-20 13:04:01 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-20 13:04:03 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-20 13:04:04 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-20 13:05:00 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sensor.date__time, new_state=<state sensor.date__time=2016-05-20, 13:05; icon=mdi:calendar-clock, friendly_name=Waktu Sydney @ 2016-05-20T13:05:00.530844+10:00>, old_state=<state sensor.date__time=2016-05-20, 13:04; icon=mdi:calendar-clock, friendly_name=Waktu Sydney @ 2016-05-20T13:04:00.548660+10:00>>
16-05-20 13:05:00 requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): 10.0.0.1
16-05-20 13:05:00 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-20 13:05:00 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sensor.ram_use, new_state=<state sensor.ram_use=51.8; unit_of_measurement=%, icon=mdi:memory, friendly_name=RAM Use @ 2016-05-20T13:05:00.564051+10:00>, old_state=<state sensor.ram_use=51.7; unit_of_measurement=%, icon=mdi:memory, friendly_name=RAM Use @ 2016-05-20T13:04:00.565772+10:00>>
16-05-20 13:05:00 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sensor.cpu_use, new_state=<state sensor.cpu_use=1; unit_of_measurement=%, icon=mdi:memory, friendly_name=CPU Use @ 2016-05-20T13:05:00.578976+10:00>, old_state=<state sensor.cpu_use=2; unit_of_measurement=%, icon=mdi:memory, friendly_name=CPU Use @ 2016-05-20T13:04:30.595720+10:00>>
16-05-20 13:05:01 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-20 13:05:02 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io

ronvl · May 20, 2016, 7:28am

Thanks for reporting that you have the same issue kwetiaw as that confirms that it is not something stupid on my side. I have been fighting around with it a couple of days now trying all kind of different scenarios but my conclusion is that something changed in version 19 that makes the PI3 to be more responsive and request/triggers are apparently handled quicker.

That is overall positive but makes forecast.io unusable as it will run out of the free 1000 request a day.
As the scan_interval is ignored by forecast (as somebody confirmed in gitter chat some time ago) I switched to openweathermap until this is fixed.

CCOSTAN · May 20, 2016, 1:45pm

I run on a PI as well. Looks like it became an issue for me with 19 but seemed to have gone away at 20 Dev. You can see the timeline in the forecast.io chart.

ronvl · May 22, 2016, 3:47pm

Thanks for your feed back… Just upgraded to 0.20 but still the same problem :-s

kwetiaw · May 27, 2016, 8:35am

i just upgraded to 0.20 as well and it still the same

16-05-27 18:31:01 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-27 18:31:03 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-27 18:31:04 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-27 18:32:00 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-27 18:32:01 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io
16-05-27 18:32:02 requests.packages.urllib3.connectionpool: Starting new HTTPS connection (1): api.forecast.io

and so forth…