No response object in query response

[skunkiechris]

Hello, 

Have been using the PG2 version of Weatherbit for quite some time now....I noticed today it stopped updating with the above error message.  I bought the PG3 module and installed it, but am still getting this message (and nothing updating) as per below:

2023-05-31 12:03:41,520 Thread-3 udi_interface ERROR query:query_conditions: No response object in query response.

2023-05-31 12:03:41,520 Thread-3 udi_interface ERROR query:query_conditions: No response object in query response.

2023-05-31 12:03:49,796 Thread-3 udi_interface ERROR query:query_forecast: No response object in query response.

2023-05-31 12:03:49,796 Thread-3 udi_interface ERROR query:query_forecast: No response object in query response.

2023-05-31 12:03:51,220 Thread-1 udi_interface ERROR query:query_forecast: No response object in query response.

2023-05-31 12:03:51,220 Thread-1 udi_interface ERROR query:query_forecast: No response object in query response.

 

Not sure if this is just a weatherbit outage, or if I'm doing something wrong?  I have set all the parameters, and in PG2 they have been set for more than a year (so couldn't have been wrong).

 

Thanks!

[bpwwer]

Usually that means you've exceeded the number of queries allowed for you plan.  It seems like some of these services have been making that limit lower over time.  It will usually reset on a daily basis so you might want to reduce how often you poll and wait a day.

[skunkiechris]

Ahhhhh, okay - thanks for your help!!

[skunkiechris]

So I swapped it with an API key I have that hasn't been used at all today, changed my polling to only have 48 calls a day (seems the limit is 50), but I'm still having issues:  (Also getting 4 lines of duplicates for each message?)

