[Changelog] aovx protocol flespi telematics hub supports aovx protocol. The list of supported devices AOVX AM300 AOVX AL300 AOVX EB100 AOVX EB110 AOVX EB120 AOVX GM100 AOVX GL100 AOVX VM300 AOVX VL300 AOVX VG300 AOVX VL350 AOVX VG200

Protocol update: Fixed LBS data parsing according to the changes of the latest firmware versions: This modification is in following firmware versions and later version: G series：AOVX_GX100-XX_H2.0_V2.0.4_v24 A series：AOVX_AX300-XX_H2.0_V2.0.4_v24 V series： VL300/VM300 series：AOVX_VX3xx-XX_H2.0_V2.0.4_v01 VG200/VG300 series：AOVX_VG300-GL_H1.2_MC25MAR01A07_V1.2.9_v02 if("undefined"!==typeof hljs)hljs._ha();else if("undefined"===typeof hljsLoading){hljsLoading=1;var a=document.getElementsByTagName("head")[0],e=document.createElement("link");e.type="text/css";e.rel="stylesheet";e.href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.7.0/styles/default.min.css";a.appendChild(e);e=document.createElement("script");e.type="text/javascript";e.onload=function(){var d={},f=0;hljs._hb=function(b){b.removeAttribute("data-hljs");var c=b.innerHTML;c in d?b.innerHTML=d[c]:(7

Fixed parsing: The wifi.signal.strength parameter which refers to tag 0xF4 has been corrected. Previously, the parameter value was incorrect. New parameter timestamp.key has been added to differentiate messages with the same timestamp but different content.

Fixed parsing: The changes affected tag 0x30 ; previously the parameter was called gsm.signal.dbm and was calculated incorrectly. Now the parameter is called gsm.signal.quality and shows the real value from 0 to 31. 99 is invalid. All changes have been agreed with the manufacturer.

Fixed parsing: Calculation of the parameter gsm.signal.dbm for tag 0xF0 is fixed. On older firmware, there may be incorrect values for this parameter, so if you get any problems with this parameter, the first thing you should do is update the firmware to the latest one. Tag 0xF9 is fixed . The error was caused by a combination of two factors, insufficient description in the protocol and the server did not take into account the parsing of extra bytes (which were not described).

Fixed parsing: indexed parameter sensor.temperature inside tag 0xF6 is now calculated as signed 2 byte integer divided by 10. It may contradict with older firmware version, if you have wrong values for this parameter - upgrade your devices to newer firmware.

Change of settings for the V series . Added configuration settings: Voltage Report interval Turn angle Speed odometer Removed settings: Temperature & humidity sensor Light sensor G-Sensor

[Changelog] aovx protocol

YuryAheichyk

Added Uplink Transparent Transmission (0x0900) message parsing

EvgenyShatilo

Added parsing for the alarm flags in the GL100 model.

kial

aovx protocol update: now TLS option can be enabled for the channels to setup receiving secure and encrypted SSL connections from devices.

namo

aovx protocol is updated: fixed finishing of command that is sent as configuration setting

baja

Update planned: in 1 week September 3rd and ending index will be removed from parameters:
sensor.illuminance.1
sensor.temperature.1
sensor.humidity.1
x.acceleration.1
y.acceleration.1
z.acceleration.1

baja

baja update installed

YuryAheichyk

Fixed a bug where devices with an identifier starting with 0 could not connect to the channel

baja

ble.sensors array-type parameter renamed to ble.beacons. Also there is extra field id added to every sensor object in the format: ident-index

YuryAheichyk

Added new command Transparent data for V-Series devices

namo

AOVX protocol is updated.
Empty idents (i.e. Device Unique ID is sent as binary zeroes 000000000000) now don't cause parsing error followed by disconnect if device connection is already identified.

YuryAheichyk

Fixed gsm.network.type parameter registration for V- series devices