Since upgrade to v.4.0.1115 CPU utilization at 100%

Follow

Steve Payne

April 15, 2019 14:42

Hi guys,

I jumped on the v.4.0.1115 download as I'd been noticing the NOAA hourly update failures frequently.

The upgrade appeared to go smoothly but each morning since the CPU utilization is at 100% and my HD12 sounds like the washing machine in spin cycle.

Just kidding about the sound.

Rebooting the device brings it back to normal (1-5% utilization) but the next morning it's back up there in spin cycle again 100% CPU utilization.

I have weather downloads from both NOAA and ForecastIO. I suspect parsing one or the other (or both) when some overnight type file unique to that time period downloads is dropping it into a loop, but this is just a swag.

You guys are great but this looks like a dud update.

 

Let me know what other information might be useful.

Thanks!

0

• 

  Steve Payne April 16, 2019 12:07

  I turned off ForecastIO (disabled) last night. This morning the HD12 was spinning again at 100% rebooted. It downloaded the latest NOAA update and shows 40,000 inches (that's a comma not decimal. 40,000 inches in meters is 1016 meters. So should I be worried? I know I should have kept that ark.

   

  

  0

  Comment actions Permalink
• 

  Steve Payne April 18, 2019 23:48

  Disabled NOAA and enabled ForecastIO. next day CPU usage at 100%. Maybe it's not weather download.

  Today I activated manual watering, and the CPU went to 100% and did not drop. Rebooting returned the HD12 to normal (less than 5%).

  It seems the high CPU utilization is triggered by a watering event. Overnight the scheduled run, even if it doesn't call for any water (which it hasn't) must be triggering the 100% CPU utilization.

  Hopefully you guys are working on this. It seems software related, this wasn't occurring prior to downloading/installing 4.0.1115.

  Thanks!

  0

  Comment actions Permalink
• 

  Steve Payne April 29, 2019 12:32

  As of Saturday April 27 the HD12 has not repeated the 100% CPU utilization.

  The event I noticed that was different 27 April was it actually activated a zone. It's been a rainy spring in Georgia (US).

  Or it could be bad data that aged out. This started before April 15.

  Sorry about the "dud" comment. It seems to be running smoothly now since Saturday (3 days of watering).

  Please consider this "fixed."

   

   

  0

  Comment actions Permalink

Please sign in to leave a comment.