jrcasselman

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 summaryI’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 configurationAmbientConsole 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 configurationConsole 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 resultsI mirrored traffic and filtered for only the Ambient console and eisy conversation. What I seeThe 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. InterpretationThe 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 withAt 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.