itelescope/state/NOTES.md
Laurence f946361149 Automation recon: portal endpoints, ACP control servers, live status
Records verified findings from a credentialed read-only recon of the
iTelescope portal (2026-07-18) in state/NOTES.md: the WebForms login flow,
the /DataService.svc JSON endpoints (GetAccountStatus, GetMyAvailablePlans,
ApplyPromoCode), the per-telescope ACP web servers behind HTTP auth
(tNN.itelescope.online / tNN.itelescope.net:80NN, confirmed on T33), the
Planner redirect to lookup.itelescope.online, and the per-site weather URLs.
Credentials themselves stay outside the repo.

state/TODO.md gains the next automation steps (map ACP endpoints, explore
the new planner, enumerate more DataService methods) and a campaign-impact
note: most Chile scopes plus several others are currently offline, including
recommended T71 and T73, so near-term work should target T33/T8/T32/T59 at
Siding Spring and status must be re-checked before any booking.
2026-07-18 21:55:52 +01:00

2.2 KiB

Notes

Working notes, gotchas, environment quirks, and dead ends to avoid. Free form. The point is to save a future session from rediscovering something the hard way.

  • Refresh the specs snapshot with: curl -sL "https://docs.google.com/spreadsheets/d/1jZWkkjewOuyNC9YzQ8y2d0pO1e4T7EBeysmQMPBVSOk/export?format=csv" -o data/itelescope-telescopes.csv
  • The CSV has multi-line cells (quoted); line count is not row count. Telescope rows start T<number>,; observatory header rows have an empty first column.
  • Sensors are 16-bit ADC unless noted (T20's ASI2400C is 14-bit).
  • Free scopes (30 min/day): T68 (Utah), T33 (Siding Spring).
  • Minimum elevation limits come from the support article, not the sheet.

Automation recon (2026-07-18, all verified live)

Credentials live OUTSIDE this repo (local claudetemp, never commit them).

  • go.itelescope.net is ASP.NET WebForms. Login: GET /login.aspx, POST UsernameTextBox/PasswordTextBox plus __VIEWSTATE, __VIEWSTATEGENERATOR, __EVENTVALIDATION, LoginButton=Login; session cookie then works everywhere.
  • JSON service at /DataService.svc (session-cookie auth): GetAccountStatus (balance, plan, renewal), GetMyAvailablePlans (per-plan, per-scope AccessDiscount), ApplyPromoCode (POST). More methods likely; enumerate from inline $.ajax calls on each page (Scripts/Common.js has none).
  • Home page /default.aspx carries live network status text (per-scope offline/online reasons) plus points balance: cheap to poll.
  • Reservation/Overview.aspx links every telescope's own control server: https://tNN.itelescope.online/ or http://tNN.itelescope.net:80NN/. These are ACP web servers behind HTTP auth accepting the same iTelescope credentials (verified read-only on T33: index.asp is a TiddlyWiki info page, min elevation 20 degrees, 900 s max exposure). Session control and plan submission happen here; ACP endpoint mapping is the next step.
  • Reservation/Planner.aspx now redirects to https://lookup.itelescope.online (new planning tool, not yet explored).
  • Weather per site: Weather/Weather.aspx?site=UDRO|SSO|DSC|SRO|AC|EYE.
  • Account: Plan-40 (GBP 32.00 per 28 days), renewal 12 Aug 2026, subscribed since Apr 2019, balance 2,638 points at recon time.