Enrollment QR codes can now carry the venue WiFi and the details a tablet's setup screens show, and each configuration can set the tablet's screen timeout.
Highlights
ProvisioningEnrollment QR codes from the fleet API can carry the venue WiFi, and the password is never stored.
ProvisioningQR codes carry the organization, the tablet's name, the logo, support contacts and an optional setup label for the setup screens.
AdminEach configuration can set the screen timeout, and new organizations start at 5 minutes.
Provisioning
NewProvisioningEnrollment QR codes created through the fleet API can carry the venue WiFi network, so the tablet joins it during setup. WPA and WPA2 Personal, WEP and open networks are supported; enterprise (EAP) networks are not. The password is written into the QR code only and is never stored or logged.
NewProvisioningEnrollment QR codes now carry what the tablet's setup screens show: the tablet's name, the organization's name and logo, and its support phone and email. This applies to QR codes from the fleet API and from the admin.
NewProvisioningThe fleet API accepts an optional one-line setup label of up to 120 characters, for example a tablet's pack, role and event, which the setup screens show under the title. The label is not stored.
ImprovedProvisioningQR codes stay small enough to scan. If the setup details would make a code too large, the least important ones are left out, the logo first. Print or show enrollment QR codes at least 13 cm wide.
Admin
NewAdminEach configuration can set how long the tablet's screen stays on without a touch, from 10 seconds to 24 hours, in the admin. Cloning a configuration copies the setting, and a configuration without one leaves the tablet's own setting alone.
NewAdminA new organization's default configuration starts with a 5-minute screen timeout. Existing configurations are unchanged.
The first release of the Nemeo server: organizations, configurations for each tablet role, enrollment with one QR code scan, notices, releases and a status history for every tablet.
Highlights
AdminEach organization has its own tablets, configurations, contact details and logo, managed in the admin.
ProvisioningEnrollment QR codes work only once and expire after a set time. Scanning one connects a tablet to its organization.
Device APIEvery request a tablet makes is signed with the tablet's own key, and the configuration the server sends back is signed too.
Device APITablets switch to an organization's backup hosts when a venue network blocks the main address.
Fleet APIA fleet API lets a partner system, such as Lumieos, list, clone and edit configurations, move tablets between them and create enrollment QR codes.
NoticesSend a notice to every tablet in an organization, to one configuration, to one role or to chosen tablets, and see how many tablets received and acknowledged it.
ReleasesLauncher and app releases are published to a release channel, and tablets install new versions from it.
OperationsA status history records each tablet's battery, network, last known location when location access is allowed, kiosk state and, where enabled during setup, which app is on screen, every 5 minutes by default. It is kept for 21 days by default, and InnovAlda can switch it off for an organization on request.
Fleet API
FixFleet APIMoving a tablet to another configuration now reaches the tablet within seconds. This covers moving one tablet, a bulk assignment, a move in the admin, a change of the organization's default configuration and deleting a configuration. Before, the tablet noticed only at its next regular check-in, up to 15 minutes later.
ImprovedFleet APIA configuration edit that changes nothing now leaves the configuration as it was: no new revision, and no tablets asked to download it again.
