Add the device.changed_api_heartbeat_state_on__date term to the model

src/balena-model.ts

@@ -682,6 +682,7 @@ export interface Device {
 		id: Types['Serial']['Read'];
 		actor: { __id: Actor['Read']['id'] } | [Actor['Read']];
 		api_heartbeat_state: 'online' | 'offline' | 'timeout' | 'unknown';
+		changed_api_heartbeat_state_on__date: Types['Date Time']['Read'] | null;
 		uuid: Types['Text']['Read'];
 		local_id: Types['Short Text']['Read'] | null;
 		device_name: Types['Short Text']['Read'] | null;
@@ -786,6 +787,7 @@ export interface Device {
 		id: Types['Serial']['Write'];
 		actor: Actor['Write']['id'];
 		api_heartbeat_state: 'online' | 'offline' | 'timeout' | 'unknown';
+		changed_api_heartbeat_state_on__date: Types['Date Time']['Write'] | null;
 		uuid: Types['Text']['Write'];
 		local_id: Types['Short Text']['Write'] | null;
 		device_name: Types['Short Text']['Write'] | null;

src/balena.sbvr

@@ -374,6 +374,9 @@ Term: device
 		Necessity: each device has exactly one api heartbeat state
 		Definition: "online" or "offline" or "timeout" or "unknown"
 
+	Fact type: device [changed api heartbeat state on] date
+		Necessity: each device [changed api heartbeat state on] at most one date.
+
 	Fact type: device has env var name
 		Term Form: device environment variable
 		Database Table Name: device environment variable
@@ -451,7 +454,7 @@ Fact type: user (Auth) has public key
 -- user public key
 
 Fact type: user public key has title
-    Necessity: each user public key has exactly one title
+	Necessity: each user public key has exactly one title
 
 
 -- application type

src/features/device-heartbeat/index.ts

@@ -250,7 +250,7 @@ export class DeviceOnlineStateManager extends EventEmitter<{
 
 		try {
 			// patch the api_heartbeat_state value to the new state...
-			const body = {
+			const baseBody = {
 				api_heartbeat_state: newState,
 			};
 			await api.resin.patch({
@@ -259,10 +259,17 @@ export class DeviceOnlineStateManager extends EventEmitter<{
 				id: deviceId,
 				options: {
 					$filter: {
-						$not: body,
+						$not: baseBody,
 					},
 				},
-				body,
+				body: {
+					...baseBody,
+					// Since the heartbeat manager is the only place that we update the heartbeat state
+					// we are updating the heartbeat's change date in here rather than a hook, so that
+					// we can avoid the extra DB request that a generic hook would require for checking
+					// whether the value actually changed or not.
+					changed_api_heartbeat_state_on__date: Date.now(),
+				},
 			});
 		} catch ($err) {
 			err = $err;

src/migrations/00093-device-last-api-heartbeat-state-change-event.sql

@@ -0,0 +1,2 @@
+ALTER TABLE "device"
+ADD COLUMN IF NOT EXISTS "changed api heartbeat state on-date" TIMESTAMP NULL;

src/translations/v7/v7.sbvr

@@ -379,6 +379,9 @@ Term: device
 		Necessity: each device has exactly one api heartbeat state
 		Definition: "online" or "offline" or "timeout" or "unknown"
 
+	Fact type: device [changed api heartbeat state on] date
+		Necessity: each device [changed api heartbeat state on] at most one date.
+
 	Fact type: device has env var name
 		Term Form: device environment variable
 		Database Table Name: device environment variable