Mike Carron

I noticed that my Custom Configuration Parameters did not contain the Units parameter so I added it. As soon as I added the Units parameter everything started working properly. My Admin Console now has valid weather data and I can program my irrigation system properly. Thanks.

How do I fix that?

Ok, that would be this file: OpenWeatherMap_5-3-2024_64124_PM.zip

Where can I find that plug-in log package? Do you mean the PG3(x) log?

Here is the log package for today. I really suspect the problem lies with my EISY, not with OpenWeatherMap. OpenWeatherMap_5-2-2024_62904_PM.zip

Bob Paauwe: I recycled the EISY as you suggested, when I redid the query I got this: 2024-04-30 13:00:49,073 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message query 2024-04-30 13:00:49,073 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING query 2024-04-30 13:00:49,073 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS query message {'address': 'controller', 'requestId': '6'} from Polyglot 2024-04-30 13:00:49,074 Command udi_interface ERROR query:query_onecall: Onecall data query failed OpenWeatherMap values are still all zero.

I sent a query from the EISY and this is what I got: 2024-04-29 18:33:03,062 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message query 2024-04-29 18:33:03,062 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message query 2024-04-29 18:33:03,062 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message query 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING query 2024-04-29 18:33:03,062 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message query 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING query 2024-04-29 18:33:03,062 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message query 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING query 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS query message {'address': 'controller', 'requestId': '5'} from Polyglot 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING query 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS query message {'address': 'controller', 'requestId': '5'} from Polyglot 2024-04-29 18:33:03,063 Command udi_interface ERROR query:query_onecall: Onecall data query failed 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING query 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS query message {'address': 'controller', 'requestId': '5'} from Polyglot 2024-04-29 18:33:03,063 Command udi_interface ERROR query:query_onecall: Onecall data query failed 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS query message {'address': 'controller', 'requestId': '5'} from Polyglot 2024-04-29 18:33:03,063 Command udi_interface ERROR query:query_onecall: Onecall data query failed 2024-04-29 18:33:03,063 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS query message {'address': 'controller', 'requestId': '5'} from Polyglot 2024-04-29 18:33:03,063 Command udi_interface ERROR query:query_onecall: Onecall data query failed 2024-04-29 18:33:03,063 Command udi_interface ERROR query:query_onecall: Onecall data query failed

By way of context, I used an ISY-994i from 2013 until it died in 2022. For that entire time there was no problem with weather data. When the 994i died I replaced it with an EISY. As soon as I installed the EISY all weather values became 0 and I have not been able to get it to report valid weather data.

This appears to be the error message: udi_interface ERROR query:query_onecall: Onecall data query failed Here is context surrounding that error message: 2024-04-25 08:06:38,907 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2024-04-25 08:06:38,907 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026692_3.cert key: 0021b9026692_3.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2024-04-25 08:06:38,907 MainThread udi_interface.interface INFO interface:addNode: Adding node OpenWeatherMap(controller) [None] 2024-04-25 08:06:38,908 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2024-04-25 08:06:38,958 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2024-04-25 08:06:38,959 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:66:92_3 - MID: 2 Result: 0 2024-04-25 08:06:39,000 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2024-04-25 08:06:39,176 Thread-4 udi_interface ERROR owm:discover: Failed to create forecast node Forecast 0 'NoneType' object has no attribute 'lower' 2024-04-25 08:06:39,177 Thread-4 udi_interface ERROR owm:discover: Failed to create forecast node Forecast 1 'NoneType' object has no attribute 'lower' 2024-04-25 08:06:39,177 Thread-4 udi_interface ERROR owm:discover: Failed to create forecast node Forecast 2 'NoneType' object has no attribute 'lower' 2024-04-25 08:06:39,177 Thread-4 udi_interface ERROR owm:discover: Failed to create forecast node Forecast 3 'NoneType' object has no attribute 'lower' 2024-04-25 08:06:39,177 Thread-4 udi_interface ERROR owm:discover: Failed to create forecast node Forecast 4 'NoneType' object has no attribute 'lower' 2024-04-25 08:06:39,177 Thread-4 udi_interface ERROR query:query_onecall: Onecall data query failed 2024-04-25 08:16:38,016 Thread-6 udi_interface ERROR query:query_onecall: Onecall data query failed 2024-04-25 08:26:38,019 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2024-04-25 08:26:38,019 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2024-04-25 08:26:38,019 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot

Refreshed login as suggested, logged back into PG3, all values are 0. I did an API call from the browser using the same coordinates as PG3x and that worked fine. I got good weather data. I double checked my configuration data (API Key, lat=38.87&lon=-121.10, forecast days (5), elevation (420) and plant type (0.23)). I'm stumped. PG3x is 3.2.21, OWM is 4.0.0 [Production].

I'm using an API Key I got before I upgraded to 4.0.0. Is that a problem? Should I get a new API key?

Update: I waited about 20 minutes, hit Restart again and am now connected. Node values for Open Weather Map are still 0 though.

I did the update, now shows OpenWeatherMP 4.0.0. I clicked on Restart and was disconnected. I got an error message saying "No Valid License." I don't recall having to get a license before.

Followed your instructions, selected the Default (free) plan from the Professional Collections. Got an API key, waited 48 hours and put it into the Polyglot configuration. I restarted Polyglot and checked the nodes. All values are 0.

How can I get an API key that will allow my EISY to retrieve valid weather data from OpenWeatherMap?