Operations and Fleet
Configure startup, remote access, per-reader dashboard access and updates that preserve identity.
Start on boot
For a standalone installation, add the StreamZet start.sh call to /cust/start on the qualified R660. Preserve OEM lines and back up the original. In SDK mode the product calls stz_product_start, so a separate start.sh boot hook is unnecessary.
# Standalone mode: add once to the OEM-approved startup hook
/mnt/spp/streamzet-jci/start.shSend commands to multiple readers
- In Fleet select Linux and sh · xSpan / embedded.
- Select readers individually or use Select all. Eligible online devices controlled by the current account are targeted.
- Run the command and review pending, running, completed, failed or expired state and output per reader.
printf 'FLEET_CHECK_OK\n'
uname -m
uptimeOpen the RFID dashboard
Use Open xSpan dashboard in the device list or terminal to open the original OEM UI in a new tab. Sign in with the OEM administrator account. The dashboard can be used alongside the terminal.
Web connections expire after 30 minutes and can be ended immediately with Close dashboard. Long-inactive tabs may need reopening. A shared URL alone does not grant access from another browser.
Execution limits
| Item | Limit |
|---|---|
| Terminal | One per reader, up to 30 minutes per session |
| Concurrent commands | Up to two per reader |
| Command length | 4,096 UTF-8 bytes |
| Command timeout | 100–120,000 ms; current Fleet UI uses 30,000 ms |
| Output | 65,536 bytes combined stdout/stderr; truncation is reported |
| Queue polling | Approximately every 30 seconds |
Update and remove
- Verify new artifact checksums and back up the current engine and startup configuration.
- Stop only StreamZet and confirm it has exited. Stopping the engine closes its remote terminal, so use the OEM deployment path for replacement.
- Replace only the engine and required CA/scripts. Preserve state/, registration.key, device name and ownership.
- Restart and confirm the same device UUID returns online. Restore the backed-up executable if needed.
To remove the integration, stop StreamZet and remove only its startup hook. Keep identity state if reinstalling. When retiring a reader, have an administrator revoke that device’s server-side credentials and securely remove local secrets.