Welcome to seevar Discussions!

[edjuh]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[ldorogi]

So, now I know, from @edjuh here is the discussions section :-)

I'm from Hungary, observing variable stars visually longer time, but not really regularly. I was always wondering to have some automated solution for making photometry wile to take all these object photos, darks and flats and make aperture photometry was a bit terrible for me, especially from time side. I own a Celestron NexStar 6SE scope and 2 binoculars from Celestron (12x60 and 20x80). When I saw this project on AAVSO forum after a day I immediately purchased a RasPi 5 and Seestar 30 Pro as I see big potential in this project. Most people buy Seestar only for taking nice photos which is OK, but there is much bigger science potential in it.

By profession I am a software developer but in total different branch (ERP based on OpenEdge, formerly called Progress), so Python is relatively new for me but I will try to learn it as I will get some free time for that :-). Therefore please forgive me if I ask stupid questions because of my missing experience, but my dream is one day to become a real contributor to this project.

[edjuh]

Jonapot kivanok .... immediately followed by ... nem te dom Magyar.

I am Dutch (Haarlem), used to work in IT for 40 years, as a Linux Sys-Admin. Started in 1973 with a 6 cm 1000 mm, followed by a F5 refractor on a EQ3, first EQ6 in the Netherlands with a C8, and now 2 x S30-pro's and AM3/Askar 71F, plus some binoculars.

When I was young I was inspired by PG Meesters / someone called Caldwell / Piet Koning ... A friend got his degree on a Variabele star project, and while visiting AstroKamps I got into variabeles and meteors. Also I do a lot of outreach events.

My experience with programming, is getting developer stuff running. Not much experience with GitHub. My main strength is setting up and knowing projects, and where they fail ;) And indeed, Seestar is nice, but can and should be used for more serious stuff.

[gasilvis]

Greetings,
I've just started my SeeVar adventure. My Seestar S50 is uptodate and I have followed the instructions in the Install.md to load a RPi 4. So far, so good!

I am a member of the AAVSO and have worked as a volunteer software engineer for the AAVSO for the last 13 years. I work as a maintainer for VPhot and am part of the AAVSOnet team that manages 9 telescopes around the world. I had a fire disaster in my own telescope dome in March and lost my 12" scope and everything near by. So for now I'm going to focus on making my Seestar a useful science instrument.

I need to read through the doc and look at some code before I begin. I'll follow Idorogi's path of running some simulations in house and then venture outside for first light.

I'll keep you all informed as I know I'm going to have questions!

Cheers,
George

[edjuh]

Hi George.

I feel you have a Dutch background, funny, many 'Dutchies' in AAVSO.
Welcome aboard, let me know if you find something. I think I read about that fire disaster, that must be devestating to watch.

Grtz ,
Ed

[gasilvis]

Now that my dome and big scope are burned up I'm switching to a S50 and the seevar application on the RPi.

Haven't some problems getting started....
Scope just sits there, doesn't appear to build a target list?
Hoping for advice.

Here's the setup:
sgeo@seevar:/seevar $ uname -a
Linux seevar 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1 (2026-03-11) aarch64 GNU/Linux
sgeo@seevar:/seevar $ head -5 ~/seevar/bootstrap.sh
#!/bin/bash

=============================================================================

Filename: bootstrap.sh

Version: 1.6.0

Objective: Install SeeVar on fresh Debian Bookworm (Raspberry Pi).

