Closed droopdog7 closed 3 months ago
Could you please humour me and double-check that you entered the new API correctly. Homebridge WS should try the 3.0 OneCall first and only fallback to 2.5 in case the 3.0 call fails with a 401.
Please set logLevel to 2, run Homebridge in DEBUG mode and capture and attach (!) the log file from startup of Homebridge WS. I’m particularly interested to see request 1.
Hopefully this is an easy fix but I signed up for API 3.0 using my credit card (and set the limit to 1000 calls). I generated a new API Key and added to my settings but I keep getting the error. It's been a few days and nothing has changed. Not sure what I am doing wrong?
[14/06/2024, 21:39:05] [Weather] warning: You need to change your OpenWeather subscription to OneCall 3.0, see https://openweathermap.org/one-call-transfer [14/06/2024, 21:39:05] [Weather] openweathermap request 2: GET 2.5/onecall?lat=33.8703&lon=-117.9253&exclude=minutely [14/06/2024, 21:39:05] [Weather] warning: openweathermap request 2: openweathermap status: 401 Invalid API key. Please see https://openweathermap.org/faq#error401 for more info.