Changelog

Changelog

v0.2.3 (2026-10-12)

• People for everyone: the collector now reads the participants of all classes of the club for today and tomorrow (one profile per club, ≤ 1 read per class every 3 hours, 2 s apart), besides the tracked/booked classes of the next 7 days. Users without bookings (and administrators without their own mywellness profile) see the club's people and leaderboard too.

v0.2.2 (2026-10-12)

• Fix (web UI behind Cloudflare): app.js, i18n.js and app.css are now served with Cache-Control: no-store and referenced with ?v=<version> from index.html. Cloudflare was caching the old app.js for 4 hours, so after an update the page (new) ran with the old script: the new "Persone" page and the 👥 button did not work until the cache expired.

v0.2.1 (2026-10-12)

• Leaderboard reads use the official widget's date formats (ISO-week Monday yyyymmdd, month yyyymm) and also read the previous week/month. Note: for Wellness Town the public leaderboard API answers an empty list even when authenticated; the "Classifica Settimanale" of the mobile app comes from an endpoint not present in the web widget, still to be identified.

v0.2.0 (2026-10-12)

• People (new, separate from the booking engine): the gateway keeps a SQLite database (/config/people.db, pure-Go driver, no cgo) with the public member data mywellness exposes — nickname, picture, "private profile" flag — plus attendance and the club's MOVEs leaderboard. A low-frequency collector reads the participants of the classes you track or booked (every 15 minutes it checks; at most one read per class every 3 hours, plus one in the 40 minutes before the start) and the weekly/monthly leaderboard hourly. Reads are authenticated but rare and do not touch the booking timing.
• API: GET /profiles/{id}/classes/{classId}/{date}/participants (live read + history: seen count, classes attended, best leaderboard positions), GET /people/members[?facility&q], GET /people/members/{id} (attendance history, leaderboard rows), GET /people/leaderboard?facility&trend=week|month[&period], GET /people/stats. Visibility follows the caller's profiles (club).
• Web UI: new Persone page (podium + leaderboard with past periods, classmates with search, member card); a 👥 button on every class in Lezioni opens the live participant list. iOS app 1.2.0 (build 20): Participants section in the class sheet, "Persone del centro" in Altro.
• Privacy: only data the Technogym app already shows to every member; private profiles stay anonymous; no personal data of third parties beyond that is collected.

v0.1.19 (2026-10-10)

• Readable profile card: GET /profiles returns card, the mywellness identity normalized (fullName, nickName, email, gender, birthDate YYYY-MM-DD, culture, measurementSystem, memberSince RFC 3339, timeZoneWindowsId, userId, extra), so clients can format dates, language, units and time zone in the user's language. The web user dialog shows the card (name, nickname, email, gender, date of birth with age, language, units, member since, time zone) with the user ID and other technical fields in a collapsible "Dati tecnici"; the iOS app (build 19) shows the same layout.

v0.1.18 (2026-10-09)

• Removing a tracked class now cancels it on mywellness too: DELETE /items/{id} unbooks a booked class and leaves the waiting list for a waiting-list class before removing it; with ?rule=1 the whole recurrence is stopped and every future booked/waiting class of the series is cancelled. The response reports removed, unbooked, leftWaitingList and errors; a class whose cancellation fails (e.g. past the cancellation deadline) stays in the list with the error. Web UI and iOS app (build 18) confirm before removing and show the outcome. Before, "Rimuovi" only dropped the gateway entry and the booking stayed on Technogym.

v0.1.17 (2026-10-08)

• Per-user scheduler settings: every gateway user, administrator or not, has their own settings (opening rules with per-rule quota, lead, burst, watching cadence, days ahead, priority notifications). They apply to the classes of that user's profiles. The administrator's old global settings become the defaults for users who have not customised anything. GET/PUT /settings now read/write the caller's own settings (custom tells whether they differ from the defaults), DELETE /settings goes back to the defaults, ?scope=default (admin) edits the defaults. Web UI: Impostazioni editable by everyone, with a scope selector for the administrator; iOS: Scheduler e osservazione editable by everyone, with "Torna alle predefinite".

v0.1.16 (2026-10-08)

• Several Technogym clubs per mywellness account: a profile is "one account at one club"; POST /profiles with copyFromProfileId adds another club for the same account, copying credentials, owner and visibility (no password needed). The web user dialog lists every club of the account (label, limit, counters, re-login, remove) with "+ Add club"; the iOS app shows a club switcher at the top of Classes and Bookings and a Clubs section in the profile page.
• GET /profiles also returns identity on profiles created as additional clubs.

v0.1.15 (2026-10-08)

• Watching ("Osservazione") is now aggressive and account-safe: free places are read from the public schedule (no token, one request per club and day shared by every profile and class) every pollSeconds (default 15 s, minimum 5) and every nearPollSeconds (default 3 s, minimum 2) in the last nearHours hours (default 4). An authenticated read every 60 s still updates participation and waiting-list position. A place is taken when availablePlaces > 0, numberOfParticipants < maxParticipants or the user's bookingUserStatus is CanBook; the booking is retried up to 3 times 0.7 s apart. Existing settings at the old default (60 s) are migrated to 15 s. Background: on 8 October a Reformer place freed, mywellness notified the waiting list, and the 30 s polling lost the race.
• Fix (false cancellations): when a schedule read would turn a booked class into "cancelled", the session is verified first (GetLoginStatus) and re-read after a new login if the token had expired. This stops the hourly "disdetta rilevata"/"già prenotata" flapping.
• Profile identity: the whole mywellness userContext (minus tokens/passwords) is stored at login and returned as identity in GET /profiles, for the profile page of the iOS app.
• Watching network errors are logged (at most every 10 minutes per class); waitingListCounter shown in the class status.