sgeo@seevar:~/seevar $ /seevar/.venv/bin/python3 --version
Python 3.13.5
sgeo@seevar:/seevar $ /seevar/.venv/bin/python3 --version
Python 3.13.5
sgeo@seevar:/seevar $ tail -50 /seevar/logs/orchestrator.log
22:03:11 [INFO] seevar.fsm — 🧠 FSM Initialized in state: IDLE
22:03:11 [INFO] seevar.pilot — DiamondSequence endpoint: 192.168.1.233:32323 (explicit argument)
22:03:11 [INFO] seevar.orchestrator — 🔭 Orchestrator starting — SeeVar Federation v2.0.0 (FSM-Governed) | scope=sgeoS50 | mission=tonights_plan.json
22:03:11 [INFO] seevar.orchestrator — ♻️ Operator reset requested from dashboard.
22:03:11 [INFO] seevar.orchestrator — STATE -> IDLE | Operator reset. Awaiting next cycle.
22:13:15 [INFO] seevar.orchestrator — Weather GO: CLEAR ✨ (age: 10min)
22:13:15 [INFO] seevar.orchestrator — STATE -> PREFLIGHT | Night sky confirmed (or forced by Simulation).
22:13:15 [INFO] seevar.orchestrator — 🛫 PREFLIGHT sequence initiated.
22:13:15 [INFO] seevar.orchestrator — [A2] Safety gate — securing zero-state
22:13:15 [INFO] seevar.neutralizer — enforce_zero_state: Alpaca REST on 192.168.1.233:32323
22:13:20 [ERROR] seevar.neutralizer — Alpaca management unreachable: HTTPConnectionPool(host='192.168.1.233', port=32323): Max retries exceeded with url: /management/apiversions (Caused by ConnectTimeoutError(<HTTPConnection(host='192.168.1.233', port=32323) at 0x7f83f25950>, 'Connection to 192.168.1.233 timed out. (connect timeout=5)'))
22:13:20 [INFO] seevar.orchestrator — [A2] ⚠️ zero-state unconfirmed — continuing to session init
22:13:20 [INFO] seevar.orchestrator — [A3] Session init baseline
22:13:25 [INFO] seevar.orchestrator — [A3] Telemetry — TelemetryBlock parse error: Alpaca management unreachable: HTTPConnectionPool(host='192.168.1.233', port=32323): Max retries exceeded with url: /management/apiversions (Caused by ConnectTimeoutError(<HTTPConnection(host='192.168.1.233', port=32323) at 0x7f80100c30>, 'Connection to 192.168.1.233 timed out. (connect timeout=5)'))
22:13:25 [INFO] seevar.orchestrator — [A3] 🛑 VETO at preflight: Alpaca management unreachable: HTTPConnectionPool(host='192.168.1.233', port=32323): Max retries exceeded with url: /management/apiversions (Caused by ConnectTimeoutError(<HTTPConnection(host='192.168.1.233', port=32323) at 0x7f80100c30>, 'Connection to 192.168.1.233 timed out. (connect timeout=5)'))
22:13:25 [INFO] seevar.orchestrator — STATE -> ABORTED | Preflight veto: Alpaca management unreachable: HTTPConnectionPool(host='192.168.1.233', port=32323): Max retries exceeded with url: /management/apiversions (Caused by ConnectTimeoutError(<HTTPConnection(host='192.168.1.233', port=32323) at 0x7f80100c30>, 'Connection to 192.168.1.233 timed out. (connect timeout=5)'))
13:26:10 [INFO] seevar.pilot — DiamondSequence endpoint: 192.168.1.233:32323 (config.scope01.ip)
13:26:10 [INFO] seevar.fsm — 🧠 FSM Initialized in state: IDLE
13:26:10 [INFO] seevar.pilot — DiamondSequence endpoint: 192.168.1.233:32323 (explicit argument)
13:26:10 [INFO] seevar.orchestrator — 🔭 Orchestrator starting — SeeVar Federation v2.0.0 (FSM-Governed) | scope=sgeoS50 | mission=tonights_plan.json
21:31:27 [WARNING] seevar.orchestrator — Weather data is 56h old — proceeding with caution
21:31:27 [INFO] seevar.orchestrator — Weather GO: CLEAR ✨ (age: 3365min)
21:31:27 [INFO] seevar.orchestrator — STATE -> PREFLIGHT | Night sky confirmed (or forced by Simulation).
21:31:27 [INFO] seevar.orchestrator — 🛫 PREFLIGHT sequence initiated.
21:31:27 [INFO] seevar.orchestrator — [A2] Safety gate — securing zero-state
21:31:27 [INFO] seevar.neutralizer — enforce_zero_state: Alpaca REST on 192.168.1.233:32323
21:31:32 [ERROR] seevar.neutralizer — Alpaca management unreachable: HTTPConnectionPool(host='192.168.1.233', port=32323): Max retries exceeded with url: /management/apiversions (Caused by ConnectTimeoutError(<HTTPConnection(host='192.168.1.233', port=32323) at 0x7fa86c5e10>, 'Connection to 192.168.1.233 timed out. (connect timeout=5)'))
21:31:32 [INFO] seevar.orchestrator — [A2] ⚠️ zero-state unconfirmed — continuing to session init
21:31:32 [INFO] seevar.orchestrator — [A3] Session init baseline
21:31:37 [INFO] seevar.orchestrator — [A3] Telemetry — TelemetryBlock parse error: Alpaca management unreachable: HTTPConnectionPool(host='192.168.1.233', port=32323): Max retries exceeded with url: /management/apiversions (Caused by ConnectTimeoutError(<HTTPConnection(host='192.168.1.233', port=32323) at 0x7fa86c5480>, 'Connection to 192.168.1.233 timed out. (connect timeout=5)'))
21:31:37 [INFO] seevar.orchestrator — [A3] 🛑 VETO at preflight: Alpaca management unreachable: HTTPConnectionPool(host='192.168.1.233', port=32323): Max retries exceeded with url: /management/apiversions (Caused by ConnectTimeoutError(<HTTPConnection(host='192.168.1.233', port=32323) at 0x7fa86c5480>, 'Connection to 192.168.1.233 timed out. (connect timeout=5)'))
21:31:37 [INFO] seevar.orchestrator — STATE -> ABORTED | Preflight veto: Alpaca management unreachable: HTTPConnectionPool(host='192.168.1.233', port=32323): Max retries exceeded with url: /management/apiversions (Caused by ConnectTimeoutError(<HTTPConnection(host='192.168.1.233', port=32323) at 0x7fa86c5480>, 'Connection to 192.168.1.233 timed out. (connect timeout=5)'))
13:16:28 [INFO] seevar.pilot — DiamondSequence endpoint: 192.168.1.233:32323 (config.scope01.ip)
13:16:28 [INFO] seevar.fsm — 🧠 FSM Initialized in state: IDLE
13:16:28 [INFO] seevar.pilot — DiamondSequence endpoint: 192.168.1.233:32323 (explicit argument)
13:16:28 [INFO] seevar.orchestrator — 🔭 Orchestrator starting — SeeVar Federation v2.0.0 (FSM-Governed) | scope=sgeoS50 | mission=tonights_plan.json
21:52:40 [INFO] seevar.orchestrator — Weather GO: CLEAR ✨ (age: 246min)
21:52:40 [INFO] seevar.orchestrator — STATE -> PREFLIGHT | Night sky confirmed (or forced by Simulation).
21:52:41 [INFO] seevar.orchestrator — 🛫 PREFLIGHT sequence initiated.
21:52:41 [INFO] seevar.orchestrator — 🛑 Nightly plan stale before hardware init — planner timer must refresh it
21:52:41 [INFO] seevar.orchestrator — STATE -> ABORTED | Nightly plan stale; run seevar-planner.service
19:38:52 [INFO] seevar.pilot — DiamondSequence endpoint: 192.168.1.233:32323 (config.scope01.ip)
19:38:52 [INFO] seevar.fsm — 🧠 FSM Initialized in state: IDLE
19:38:52 [INFO] seevar.pilot — DiamondSequence endpoint: 192.168.1.233:32323 (explicit argument)
19:38:52 [INFO] seevar.orchestrator — 🔭 Orchestrator starting — SeeVar Federation v2.0.0 (FSM-Governed) | scope=sgeoS50 | mission=tonights_plan.json
21:33:55 [INFO] seevar.orchestrator — Weather GO: CLEAR ✨ (age: 1min)
21:33:55 [INFO] seevar.orchestrator — STATE -> PREFLIGHT | Night sky confirmed (or forced by Simulation).
21:33:55 [INFO] seevar.orchestrator — 🛫 PREFLIGHT sequence initiated.
21:33:55 [INFO] seevar.orchestrator — 🛑 Nightly plan stale before hardware init — planner timer must refresh it
21:33:55 [INFO] seevar.orchestrator — STATE -> ABORTED | Nightly plan stale; run seevar-planner.service
sgeo@seevar:/seevar $
The config.toml is :

