📡 BLE Sensors — Wireless Data Reading

Guide to configure BLE sensor reading on Rinho IoT devices.

🤔 What is BLE sensor reading for?

The BLE module allows connecting wireless sensors to the GPS device:

• 🌡️ Temperature and humidity — Cold chain with Rinho Condition (L02S) sensors
• ⛽ Fuel — Tank level with Escort TD BLE
• 🚪 Doors — Open/close with magnetic (Hall) sensor
• 🏷️ Presence — Driver, tool or trailer detection with iBeacon
• 🆘 Panic — Wireless emergency button with MoKo W6 wristband

🔧 Prerequisites

Before starting:

🔄 Choose and load BLE firmware

Spider IoT / Smart IoT

The ESP32 has two interchangeable firmware partitions. To use BLE, the Nimble firmware must be loaded:

Zero IoT

The Zero IoT has a single firmware that includes both BLE and WiFi. No firmware change is needed, but both features cannot be active simultaneously:

// Use BLE: turn off WiFi
>SSSWIFPWR00<
 
// Use WiFi: turn off BLE
>SSSBTHPWR00<

Load Nimble firmware on Spider / Smart IoT

>SFRMM1<   // Via WiFi (faster)
>SFRMM2<   // Via cellular (if no WiFi)

>QVR<

>RVR RINHO IOT v1.09.16 SP EG915U LC86G 16MB NIMBLE 2025-01-15 10:30:00;ID=...

🌡️ Case 1: Temperature and humidity sensor — Rinho Condition (L02S)

The most commonly used sensor with Rinho devices. It measures temperature, humidity and has a magnetic sensor (Hall) for door detection.

📦 Rinho Condition datasheet · Cargando...

Step 0: Power on the sensor

The sensor comes powered off from factory:

1. Unscrew the bottom cap of the sensor (counterclockwise)
2. Remove the cap to access the interior
3. Press the internal button for 3 seconds until the LED blinks
4. Screw the cap back on

Step 1: Configure the sensor with BeaconX Pro

Step 2: Configure BS on the device

>SBS00E,AC233FA24B16,10,60,0,INVALID<

Step 3: Verify reading

Query sensor attributes with the QBS command:

>QBS00<           // General sensor status
>QBS00.temp<      // Temperature (e.g., 23.5)
>QBS00.hum<       // Humidity (e.g., 65)
>QBS00.mag<       // Magnetic (0=closed, 1=open)
>QBS00.batt<      // Sensor battery (%)
>QBS00.rssi<      // BLE signal strength

Typical full response:

>RBS00E,AC233FA24B16,10,60,0,INVALID;mag_st:0,mot_st:0,mag_cnt:5,mot_cnt:0,x:0,y:0,z:0,temp:23.5,hum:65,batt:95,tag:MK,rssi:-52;ID=...

⛽ Case 2: Fuel sensor (Escort TD BLE)

The Escort TD is a wireless fuel level sensor installed in the tank.

Configure BS

>SBS01E,A1B2C3D4E5F6,30,60,10,INVALID<

Query level

>QBS01.fuel_lvl<   // Fuel level
>QBS01.battery<    // Sensor battery
>QBS01.temp<       // Temperature

Response:

>432;ID=...    // 432 = fuel level (unit depends on sensor)

🏷️ Case 3: iBeacon for presence and panic

iBeacons are simple beacons that broadcast their identity. Useful for knowing if a driver, tool or trailer is nearby.

Configure BS with iBeacon

>SBS02E,AABBCCDDEEFF,2,30,5,0<

Use signals in rules

Each BS sensor generates automatic signals that can be used in the event engine:

Rule example: Report when a driver boards or leaves the vehicle:

// Rule: when driver's beacon is detected, report
>SRL00E;TRG=BS02+;ACC={GCQ00H}<
 
// Rule: when beacon is lost, report
>SRL01E;TRG=BS02-;ACC={GCQ00H}<

🔍 BSW: Auto-detection for dynamic scenarios

The BSW (Bluetooth Smart Wildcard) system automatically detects sensors without knowing their MAC beforehand. It filters by iBeacon UUID, Major and Minor.

When to use BSW instead of BS?

Example: Tractor connecting to different trailers

Each trailer has a beacon with the same UUID but different Major. The tractor automatically detects which trailer is attached:

// BSW00 captures beacons with specific UUID and injects into BS00
>SBSW00E,00,2F234454CF6D4A0FADF2F4911BA9FFA6,0,0,30,5<

Query BSW status

>QBSW00<

Response with detected device:

>RBSW00E,00,2F234454CF6D4A0FADF2F4911BA9FFA6,0,0,30,5;detects:1,active:1,mac:AA:BB:CC:DD:EE:FF,rssi:-45,distance:1.50,age:3;ID=...

BSW with multiple targets

