An OBD-II dongle with LTE and GPS that puts a vehicle on the Alarm.com app for location, tow alerts and driving behaviour. Cellular only, with no local or Home Assistant path.
Selora does not recommend this device
The dongle reports over its own LTE connection to Alarm.com's cloud and never touches the local network, so there is no local API, no Home Assistant integration, and nothing on site to read.
Vehicle arrival is a useful automation trigger, but this is the most closed way to obtain it: a separate cellular subscription for a device that reports to one vendor. Many cars now expose location and lock state through a manufacturer integration Home Assistant already supports, and a phone or a Bluetooth beacon covers arrival detection for the rest without any extra hardware.
- A car manufacturer integration Home Assistant supports directly, where the vehicle offers one
- Phone-based presence or a Bluetooth beacon, for arrival detection without a subscription
It plugs into the car’s OBD-II port and reports over LTE Cat M1 with integrated GPS and a triple-axis accelerometer, so it covers location, unexpected movement while parked, and driving alerts. It replaces the older ADC-3035L-AT.
The interesting use in a house is presence: a car arriving is the earliest reliable signal that someone is coming home, earlier than a phone crossing a geofence and far earlier than a door opening. That is a genuinely good automation trigger.
None of it is available locally. The dongle talks to Alarm.com’s servers over its own cellular connection and never touches the house network, so there is nothing on site for Home Assistant to read even in principle.
Most modern cars expose the same arrival signal through their own manufacturer integration, several of which Home Assistant supports directly, and those need no extra hardware or subscription.
Hardware availability
Recipes using this device
No recipes reference this device yet.