[Changelog] webfleet-connect protocol

omol

We've implemented integration with Webfleet platform via WEBFLEET.connect API as a channel protocol.

omol

We've updated webfleet-connect protocol:

added fetching vehicles information and using it for proper identification of objects from the events (vehicle identnumber is used as device ident)
message type 80000810 now is interpreted as a crash event.

omol

Webfleet connect protocol has been updated.

Default ident has been changed to the following template: objectno:{WEBFLEET OBJECTNO VALUE}. Default ident is set in the messages for which corresponding vehicle is not found or vehicle's ident (identnumber in Webfleet terms) contains characters banned for flespi ident.

omol

omol
Fix: objectuid is used instead of objectno for default ident.

namo

Webfleet-connect protocol is updated.
The following tachograph-related data parameters (msg_class=8) are supported for the protocol:

dt_cardid - flespi parameter tacho.driver.card.code
dt_cardaction - flespi parameters tacho.driver.card.action.enum (numeric value) and tacho.driver.card.action (corresponding string description)
dt_cardtype - flespi parameters tacho.driver.card.type.enum (numeric value) and tacho.driver.card.type (corresponding string description)
dt_slot - flespi parameter tacho.driver.card.slot
dt_state - flespi parameter tacho.driver.card.status (true - driver card is connected, false - disconnected)
event_time - flespi parameter event.timestamp
workstate - flespi parameters tacho.driver.work.state.enum (numeric value) and tacho.driver.work.state (corresponding string description)

YuryAheichyk

Webfleet-connect protocol is updated, added parameters:

rpm - flespi parameter can.engine.rpm
gear - flespi parameter can.gear
fuel_level - flespi parameter can.fuel.volume

YuryAheichyk

Webfleet-connect protocol has been updated: the msg_time parameter is now registered as the send.timestamp flespi parameter. If the message contains the event_time parameter, it will be used as the timestamp flespi parameter. Otherwise, the pos_time parameter will be registered as timestamp.