I was mistaken as to what I am using in my production setup. The name changed from AmbientPoly in PG2 to AmbientWeather in PG3? I am using AmbientWeather (Simplex Technology) on PG2 in my production setup with great success, it provides 21 weather nodes with proper names and values that work. Also noted that AmbientWeather (Simplex Technology) on PG2 uses both an API and APP keys. I noted on the AmbientWeather.net account page where the API Keys are managed: "Developers: An Application Key is also required for each application that you develop. Click here to create one." If this key is created on your side, maybe there is a problem with the APP Key in PG3?
To install AmbientWeather PG3 I create an API Key on https://ambientweather.net/account like I did for version 2 and enter it in the config, but unlike PG2 there isn't the macAddress option under Custom Configuration Parameters in PG3.
In the logs for AmbientWeather PG3 I see 'Invalid API key', but you can see that the key works just fine in both PG2 versions (I created a new key and entered it in the other PGs one at a time restarting the PG to test the new key), I tested the key in both Ambient versions on PG2, they PG2 versions worked and gave no API Key errors, the same API Key in PG3 gives the API Key error in the logs. Now they all have new individual API Keys PG2 versions work and PG3 is still broken...
I have attached screen shots to display the issues with AmbientWeather-Bob Paauwe-PG3 and examples of how each PG version looks. The four PG3 sub nodes all have 1 parameter, battery level (1 volts). After installing AmbientPoly in PG2 again and looking deeper, some parameters non-functional, like Illumination/Lux stays at 0 and works fine in AmbientWeather in PG2 an is displaying the current lux at 4445 and fluctuating correctly with current conditions.