Ambient Console not working

[StangManD]

So I have Ambient Weather already up and running however wanted to keep things local and not have to call out to the web for the data that's inside of my network.  Anyway, that being said, I've followed the directions to a T from what I can tell however it's just simply sitting there with 0 nodes.  The devices can communicate on the network and I have verified the config settings over and over thinking it has to be something simple/stupid.  Well no dice, I'm just sitting here with no idea what to do next.

 

I have a WS-5000 weather station and updated it to the latest firmware today which gives me the ability to define the custom server option (same as the WS-2000).  I have configured it exactly as it should, IP of the Eisy, (default) port defined in the configuration of Ambient Console, and have it set to send the same ambient weather type of data, assuming that's what it needs (I've tried both settings and neither work).  I have set the path to /pg3x? as the instructions say from the store, and I have also tried the path /api/ambientweather/metrics? as the github instructions say.  Neither are working.

 

Need some help here please.

 

Thanks in advance

[StangManD]

Also noticing if I change the "Station Name" field and save, it saves successfully but there is a notice that pops up that says, "Failed to start Console monitoring service."  It's just a blue banner notice type of message, not an error from what I can tell.  Also when I review the log during a "restart" of the node server, it doesn't have any obvious errors at all in it, seems like it starts just fine.

[bpwwer]

If it's failing to start the monitor, nothing will work.  The log should show a similar error with more information if the log level is set to info or debug.

The most likely reason for it failing is that the port you configured is being used by something else on the system preventing the plug-in from being able to use it. 

The default is 7501 which is not a port commonly used but no guarantee that it's not.

[StangManD]

Edit - nevermind... it was a firewall rule across VLANs.  Thank you for taking the time to respond... I accidentally had my response (from Eisy to weather station) disabled.  It's good to go now.  Thank you!

 

Edited 6 hours ago by StangManD