Currently there are 8 categories of events generated by the platform:
Alarm (
alarm)Command Result (
commandResult)Geofence (
geofenceEnter,geofenceExit)Ignition (
ignitionOn,ignitionOff)Maintenance (
maintenance)Motion (
deviceMoving,deviceStopped)Overspeed (
deviceOverspeed)Status (
deviceOnline,deviceOffline)
To forward those events to your own system / backend see https://powunity.atlassian.net/wiki/spaces/BTAPI/pages/163348682/BikeTrax+API#Webhook-Integration
...
This type of event generated when a new position contains the alarm attribute. The device emits these alarms when it has been armed.
Command Result
Answers on commands (like arm / disarm) are stored in the result attribute. The platform generates this type of event if the position contains the result attribute.
...
This event is generated if device started or stopped moving. If the reported speed is more than 2km/h BikeTrax is considered moving, and if speed is less than that BikeTrax is considered to have stopped.
| Note |
|---|
Currently, if there is no ignition status because there is no external power supply or the supply is not turned on, then there will be several stops recorded during a given bike ride. |
Overspeed
The server generates this event if device exceeds the configured speed limit. Speed limit value can be set via the device or group attribute speedLimit.
...
The server generates this event type when device status changes (online/offline/unknown). Online means that BikeTrax is connected to the server and sending reports. Offline means that BikeTrax is not connected to the server, or did not send anything in the past 3 minutes.
...