Document Gladacres diagnostic loading investigation and remaining uptime delay

ATOM-DEVICES-GUIDE.md

@@ -88,4 +88,10 @@ Original page Copy: /tmp/atom-devices-before.json. Final table draft: /tmp/atom-
 | R Reimer Farms | `rrf` | `water` — Water |
 | Simon Loewen | `simon_loewen` | `main` — Main |
 | Swalwell Church | `swalwell_church` | `controller` — Controller |
-| Sweet Grass | `sweetgrass` | `main` — Main PC |
+| Sweet Grass | `sweetgrass` | `main` — Main PC |
+
+## Gladacres delayed readings investigation — October 21, 2026
+
+October 21 Gladacres check: all 30 diagnostic/maintenance entries are enabled and Terminal is configured as {}. The native Device Status page and Atom dashboard both populated readings without any saved configuration change (CPU 63.7 °C, HMI 1012 observed). Most diagnostics poll every 600 seconds; uptime is configured for 10 seconds but was about 2–5 minutes old during checks. Initial blank register-table values were not proof of a complete outage. Delayed uptime reporting remains unexplained; no agent/connection cause or repair was established. No commands, resets, updates, reboots, service restarts or log uploads. See GLADACRES-GUIDE.md.
+
+Cloud guide: https://chatgpt.com/space/page_31b800d9541c8191b7eddf6ee2fac319

GLADACRES-GUIDE.md

@@ -0,0 +1,27 @@
+# Gladacres production diagnostics
+
+Verified October 21, 2026. Site https://www.atomhmi.com/site_gladacres/; site ID gladacres. Device barn / Barn. Device Status page: /site_gladacres/page_device_status. Cross-site dashboard: /site_atom/page_devices, Gladacres / Barn (barn).
+
+## Investigation: diagnostic readings initially blank
+
+The user reported registers not loading. The Atom dashboard initially showed stale uptime and missing CPU/IP readings. Manage Registers initially displayed blank values for all 30 rpi_ entries despite Enabled Yes. This initial table was not reliable evidence that the device had no values: the native Device Status page subsequently populated CPU, disk, memory, IP, firmware, HMI and Node readings, and the cross-site dashboard subsequently populated too, without any saved configuration changes.
+
+Observed Device Status readings included 1500 MHz CPU clock, 63.7 °C CPU temperature, 31% CPU usage, 7903 MB disk used / 101005 MB available / 8%, 374 MB memory used / 1492 MB available, HMI 1012 and Node 20.2. Local/tunnel IP fields also populated; addresses are omitted from this guide. Uptime was about 227 days. These are dated snapshots, not limits or guaranteed current values. The dashboard's uptime timestamp was roughly 2–5 minutes old across observations, correctly exceeding its 120-second Recent threshold. No persistent complete diagnostic outage was reproduced, but the reason for delayed uptime reporting was not established.
+
+## Verified configuration
+
+Barn has calculator, modbus_localhost and terminal sources. Inspected Terminal: ID terminal, type Terminal, configuration {}. Closed without saving. All 29 standard diagnostic/maintenance definitions plus rpi_upload_logs exist and are enabled. Read the full current definitions using native Advanced import validation with [] and Delete Unused OFF; insert/update/delete were all empty, and the audit dialog was closed without Submit.
+
+- rpi_uptime: awk '{print $1}' /proc/uptime; ON_CHANGE, 10 seconds.
+- rpi_service_uptime: existing systemctl/date age command; ON_CHANGE, 10 seconds.
+- rpi_atom_hmi_version and rpi_model: ON_CHANGE, 60 seconds.
+- CPU, disk, memory, firmware, IP and throttling/voltage readings: ON_CHANGE, 600 seconds. Node version retains its existing 3600-second interval.
+- rpi_atom_hmi_update, rpi_reboot, rpi_restart_service and rpi_upload_logs: DISABLED automatic polling. None were triggered. Upload Logs sends data externally and must not be used as a casual read-only diagnostic action.
+
+Several older definitions include address.priority:0. Existing disk commands select /dev/root, and model detection uses /proc/cpuinfo Hardware. Despite those older forms, this inspection observed working disk/model readings; they were not replaced speculatively. The dashboard backup's Gladacres expressions consistently target gladacres:barn:rpi_*; the working dashboard readback supports that mapping. No wrong-device binding was demonstrated.
+
+## Outcome and remaining question
+
+Read-only investigation only: no page/register/slave/recording settings saved, no update/restart/reboot, no uploaded logs and no PLC writes. Readings appeared on both native and cross-site pages during the investigation. Slow first-load population and 600-second metric polling should be distinguished from absent definitions. The 2–5 minute age seen on uptime remains unexplained despite a configured 10-second interval; do not label a connection/agent/network cause as proven. If it persists, a device-side polling/publishing/log investigation is the next step; no such logs were collected here.
+
+Local evidence: /tmp/gladacres-register-definitions-before.json (current definition audit), /tmp/gladacres-device-status-readings.jpg, /tmp/gladacres-dashboard-loaded.jpg. These are local artifacts, not synchronized through Git. Do not commit raw network addresses, logs or credentials.