2023-05-31 13:19:09,776 MainThread udi_interface      INFO     __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting...
2023-05-31 13:19:09,776 MainThread udi_interface      INFO     __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting...
2023-05-31 13:19:09,776 MainThread udi_interface      INFO     __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting...
2023-05-31 13:19:09,776 MainThread udi_interface      INFO     __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting...
2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO     interface:__init__: Initialization received from Polyglot V3 3.1.26  [ISY: 5.6.0, Slot: 10]
2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO     interface:__init__: Initialization received from Polyglot V3 3.1.26  [ISY: 5.6.0, Slot: 10]
2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO     interface:__init__: Initialization received from Polyglot V3 3.1.26  [ISY: 5.6.0, Slot: 10]
2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO     interface:__init__: Initialization received from Polyglot V3 3.1.26  [ISY: 5.6.0, Slot: 10]
2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO     interface:__init__: Connect: Network Interface: {'addr': '172.26.18.3', 'netmask': '255.255.255.0', 'broadcast': '172.26.18.255'}
2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO     interface:__init__: Connect: Network Interface: {'addr': '172.26.18.3', 'netmask': '255.255.255.0', 'broadcast': '172.26.18.255'}
2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO     interface:__init__: Connect: Network Interface: {'addr': '172.26.18.3', 'netmask': '255.255.255.0', 'broadcast': '172.26.18.255'}
2023-05-31 13:19:09,779 MainThread udi_interface.interface INFO     interface:__init__: Connect: Network Interface: {'addr': '172.26.18.3', 'netmask': '255.255.255.0', 'broadcast': '172.26.18.255'}
2023-05-31 13:19:09,780 Interface  udi_interface.interface INFO     interface:_startMqtt: Connecting to MQTT... localhost:8883
2023-05-31 13:19:09,780 Interface  udi_interface.interface INFO     interface:_startMqtt: Connecting to MQTT... localhost:8883
2023-05-31 13:19:09,780 Interface  udi_interface.interface INFO     interface:_startMqtt: Connecting to MQTT... localhost:8883
2023-05-31 13:19:09,780 Interface  udi_interface.interface INFO     interface:_startMqtt: Connecting to MQTT... localhost:8883
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:start: No node server version specified. Using deprecated server.json version
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:start: No node server version specified. Using deprecated server.json version
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:start: No node server version specified. Using deprecated server.json version
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:start: No node server version specified. Using deprecated server.json version
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:db_getNodeDrivers: controller not found in database.
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:db_getNodeDrivers: controller not found in database.
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:db_getNodeDrivers: controller not found in database.
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:db_getNodeDrivers: controller not found in database.
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6', 'requestId': False}}
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6', 'requestId': False}}
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6', 'requestId': False}}
2023-05-31 13:19:09,781 MainThread udi_interface.interface WARNING  interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.6', 'requestId': False}}
2023-05-31 13:19:09,782 Interface  udi_interface.interface INFO     interface:_startMqtt: Using SSL certs: 0021b9026524_10.cert 0021b9026524_10.key
2023-05-31 13:19:09,782 Interface  udi_interface.interface INFO     interface:_startMqtt: Using SSL certs: 0021b9026524_10.cert 0021b9026524_10.key
2023-05-31 13:19:09,782 Interface  udi_interface.interface INFO     interface:_startMqtt: Using SSL certs: 0021b9026524_10.cert 0021b9026524_10.key
2023-05-31 13:19:09,782 Interface  udi_interface.interface INFO     interface:_startMqtt: Using SSL certs: 0021b9026524_10.cert 0021b9026524_10.key
2023-05-31 13:19:09,789 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Connected with result code 0 (Success)
2023-05-31 13:19:09,789 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Connected with result code 0 (Success)
2023-05-31 13:19:09,789 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Connected with result code 0 (Success)
2023-05-31 13:19:09,789 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Connected with result code 0 (Success)
2023-05-31 13:19:09,790 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_10 -  MID: 2 Result: 0
2023-05-31 13:19:09,790 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_10 -  MID: 2 Result: 0
2023-05-31 13:19:09,790 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_10 -  MID: 2 Result: 0
2023-05-31 13:19:09,790 MQTT       udi_interface.interface INFO     interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_10 -  MID: 2 Result: 0
2023-05-31 13:19:09,833 MQTT       udi_interface.interface INFO     interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,)
2023-05-31 13:19:09,833 MQTT       udi_interface.interface INFO     interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,)
2023-05-31 13:19:09,833 MQTT       udi_interface.interface INFO     interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,)
2023-05-31 13:19:09,833 MQTT       udi_interface.interface INFO     interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,)
2023-05-31 13:19:12,817 MainThread udi_interface.interface INFO     interface:addNode: Adding node WeatherBit Weather(controller) [None]
2023-05-31 13:19:12,817 MainThread udi_interface.interface INFO     interface:addNode: Adding node WeatherBit Weather(controller) [None]
2023-05-31 13:19:12,817 MainThread udi_interface.interface INFO     interface:addNode: Adding node WeatherBit Weather(controller) [None]
2023-05-31 13:19:12,817 MainThread udi_interface.interface INFO     interface:addNode: Adding node WeatherBit Weather(controller) [None]
2023-05-31 13:19:14,621 Thread-3   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for current
2023-05-31 13:19:14,621 Thread-3   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for current
2023-05-31 13:19:14,621 Thread-3   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for current
2023-05-31 13:19:14,621 Thread-3   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for current
2023-05-31 13:19:14,621 Thread-3   udi_interface      ERROR    query:query_conditions: No response object in query response.
2023-05-31 13:19:14,621 Thread-3   udi_interface      ERROR    query:query_conditions: No response object in query response.
2023-05-31 13:19:14,621 Thread-3   udi_interface      ERROR    query:query_conditions: No response object in query response.
2023-05-31 13:19:14,621 Thread-3   udi_interface      ERROR    query:query_conditions: No response object in query response.
2023-05-31 13:19:23,381 Thread-1   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for forecast/daily
2023-05-31 13:19:23,381 Thread-1   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for forecast/daily
2023-05-31 13:19:23,381 Thread-1   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for forecast/daily
2023-05-31 13:19:23,381 Thread-1   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for forecast/daily
2023-05-31 13:19:23,381 Thread-1   udi_interface      ERROR    query:query_forecast: No response object in query response.
2023-05-31 13:19:23,381 Thread-1   udi_interface      ERROR    query:query_forecast: No response object in query response.
2023-05-31 13:19:23,381 Thread-1   udi_interface      ERROR    query:query_forecast: No response object in query response.
2023-05-31 13:19:23,381 Thread-1   udi_interface      ERROR    query:query_forecast: No response object in query response.
2023-05-31 13:19:23,384 Thread-3   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for forecast/daily
2023-05-31 13:19:23,384 Thread-3   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for forecast/daily
2023-05-31 13:19:23,384 Thread-3   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for forecast/daily
2023-05-31 13:19:23,384 Thread-3   udi_interface      ERROR    query:_get_weather_data: HTTP request failed for forecast/daily

