Unable to get API generated

Mike Carron · April 18

I know I need a Professional Collections API key. I'm trying to get one but not having much luck.

I can get to https://openweathermap.org/price#weather which in turn leads me to https://home.openweathermap.org/ where I click on the Get API Key in the Free column. That click gets me to https://home.openweathermap.org/ (again), this time with a notice that I am already signed in and with nothing about Professional Collections that I can find.

I would very much like to use a Professional Collections API key if I could figure out how to get one.

Geddy · April 18

@Mike Carron welcome to the forums for Universal Devices. Seems like you should look at the OpenWeatherMap FAQ/Support area for assistance.

https://openweathermap.org/faq

When I try the first link you posted and click on the "Subscribe" under any options it takes me to a signup screen.

The free one goes to: https://home.openweathermap.org/users/sign_up

bpwwer · April 19

If you're signed in, you should see something like this:

image.png.1f7a4f26f794cce0ec8bc511c2d28f89.png

Then going to "Billing plans" will show which plan(s) you're subscribed to and "API Keys" will let you generate keys for the plan(s) you're subscribed to.

Mike Carron · April 19

I understand that the plug-in only works with the Professional Collections API. How do I get one?

bpwwer · April 21

Create an account on openweathermap.org
log in to the account you created.
Go to "My Services" from your account menu
Go to "Billing Plans"
Subscribe to a plan from the Professional Collections
Go to "API Keys"
Press the "Generate" button to generate a new API key

Once you generate the API key, it can take anywhere from 1 to 48 hours before that key is active and usable. Once it has been activated by OpenWeatherMap, it can be used in the plug-in.

Mike Carron · April 24

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.

bpwwer · April 24

It appears that OpenWeatherMap made changes that broke the requests the plug-in was making to that API. I've updated the plug-in to version 4.0 and changed it to use the OneCall 3.0 API instead of the Professional Collection API.

Mike Carron · April 24

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.

Mike Carron · April 24

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

bpwwer · April 24

The "No Valid License" is from PG3. All plug-ins require a license to run, even free plug-ins. So at some point you did get a license for plug-in. Probably just a temporary outage when your PG3 tried to verify you had a valid license.

API keys from OpenWeatherMap can take as long as 48 hours to become active and work.

Mike Carron · April 25

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?

Geddy · April 25

@Mike Carron You might need to refresh your login with the ISY Portal account/profile. The easiest way to do that is:

login to PG3 dashboard (https://eisy.local:3000 - replace eisy.local with polisy.local if using a Polisy)
go to System | Switch Portal Profile
then login (to the portal)
Screen will refresh back to Polyglot
click the Logout button (polyglot web access - top right)
Log back into PG3

You shouldn't need a new API. Everything was working fine for me prior to the 4.0 update and continued after the update.

Mike Carron · April 25

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].

bpwwer · April 25

If you set the log level of the plug-in to debug and look at the log entry for a query, what is OpenWeatherMap returning? It will either return an error (which will point us at what is wrong) or it will return data.

Mike Carron · April 25

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

Mike Carron · April 29

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.

bpwwer · April 29

It looks like you switched the log level to debug, but didn't wait for a query to happen as there's no query results when in debug in the log snippet above.

In most cases, the query failure is related to an invalid API key followed by the location format being incorrect. Your location looks to be correct.

Without a complete debug log I can't help.

btreinders · April 30

Not working for me either now once I updated. Are we saying we need a professional plan that costs money? I can't see any that don't eventually say you have to pay $0.15 per 100 calls. Says free at first and then requires a payment method.

Mike Carron · April 30

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