HANDOFF.md

@@ -2,6 +2,12 @@
 
 Last updated: 2026-10-21 (America/Edmonton)
 
+## Gladacres read-only diagnostics check — October 21, 2026
+
+October 21 Gladacres check: all 30 diagnostic/maintenance entries are enabled and Terminal is configured as {}. The native Device Status page and Atom dashboard both populated readings without any saved configuration change (CPU 63.7 °C, HMI 1012 observed). Most diagnostics poll every 600 seconds; uptime is configured for 10 seconds but was about 2–5 minutes old during checks. Initial blank register-table values were not proof of a complete outage. Delayed uptime reporting remains unexplained; no agent/connection cause or repair was established. No commands, resets, updates, reboots, service restarts or log uploads. See GLADACRES-GUIDE.md.
+
+Cloud guide: https://chatgpt.com/space/page_31b800d9541c8191b7eddf6ee2fac319. Local definition audit and screenshots are listed there. No site changes were saved; the current dashboard remains 31 sites / 33 devices and retired sites remain retired.
+
 ## Demo and Westland retirement cleanup — October 21, 2026
 
 Current status — October 21, 2026: the user deleted and retired Demo (site_demo) and Westland (site_westland). Removed their five dashboard rows: Demo/demo, Demo/main, Demo/unknown, Westland/test_trailer and Westland/trailer_1. The saved dashboard now has 33 non-Global devices across the 31 accessible sites (30 with devices; Atom has Global scope only). The current Select Site catalog independently showed 31 sites and neither retired site. Do not recreate either site, its devices, diagnostic registers or Terminal sources unless the user explicitly requests reinstatement.

PROJECT.md

@@ -70,3 +70,9 @@ October 21 resolution: user chose to remove the unverified Time Since Start and
 ## Retired sites — October 21, 2026
 
 Current status — October 21, 2026: the user deleted and retired Demo (site_demo) and Westland (site_westland). Removed their five dashboard rows: Demo/demo, Demo/main, Demo/unknown, Westland/test_trailer and Westland/trailer_1. The saved dashboard now has 33 non-Global devices across the 31 accessible sites (30 with devices; Atom has Global scope only). The current Select Site catalog independently showed 31 sites and neither retired site. Do not recreate either site, its devices, diagnostic registers or Terminal sources unless the user explicitly requests reinstatement.
+
+## Gladacres delayed readings investigation — October 21, 2026
+
+October 21 Gladacres check: all 30 diagnostic/maintenance entries are enabled and Terminal is configured as {}. The native Device Status page and Atom dashboard both populated readings without any saved configuration change (CPU 63.7 °C, HMI 1012 observed). Most diagnostics poll every 600 seconds; uptime is configured for 10 seconds but was about 2–5 minutes old during checks. Initial blank register-table values were not proof of a complete outage. Delayed uptime reporting remains unexplained; no agent/connection cause or repair was established. No commands, resets, updates, reboots, service restarts or log uploads. See GLADACRES-GUIDE.md.
+
+Cloud guide: https://chatgpt.com/space/page_31b800d9541c8191b7eddf6ee2fac319

cloud-knowledge-base.json

@@ -8,6 +8,7 @@
     "KAV-GUIDE.md": "page_d9313668d27c81919b7c480852c0c082",
     "LAZY-B-GUIDE.md": "page_de033ca7a7b881918b94f89dddea9820",
     "LONE-PINE-GUIDE.md": "page_814209734aa88191bede6b68a663098e",
-    "SWEET-GRASS-GUIDE.md": "page_c260b18f6fc08191b2f64da8e5b97182"
+    "SWEET-GRASS-GUIDE.md": "page_c260b18f6fc08191b2f64da8e5b97182",
+    "GLADACRES-GUIDE.md": "page_31b800d9541c8191b7eddf6ee2fac319"
   }
 }