bpaauwe / udi-climacell-poly Goto Github PK

During troubleshooting, I discovered that sometime on 11 December 2020, current observation and forecast data ceased updating.

My API key is valid - issued on 7 November 2020

The following error messages appear in the log:

2021-01-16 13:51:38,306 [Controller] [ERROR] Current observation update failure
2021-01-16 13:51:38,307 [Controller] [ERROR] 'data'
2021-01-16 13:53:38,079 [Controller] [DEBUG] longpoll
2021-01-16 13:53:38,079 [Controller] [DEBUG] -------------
2021-01-16 13:53:38,080 [Controller] [DEBUG] FORECAST: https://data.climacell.co/v4/timelines?location=41.947460,-87.654732&timesteps=1d&endTime=2021-01-16T13:53:38Z&fields=precipitationIntensity,precipitationType,precipitationProbability,temperatureMin,temperatureMax,temperatureApparent,dewPoint,windSpeedMin,windSpeedMax,windSpeedAvg,windGust,pressureSeaLevelMin,pressureSeaLevelMax,visibility,humidityMin,humidityMax,humidityAvg,windDirection,cloudCover,cloudCeiling,cloudBase,solarGHI,weatherCode,moonPhase
2021-01-16 13:53:38,294 [Controller] [DEBUG] FORECAST: {'message': 'The method requires authentication, but it was not presented or is invalid.', 'code': 401001, 'type': 'Invalid Key'}
2021-01-16 13:53:38,294 [Controller] [ERROR] Forecast data failure: 'data'

api.climacell.co is no longer a valid DNS entry. Appears to have been rebranded, purchased by tomorrow.io on main website.

Been a while since I looked at my Polyglot

Options:

1. Same API / New DNS = Update this Polyglot
2. Different API = New Polyglot

Has this been looked at? Perhaps this should be removed from NodeServer Store to avoid confusion

I had all working fine, but had to re-install the server node and now I see that two Node Substitutes Variables for the Forecast Node are returning numbers instead of words. This is for GV19 that must return the day of the week and now returning one digit number and GV13 that must return the Weather conditions and now is returning a 2 digit number. The corresponding fields in ISY are populated correctly with description, not numbers. I use the node substitutes variables in a small program that is sending me weather forecast everyday.
This is the program:

Forecast for: ${sys.node.n001_forecast_1.GV19}
Weather Conditions: ${sys.node.n001_forecast_1.GV13}
Chance of Rain: ${sys.node.n001_forecast_1.GV18}
Rain Amount: ${sys.node.n001_forecast_1.GV6}
Max Temp: ${sys.node.n001_forecast_1.GV0}
Min Temp: ${sys.node.n001_forecast_1.GV1}
Max Wind: ${sys.node.n001_forecast_1.GV7}

And these are the results:

Forecast for: 1
Weather Conditions: 15
Chance of Rain: 10%
Rain Amount: 0.3 mm
Max Temp: 21.1°C
Min Temp: 11.7°C
Max Wind: 5.9 meters/sec

The min/max values pulled from the API aren't daily min/max values but are in fact "variances within the area" for the current point in time. Even on the forecast API's these values aren't daily max/min values.

Suggest removing ETo and max/min values from this interface, so it doesn't confuse people.

The only API which shows daily max/min is one that is on a Paid account.

See below from: https://openweathermap.org/faq

--

In the Current Weather API, Hourly Forecast API and 5 day / 3 hour Forecast API

The temp_min and temp_max fields are optional parameters that mean minimum/maximum at the moment of calculation. This is the minimum/maximum currently observed or forecasted temperature (within large megalopolises and urban areas).

In the 16-Day Forecast API

The list.temp.min and list.temp.max fields are minimum/maximum daily temperature, and show the minimum and maximum temperatures in the day.

You already closed the old bug so opening new issue.

This still is not working. Updated to 1.01. I changed from 12 to 15 days. The new 3 days came into ISY but never updated. The old 12 continued. So I erased the entire node Server and added it again. Started with 15 day forecast. None of the 15 updated. Changed back to 12 days and restarted node server and instantly the 0-11 updated.

Two logs attached. First one is after the reinstall with 1.01 and 15 day. Then the second includes the time when I switched to 12 day.

Climacell_logs_2020-4-10_212219.zip
Climacell_logs_2020-4-10_211849.zip

I am using Climacell Poly with a free API Key. I can get the current weather data but not the forecast. Any ideas what is wrong, or what I could try?

This is what I am seeing in the log:
2021-03-24 17:24:06,550 NodeServer polyinterface DEBUG climacell:query_forecast: -------------
2021-03-24 17:24:06,551 NodeServer polyinterface DEBUG climacell:query_forecast: FORECAST: https://data.climacell.co/v4/timelines?location=34.2004922,-118.4374168&timesteps=1d&endTime=2021-03-26T00:24:06Z&fields=precipitationIntensity,precipitationType,precipitationProbability,temperatureMin,temperatureMax,temperatureApparent,dewPoint,windSpeedMin,windSpeedMax,windSpeedAvg,windGust,pressureSeaLevelMin,pressureSeaLevelMax,visibility,humidityMin,humidityMax,humidityAvg,windDirection,cloudCover,cloudCeiling,cloudBase,solarGHI,weatherCode,moonPhase
2021-03-24 17:24:06,886 NodeServer polyinterface DEBUG climacell:query_forecast: FORECAST: {'code': 400005, 'type': 'Rule Violation', 'message': 'The request violated the following requirements:\n1. The timestep 1d requested is bigger than the total time window (start to end time)'}
2021-03-24 17:24:06,886 NodeServer polyinterface ERROR climacell:query_forecast: Forecast data failure: 'data'

Any ideas what is wrong, or what I could try?

Hi -

I am trying to use Climacell Weather on my Polisy mostly for the forecast information. (I use WeatherLink to get to my local Davis weather station current weather information.) Climacell will not load data into the ISY. I've restarted the node server several times. I also restarted my Universal Devices ISY. But I still don't get forecast data from Climacell. A configuration screen shot and my recent log file is attached. FWIW...In the log I notice a message indicating that "...string indices must be integeres".

Just so you know I'm new with Polisy but thought I'd ask this question...thanks for your patience.

Thanks,

Steve

My weather data is fine and looks great but forecast days are all the same. I tried 0-15 although not sure if the FREE API includes more than 5 or 7 but they all say Monday and they all have zeros for the data.