I setup AmbientWeather v2.0.6 on PG3 v3.1.13 on IoP v5.4.4. Put in the API Key and it created 3 nodes in PG3 and on IoP. In the AmbientWeather Node Server on PG3 web interface I see the following nodes:

Node 1 - Weather Station - 1 property, just the name
Node 2 - Main (outside array) 19 properties
Node 3 - Indoor (inside array) 7 properties

On IoP is see:
Node 1
Node 2 - Main - 7 properties
Node 3 - Indoor - 7 properties

The properties and values on Node 2 and 3 are both from Node 3, The number of properties and values I see in PG3 for node 2 are not displayed in IoP at all. 

Also in Programs, Node 2 doesn't show up at all, only 1 and 3. 

bpwwer how do I get the Nodes displayed in PG3 to display correctly on the IoP??

Did you restart the admin console?  You always have to restart the admin console after installing a node server or the admin console won't know how to display the nodes created by the node server.

10 minutes ago, bpwwer said:

Did you restart the admin console?  You always have to restart the admin console after installing a node server or the admin console won't know how to display the nodes created by the node server.

Yes, hit load profile on the PG3 interface, restarted admin console, same node mismatch. Also stopped node and started, then restarted admin console, same node mismatch.

 

I don't have an Ambient station or account so I'd need access to your data to test and debug.

It sounds like something could be wrong in the profile files created for your data.  It should log what it is creating for the node definitions if you enable debug level logging.  So first do that and send me the log.

Sent the logs and my API Key 

When you look in the Admin Console you and click on the node server you should see Nxxx_zzzzzzzzz - Ambient Station

xxx should be the Node server slot in IOP and ZZZZZZZ is the MAC address of your station. 

@bpwwerMine is working as designed.  Just FYI....

Edited November 9, 20222 yr by tlightne

On PG3:
Node 1 - Parent Node - 943cc64511f
Node 2 - main - 943cc64511f_1

Node 3 - indoor - 943cc64511f_2

On IoP Admin:
Node 2:

Node 3:

 

 

A just releases a new version (2.0.7) that should fix the issue.

The problem was that @jkosharek's  station is reporting battery data that I had not seen before and the data parser ended up generating two battery drivers with the same name in the node.  The ISY doesn't like that and the node was not really valid, hence it wasn't able to display it properly in the admin console.

Great work bpwwer: