We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
update pic
docs(wiki): document the number of transfers field
docs(wiki): document the RMV and VMT HAFAS profiles The adapter offers hafas:rmv (Rhine-Main/Mainz) and hafas:vmt (Thuringia) in the profile dropdown and loads both profiles in hafasService, but neither appeared anywhere in the wiki. Add them to the profile, service and per-profile product tables, describe both profiles on the services page and list their product keys (sBahn, uBahn, longDistanceTrain, regionaTrain, regionalTrain, ast, cableCar) in the transport mode table, which was still limited to the 18 products of the other profiles. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(wiki): mark the vendo:db profile as disabled The "Vendo - Deutsche Bahn" client option is disabled in the adapter since v0.10.0 because the db-vendo endpoint returns OPS_BLOCKED, but the wiki still recommended it as the preferred profile for Germany. Flag it as disabled on every page that lists it, point Germany-wide setups at motis:compat instead and add an FAQ entry explaining why the option is greyed out. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(wiki): document the departures time window field The station config field "Zeitfenster (Minuten)" / "Time Window" (native `duration`) was not documented anywhere in the wiki. - Departures (DE+EN): new section covering the field (default 60, min 1, max 720), that the window is counted from the start time set by the time offset, and that it interacts with the departure count — whichever limit applies first wins, so a larger window alone is useless at busy stops unless the departure count is raised too. - Refresh admin departures screenshot to show the field. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(wiki): document object count warning limit The objectsWarnLimit setting was missing from the wiki entirely. - Configuration (DE+EN): new section in the Settings block covering the field (min 5000, step 100, no adapter default), how it reaches the js-controller via system.adapter.<ns>.objectsWarnLimit on adapter start, and that values below the minimum are discarded. - Departures (DE+EN): note that the departure count drives the object count, linking to the new section. - Journeys (DE+EN): note that journeys are object-heavy (connections x legs per route), linking to the new section. - Refresh admin configuration screenshot to show the new field. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(wiki): sync pages with current code Align wiki with adapter code after audit of datapoints, config, services and journey pages (DE + EN kept in sync). - Datapoints: fix journey-level StationFrom/StationTo table (lowercase json/name/type/id, add Location + stops subtree, drop Platform); clarify that walking legs still get a StationFrom channel; note that per-leg delay states ignore the delay offset (threshold 0s); fix example datapoint paths. - Configuration (DE): serviceType and profile are stored as separate native fields, not combined; combined hafas:vbb value is UI-only. - Configuration (DE+EN): delayOffset triggers only when delay exceeds the offset (>120s), not at exactly 2:00. - Journeys: new journeys default to sequential "Journey N", not empty. - Services: MOTIS/Transitous region is "DE & Europe" (per UI label), and the MOTIS client is initialised with throttling too. - Departures: field heading "Time Offset (minutes)" -> "Time Offset".
Updated en Widgets (markdown)
Updated Widgets (markdown)
Updated _Sidebar (markdown)
docs: Fügt Links zur Startseite in mehreren Dokumenten hinzu
Destroyed en _Sidebar (markdown)
init Wiki
docs: Wiki-Dokumentation hinzugefügt (DE+EN, alle Seiten)
Initial Home page