I've attached my config, I can't quite figure out what's wrong?

Thanks again!

Edited May 31, 2023 by skunkiechris

[bpwwer]

The duplicated lines is just because PG3 has multiple streams open to the log file, reloading the page in the browser should close those and resolve that.

Try enabling debug log level to see if provides more information on why the queries are failing.

[skunkiechris]

That was helpful, it gave me the URL's that are failing, now it's a 429 (too many requests in a given amount of time) which is weird, since this was an API key that had not been used at all today.  I'll just let it sit in the stopped state and try it later/tomorrow.  Thanks for your quick response!!

[skunkiechris]

I ended up upgrading my package to ensure this doesn't happen again, as the weatherbit stats are used heavily in irrigation, especially for some delicate plants that need to be watered during the day!

One curiosity.  At debug level I get the following message four times every two seconds endlessly:

DEBUG    Controller:start: *** Waiting for all nodes to be added

As far as I can tell, all nodes are there!  Any ideas or should I just ignore it? Thanks!

[bpwwer]

Yes, you can ignore it, but unless you're actually trying to debug an issue, it's best to leave the log level at info or even error

[skunkiechris]

Weird though, I upgraded to the 25,000 queries/day, as I mentioned, and I'm still getting the original error message, which is confusing.  

 

2023-06-01 11:47:41,784 Command udi_interface ERROR query:query_conditions: No response object in query response.

 

When I manually hit the URL it is displaying in the debug level log literally nothing happens. It gives no success, no fail. nothing at all. 😕  Which make me assume it's not an issue on your side.... 🤷

 

Edit: My short poll is 300 and my long poll is 1800, well withing the 25,000 limit!!

 

Edited June 1, 2023 by skunkiechris

[bpwwer]

Can you post/pm me the URL?

If the server isn't responding at all to the query, yeah, I can't fix that in the node server. But I can check the query and make sure the node server is creating an invalid query.

[khowell]

Bob, have you found a solution to this issue?

I am also not getting valid forecast data from weatherbit.  I.E. it is now Friday and my Forecast 0 node says it is Thursday (it should say Saturday). The main node data "WeatherBit Weather" appears to be correct.

 

I have included the log package.  At 16:40 I manually queried the Forecast 0 then Weather nodes as can be see in the log file.

 

My configuration is still shortPoll=300 and longPoll=600 on a free account.  It doesn't look like I am exceeding the daily count as there is no change to the information for the day.

 

Thank you,
-Kerry

WeatherBit_6-9-2023_24021_PM.zip

[skunkiechris]

The limit on the free account is 50 queries per day (as of when I have no idea).  So a short poll of 300 will quickly exceed your max.  I'm not sure how they work that, as when I was experiencing it I waited a day but still got nothing.  I eventually upgraded to the $40 plan and everything started working fine.

[bpwwer]

I just tried one of your queries and this is the response from WeatherBit

Quote

Your request count (56) is over the allowed limit of 55 per day - Upgrade your key, or retry after 507.13333333333 minutes

[khowell]

Thank you, I will raise my poll rate to 3600 to keep under the 50 per day and see how that works.

Edited June 10, 2023 by khowell