Template:FTX Bluetooth: Difference between revisions

VisualWikitext

@@ Line 1: / Line 1: @@
-Teltonika Telematics
+{{#switch: {{{model}}}
+| FTC305
+| FTM305
+| FTC134
+| FTM134
+| FTC924
+| FTC927
+| FTM927
+| FTC965
+| FTC887
+| FTM887
+| FTC308
+| FTM308 =
+==Eye-Sensor activity monitoring scenario==
+=== <u>Introduction</u> ===
+The '''Activity Monitoring''' Scenario is designed to track the presence of '''Teltonika Telematics EYE Sensor''' devices by monitoring their '''BLE advertisement data'''. This functionality allows the system to detect when a device '''appears''' or '''disappears''' from the monitored area, ensuring continuous tracking and logging of sensor activity.
+When the EYE Sensor is in the field, the scenario updates all '''IO elements''' provided by the device and generates periodic records to maintain an accurate activity log.
+=== <u>Functionality</u> ===
+The '''Activity Monitoring Scenario''' operates as follows:
+'''Detecting BLE Advertisements:'''
+* The scenario listens for BLE advertisement signals from EYE Sensor devices.
+* If a device is detected, it is added to the active monitoring list.
+'''Monitoring Device Presence:'''
+* The system continuously checks for '''appear/disappear events.'''
+* If a device stops sending signals (disappears), the scenario updates the monitored device list accordingly.
+'''Updating IO Elements:'''
+* When a device is active, the scenario updates '''all IO elements''' provided by the EYE Sensor.
+* Periodic records are generated to ensure real-time status updates.
+'''Scenario Enable/Disable Option:'''
+* While the scenario is part of the '''global configuration''', users have the option to '''enable or disable it manually.'''
+* By default, the '''Activity Monitoring Scenario is always enabled.'''
+=== <u>Prerequisites</u> ===
+To ensure proper operation of the '''Activity Monitoring Scenario''', the following conditions must be met:
+'''Device Compatibility:'''
+* The scenario requires a '''Teltonika Telematics EYE Sensor''' with BLE functionality.
+* The tracking device must support '''BLE scanning and advertisement processing.'''
+'''Firmware & Configuration:'''
+* The device must run a firmware version that supports '''Activity Monitoring'''.
+* The scenario must be '''enabled in the device’s configuration settings''' (if not using the default setting).
+'''BLE Signal Conditions:'''
+* The EYE Sensor must be '''within range''' of the tracking device’s BLE receiver.
+* BLE signal interference should be minimized to ensure '''consistent detection'''.
+'''Power & Connectivity:'''
+* The tracking device should be '''powered on''' and capable of processing BLE advertisements.
+* A '''stable power supply''' is required to maintain continuous monitoring.
+'''Data Collection & Logging:'''
+* The device must be configured to '''log periodic records''' for accurate activity tracking.
+* Ensure the system has sufficient '''storage capacity''' for storing sensor data.
+==Eye-Sensor Temperature/Humidity monitoring scenario==
+=== <u>Introduction</u> ===
+This scenario monitors '''Bluetooth Low Energy (BLE) temperature and humidity sensors''', dynamically tracking detected devices and logging environmental changes.
+=== <u>Prerequisites</u> ===
+To ensure the scenario functions correctly, the following conditions must be met:<br>
+'''BLE Support''' – The device must support '''BLE scanning''' to detect temperature and humidity sensors.<br>
+'''Compatible BLE Sensors''' – The scenario works with '''BLE temperature and humidity sensors''' that broadcast their data.<br>
+'''BLE Event Handling''' – The device must process the following '''BLE events''':
+* ble.device_detected – Triggered when a new BLE sensor is detected.
+* ble.device_expired – Triggered when a BLE sensor is no longer detected.
+=== <u>How It Works</u> ===
+* The scenario '''automatically tracks BLE sensors''' in real time.
+* When a '''new sensor is detected''', the scenario '''adds it to the monitored list''' and logs its data.
+* If a '''previously monitored sensor disappears''', it is '''marked as expired''', and the scenario updates its status.
+* The device '''updates IO elements''' to reflect temperature and humidity changes.
+=== <u>Scenario States</u> ===
+'''Device Detection''':
+* When a BLE sensor is detected (ble.device_detected), the scenario adds it to the active monitoring list.
+* It differentiates between '''newly detected sensors''' and those that are '''already being tracked'''.
+'''Data Monitoring & Logging''':
+* The scenario continuously monitors temperature and humidity values.
+* If significant changes occur, '''an event is recorded''' to log the updated readings.
+* The scenario updates '''IO elements''' to reflect the latest environmental data.
+'''Device Expiration''':
+* If a BLE sensor is no longer detected for a configured time (ble.device_expired), the scenario marks it as expired.
+* The scenario removes it from the active monitoring list and updates IO elements accordingly.
+'''Continuous Tracking''':
+* As new BLE sensors appear and old ones expire, the scenario '''dynamically''' '''manages the list''' of monitored devices.
+* This ensures that only currently active sensors are logged and processed.
+=== <u>Expected Behavior</u> ===
+* '''Real-time monitoring''' of BLE temperature and humidity sensors.
+* '''Automatic tracking''' of newly detected and expired sensors.
+* '''Logging of temperature and humidity changes''' for records and reports.
+* '''IO element updates''' to reflect the latest sensor readings.
+==Eye-Sensor magnet detection scenario==
+=== <u>Introduction</u> ===
+This scenario enables '''magnet detection''' using the '''Teltonika Telematics EYE Sensor''', allowing users to track '''door, gate, or valve openings and closings''' based on magnet presence. When a magnet is detected or removed, the device generates an '''I/O event''', notifying the user of the state change.
+=== <u>Prerequisites</u> ===
+To use this scenario, the following conditions must be met:<br>
+'''Compatible Hardware''' – Requires a Teltonika EYE Sensor capable of magnet detection.<br>
+'''BLE Support''' – The tracking device must support Bluetooth Low Energy (BLE) scanning.<br>
+'''Scenario Activation''' – The scenario is enabled by default but can be manually enabled/disabled by the user.
+=== <u>How It Works</u> ===
+* The '''EYE Sensor''' monitors for the presence or absence of a magnet.
+* When the '''magnet is detected''', the scenario registers a '''closed state''' (e.g., door closed).
+* When the '''magnet is removed''', the scenario registers an '''open state''' (e.g., door opened).
+* The device generates an '''I/O event''' upon any state change.
+=== <u>Scenario States</u> ===
+'''Magnet Present (Closed State)''':
+* The sensor '''detects the magnet''', indicating that the '''door, gate, or valve is closed'''.
+* An '''I/O event is recorded''' to log the closed state.
+'''Magnet Removed (Open State)''':
+* The sensor no longer detects the magnet, indicating that the '''door, gate, or valve is open'''.
+* An '''I/O event is recorded''' to log the open state.
+'''User-Controlled Activation''':
+* The scenario is '''enabled by default''', but users can '''manually enable or disable''' it as needed.
+==Identification scenario==
+===Parameter Description===
+'''Authorized Devices List'''
+* Maintains a list of devices that have been authenticated and are permitted to connect or be recognized without further checks.
+* When a new device is approved, it’s added to this list.
+'''Scenario functionality can be divided into 5 states:'''
+* '''Idle'''
+** Waits for detection or expiration events.
+** If a device detected event occurs, transitions to Authorization.
+** If a device expired event occurs, transitions to Device Expired.
+* '''Authorization'''
+** Triggered when a new device is detected.
+** Checks if the device is authorized:
+*** If not authorized, it returns to Idle (no record generated).
+*** If authorized and first occurrence, transitions to Device Online.
+*** If authorized and subsequent occurrence, transitions to Device Update.
+* '''Device Online'''
+** Generates a "Device Online" record (e.g., AVL) for an authorized device’s first recognition.
+** Moves the device to the “already authorized devices” list.
+** Returns to Idle.
+* '''Device Update'''
+** Reached if the device is authorized and not in its first occurrence.
+** Updates the device record to reflect the new detection time or any changes in state.
+** Returns to Idle.
+* '''Device Expired'''
+** Triggered if the device’s authorization has ended (e.g., time limit expired or device removed from the system).
+** If the device is still in the authorization list, generates a “Device Expired” record and removes the device from the authorized list.
+** Returns to Idle.
+'''Record Generation'''
+* Periodic or Eventual: Records related to device detection can be configured with different priorities—Low (periodic) or High (immediate).
+* Record Types
+** Device Online
+** Device Update
+** Device Expired
+[[Category:{{{model}}} Configuration]]
+}}

Latest revision as of 08:54, 2 June 2026