NODE Changelog

Version 1.3

Bug

• [NODE-68] - DVRs reporting incorrectly that they are in install mode
• [NODE-69] - Events are not properly closed when they have alerts/notifications
• [NODE-73] - DVR/Geofence are not properly working
• [NODE-76] - Possible Accident Alert is triggered eventhough the accident probability is 0
• [NODE-85] - Face Recognition licenses are not propagating to camera
• [NODE-90] - Alerts Template -> after login, it doesn't show you the pop-up with the alert (just when you are previosly logged in)

Story

• [NODE-55] - When you request 'Check Driver', but another event is on going, the Driver field is not populated properly. Appears 'Unknown Driver'
• [NODE-62] - Extend Alerts/Notifications flow for all event types
• [NODE-64] - Extend MYSQL event flow for covered camera and seat belt events
• [NODE-65] - Implement data flow for cameras connecting via wi-fi to LTI
• [NODE-67] - Move Node project from SVN to Git
• [NODE-75] - Implement signal strength for AI camera
• [NODE-78] - Implement AOSP OTA update
• [NODE-80] - Optimize GPS Tracker Loading time when entering on page
• [NODE-87] - Implement new features for camera protocol
• [NODE-88] - Re-design alerts template

Version 1.2

Bug

• [NODE-10] - Stonkam DVR Version is reported incorrectly on connection
• [NODE-12] - Modify date format for DVR alerts
• [NODE-43] - Update camera firmware version on health package receive -- for sending to GlobalCenter
• [NODE-44] - DVR Alerts not triggering on camera changed status

Story

• [NODE-11] - Stonkam DVR: DVR Check-in in AC does not match SIM activity data
• [NODE-14] - Insert events data sent via cell to MySql database
• [NODE-15] - Stonkam DVR update device configurations remotely
• [NODE-16] - Bring FW version into e-mail body of "Blue X2 cameras" Alert
• [NODE-17] - Study memory database solutions (Redis or similar)
• [NODE-19] - Verify event trigger based on speed per road segment
• [NODE-23] - Cellular download implementation
• [NODE-24] - Create a new method to accept high resolution speed and location data
• [NODE-25] - Implement mechanism to configure remotely the DVR
• [NODE-28] - Create method to return current address to LTI
• [NODE-29] - Only return current address to regular vehicles, not intermodals
• [NODE-31] - Study and create a mesh network implementation for scaling
• [NODE-32] - Modify intercommunication processes to be aware of the mesh layer
• [NODE-33] - Test and debug the mesh inter-instances communication
• [NODE-36] - Study the differences between the XML configuration file and the JSON update object for Stonkam DVR
• [NODE-37] - Remotely push firmware updates via GSM
• [NODE-38] - Create mechanism to upload additional events images from camera
• [NODE-39] - When you request a Live Telematics event and another event is on going, stop the spinner and show a 'connection error / please try again later / another event is on going'
• [NODE-40] - Create mechanism for remotely update FW notification
• [NODE-42] - When an error comes in Global Center, please show in the interface 'Error: [code_error]'
• [NODE-48] - Refactoring of the driver assignation area
• [NODE-49] - AWS Rekognition face clustering evaluation
• [NODE-51] - Implementation for FaceNet clustering algorithm
• [NODE-53] - Add Event_ID field into Possible Accident alert row
• [NODE-54] - Add 31.0 to X2 OTA deployments & test deploy to idrive
• [NODE-56] - Implement day / night package handling
• [NODE-57] - Extend MYSQL implementation to include day / night in lt_transfer_last
• [NODE-58] - Update routes with day/night format (alter schema => lock)
• [NODE-59] - Create new tables for daily stats, including trigger from routes
• [NODE-60] - Parse ICCID from SkDVRs and add it in the proper places -- including assignation

Version 1.1

Bug

• [NODE-1] - LTI node bug fixing

Story

• [NODE-8] - Disable 'is_accident' for intermodals

Sub-task

• [NODE-9] - Sometimes the wrong driver is displayed for the vehicle

Version 1.0

Bug

• [NODE-6] - Scope leak on device settings

Sub-task

• [NODE-2] - Node error : RSV2 and RSV3 must be clear
• [NODE-3] - On Connect, Node server sends settings twice
• [NODE-4] - Node error "undefined[501]" in LTI