One dedicated portal account is all it takes: SmartTile reads every Instant On site's switches, access points, ports, PoE, clients, SSIDs and the portal's own alerts, and turns a device going offline into the same alert and ticket as any other outage.
Instant On is built for sites without a network engineer on hand — and it has no official API, no SNMP and no CLI in cloud mode. So a 1930 switch at a branch goes dark and nobody hears about it until the phones stop. SmartTile signs in to the Instant On cloud the way the portal does, reads only, and puts every site next to your circuits and firewalls, with the ticket in the IT Service Management (ITSM) system you already use.
Sites, then each site's inventory: 1830 / 1930 / 1960 switches and AP11–AP25 access points with serial, MAC, model, IP, firmware, uptime and client count.
Online, offline, or reachable-but-busy (firmware update, reboot) per device from the cloud. Adjustable 30–3,600 s. A device missing from its site's inventory for 3 two-minute periods is offline.
Map an Instant On device to its SmartTile device (ping off) and the portal owns its up/down: DOWN with state history, then the normal alert and auto-ticket after 14 min offline.
Every switch port (link state, PoE delivered, total watts) and every AP radio, the uplink device, and a “firmware update available” flag per device.
The portal's site health and reason, wired / wireless clients, 24-hour traffic, and the portal's own alert feed — raised and cleared times kept.
Wired and wireless clients every 10 minutes (SSID, VLAN, signal, band, OS, the AP or switch they are on) and every SSID with its security and client count.
| Field | Where it comes from |
|---|---|
| Portal e-mail | The dedicated account you invited |
| Password | Set when that invitation was accepted |
| Authenticator key | Account → Security → two-step verification → Copy key (base32 or otpauth:// link) |
| Auto re-login | On by default |
sso …/aio/api/v1/mfa/validate/fullsign in (answers the 2FA challenge with a generated code)sso …/as/token.oauth2PKCE code exchange and refresh — the portal's own session renewal/sitesthe sites the account can see; also the Test call/sites/{id}/inventoryswitches + APs: status, ports, PoE, radios, firmware/sites/{id}/landingPage · /alertsSummarysite health, client counts, 24 h traffic/sites/{id}/alertsthe portal's alert feed/sites/{id}/clientSummarywired + wireless clients/sites/{id}/networksSummarySSIDs/sites/{id}/administration · /timezone · /maintenanceportal accounts, time zone, maintenance window (nightly)Every Instant On API call is a GET. SmartTile never turns two-step verification off; it generates the 6-digit code from the stored key only when HPE asks for one.
Password and authenticator key are encrypted AES-256-GCM — the key under a separate encryption key — each bound to your tenant. Neither is ever returned by the API or shown again.
If sign-in fails (bad password, key rejected, locked, HPE changed the sign-in) the account shows connection broken, your admins are e-mailed once, and retries back off from 5 minutes to 6 hours.
Every request is scoped to your organization; changes need an admin. Each account has Active / Paused, and the integration and its 2FA support each have an on/off switch plus a server kill switch.
| Objection | Answer |
|---|---|
| “We will not turn two-factor off.” | You do not have to. Paste the authenticator key once; SmartTile answers the code itself. |
| “Will SmartTile push firmware?” | No. Instant On has no upgrade API. SmartTile flags an available update, and with FirmwareAutomate tickets, schedules and verifies it — the update is applied from the portal. |
| “HPE could change the portal.” | Then the account shows connection broken with the reason, admins are e-mailed, and Run diagnostics lists every endpoint's status code (never values) for support. |