Runs ping on the Core against an address you choose and returns the device output. Use it to prove that a Core can reach a specific host on the customer network or on the internet — a camera, a gateway, a DNS server, an NVR. To check the Core's connection to Lumana itself use POST /v1/troubleshooting/cores/connectivity-test, which pings a fixed Lumana host and needs no address. The command is published to the Core and the HTTP response is held open until the device answers. On success the body is the device's own output merged with sessionId and state. state is a NUMBER, not a word - 0 completed, 1 the device did not answer in time, 2 the device reported an error, 3 the command was not sent because the Core was out of sync. A call that times out answers 408 with { message, state: 1, responseBody } and carries NO sessionId and no device output. The shape of the device output depends on the Core software version and is passed through untouched, so treat it as free-form diagnostic data rather than a fixed schema.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
The request body is invalid. The response names the field to correct.
Unauthorized. Missing or invalid credentials.
No such Core in this organization. Returned both for a Core id that does not exist and for one that belongs to another organization.
The Core did not answer within 120 SECONDS, after which the call answers 408 Request Timeout and the command may still complete on the device. The body is { message: "Request Timeout", state: 1, responseBody } — no sessionId and no device output. This usually means the device is offline or has lost its connection to Lumana.
The diagnostic could not be dispatched, or the Core answered with an error. The body carries state: 2 (error) and the device message when there is one.