v0.1.14 (2026-10-07)

• Fix (limits): classes covered by a rule with its own maxBookings (e.g. Reformer 3) now have a separate quota: they are no longer counted in the profile-wide limit (default 5) and are checked only against their own rule. Before, a profile with 5 active bookings including Reformer classes could not book anything else, and vice versa; this blocked the Reformer booking of 5 October at the Wellness Town club. activeBookings in GET /profiles now excludes classes with their own quota; limits keeps the per-rule counters.

v0.1.13 (2026-10-04)

• Fix: mywellness session tokens expire after about an hour and the schedule API then answers as an anonymous user (no isParticipant), so active bookings dropped to 0 and limits/cancellation detection were wrong. The gateway now verifies the session with GetLoginStatus (at most every 5 minutes) before authenticated reads, books, cancellations and waiting-list operations, and logs in again automatically when the token is invalid.

v0.1.12 (2026-10-04)

• User isolation: devices that log in with selfOnly: true (the iOS app) see only the signed-in person's profile, items, bookings and log, even for administrators; user management is web-only. Existing app devices are migrated. Regular users are isolated on the web too; administrators keep the family view in the web UI.

v0.1.11 (2026-10-04)

• Human-like traffic: watching every 60 s by default (minimum 15), 30 s in the 4 hours before the class, ±15% jitter; one schedule request per profile and day shared by all tracked classes of that day (10 s cache); browser User-Agent. Existing settings below 30 s are migrated to 60 s.

v0.1.10 (2026-10-04)

• Booking time always comes from the matching rule (hour:minute); "follow the club" now decides only the opening day. Fixes rules set to 05:01 still showing 05:00.
• Per-rule active-bookings limit (maxBookings on a rule, e.g. Reformer 3) in addition to the per-profile limit; GET /profiles returns limits counters.

v0.1.9 (2026-10-03)

• Opening rules: a named rule always decides the booking time (even with "follow the club" on); the club's reported opening time applies only to classes covered by *.

v0.1.8 (2026-10-03)

• Local-only administrators (no mywellness account) can be created; the mywellness account is required only for regular users.

v0.1.7 (2026-10-03)

• Profiles created before 0.1.6 reload their mywellness identity (name, picture) automatically at the first refresh.

v0.1.6 (2026-10-03)

• Visibility: non-admin users see only their own profile (and profiles explicitly shared with them); administrators see every profile and can switch between them in the app and the web UI.
• Profile identity from mywellness (firstName, lastName, nickName, email, pictureUrl, thumbUrl) stored at login and exposed in GET /profiles; avatars in the web UI.

v0.1.5 (2026-10-03)

• Recurrences attach only occurrences on or after the chosen class.
• Users: per-user dialog (gateway access, role, mywellness account with link/re-login/unlink/remove, assign an orphan account); role changes and deletion allowed for any admin as long as one admin remains; deleting a user keeps their mywellness account as orphan.

v0.1.4 (2026-10-03)

• Leave the mywellness waiting list from the gateway (POST /profiles/{id}/leave-waiting-list {classId, partitionDate, removeItem} → item becomes cancelled); Unbook result codes handled (TooLate = less than 2 hours before, BookingNotAvailable); outline eye icon on password fields.

v0.1.3 (2026-10-03)

• Web UI: "Utenti e account mywellness" merges users and profiles: adding a user requires their mywellness email/password and creates the person's profile; every profile has Modifica (label, mywellness password, max bookings, visibility, owner user); link an account to an existing user.

v0.1.2 (2026-10-03)

• Theme and language selectors moved into Settings; eye toggle on password fields.
• Edit existing users (PUT /users/{id}: username, displayName, isAdmin, password) and link a mywellness account to an existing user from the users table; GET /users returns profileId/profileLabel; hint on the Profiles page when the signed-in person has no own profile.

v0.1.1 (2026-10-03)

• Web UI: theme (system/light/dark) and language (it/en/es/fr/de) selectors in the header; automatic refresh (20 s, and on tab focus) of bookings, classes and log.
• Gateway users can own their mywellness profile (userId): created with the user (setup / add user with optional mywellness credentials) or linked with mine: true; GET /me returns myProfileId and clients default to it.
• Web UI: profile selector in every section, "Ultime attività" card on the bookings page, log filters (profile, level), opening-rules table with matched-classes preview and explicit add/delete, stale-view fix.

v0.1.0 (2026-10-03)

• First release: multi-profile engine (scheduler at opening time, waiting list, continuous watching of freed spots, weekly recurrences, per-club booking limit), external cancellation sync, APNs Time Sensitive push, web UI with walkthrough, REST API for the Wellness Booking iOS app, Unraid template, GHCR multi-arch image.