Who it is forA lot operator or smart-building integrator who has LED road signs or a Home Assistant setup and needs live availability to drive them.
The problemSigns and automations cannot show lot availability without a live data source that reports capacity changes.
The outcomeMQTT messages fire on capacity thresholds or single-space transitions, and staff get notified when capacity hits a set level such as 95%.
What you need first
- One or more IP, RTSP, or snapshot-capable cameras with a reachable stream URL or snapshot endpoint
- A Windows PC for the native installer, or a Linux host with Docker for the container
- Access to the Releases page or the ghcr.io container image
- A Developer Cloud API key from lotvulture.com, only if using the cloud API use case
Steps
- Complete the dashboard setup and confirm occupancy states appear on the live dashboard.
- Open the alerting subsystem in the dashboard and create an MQTT alert.
- Set the trigger to a lot capacity threshold, such as 95%, or to single space transitions.
- Point the MQTT alert at your broker and topic that the sign or Home Assistant reads.
- Trigger a test change by occupying or freeing a mapped space and confirm the message arrives.
Prompt for your agent
For the repo lotvulture/lotvulture, configure an MQTT alert in the Lot Vulture dashboard that fires when lot capacity reaches 95 percent, targeting the broker at <mqtt_broker_address> and topic <topic_name>. Report the alert configuration you created and the message payload received, and verify that a test occupancy change produces exactly one message on the topic.
Caveat. The README does not document the exact MQTT payload format or the alert setup menu, so check the dashboard and the Developer Guide before wiring it to a sign.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page