Hello all,

Environment:

EISY (5226)
Firmware: v6.0.5
OpenADR
Network Module
Portal Integration
A10/x10

Polyglot 3x
- Purchased both AmbientWeather and AmbientConsole (neither will connect) - switched to AmbientConsole so everything was connected on L2 network and I could be 100% sure what is happening - below is details:

Under "Dashboard" i'm getting "Current Status" Disconnected

Otherwise:
PG3x Version 3.4.19
Status: Connected
Frontend Version: 3.4.19
IoX Version: 6.0.5   Connected
Uptime: 14 Hour(s) 50 Minute(s) 1 Second(s) 
(c) 2026 UDI

Note: Had Preplexity helping me debug - it and I are at our end on what to try next. I've also uninstalled

AmbientConsole setup summary

I’m trying to get an Ambient Weather console feeding local data into eisy through the AmbientConsole node server in PG3x.

Already documented:

• PG3x version: 3.4.19.

• IoX/eisy version: 6.0.5.

• PG3x status: Connected.

• IoX status: Connected.

Polyglot 3x configuration

• AmbientConsole node server installed and running in PG3x.

• Profile shows Ambient Console.

• User ID field displays the eisy MAC address, which appears normal for this plugin/setup.

• I tested the listener port on eisy/plugin side with 7501, then changed to 7502.

• PG3x remains connected to IoX throughout.

Ambient Weather console configuration

• Console IP: 192.168.1.251.

• eisy IP: 192.168.1.100.

• Console and eisy are on the same LAN.

• Console is configured for Customized upload.

• Console is pointed at the eisy IP and the configured listener port.

• Ambient protocol settings were used as expected for the local console feed.

Packet capture results

I mirrored traffic and filtered for only the Ambient console and eisy conversation.

What I see

• The console opens a TCP connection to eisy on the configured port.

• Example on port 7501:

  • Console 192.168.1.251 sends SYN to eisy 192.168.1.100:7501.

  • eisy responds with RST, ACK.

• Same behavior occurred after switching to port 7502:

  • Console attempts TCP connection to 192.168.1.100:7502.

  • eisy again responds with RST, ACK.

Interpretation

• The LAN path is working; the packets are reaching eisy.

• The connection is being actively rejected by eisy.

• This looks like the service on the eisy side is not accepting the socket, not a console-side Wi-Fi/IP issue.

• Since both ports behave the same way, this does not appear to be a simple bad-port-selection problem.

What I’m looking for help with

At this point I’m trying to determine whether:

• the AmbientConsole node server is not actually binding/listening correctly,

• there is a plugin configuration issue,

• a port conflict or service conflict exists on eisy,

• or the node server needs to be reinstalled/reset.

If you want, I can also turn this into a more concise forum post with bullet points and the packet capture included as a short evidence section.

23 minutes ago, jrcasselman said:

Polyglot 3x configuration

• AmbientConsole node server installed and running in PG3x.

• Profile shows Ambient Console.

• User ID field displays the eisy MAC address, which appears normal for this plugin/setup.

• I tested the listener port on eisy/plugin side with 7501, then changed to 7502.

• PG3x remains connected to IoX throughout.

This information is coming from eisy -> Plugins -> Configuration -> [slot range] -> slot with AmbientConsole installed right?

Are you changing the port number in that "Plugin Configuration" form? If so don't. That is configuring the connection between the plugin and IoX. All current plugins do that automatically. Changing anything there will just break things. In fact, just ignore that whole menu.

The only plugin configuration you do is from PG3x. From the dashboard, click the plugin's Details button. From there, click the Configuration button. From there you can configure the port # and the station name. It should default to port 7501 and the name is just a string you want it to use for the node name.

All plugins also have built in logging facilities. You'll see that option from the plugin's details page. To debug issues with a plugin, you should set the log level to debug, restart the plugin and then examine the log. If you need help, posting the log here or PMing it to the plugin's author is the best way to get support.

I’ve gone through a full remove-and-reinstall cycle and wanted to summarize what I’ve done and what I’m seeing now.

FYI: Just cleared all the logs from EISY (error and normal log). restarted then plugin from Polyglot V3. Also went to it’s debug log page and said it was running.

Then waited to see packet sent from Ambient console to the eisy IP and the reply (image).

Once saw packet,
- Looked at Polyglot 3x - log / debug (nothing)
- Looked at eisy event log, nothing of value
- Looked at eisy error log - see attached, though doesn’t look like anything.

System / versions

• PG3x: 3.4.19

• IoX / eisy: 6.0.5

• PG3x status: Connected

• IoX status: Connected

What I removed and reinstalled

1. Deleted the AmbientConsole plugin from PG3x.

2. Confirmed the eisy plugin slot list was empty afterward.

3. Reinstalled AmbientConsole from PG3x purchases.

4. Selected slot 1 during reinstall.

5. Verified that PG3x put AmbientConsole back into slot 1 on eisy.

Current AmbientConsole configuration

In PG3x, under the AmbientConsole plugin configuration:

• shortPoll = 60

• longPoll = 600

• Port = 7501

• Station Name = blank

These are the default values, and I have left them unchanged.

Ambient Weather console configuration

Ambient console is configured on the same LAN as eisy.

• Ambient console IP: 192.168.1.251

• eisy IP: 192.168.1.100

• Console is pointed to the eisy IP

• Custom server/path configured for the AmbientConsole setup

• I also tested a second port after the first one failed, but behavior was unchanged

What I’m seeing in Wireshark

I mirrored the traffic and filtered only the Ambient console and eisy conversation.

What I see:

• Console initiates TCP to eisy on the configured port.

• eisy responds immediately with RST, ACK.

• I saw this behavior on both port 7501 and port 7502.

• I do not see the session proceeding to the point where actual weather payload data is accepted.

What I’m seeing in logs

• AmbientConsole debug log shows no obvious errors.

• eisy logs show normal IoX/system traffic and plugin framework activity, but nothing that looks like a successful Ambient weather ingest.

• I do not see an error in the AmbientConsole log that explains the TCP reset.

What this suggests

At this point the LAN path is clearly working because the console reaches eisy and eisy responds. The issue appears to be on the eisy/plugin side where the TCP session is being refused before the weather data is accepted.

ISY Error Log.v6.0.5__Fri 2026.06.19 12.58.31 PM.txt

The plugin is running (or should be) on the eisy and the eisy's ip address in your case is 192.168.1.100 and will always be active when eisy powered up and running.

From your screen shot of PG3x, the plugin is not running (status: Disconnected). The question that needs to be answered is why didn't the plugin start?

You said you level the Station Name blank. What you enter here is what the node in the IoX node list will be named. By leaving it blank, the name will default to "unknown".

Try this:

1. With the log level set to debug, like what your screenshot is showing

2. Restart (or Start) the plugin.

3. The log file should start populating

If the log doesn't start populating, that means PG3x was unable to start the plugin. The reason should show up in the PG3x log file so go click the "Log" button at the upper right of the screen. Depending on what plugins are running, this log may be capturing a lot of messages, so click the autoscroll to turn that off and then scroll back and look for error messages related to AmbientConsole.

When the plugin is running, it will start a server listening on port 7501. When the plugin is not running, there's nothing listening on port 7501 so the connection is rejected.