- HARDWARE
- NETWORK
- ACTION
- LOGS
Short answer
Why are my IoT devices showing as offline?
Your AI checks device health and runs network diagnostics to find the break in the chain. You'll see if the issue is the hardware or the cellular connection. This breakdown shows you exactly where the fault lies.
Diagnostic outcomes
Where every issue lands.
The AI categorizes its findings into these four areas.
HARDWARE
Device status reports
The AI identifies if a device is powered down or physically damaged. You get a clear list of specific hardware states.
NETWORK
Connectivity failures
The AI pinpoints where the signal dropped. You'll see if the issue is local interference or a carrier outage.
ACTION
Manual fixes needed
When the AI hits a wall, it tells you what a human needs to do on-site. This prevents wasted time on remote fixes that won't work.
LOGS
Error summaries
The AI pulls relevant error codes from the connection attempt. You get a clean summary of why the handshake failed.
The workflow
What your AI does when a device goes dark.
The AI moves from simple status checks to deep network analysis.
Check device health
The AI pulls the latest telemetry to see if the device is responding to the network.
get_device_statusAnalyze the signal
If the device is active but unreachable, the AI looks for specific network faults.
diagnose_connectivityIsolate the fault
The AI compares device status against network health to see if the problem is the hardware or the carrier.
get_device_statusdiagnose_connectivityFlag human intervention
The AI identifies issues like physical tampering or local power loss that it cannot fix remotely.
get_device_status
Try it
Copy these to start.
Use these prompts to kick off your troubleshooting.
Starting points
Swap out the device IDs or names for your actual AT&T IoT identifiers.
AT&T IoT Connector
You're all set. Choose your MCP client and follow the setup instructions.
https://edge.vinkius.com/vk_preview_YFstwCIlx1nPc9O3GzBKiwQJk2qplbw9H9PNBDuZ/mcpClaude Desktop
Follow the steps below to connect in seconds.
- 1In Claude Desktop, open Settings → Connectors.
- 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
- 3Click Add and start a new chat — AT&T IoT capabilities are ready to use.
{
"mcpServers": {
"att-iot-mcp": {
"url": "https://edge.vinkius.com/vk_preview_YFstwCIlx1nPc9O3GzBKiwQJk2qplbw9H9PNBDuZ/mcp"
}
}
}Check the status of device ID 99283 and tell me why it's offline.
Run a connectivity diagnosis on the sensor group in the Chicago warehouse.
Which devices in my AT&T IoT fleet are currently showing signal interference?
List all devices that have failed their last three connectivity checks.
Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline
Start here
Connect AT&T IoT once, then ask.
Just link your account once. Your credentials stay encrypted, and you can immediately start asking questions about your fleet.
Connect AT&T IoT to your AIFAQ
How this task behaves.
- 01
Can the AI fix the connection for me?
No. The AI identifies the problem, but you must perform the physical or configuration changes yourself.
- 02
Can the AI change my device settings?
No. The tools only allow the AI to read status and diagnose connectivity; it cannot push new configurations to your hardware.
- 03
Does the AI see my login credentials?
No. Your login stays encrypted and is never visible to the AI or the Vinkius platform.
- 04
How does it know if a device is offline?
It uses the get_device_status tool to check the real-time state reported by the AT&T network.
- 05
Can it tell the difference between a dead battery and a bad signal?
Yes, by comparing the device status with the results of a connectivity diagnosis.
More questions about AT&T IoT? The Connector page answers them. See everything the AT&T IoT Connector can do
Connect AT&T IoT to Claude, Cursor, ChatGPT & more
