Pocket Garage
Vehicle fuel and costs with Pocket Garage, switching to LubeLogger, and server-managed Pocket Money transactions without duplicate app payments.
iPhoneMacAndroidOn this page
Pocket Garage keeps your vehicles, fuel-ups, service, repairs, upgrades and expenses. Pocket Homelab uses it in the Vehicles workspace, with vehicle history, record entry, edits, deletes and offline queued records. Its connection is called Garage in Settings → Services.
Choose the app
Open Settings → Services → Garage. The Garage app selector uses tabs: Pocket Garage first, LubeLogger second, matching Money’s application selector. The fields follow the selected app and both apps’ credentials are kept, so you can switch back. New setups start with Pocket Garage; an existing LubeLogger-only setup stays on LubeLogger.
- Create an API token in Pocket Garage’s Settings.
- Choose Pocket Garage in the app, enter its base address and token, then Test connection.
- Set the shared currency, distance and volume labels and preferred vehicle if needed.
You can also receive the Garage connection through Pocket Core.
| Key | Field | Required | Secret | Where to get it |
|---|---|---|---|---|
GARAGE_BACKEND | Garage app | Optional | — | pocket or lubelogger. Select the application in Garage settings. |
GARAGE_URL | Pocket Garage URL | Required | — | Base address of your Pocket Garage server. |
GARAGE_API_KEY | Pocket Garage API token | Required | Secret | Create a token in Pocket Garage Settings. Stored in the Keychain on Apple. |
The existing LUBELOGGER_CURRENCY, LUBELOGGER_DISTANCE_UNIT, LUBELOGGER_VOLUME_UNIT and
LUBELOGGER_VEHICLE_ID settings are shared by both apps. The prefix stays the same for existing imports.
Money transactions belong to Garage
When Pocket Garage’s Money integration is enabled and its account is configured, Garage’s server creates, updates and removes the linked Money transaction with the vehicle cost. Configure that integration in Pocket Garage. You do not need to add a second transaction in Pocket Homelab’s Money screen.
With Pocket Garage selected, the app hides payment templates, payment defaults and the action to create a missing payment. The record’s payment card explains that Garage manages it and opens Garage to check the link or a sync error. Offline records follow the same rule when they are sent later.
With LubeLogger selected, the existing optional payment-entry flow remains available: add a transaction with a vehicle record or from its details using your Money templates. See LubeLogger.
Switching and offline records
Each server keeps its own data; changing the selector does not migrate vehicles or records. Cached data and queued actions belong to the provider and credentials they were created with. Switching applications does not send an old LubeLogger action to Garage, or an old Garage action to LubeLogger.
The app sends vehicle costs to Garage’s native API so its Money integration runs. Garage keeps the record’s currency, parts, tags, category and vendor when the app edits the supported fields.