Auto/atom-hmi-ui-chatgpt
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record user-confirmed alarm log database migration

Browse Source
This commit is contained in:
snkbyte
2026-10-21 19:29:40 +00:00
parent a54a5cc4e8
commit 7e5e6f9f66
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HANDOFF.md
+1 -1
View File
@@ -56,4 +56,4 @@ Use Atom GIT to open Auto/atom-hmi-ui-chatgpt on master. Read AGENTS.md, PROJECT
### Alarm history lookup — October 21, 2026
User requested checking whether any Bin G alarm previously occurred. Opened the alarm icon → Alarm History at https://www.atomhmi.com/site_sweetgrass/alarm_history. Requested Last 30 Days (September 22–October 21, 2026), then freshly reloaded and requested October 21, and finally Yesterday (October 20). Every attempt remained on Loading... without a history table, records, or an explicit empty-result message. No browser warning/error logs were captured. Occurrence, timestamps and retention therefore remain unverified; this is not evidence of no prior Bin G alarms. No acknowledgement, reset, alarm edits, register writes or page saves performed. Next: retry when history retrieval works, search Bin G / ALM-436 / Codesys Bin G Hi-Hi identifiers, and record the returned range and timestamps.
User requested checking whether any Bin G alarm previously occurred. Opened the alarm icon → Alarm History at https://www.atomhmi.com/site_sweetgrass/alarm_history. Requested Last 30 Days (September 22–October 21, 2026), then freshly reloaded and requested October 21, and finally Yesterday (October 20). Every attempt remained on Loading... without a history table, records, or an explicit empty-result message. No browser warning/error logs were captured. Occurrence, timestamps and retention therefore remain unverified; this is not evidence of no prior Bin G alarms. No acknowledgement, reset, alarm edits, register writes or page saves performed. User-confirmed update on October 21, 2026: Atom HMI was just updated and alarm logs moved to a new database; previous history is no longer available. This supersedes the earlier plan to retry for pre-migration records. Historical Bin G occurrences cannot be determined from the current database. The migration explains unavailable prior history, but the cause of the observed Loading... UI was not independently established. The intended Bin G enable/disable alarm path remains unresolved; determine it from current configuration or user/PLC confirmation.
SWEET-GRASS-GUIDE.md
+1 -1
View File
@@ -85,4 +85,4 @@ Asked whether the intended control is the Codesys level Hi-Hi alarm or the exist
### Alarm history lookup — October 21, 2026
User requested checking whether any Bin G alarm previously occurred. Opened the alarm icon → Alarm History at https://www.atomhmi.com/site_sweetgrass/alarm_history. Requested Last 30 Days (September 22–October 21, 2026), then freshly reloaded and requested October 21, and finally Yesterday (October 20). Every attempt remained on Loading... without a history table, records, or an explicit empty-result message. No browser warning/error logs were captured. Occurrence, timestamps and retention therefore remain unverified; this is not evidence of no prior Bin G alarms. No acknowledgement, reset, alarm edits, register writes or page saves performed. Next: retry when history retrieval works, search Bin G / ALM-436 / Codesys Bin G Hi-Hi identifiers, and record the returned range and timestamps.
User requested checking whether any Bin G alarm previously occurred. Opened the alarm icon → Alarm History at https://www.atomhmi.com/site_sweetgrass/alarm_history. Requested Last 30 Days (September 22–October 21, 2026), then freshly reloaded and requested October 21, and finally Yesterday (October 20). Every attempt remained on Loading... without a history table, records, or an explicit empty-result message. No browser warning/error logs were captured. Occurrence, timestamps and retention therefore remain unverified; this is not evidence of no prior Bin G alarms. No acknowledgement, reset, alarm edits, register writes or page saves performed. User-confirmed update on October 21, 2026: Atom HMI was just updated and alarm logs moved to a new database; previous history is no longer available. This supersedes the earlier plan to retry for pre-migration records. Historical Bin G occurrences cannot be determined from the current database. The migration explains unavailable prior history, but the cause of the observed Loading... UI was not independently established. The intended Bin G enable/disable alarm path remains unresolved; determine it from current configuration or user/PLC confirmation.