To monitor temperature in 4 zones of a refrigerated trailer, with one sensor per zone:

// BSW00 captures sensors with Major 1-4 and distributes them to BS00-BS03
>SBSW00E,00:01:02:03,2F234454CF6D4A0FADF2F4911BA9FFA6,1,4,60,0<

📊 Integrate BLE data into reports

To have the platform receive BLE sensor data, configure a user report (SUC) that includes QBS tokens:

Example: Report with temperature and humidity

>SUC04 $RCQ| #| QCQ,5,64| $;PA=temp:2:| QBS00.temp| $;PA=hum:2:| QBS00.hum| $;PA=mag:1:| QBS00.mag<

Data types for PA parameters

Generate the report

>GCQ04H<    // Generates a SUC04 report and sends it

See G command for more generation options.

Device response:

>RCQ04...;PA=temp:2:23.5;PA=hum:2:65;PA=mag:1:0;ID=...

🔗 Create rules with BLE sensors

BS signals can be used to create automations with rules (RL) and user triggers (UV):

Example 1: High temperature alert

First create a user trigger (UV) that monitors temperature and activates when it exceeds 35 degrees:

// UV00: monitors QBS00.temp (float), activates when value is between 350 and 9999
// (sensor reports temp x10, so 350 = 35.0 degrees)
>SUV00FQBS00.temp,0,10,350,9999<
 
// Rule: if UV00 activates (high temp), generate report
>SRL02E;TRG=UV00+;ACC={GCQ04H}<
 
// Rule: if UV00 deactivates (normal temp), generate report
>SRL03E;TRG=UV00-;ACC={GCQ04H}<

Example 2: Door open alert (magnetic sensor)

// UV01: monitors magnetic state, activates when mag is 1 or more
>SUV01FQBS00.mag,0,10,1,2<
 
// Rule: door open (magnetic = 1)
>SRL04E;TRG=UV01+;ACC={GCQ04H}<
 
// Rule: door closed (magnetic = 0)
>SRL05E;TRG=UV01-;ACC={GCQ04H}<

Example 3: Driver presence (direct BS signal)

// BS02 has the driver's iBeacon
// Rule: report when driver boards (beacon detected)
>SRL06E;TRG=BS02+;ACC={GCQ00H}<
 
// Rule: report when driver leaves (beacon lost)
>SRL07E;TRG=BS02-;ACC={GCQ00H}<

🐛 BLE Debugging

When a sensor doesn’t appear or data is incorrect, enable BLE debug:

View raw BLE frames

Use the DB command to enable BLE debug:

>SDB0+BLX<

This shows in the debug console all BLE packets received by the device, including MACs, types and raw data. Useful for:

• Verifying the sensor is broadcasting
• Confirming the MAC address
• Checking if the sensor type is correct
• Diagnosing unknown sensors

Disable BLE debug

>SDB0-BLX<

Enable general debug

>SDB1<    // Level 1: main messages
>SDB2<    // Level 2: more detail

🔧 Troubleshooting

📱 Useful apps

📝 Full example

Typical configuration of a device with Rinho Condition (L02S) temperature sensor and driver presence beacon:

// 1. Verify BLE firmware
>QVR<
>RVR RINHO IOT v1.09.16 SP EG915U LC86G 16MB NIMBLE ...;ID=...
 
// 2. Configure temperature sensor on BS00
>SBS00E,AC233FA24B16,10,60,0,INVALID<
>RBS00E,AC233FA24B16,10,60,0,INVALID;...
 
// 3. Verify temperature reading
>QBS00.temp<
>23.5;ID=...
 
// 4. Configure driver beacon on BS02
>SBS02E,DDEEFF112233,2,30,5,0<
>RBS02E,DDEEFF112233,2,30,5,0;...
 
// 5. Create report with temperature
>SUC04 $RCQ| #| QCQ,5,64| $;PA=temp:2:| QBS00.temp| $;PA=hum:2:| QBS00.hum<
 
// 6. Rule: report when driver boards/leaves
>SRL00E;TRG=BS02+;ACC={GCQ04H}<
>SRL01E;TRG=BS02-;ACC={GCQ04H}<
 
// 7. Rule: high temperature alert
>SUV00FQBS00.temp,0,10,350,9999<
>SRL02E;TRG=UV00+;ACC={GCQ04H}<
 
// 8. Test manual report
>GCQ04H<
>RCQ04...;PA=temp:2:23.5;PA=hum:2:65;ID=...

📖 Command summary

🎯 Next steps

• 📲 BLE Pairing (SPP) — Wireless terminal for phone configuration
• 🚀 Getting Started — Basic device configuration
• 📶 Configure WiFi — WiFi as an alternative channel
• 🧠 Event Engine — Create advanced rules
• 📡 BLE Commands — Full reference for BS, BSW and BE