Skip to content

Commit 766fc46

Browse files
kbeaugrandCopilot
andauthored
Update specs/001-device-status/spec.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent 5448d25 commit 766fc46

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

specs/001-device-status/spec.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99

1010
### User Story 1 - View Device Status Without Confusion (Priority: P1)
1111

12-
Non-technical users need to view their device list without being confused by misleading status indicators. Currently, LoRaWAN devices that send data infrequently (every 30 minutes to 24 hours) appear as "disconnected" most of the time because the Connection State column only shows "connected" when there's an active connection to IoT Hub. This causes users to think devices are malfunctioning and generates unnecessary support requests.
12+
Non-technical users need to view their device list without being confused by misleading status indicators. Currently, LoRaWAN devices that send data infrequently (every 30 minutes to 24 hours) appear as "disconnected" most of the time because the Connection State column only shows "connected" when there's an active connection to the configured cloud IoT service (for example, Azure IoT Hub or AWS IoT Core). This causes users to think devices are malfunctioning and generates unnecessary support requests.
1313

1414
**Why this priority**: This is the core problem causing user confusion and unnecessary support overhead. Removing the misleading Connection State column immediately solves the primary pain point.
1515

0 commit comments

Comments
 (0)