FlowFuse / FlowFuse/device-agent

Device status in the platform is often out of step

Open
#231 0 comments 0 reactions 0 assignees View on GitHub
needs-triage size:XS
Dominant language
JavaScript
Stars
20
Forks
10
Avg merge
9d 4h
Merged PRs (30d)
9

Description

### Current Behavior

Device status changes are not immediately transmitted to FF upon occurrence. For example, when device agent is SIGTERM'd the status is left shown as "running" on the platform.

e.g. In nr-launcher, when the process exits, we immediately get updated status however the device agent does not have the same tight integration and requires the agent `checkin` procedure to update the platform

### Background

Somewhat related to https://github.com/FlowFuse/device-agent/issues/230 once the device agents launcher and nr-launcher have better parity on audit logging, we will see discrepancies between status and the audit log. For example, the device status will show "running" but the audit log will show "crashed" or "stopped"

### Expected Behavior

Device Agent would ideally call `checkin` when state changes, especially upon start, stop, restart & crash to provide more accurate state info to the platform

### Steps To Reproduce

run device agent, kill device agent, see state as "running"

### Environment

- FlowFuse version: 2.x

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.