=============================================================================

Filename: config.toml.example

Version: 2.0.0

Objective: Template for SeeVar configuration. bootstrap.sh copies this to

config.toml and patches it interactively. You can also edit

config.toml directly after installation.

Required sections : [location], [aavso], [planner], [storage], [[seestars]]

Optional sections : [weather], [notifications], [network]

Leave optional string fields empty ("") to disable them.

=============================================================================

-----------------------------------------------------------------------------

LOCATION — required

These coordinates are the GPS fallback when the hardware GPS is unavailable.

maidenhead is also the home-detection trigger: if maidenhead matches

[network] home_grid the pipeline knows it is at home and expects a NAS.

-----------------------------------------------------------------------------

[location]

29 Summer St, Arlington

#lat = 42.419341
#lon = -71.1539776
#elevation = 66.0
#maidenhead = "FN42kk"
bortle = 7 # 1 = pristine dark sky, 9 = city centre
horizon_limit = 50.0 # minimum target altitude in degrees
moon_avoidance = 30.0 # minimum angular distance from moon in degrees

194 Clipper Rd, Bourne

lat = 41.71
longitude = -70.63379427676018
elevation = 3.0
maidenhead = "FN41qr"

Manual obstruction boxes are always applied as safety floors, even when a

scanned data/horizon_mask.json profile exists. Use these for houses, roofs,

