[Changelog] eview protocol

baja

This topic will be used to post changes in eview protocol implementation.

The list of supported devices:

Eview EV-04
Eview EV-05
Eview EV-07B
Eview EV-08
Eview EV-09
Eview EV-201
Eview EV-202

baja

Custom command added to eview protocol
Slight change in naming scheme of Alarm Code (0x02) parameters
alarm.panic.stop.status renamed to alarm.panic.stop
alarm.panic.status renamed to alarm.panic.start
Both parameters are stored now, on 08 December deprecated parameters will be removed.

baja

Alarm code table code bits 26 to 29 are parsed to boolean parameters geofence.status.1 to geofence.status.4

baja

vehicle.state and vehicle.state.bitmaks parameters added for Alarm code bits. It will allow our users to apply any logic based on alarm bit values
Configuration message "Get Timestamp" 0x12 - now has correct response with the timestamp

baja

Settings for phone numbers added for EV-04 device type
Slight change in parameter naming scheme for amber, welfare and fall alerts to avoid overwriting of alarms starts and stops which are both present in one packet:
welfare.alarm.status is splitted to welfare.alarm.start and welfare.alarm.stop
amber.alarm.status is splitted to amber.alarm.start and amber.alarm.stop
fall.alarm.status is splitted to fall.alarm.start and fall.alarm.stop
Both parameters are stored now, on 08 December deprecated parameters will be removed.

baja

Wrong parsing detected: movement.status does not reflect bits for motion alerts carefully so
movement.status = false will be renamed to no.motion.alarm = true
movement.status = true will be renamed to motion.alarm = true
Both parameters will be registered until December 27th.
Setting for motion alert added for EV-04 device type

baja

baja parsing change applied

New settings implemented:

Working mode
No Disturb
Reboot
Find me

baja

Settings added:

IP&port
time interval
continue locate time parameter

namo

Eview protocol is updated: changed format of wifi.mac.address parameter.
Old format: 101331DDBA41
New format: 10:13:31:dd:ba:41

baja

The protocol will be affected by the change in type of parameters gsm.mcc and gsm.mnc to be installed in 2 weeks - May 23rd, 2022: both parameters that now have type "string" will be stored as "number". The possible leading zeroes in MNC will be ignored (e.g. the value "01" will be stored as 1).

namo

Eview protocol is updated: fixed parsing of New wifi loc info 0x19 key of Data Command 0X01 for Eview EV-07B

namo

Eview protocol is updated: added new settings for Eview EV-05 device:

Server IP and Port - Connectivity tab
Time Interval, Continue Locate Time Parameter - Tracking tab
Working Mode, Password Protect , No Disturb - System params tab
Phone Switches, Phone Number 1 - Phone Number 10 - Phone tab
Fall Down Alert, GEO Alert 1 - GEO Alert 4, Motion Alert, No-Motion Alert, Over Speed Alert, Tilt Alert, Power Alert, Alarm Clock 1 - Alarm Clock 4 - Alarm tab

namo

Eview protocol is updated: fixed parsing of Alarm Code field of Data Command 0x01 for Eview EV-201.
Mapping of the field's bits to flespi.parameters is below:

Bit 0 Battery-Low Alert - battery.low.alarm
Bit 4 GEO-1 Alert - geofence.alarm.1
Bit 5 GEO-2 Alert - geofence.alarm.2
Bit 6 GEO-3 Alert - geofence.alarm.3
Bit 7 GEO-4 Alert - geofence.alarm.4
Bit 8 Power OFF Alert - power.off.alarm
Bit 9 Power ON Alert - power.on.alarm
Bit 11 No-Motion Alert - no.motion.alarm
Bit 24 Beacon leave home alert - beacon.leave.home.alarm
Bit 25 Beacon come home alert - beacon.come.home.alarm
Bit 30 BLE disconnected - ble.disconnected.alarm

namo

Eview protocol is updated: settings Phone Number 1 - Phone Number 10 (Phone tab) for Eview EV-05 are improved and now they allow to specify Contact Name and Contact Photo (URL) for each phone number:

namo

Eview protocol is updated: added Continue Locating setting (Actions tab) for Eview EV-05 device type:

namo

Eview protocol is updated: changed parsing of WiFi parameters for New wifi loc info 0x19 key of Data Command 0x01: all wifi.* parameters are registered with indices, starting from 1.
The example of resulting message is below:

{
"event.enum": 25
"timestamp": 1663052690
"wifi.mac.address.1": "50:EB:F6:69:F2:A8"
"wifi.mac.address.2": "44:13:D0:BD:0A:A3"
"wifi.mac.address.3": "90:FD:73:F9:5C:61"
"wifi.mac.address.4": "E8:5A:D1:F1:A0:1B"
"wifi.mac.address.5": "A4:17:8B:AC:6F:E0"
"wifi.signal.strength.1": -54
"wifi.signal.strength.2": -61
"wifi.signal.strength.3": -78
"wifi.signal.strength.4": -91
"wifi.signal.strength.5": -92
"wifi.ssid.1": "Home2"
"wifi.ssid.2": "Mix9"
"wifi.ssid.3": "My WiFi_2.4G"
"wifi.ssid.4": "Unicorn"
"wifi.ssid.5": "107_11_11"
...
}

baja

Bugfix in server_ip_port setting: TCP/UDP flag and GPRS enable flag had not been sent which resulted in corrupted data in the command
SMS commands to set IP:port and APN added

shal

Eview protocol is updated: integrated freshly introduced by new firmware revisions Key 0x2B for Command 0x01 which contain Cell Towers data for WCDMA/LTE (EV07BX/EV04/EV05 Only).

Also added to eview protocol source information for each parameter. This information is available on the eview protocol page at flespi.com website or via special messages parameters utility built-in flespi.io: