[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).