trees, balconies, or any sector where an experimental scan is not trustworthy.

[[location.obstructions]]

label = "west_house_roof"

az_start = 225.0

az_end = 355.0 # wrap-around sectors are allowed, e.g. 330 -> 20

min_alt = 70.0

-----------------------------------------------------------------------------

HORIZON — optional

profile_enabled : true uses the configured profile_path when present.

profile_path : relative paths are resolved from the SeeVar repository root.

profile_required: true fails planning if the profile is missing or unreadable.

safety_floor_deg: hard minimum altitude before manual obstructions are applied.

[location].horizon_limit is also honored as a safety floor.

-----------------------------------------------------------------------------

lon = -70.63
[horizon]
profile_enabled = true
profile_path = "data/horizon_mask.json"
profile_required = false
safety_floor_deg = 15.0

-----------------------------------------------------------------------------

AAVSO — required

observer_code : your official AAVSO observer code (e.g. REDA)

webobs_session_cookie : optional — authenticated apps.aavso.org session cookie

for live WebObs submission automation.

Preferred format:

"app2_session=...; canary=false"

webobs_token : optional legacy fallback — if set and webobs_session_cookie

is empty, SeeVar treats this as the raw app2_session value.

target_tool_api_key : optional — needed for live AAVSO Target Tool API access.

This is separate from WebObs login/cookie submission.

target_key : legacy alias for target_tool_api_key.

The bundled seed catalog works without these keys.

-----------------------------------------------------------------------------

[aavso]
observer_code = "SGEO"
webobs_session_cookie = ""
webobs_token = ""
auto_submit = true
sanity_enabled = true
max_mag_error = 0.5
sanity_margin_mag = 1.0
peer_sanity_enabled = true
peer_sanity_margin_mag = 0.35
peer_sanity_window_days = 120
peer_sanity_min_obs = 5
max_peak_adu = 58000.0
target_tool_api_key = ""
target_key = ""

-----------------------------------------------------------------------------

BAA — optional

Used only for the BAA-modified AAVSO Extended export variant.

observer_code can differ from your AAVSO observer code.

Leave empty to let SeeVar derive sane defaults from [location] and [[seestars]].

-----------------------------------------------------------------------------

[baa]
observer_code = ""
telescope = ""
camera = ""

-----------------------------------------------------------------------------

PLANNER — required

sun_altitude_limit : astronomical darkness threshold in degrees (-18.0)

simulation_mode : true = run without hardware (development only)

Always false for real observations.

-----------------------------------------------------------------------------

[planner]
sun_altitude_limit = -12.0
cadence_divisor = 20 # period / cadence_divisor = observation interval (1/20th rule)
cadence_fallback_days = 3.0 # fallback cadence (days) for targets without a known period
fleet_mode = "single" # single = one shared queue, split = divide when 2+ scopes are active, auto = choose by active scope count
simulation_mode = false
secondary_catalogs = [] # optional filler imaging catalogs: ["messier", "caldwell", "sharpless", "herschel400"]
secondary_max_targets = 0 # 0 = no cap once enabled
secondary_duration_sec = 900 # per-object imaging block for secondary catalogs
secondary_after_photometry = true # true = run filler imaging only after variable postflight/reporting
secondary_output_dir = "" # optional; default is [storage].primary_dir/secondary_catalogs

-----------------------------------------------------------------------------

FLIGHT — optional

A7 pointing verification must fail fast. If it cannot solve a 2s verification

frame in roughly half a minute, the target is probably clouded, blocked, or

off-field; move on instead of burning the night.

For quick pre-alignment before a session, run:

.venv/bin/python dev/tools/telescope/prealign_pointing.py --points 3 --exposure-sec 5

-----------------------------------------------------------------------------

