Tried on the real BGW320 (firmware 6.40.4): posting the Restart form only
answers 302 to /cgi-bin/restarting.ha, and the modem keeps running (its
uptime carried on). Loading that page, as a browser does, starts the
restart ("restarting ... approximately 155 seconds"). restart() now
follows the redirect and only reports 'accepted' when that page says it
is restarting.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Admins get a Restart modem button on the WAN / Fiber panel (needs
modem.access_code). After a confirmation it:
1. switches an Uptime Kuma maintenance window on (new kuma.py: logs in
over Kuma 2's Socket.IO API and resumes/pauses one pre-made manual
window, uptime_kuma.maintenance_id); if Kuma fails it stops and asks
whether to go on without it,
2. starts Gandalf maintenance (global suppression, 20 minutes at most),
3. posts the gateway's Restart Device form (ModemAdmin.restart), undoing
1 and 2 if that fails.
The monitor waits for the modem to answer with its WAN up and an uptime
showing it restarted, then switches Kuma off, ends the suppression and
records how long it took; after 30 minutes it ends both regardless. The
panel shows the restart in progress and the result for an hour.
New dependency: python-socketio[client].
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>