jkosharek Posted January 12, 2022 Posted January 12, 2022 Just purchased the PGv3 AmbientWeather to move from the PGv2 that I am running, I created a new API Key on AmbientWeather.net and added it to the API Key 'Custom Configuration Parameters' and restarted AmbientWeather. It creates a new node on the ISY with the correct station name and 4 sub nodes main, indoor, five, two. The PGv2 has 21 Nodes @bpwwer any ideas?
bpwwer Posted January 12, 2022 Posted January 12, 2022 @jkosharek I'm not sure what you're asking for ideas about. The PG3 node server is a replacement for the two different Ambient node servers available on PG2 and as such, it is different from both. It creates nodes based on the data it gets from AmbientWeather.net. There should be a node for each sensor it finds.
jkosharek Posted January 12, 2022 Author Posted January 12, 2022 I purchased and installed the PGv3 AmbientWeather and the nodes it created are incomplete and don't work. AmbientWeather PG3 seems to be broken.
bpwwer Posted January 12, 2022 Posted January 12, 2022 I just installed and tested and it is working correctly. You'll have to provide specific details about what is not working for you. I can't see your station(s), your data, or what it's doing on your system. AmbientWeather has a lot of different hardware with different configurations and I'm only able to test with a small sub-set of that. Please provide data on the hardware. Also check the log for errors.
jkosharek Posted January 13, 2022 Author Posted January 13, 2022 I Have a WS-2000 with an additional indoor temp sensor, and inside and outside Air Quality. It creates the weather station name correctly on the ISY and then 4 other devices with names that make zero sense. Works perfect on PG2. I’ll reinstall and dig through the logs. Would it help if I created you an API Key to test with?
bpwwer Posted January 13, 2022 Posted January 13, 2022 It sounds like the correct nodes based on what you've said. The node names come from the data. 'main' is probably the WS-2000 sensors 'indoor' is probably the additional indoor sensor 'five' and 'two' are probably the air quality, one of those is indoor sensors and the other outdoor. When Ambient Weather sends the data, it suffixes the various keys with which device the data is from but it uses things like 'temp' for the main temperature, 'tempin' for an indoor temperature, 'temp2', 'temp3', etc. for other temperature sensors. The node server organizes it by the suffix, 'main' for values with no suffix, 'indoor' for values with 'in' suffix, 'five' for sensors with '5' suffix. That was the best way I could think of to organize it without making you manually enter what every values means.
jkosharek Posted January 13, 2022 Author Posted January 13, 2022 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.
jkosharek Posted January 13, 2022 Author Posted January 13, 2022 I may have discovered the issue, in the log the MAC address is wrong, the log lists f4cfa2cd9c6 and the actual mac is F4CFA2CD9C06 (F4:CF:A2:CD:9C:06) AmbientWeather on PG3 dropped a 0 in the MAC or station identifier.
bpwwer Posted January 13, 2022 Posted January 13, 2022 I'm not seeing any problems with the node server on my installation. The API key I was given to test with is for a setup with 3 stations each of which has various sensors and they are all reporting correctly. If it is saying the API key is invalid, then it is not going to initialize properly which may be part of the problem. Can you generate a key for me and PM it to me? The PG3 node server is different from both of the PG2 versions. The PG2 versions were only able to support specific station types and sensor types, because of the design used, new station types or sensor types had to be added to the code as we were made aware of them. The PG3 version is designed to create the nodes based on what shows up in the data from AmbientWeather. So it should adapt automatically to new stations and new sensors. This also means that the way the data is organized into nodes is different. Instead of having a node for indoor temperature, it has a indoor node with the temperature being one of the values of that node. The indoor node will contain values for what types of sensors the indoor device has (temp, humidity, etc.). Your screen shot for the PG3 version looks correct. Based on what I see above, your indoor node should have temperature, dewpoint, humidity, feelslike, and battery. The MAC address is used to generate a node address. To do that, it removes the ':' and '0' characters. This is to make it work with ISY limitations on how a node address is formatted. Otherwise, the node server doesn't care what the MAC address is.
jkosharek Posted January 13, 2022 Author Posted January 13, 2022 PM Sent, here is what indoor looks like:
Recommended Posts