Meteobridge 5.0, build 14008 Breaks Connection to PWSWeather and Ecowitt GW1000

[justanothercog]

My Meteobridge server stopped sending data to PWSWeather as of Nov. 1. That’s the day after the device shows Meteobridge being updated to Meteobridge 5.0 (Oct 31 2020, build 14008). I noticed that the settings for PWSWeather are “Station ID” and “Password”. After reentering the information again, the server sent a data set to PWSWeather but that was it. PWSWeather issues an API key that would normally be entered into a “Key” field (like WeatherCloud). I copied and pasted my PWSWeather API key into the password field and it now seems to be working. I’m assuming that the API Key is the correct info to enter into the “Password” field at this point.

It would be nice if Meteobridge would label this field correctly, if the API Key is indeed the correct info to enter there.

The other issue that the 5.0, build 14008, update seems to have caused, is that it stopped receiving all data from my Ecowitt GW1000 on Nov. 1. I had both devices set up on my “Guest” wireless network and everything had been working perfectly since I set this all up last year. I solved this new issue by putting both devices on the main wireless network (non-guest) and Meteobridge began receiving data from the Ecowitt device. I can only assume that this issue was created by the Meteobridge update because all the other Weather networks that my Meteobridge sends to, stopped receiving data as of Nov. 1. I have no idea as to why this worked fine for over a year on the Guest network and why Meteobridge 5.0 broke it. After solving that issue, I still had the problem with PWSWeather not receiving data but was able to resolve that after a few days by putting the API Key into the “Password” field.

[admin]

I don't think the wifi issues are related to the update. Nothing has changed in that code section. Renaming "Password" to "API-key" for PWSWeather (good to hear that someone still feeds to there) will be done in next release.

[galfert]

The change with PWSweather.com to use API key instead of password is new thing that is not fully implemented yet. I'm still using my password instead of the API key. My Meteobridge is running 5.0 build 14008 and it is uploading to PWSweather using my PWSweather password.

Perhaps this is something that they are enforcing on an account by account basis. Meaning a new account with PWSweather may be required to use the API key but an older account may still be able to use password instead. I can also see that there is a new PWSweather account management portal and maybe as long as you don't do any updates to your account it keeps accepting the password but as soon as you accept and make a new change then the API use is enforced. Only a guess at this point.

[wvdkuil]

I don't think the wifi issues are related to the update. Nothing has changed in that code section. Renaming "Password" to "API-key" for PWSWeather (good to hear that someone still feeds to there) will be done in next release.

pwsweather will be more important when Darksky stops with their free "developer" forecasts next year.

Uploading to pwsweather allows you to use a free version of Aeris weather forecasts, current conditions (and some maps).

Wim