Jump to content

Climacell has no forecast info


drprm1
Go to solution Solved by bpwwer,

Recommended Posts

Finishing up migrating from 994 to eisy…Everything good except one nodeserver, Climacell, is giving the correct current weather data but not populating the forecast days. All days have the same template with no data. 

Have deleted and reinstalled Climacell a few times with no help.All other nodesevers work well.

PG3X 3.1.26

Link to comment
Checked the config  tab many times and it is correct. Also restarted AC with no luck.

The error log on restart is below. Only thing I see is last line.."Forecast data failure".....

 
 
 
023-05-15 07:29:20,116 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30
2023-05-15 07:29:20,470 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting...
2023-05-15 07:29:20,473 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.26 [ISY: 5.6.0, Slot: 7]
 
023-05-15 07:29:20,473 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.1.50', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'}
2023-05-15 07:29:20,474 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883
2023-05-15 07:29:20,475 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database.
2023-05-15 07:29:20,475 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.1', 'requestId': False}}
2023-05-15 07:29:20,476 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026226_7.cert 0021b9026226_7.key
2023-05-15 07:29:20,483 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success)
2023-05-15 07:29:20,483 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:62:26_7 - MID: 2 Result: 0
2023-05-15 07:29:20,526 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,)
2023-05-15 07:29:23,489 MainThread udi_interface.interface INFO interface:addNode: Adding node Climacell Weather(controller) [None]
2023-05-15 07:29:23,490 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status.
2023-05-15 07:29:23,549 Thread-1 udi_interface ERROR climacell:parameterHandler: ***** Entered parameter handler....
2023-05-15 07:29:34,275 Thread-3 udi_interface ERROR query:query_forecast: Forecast data failure: 'data'
Link to comment

Looks like you need some assistance from the node server creator regarding:

2023-05-15 07:29:23,549 Thread-1 udi_interface ERROR climacell:parameterHandler: ***** Entered parameter handler....
2023-05-15 07:29:34,275 Thread-3 udi_interface ERROR query:query_forecast: Forecast data failure: 'data'

I am flagging @bpwwer for you.

Edited by DennisC
Added flag to Bob.
  • Like 1
Link to comment

I did see this in the instructions:

* How often to poll the climacell weather service for current condition data (in seconds).
 Long Poll
* How often to poll the climacell weather service for forecast data (in seconds). Note that the data is only updated every 10 minutes. Setting this to less may result in exceeding the free service rate limit.

Link to comment

Yes....

Seeing this line every 10 minutes

2023-05-15 07:59:20,328 Thread-31 udi_interface ERROR query:query_forecast: Forecast data failure: 'data'

The poll settings are the same as before the migration so should work 🤞

Edited by drprm1
Link to comment

If you set the log level to 'debug' you'll get more information.  It will display the actuall http request that it is making for the forecast data and it will display what the server returns.

The error message is because the server did not return any forecast data.

Link to comment
  • Solution

The is what the server is sending in response:

The plan is restricted and cannot perform this action. Adjust action and try again: endTime cannot be more than 5 days ahead.'

It sounds like you're requesting more days of forecast than your plan allows.  Reduce the number of forecast days to 5 or less.

  • Like 1
Link to comment
  • 1 month later...

I've bitten by this same issue too.  I've been using 7 as my 'Forecast Days'  for a year or more and it's worked fine.  I suspect a 'policy' change at Climacell, but I don't know when.  I've now switched to a 4 day forecast request.  Thanks for posting this!

Edited by rwsani99
Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...