en FAQ
| Region | Recommended service/profile |
|---|---|
| Germany (DB, IC, ICE, regional trains) |
MOTIS Transitous (compat) — Vendo (DB) is currently disabled |
| Berlin & Brandenburg (BVG, S-Bahn) | HAFAS – VBB |
| Austria (ÖBB) | HAFAS – ÖBB |
| Northern Germany (VBN, Bremen/Lower Saxony) | HAFAS – VBN |
| Rhine-Main (Frankfurt, Wiesbaden, Mainz) | HAFAS – RMV |
| Thuringia | HAFAS – VMT |
| Other regions (experimental) | MOTIS Transitous (compat) |
For more details: Transport Services
The option has been deliberately disabled since adapter version 0.10.0: Deutsche Bahn's db-vendo endpoint answers the adapter's requests with OPS_BLOCKED — a server-side block the adapter cannot work around. Rather than letting queries run into nothing, the profile is greyed out in the dropdown.
If you previously used vendo:db, switch the instance to another profile — motis:compat (Transitous) for Germany-wide coverage, or the matching HAFAS profile for regional coverage. The option will be re-enabled once the block is lifted; the code for it stays in the adapter.
There is no hard-coded upper limit. The number is practically limited by system resources and the polling interval. Each stop and journey generates one API call per polling cycle.
Yes. Multiple instances are possible and useful when different services need to be used simultaneously (e.g. HAFAS and MOTIS at the same time), since only one service is configured per instance.
Node.js ≥ 22 and js-controller ≥ 7.0.6 are required. Older versions are not supported.
Possible causes:
- Stop ID not found — The entered ID or search term returns no results. Check the ID using the stop search in the adapter configuration.
- Transport mode filter too restrictive — All transport modes are disabled. Enable at least one.
- Time offset too large — The configured time offset (minutes) is beyond the available departures in the query window. Reduce the time offset or increase the time window.
- API not reachable — The API of the selected service is temporarily unavailable. Check the adapter log for error messages.
- Adapter stopped — Check in ioBroker Admin that the adapter is running (green icon).
The delay value is given in seconds. A value of 120 means 2 minutes delay. Negative values mean the vehicle departs earlier than planned.
-
Departure— actual (real-time) departure time; includes the delay -
DeparturePlanned— scheduled departure time according to the timetable
When no real-time data is available, Departure equals the planned time.
The time offset filters out departures happening in less than N minutes. Useful when the walk to the stop takes a few minutes and you want to hide departures you can no longer catch.
Example: Time offset = 5 → Only departures at least 5 minutes away are shown.
Not all services and profiles provide operator information. If the API returns no operator, the datapoint remains empty.
- Origin or destination stop not configured — Journeys require at least one configured departure stop as a source. Check that the selected stops exist in the "Departures" tab.
- Service does not support journey search — Journey search is only supported by services that offer this feature. MOTIS Transitous may have limited support.
- Same origin and destination — Origin and destination must be different stops.
- Journey — the complete connection from A to B
- Leg — a single travel segment within the journey (e.g. a subway ride or a walking transfer)
The widgets were developed for ioBroker VIS 1.x. VIS 2.x is untested and not officially supported at this time.
- Check that the entered Object ID is correct (JSON datapoint of the stop/journey, e.g.
public-transport.0.Stations.{id}.json). - Check that the adapter is running and the JSON datapoint contains valid data.
- Make sure VIS has access to the ioBroker state.
The widgets support standard VIS CSS classes. Custom adjustments can be made via the CSS field in the VIS editor. The class prefixes are pub-trans-deptt-* (departure table) and pub-trans-conn-* (connections table).
The NSPanel Lovelace UI Adapter. It must be installed and configured separately.
Enable the "NSPanel Channel" toggle in the respective stop or journey configuration. The datapoints are created automatically on the next polling cycle.
Details: NSPanel Integration