[flight]
alpaca_port = 32323
alpaca_client_id = 42
gain = 80
settle_seconds = 8
pointing_verify_exposure_sec = 2.0
pointing_plate_solve_timeout_sec = 35
pointing_plate_solve_cpulimit_sec = 30
pointing_plate_solve_radius_deg = 5.0
pointing_plate_solve_downsample = 1
pointing_tolerance_arcmin = 12.0
pointing_max_retries = 2
pointing_gross_error_arcmin = 180.0
pointing_gross_max_retries = 1
pointing_accept_target_in_frame = true
pointing_edge_margin_px = 250
verify_retention_sets = 40
pointing_model_enabled = true
pointing_model_max_age_hours = 12.0
frame_retry_limit = 0
prealign_before_flight = false
prealign_points = 3
prealign_exposure_sec = 5.0
prealign_timeout_sec = 600
prealign_required = true
prealign_allow_partial = false
prealign_min_alt = 35.0
prealign_max_alt = 82.0
prealign_solve_radius_deg = 20.0
prealign_solve_timeout_sec = 90
prealign_solve_downsample = 2
prealign_wide_fallback = true
prealign_wide_exposure_sec = 5.0
prealign_wide_gain = 0
prealign_wide_solve_radius_deg = 60.0

seestar_alp is a diagnostics/API workbench by default.

Keep production science flight on firmware Alpaca unless this is explicitly enabled.

[seestar_alp]
enabled = false
base_url = "http://127.0.0.1:5555"
mode = "diagnostic" # diagnostic | controlled

-----------------------------------------------------------------------------

STORAGE — required

lifeboat_dir : local fallback when RAID1 / NAS is not available

primary_dir : main archive destination (RAID1 mount or local)

-----------------------------------------------------------------------------

[storage]
lifeboat_dir = "/seevar/data/local_buffer"
primary_dir = "/seevar/data/local_buffer"
target_dir = "/seevar/data"
sequence_dir = "/seevar/data/sequences"
comp_star_dir = "~/seevar/data/comp_stars"

-----------------------------------------------------------------------------

WEATHER — optional

Multi-source: open-meteo + MET Norway/Yr.no + Clear Outside + optional KNMI.

All thresholds are tunable here — no code changes required.

fog_abort = false disables the fog veto entirely (not recommended).

Clouds are science no-go. Rain/fog/thunder/wind are hard aborts.

-----------------------------------------------------------------------------

[weather]
max_precip_mm = 0.5 # mm/hr — rain hard abort
max_wind_kmh = 30.0 # km/h — wind hard abort
max_cloud_low_pct = 30.0 # % — low cloud science no-go
max_cloud_mid_pct = 50.0 # % — mid cloud science no-go
max_cloud_high_pct = 70.0 # % — high cloud science no-go
max_cloud_total_pct = 70.0 # % — total cloud science no-go
max_humidity_pct = 90.0 # % — humidity warning only (HUMID) — dew heater cue
fog_abort = true # bool — any fog reading aborts the session

-----------------------------------------------------------------------------

POSTFLIGHT — optional

Caps plate solving so a bad roof/cloud frame cannot pin the accountant for

hours. Candidate order is stack first, then newest calibrated single frames.

-----------------------------------------------------------------------------

[postflight]
max_plate_solve_candidates = 3
plate_solve_timeout_sec = 90
plate_solve_cpulimit_sec = 75
auto_stage_reports = true
report_mirror_dir = "/mnt/astronas/reports"
auto_park = true
auto_shutdown_scope = false

-----------------------------------------------------------------------------

CALIBRATION — optional

Darks are reusable across equivalent Seestar models, but only for matching

exposure/gain and a nearby camera temperature bin. Tighten this if dark current

mismatch becomes visible; loosen only for emergency beta recovery.

-----------------------------------------------------------------------------

[calibration]
dark_temp_tolerance_c = 4.0

-----------------------------------------------------------------------------

NOTIFICATIONS — optional

Create a Telegram bot via @Botfather to receive session alerts.

Leave both fields empty to disable notifications entirely.

-----------------------------------------------------------------------------

[notifications]
telegram_bot_token = ""
telegram_chat_id = "@gasilvis"

-----------------------------------------------------------------------------

NETWORK — optional

Required only if you have a NAS on your home network.

home_grid must match [location] maidenhead for NAS detection to activate.

If you are at a remote site (maidenhead != home_grid) the NAS is skipped.

-----------------------------------------------------------------------------

[network]
nas_ip = ""
nas_port = 445
home_grid = "IO91WM"

-----------------------------------------------------------------------------

FLEET — required

One [[seestars]] entry per telescope.

