Open mikejgray opened 1 year ago
have to ask, an api key is set in the backend config? Had no problems while requesting owm from the personal backend.
"microservices": {
"ovos_fallback": true,
"wolfram_provider": "auto",
"weather_provider": "auto",
"geolocation_provider": "auto",
"wolfram_key": "",
"owm_key": <some_key>
},
Besides, the new weather skill is not requesting from owm any more
have to ask, an api key is set in the backend config? Had no problems while requesting owm from the personal backend.
"microservices": { "ovos_fallback": true, "wolfram_provider": "auto", "weather_provider": "auto", "geolocation_provider": "auto", "wolfram_key": "", "owm_key": <some_key> },
Besides, the new weather skill is not requesting from owm any more
Yes it is. The weather skill not using owm may be the issue. I was running on all latest betas for OVOS - are you also, or are you on stable versions?
with weather i'm on a pr branch. (refactor/translatable
)
But there wouldn't be a owm call with weather v.0.0.1a8 / a7 either
this has something to do with the admin_key
value. I just came across the same error while doing a UI when trying to do a request without authorization. I guess the endpoint for weather wants admin access?
I'm seeing this in my personal backend logs: