VRE Command — Extended Version
Returns the same reply as VR and adds the number of configurable resources the firmware handles: flags, timers, rules, geofences, destinations, etc.
What is it for?
- 🔢 Know how many resources there are — how many rules, timers, flags or geofences you can use before building a configuration
- 🧩 Compare firmware versions — see whether a version enlarged a module
- 📞 Technical support — identify the firmware and its capacity in a single reply
Syntax
| Action | Command | Response |
|---|---|---|
| Query | QVRE | RVR <version> U..|IN..|XP..|TD..|WP..|VL..|DC..|CID..|SM..|DS..|IP..|RL..|ICL..|UV..|UC..|XB.. |
The reply starts with RVR, like the QVR reply: there is no RVRE prefix.
Example
Zero IoT
>QVRE<
>RVR RINHO IOT v1.09.28.T63 ZE EG915U LC86G 8MB WIFI NIMBLE 2026-10-14 19:45:02 U128|IN10|XP3|TD32|WP32|VL16|DC5|CID10|SM5|DS5|IP6|RL196|ICL100|UV48|UC16|XB8;ID=863238074487135;*7A<VR vs VRE comparison
// VR: version
>QVR<
>RVR RINHO IOT v1.09.28.T63 ZE EG915U LC86G 8MB WIFI NIMBLE 2026-10-14 19:45:02;ID=863238074487135;*4F<
// VRE: version + resources
>QVRE<
>RVR RINHO IOT v1.09.28.T63 ZE EG915U LC86G 8MB WIFI NIMBLE 2026-10-14 19:45:02 U128|IN10|XP3|TD32|WP32|VL16|DC5|CID10|SM5|DS5|IP6|RL196|ICL100|UV48|UC16|XB8;ID=863238074487135;*7A<Resource list fields
| Field | Resource | Example | Command |
|---|---|---|---|
U | User flags | U128 | SS / QSS |
IN | Inputs | IN10 | IN |
XP | Outputs | XP3 | XP |
TD | Timers | TD32 | TD |
WP | Waypoints / circular geofences | WP32 | WP |
VL | Speed limits | VL16 | VL |
DC | Heading-change triggers | DC5 | DC |
CID | Caller ID numbers | CID10 | CID |
SM | SMS destination numbers | SM5 | SM |
DS | Voice destination numbers | DS5 | DS |
IP | Report IP destinations (indices 0-6 except IP2, which is the FOTA URL) | IP6 | IP |
RL | Event engine rules | RL196 | RL |
ICL | Authorized codes | ICL100 | ICL |
UV | User triggers | UV48 | UV |
UC | Report templates | UC16 | UC |
XB | Capture buffers | XB8 | XB |
These are the resources the firmware handles, not the hardware: IN and XP give how many inputs and outputs the software module has, not how many are wired on the device. A Zero IoT has 2 physical inputs and 1 output even though it reports IN10 and XP3.
Compatibility
💾Firmware v1.03.00
SPLegacy
ULLegacy
MTLegacy
💾Firmware v1.00.00
SP-IOT
SM-IOT
ZE-IOT
See Also
- VR Command - Basic version
- FOTA Update - Remote update
- Diagnostics - Diagnostic commands
Last updated