eISY r2, firmware 5.9.1_18. Ticket #28916 open since Friday, awaiting agent reply.

Symptoms:

- REST API on port 8080 returns HTTP 200 with XML, but device on-levels are all zero

- UD Mobile can see device list but errors when querying individual devices

- Web UI on port 8443 returns 404 at root, /ui prompts for auth but shows empty device templates (no ST, OL, or RR values) even with PLM connected

- Debug log shows repeated "failed connecting to udx" — cloud portal never reconnects

- ping my.isy.io: 100% packet loss. ping 8.8.8.8: works fine

What I've tried:

- Confirmed eISY is reachable on LAN (SSH works, ports 8080 and 8443 open)

- Restarted ISY service (came back up at 16:07 on 2/19, same symptoms)

- Checked pfSense firewall — no blocked traffic to/from 10.227.0.241

- curl to my.isy.io:443 succeeds, but the ISY service itself can't reach UDX

- SYSOUT.LOG shows normal startup sequence including "Starting the Portal Service" and "Ready to Run Programs" but portal never actually connects

The ISY process is alive and knows about all my Insteon nodes, but it can't talk to the cloud or return live device status through REST. It's been like this since 2/19 around 13:17 EST. Nothing changed on my end — was working fine that morning.

Anyone else seeing this on 5.9.1_18? Any suggestions welcome. Thanks.

Are you sure it didn't launch an update? Is it still showing as 5.9.1_18 in the /var/isy/FILES/WEB/sysconfig.txt file?