Closed loudgazelle closed 4 years ago
after removing the homebridge-weather-plus config from config.json homebridge is stable and not stuck in a restart loop.
prior to removing homebridge-weather-plus from config.json I updated my config to the following in an attempt to resolve the error, but the error persisted and homebridge continued to be stuck in a restart loop.
"units": "us",
"interval": 10,
"stations": [
{
"service": "openweathermap",
"key": "XXXX",
"locationId": 4393217,
"locationGeo": [
XXXX,
XXXX
],
"locationCity": "Kansas City, US",
"language": "en",
"compatibility": "both",
"units": "us",
"forecast": [
0
],
"conditionCategory": "simple",
"now": true,
"extraHumidity": false,
"tresholdCloudCover": 80
}
],
"platform": "WeatherPlus"
Got exactly same issue. Is started doing this few days ago. Maybe API has changed.
@kfalkiewicz are you also getting emails from OpenWeather stating you're making a large number of API calls as I describe in issue #135?
No, only this error message.
Thanks for reporting! The OWM API seems a bit unstable. I will release a fix in the next few minutes.
Fixed in v3.2.2 (hopefully 😃)
@loudgazelle I'm still invastigating your api limit exceeding issue.
yes, i can confirm 3.2.2 fixed it, and I'm able to run w/o issue.
I'm experiencing an issue that seems similar to #121 in that it's crashing all of HomeBridge - it appears to be due to homebridge-weather-plus not handling the TypeError correctly. This has put HomeBridge in a restart loop.
the error has occurred 110 times in the span of 29 minutes:
full details showing timing
This is probably further exacerbating issue #135, which I just logged, but I suppose it may also be caused by issue #135 if I'm getting rate limited by their API, but the "block logs" section of their site doesn't show that I've been blocked.