> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/device-related-questions/why-a-teltonika-output-wont-activate-when-immobilizer-is-enabled.md).
# Why a Teltonika Output Won’t Activate When Immobilizer Is Enabled
### Question
Why can’t I turn on a Teltonika digital output from the platform when that output is assigned to the Immobilizer scenario?
### Answer
Teltonika Immobilizer is not a platform switch. It is a device-level scenario that takes full control of the assigned digital output (DOUT). That is why a GPRS command from Navixy platform often looks successful on the platform side, but the output never changes.
#### What Immobilizer actually does
On Teltonika devices, Immobilizer is designed to stop anyone from starting the vehicle unless the tracker itself authorizes the driver. Authorization happens locally, not in the cloud. Typical methods are:
* a 1-Wire iButton or RFID card
* a configured BLE beacon
The assigned DOUT is the actuator. According to Teltonika’s own logic:
1. When the Immobilizer is active, the selected DOUT goes high (1) and blocks the starter, depending on which output the device has been configured to use.
2. The tracker waits for a valid key, RFID, or BLE beacon.
3. Only after that local authorization does the DOUT go low (0) and allow the engine to start.
4. After ignition is turned off and the Ignition Off timeout expires, the scenario resets. The next start requires authorization again.
If Depend on Ignition is enabled, the output stays low until ignition is detected, then it goes high and waits for the key or beacon. If that option is disabled, Immobilizer can take the output immediately after the scenario is enabled.
**In both cases, the decision lives inside the tracker.**
#### Why a platform DOUT command is not enough
Navixy already has standard commands to control physical outputs. For Teltonika, that is typically something like `setdigout`. Those commands work when the output is a normal digital output.
They do not complete Immobilizer authorization.
A standard output command only says: *set this pin high or low*. Immobilizer requires something different: *has the configured key or beacon been detected by this device?* If the tracker accepted a remote DOUT command as a valid release, anyone with platform access could bypass the hardware authorization step. That would defeat the purpose of Immobilizer.
This is also why Teltonika treats Immobilizer as the highest-priority DOUT scenario. Officially, Immobilizer cannot share the same output with other features because it takes full control of that DOUT. Other commands, including platform output control, can be ignored while the scenario owns the pin.
Navixy documents the same idea at platform level: some manufacturers implement scenario-based omission. The platform can send the command, but the device decides whether to apply it.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://navixy.com/docs/qna/device-related-questions/why-a-teltonika-output-wont-activate-when-immobilizer-is-enabled.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