model : must match a file in core/hardware/models/ (S30, S30-Pro, S50)

ip : telescope IP address on your local network — set TBD until known

mount : altaz for all current Seestar units

The bootstrap telescope questionnaire fills in the first entry.

Add further telescopes by copying this block.

-----------------------------------------------------------------------------

[[seestars]]
name = "sgeoS50"
model = "S50"
#ip = "192.168.1.190"
ip = "192.168.1.233"
mount = "altaz"

[[seestars]]

name = "Anna"

model = "S30-Pro"

ip = "TBD"

mount = "altaz"

[[seestars]]

name = "Henrietta"

model = "S50"

ip = "TBD"

mount = "altaz"

-----------------------------------------------------------------------------

KNMI — optional but recommended for Netherlands observers

Real 10-minute measured data from the nearest KNMI weather station.

Register for a free API key at: https://developer.dataplatform.knmi.nl/register/

Find your nearest station ID via:

https://api.dataplatform.knmi.nl/edr/v1/collections/10-minute-in-situ-meteorological-observations/locations

-----------------------------------------------------------------------------

[knmi]
edr_api_key = "" # Your personal EDR API key
station_id = "0-20000-0-06240" # Schiphol Airport (nearest to Haarlem)
station_name = "Schiphol" # Human-readable label for logs
okta_limit = 6 # Cloud cover abort threshold (0-9 oktas)
vv_limit = 5000 # Visibility abort threshold (metres)
ww_rain_limit = 50 # Present weather code >= 50 = rain abort
ww_fog_limit = 10 # Present weather code >= 10 = fog warning
[astrometry_net]
api_key = ""
base_url = "https://nova.astrometry.net/api/"
enabled = false

[mission]
max_targets = 0 # 0 = no cap; set to e.g. 5 for short test nights

I've checked out :
git status
On branch codex/private-seestar-alp-control
Your branch is up to date with 'origin/codex/private-seestar-alp-control'.

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: core/preflight/chart_fetcher.py

What newb think have I missed?
Thx,
George
SGEO

[edjuh]

Hi George.
This is too rich as feedback for me.
What I understand, you did do a good installation, but no list/action.
It might very well be, you use 18 degrees sun under horizon, but as we near 21 June, there is no astronomical dark.
Change that to 12 deg or less

now in your config.toml - sun_altitude_limit : astronomical darkness threshold in degrees (-18.0)

Things like KNMI etc, forget that, that is for the Dutch users ;)

Can you confirm you have a tonights_plan.json ? ( in /seevar/data )
Or this vsx_catalog.json or campaign_targets.json ? ( in /seevar/catalogs )

[gasilvis]

I had figured out that sun altitude issue and changed it to -12 to avoid waiting and extra hour for -18.

There is a tonights_plan.json, but the targets list is empty.

Campaign_targets.json exists.

no vsx_catalog.json, though I did get the 900 stars fetched with char_fetcherpy
Note on that. The issue with failed queries is the request timeout, not any throttling. Change that to 30 and you get 98% of the reauests.
That being said, HQ was not pleased with the 900 query load on VSD, though I told them it was one time.
In there future there will be an API key on these requests.

George

[edjuh]

fix config/IP, run planner, then re-test ( short version )

• “no target list” is not the first blocker.
• Log shows Alpaca unreachable at 192.168.1.233:32323.
• Later log shows stale nightly plan: run seevar-planner.service.
• Config paste looks partly template/duplicated: lon and longitude, odd ~~

There is a 'seestars' list, which now reflect my scopes. Do ensure it reflects your telescope(s)
Problem with the list fetching is known. I could put the list on Github, but that kind of beats the AAVSO purpose of providing them.

Thank you for testing btw, it does show a new user should be better guided through the setup.

Which reminds me ... did you install via bootstrap.sh ?

Grtz Ed

[gasilvis]

Making some progress understanding the workflow, but no images yets.

• Do you need to run bootstrap each time you run a session? Each time you edit the config.toml?
• If you abort from the webpage, how do you restart?
  As you mentioned, a guide for new users would help.
  Thx
  George

[edjuh]

Bootstrap.sh is the installer, so no.
config.toml is fixed information.
the abort button is for that specific session, it will restart the next day, if conditions are right.

I feel like you missed the main idea of this project. Fully automated, and little to no human intervention.
It all depends on the weather, but once there is a clear sky, the system is designed to 'just' observe the daily objects, and return a report on the variable star magnitude.