Notecard Error and Status Codes
Notecard API responses may include one or more error or status codes denoted by
curly braces, e.g. {sync-begin}. These codes are static and persist across API
versions.
note-
The Related APIs column refers to Notecard API requests whose response may contain this code, either as an
errreturned by the request, or as part of thestatusreported by the request. -
This list is a best-effort guide, not an exhaustive guarantee. Some error/status codes could in principle appear in other API responses through indirect code paths in the Notecard firmware.
-
If you encounter a code not on this list, or have any other technical questions, please reach out on the Blues Developer Forum for assistance.
| Code | Definition | Resolution | Related APIs |
|---|---|---|---|
{address-assigned} | Successful DHCP resolution and IP address assigned. | card.wificard.wirelesshub.sync.status | |
{auth} | Notehub unable to authenticate Notecard. | Check accompanying status for more details - if the situation persists contact Blues. | hub.statushub.synchub.sync.status |
{auth-retry} | Notehub authentication failed. System is attempting to retry auth. | Check accompanying status for more details - if the situation persists contact Blues. | hub.statushub.synchub.sync.status |
{bad-bin} | Binary data is corrupted or in an unexpected format. | Check accompanying status for more details - if the situation persists contact Blues. | Any Notecard API request |
{cell-disconnect-begin} | Modem disconnection requested. | card.wirelesshub.sync.status | |
{cell-disconnected} | Modem disconnected. | card.wirelesshub.sync.status | |
{cell-registered} | Wireless service successfully registered. | card.wirelesshub.sync.status | |
{cell-registration-wait} | Waiting for wireless service to be registered. | card.wirelesshub.sync.status | |
{cell-scan} | Connection state reported while cell tower scan results are pending (can take up to 2 minutes). | card.attncard.wirelesshub.sync.status | |
{cell-scan-wait} | Logged while waiting on a cell tower or WiFi scan for triangulation. Each scan is limited to 2 minutes. | card.wirelesshub.sync.status | |
{checkpointed} | Pending Notefile changes have been written from memory to flash storage. This is a normal status, not an error. | file.changesfile.clearfile.deletenote.addnote.changesnote.deletenote.getnote.update | |
{connect-aborted} | Connection attempt was manually aborted. | hub.statushub.synchub.sync.status | |
{connect-failure} | A network connection attempt failed. Reported by the WiFi transport and by the NTN (Starnote) transport. | On WiFi, check the SSID configuration using card.wifi and try re-setting the password. On NTN, see Diagnosing Satellite Connectivity Issues. | card.transportcard.wificard.wirelesshub.sync.statusntn.status |
{connect-ll-failure} | The link to the cellular modem timed out while establishing a data connection. | Notecard retries automatically. If the situation persists, consult Diagnosing Cellular Connectivity Issues. | hub.sync.status |
{connected} | Notecard is connected to the cellular network. | card.transportcard.wificard.wirelesshub.statushub.synchub.sync.statusntn.status | |
{connected-closed} | Notecard has closed its connection to the cellular network. | hub.sync.status | |
{connecting} | Notecard is connecting to the cellular network. | card.transportcard.wificard.wirelesshub.sync.statusntn.status | |
{crc} | CRC check failed, indicating possible data corruption during transport or storage. | Attempt the request again and if the situation persists contact Blues. | Any Notecard API request |
{dead} | A Note cannot be added to an outbound queue because Notecard's power source is in a critically low ("dead") power state. | Restore the power source, or set "allow": true on the request to add the Note anyway. | note.addnote.update |
{device-delay-5}{device-delay-10}{device-delay-15}{device-delay-20}{device-delay-30}{device-delay-60} | Notehub is throttling device connection. Notecard waits roughly [n] minutes before reconnecting. | If the situation persists for > 60 minutes, contact Blues. | hub.statushub.synchub.sync.status |
{device-disabled} | This Notecard has been disabled on Notehub. | Unblock the device using this guide. | hub.statushub.synchub.sync.status |
{dfu-bad-target} | The requested Notecard firmware isn't appropriate for this type of Notecard. | Verify that you are using the correct Notecard firmware binary for the type of Notecard you are using. | card.dfudfu.statushub.sync.status |
{dfu-config-backup} | Failed to backup config prior to switching to the new Notecard firmware. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-dl} | Too many consecutive errors when downloading the firmware image from Notehub. | Re-check the firmware binary on Notehub and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-dl-chunk-length} | Image chunk from Notehub doesn't have the requested length. | Re-check the firmware binary on Notehub and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-dl-md5} | The MD5 of the downloaded firmware image doesn't match the MD5 reported by Notehub. | Verify the Notecard firmware binary matches the MD5 checksum documented in Firmware Releases, then retry the DFU to force a fresh download. | card.dfudfu.statushub.sync.status |
{dfu-ext-chunk} | Error getting a chunk from external storage. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-ext-get-length} | Failed to get the length of the image in external storage. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-ext-length} | The number of bytes actually stored in external storage doesn't match the length of the image according to the metadata from Notehub. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-ext-written} | The number of bytes allegedly written to external storage doesn't match the length of the image according to the metadata from Notehub. "allegedly" because the "actual" length check is done later. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-in-progress} | Notecard device firmware update is in progress. | While a Notecard DFU is in progress the Notecard defers Notehub syncs and rejects note.add/note.template, so a manually-issued hub.sync may appear to do nothing. Wait for the update to finish, checking progress with dfu.status; syncs and Note additions resume automatically once DFU is no longer in progress. | note.addnote.template |
{dfu-int-append} | Appending image bytes to internal storage failed. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-int-chunk} | Error getting a chunk from internal storage. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-int-chunk-length} | Image chunk from internal storage doesn't have the requested length. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-modem-fs} | When using the modem for external storage, failed to use the modem's filesystem. | Attempt the DFU again and if the situation persists contact Blues. | card.wirelesshub.sync.status |
{dfu-not-ready} | Notecard is not yet in a state where DFU can proceed, for example because it is not in DFU operating mode or is still closing a network connection. | Notecard retries on its own. If the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-post-md5} | After booting up new Notecard firmware, the firmware's MD5 is bad. | Verify the Notecard firmware binary matches the MD5 checksum documented in Firmware Releases. | card.dfudfu.statushub.sync.status |
{dfu-pre-md5} | Before switching to the new Notecard firmware, the firmware's MD5 is bad. The image length matched the metadata from Notehub but the contents did not, which usually means the download or the write to flash was corrupted. | Verify the Notecard firmware binary matches the MD5 checksum documented in Firmware Releases. If the MD5 on Notehub is correct, the most common causes are an unstable power supply during the flash write and a cached copy of a bad download. Force a full re-download with {"req":"dfu.status","name":"card","start":true}, or upload the binary to Notehub again under a new filename and point the firmware assignment at the new file. Also confirm the Notecard has a stable power source (ideally USB) for the duration of the update. | card.dfudfu.statushub.sync.status |
{dfu-sig} | The new Notecard firmware image doesn't contain the Notecard firmware signature. | Verify the Notecard firmware binary matches the MD5 checksum documented in Firmware Releases. | card.dfudfu.statushub.sync.status |
{dfu-superseded} | The DFU was interrupted by another type of DFU (e.g. a host DFU superseded a Notecard DFU, or vice-versa). | Verify your DFU process to avoid conflicts. | card.dfudfu.statushub.sync.status |
{dfu-total-length} | The total number of image bytes, meaning both internal and external storage, doesn't match the number of image bytes read from Notehub. | Re-check the firmware binary on Notehub and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{dfu-watchdog} | The DFU process did not advance the work timer quickly enough, triggering a watchdog timeout. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{disconnected} | Notecard is disconnected from the network. | card.transportcard.wificard.wirelesshub.statushub.synchub.sync.statusntn.status | |
{disconnecting} | Notecard is in the process of disconnecting from the network. | card.transportcard.wirelesshub.sync.statusntn.status | |
{env-not-modified} | In response to env.set, indicates environment variables have not been modified. | env.getenv.modified | |
{extended-network-failure} | Modem unable to connect to network after an extended time period and Notecard is in a Network Registration Failure Penalty Box. | Consult our guides on Diagnosing Cellular Connectivity Issues and Understanding Notecard Penalty Boxes. | card.dfucard.wificard.wirelessdfu.statushub.statushub.synchub.sync.status |
{extended-service-failure} | Unable to connect to Notehub after an extended time period and Notecard is in an Inability to Connect to Notehub Penalty Box. | Check the Notehub.io Status Page for updates and consult our guide on Understanding Notecard Penalty Boxes. | card.dfudfu.statushub.statushub.synchub.sync.status |
{file-max} | Triggered when certain Notecard operations enforce a maximum "chunk" size and a specific chunk is larger than expected. | Check accompanying status for more details - if the situation persists contact Blues. | card.tracefile.changesfile.clearfile.deletenote.addnote.changesnote.deletenote.getnote.update |
{file-min} | Triggered when certain Notecard operations enforce a minimum "chunk" size and a specific chunk is smaller than expected. | Check accompanying status for more details - if the situation persists contact Blues. | file.changesfile.deletenote.add |
{file-open} | Notecard filesystem file open error. | Check accompanying status for more details - if the situation persists contact Blues. | card.dfudfu.statusfile.changesfile.deletehub.sync.statusnote.add |
{file-storage-full} | Notecard's filesystem is more than 80% used, so no further Notes may be added. | Notecard must be synced to Notehub before more Notes can be added. | file.changesfile.deletenote.addnote.changesnote.deletenote.getnote.templatenote.update |
{file-write-failure} | A write or flush to Notecard's filesystem failed, which the firmware treats as the filesystem being full. | Notecard must be synced to Notehub before more Notes can be added. | file.changesfile.deletenote.add |
{filesys-reinit} | Notecard filesystem is being reinitialized. | file.changesfile.clearfile.deletenote.addnote.changesnote.deletenote.getnote.update | |
{full} | A Notefile limit was reached: 100 Notes in the Notefile, 100KB of Notes held in memory, or the 80% filesystem limit. | Notecard must be synced to Notehub before more Notes can be added. | file.changesfile.deletenote.addnote.changesnote.deletenote.getnote.update |
{gps} | The current status of GPS connectivity. | card.locationcard.location.modecard.location.track | |
{gps-active} | GPS has started and is currently active. | card.locationcard.location.modecard.location.track | |
{gps-inactive} | GPS is inactive. | card.locationcard.location.modecard.location.track | |
{gps-penalty} | GPS is in a penalty box. | card.locationcard.location.modecard.location.track | |
{gps-sats} | The number of GPS satellites visible by the device. | card.locationcard.location.modecard.location.track | |
{gps-signal} | Information about the current GPS signal strength. | card.locationcard.location.modecard.location.track | |
{gps-starting} | GPS is starting. | card.locationcard.location.modecard.location.track | |
{host-dfu-fatal} | Notecard Outboard Firmware Update was unable to complete. | Check accompanying status for more details - if the situation persists contact Blues. | card.dfu |
{host-retry} | Notecard is retrying a connection attempt. | hub.statushub.synchub.sync.status | |
{host-unreachable} | Unable to connect to Notehub TCP socket. | Check accompanying status for more details - if the situation persists contact Blues. | hub.statushub.synchub.sync.status |
{hub-mode} | The JSON request requires the Notecard to be in a particular hub.set mode. | Check accompanying status for more details - if the situation persists contact Blues. | hub.signal |
{hub-not-connected} | JSON request requires that Notecard be connected to Notehub. | Notecard must be in continuous mode to use this request. | hub.signalhub.statushub.synchub.sync.status |
{idle} | Modem is currently disconnected and idle. | card.wificard.wirelesshub.sync.status | |
{incompatible} | Incompatible JSON request fields. | Check accompanying status for more details - if the situation persists contact Blues. | card.binary.putcard.dfudfu.statushub.sync.statusnote.addnote.template |
{io} | A problem on the I/O channel between the host and Notecard. On its own it means Notecard could not parse the received JSON; it also accompanies the more specific {crc} and {bad-bin} codes. | This is usually due to dropped characters or corruption, host should retry the request. | Any Notecard API request |
{joining-network} | Notecard is in the process of joining a network. | hub.sync.statuscard.wireless | |
{memory} | Notecard was unable to allocate memory to complete the request. | Retry the request. If the situation persists contact Blues. | Any Notecard API request |
{modem-off} | Wireless modem is off. | card.wificard.wirelesshub.sync.status | |
{modem-on} | Wireless modem is on. | card.wificard.wirelesshub.sync.status | |
{modem-power-failure} | Insufficient battery current available for power-on of modem and Notecard is in an Insufficient Power Supply Penalty Box. | Check the Notecard datasheet for power requirements and consult the guide on Understanding Notecard Penalty Boxes. | card.locationcard.location.modecard.location.trackcard.wirelesshub.sync.status |
{net-init} | Wireless network interface is initializing. | card.wirelesshub.statushub.sync.status | |
{network} | General wireless connectivity error. | Check accompanying status for more details - if the situation persists contact Blues. | card.dfucard.transportcard.wificard.wirelessdfu.statushub.statushub.synchub.sync.statusntn.status |
{network-error-wait} | Waiting to retry after a network error. | hub.sync.status | |
{network-timeout} | Network connection timed out. | hub.statushub.synchub.sync.status | |
{network-up} | Successfully connected to a network. | card.attncard.wificard.wirelesshub.sync.status | |
{no-address} | Notecard WiFi is unable to obtain IP address from access point. | Try re-setting the password using card.wifi or SoftAP feature. | card.wificard.wirelesshub.sync.status |
{no-changes} | Indicates a sync was performed, but no new changes were detected to process. | hub.statushub.synchub.sync.status | |
{no-handler} | Notehub internal error. | Check accompanying status for more details - if the situation persists contact Blues. | hub.synchub.sync.status |
{no-mojo} | Making a card.power request without an attached Mojo. | card.power | |
{no-ntn-module} | An external NTN (Non-Terrestrial Network) module (e.g. Starnote) is not detected. This code is also returned when an NTN request is made on a Notecard that already has integrated NTN — such as a Notecard for Skylo. | If you are using an external module, verify the Starnote is paired with the Notecard in the Notecarrier. If your Notecard has integrated NTN, do not attach an external module — use the Notecard's built-in satellite connectivity instead. | ntn.gpsntn.resetntn.status |
{no-session} | There is no active Notehub session when one is currently required. | Verify a successful connection with Notehub and retry request. | card.transporthub.synchub.sync.status |
{no-status} | No status information returned from a request to a connected NTN device. | Check accompanying status for more details - if the situation persists contact Blues. | ntn.status |
{no-time} | The network time has not been set or synchronized on Notecard. | Perform a sync with Notehub to set the time. | card.time |
{normal} | No abnormal condition to report. card.status always reports this status. | card.status | |
{not-connected} | Notecard is not connected to a network. | card.transportcard.wificard.wirelesshub.statushub.synchub.sync.statuswebweb.deleteweb.getweb.postweb.put | |
{not-encrypted} | A note.get request set "decrypt": true, but the Note's body is not encrypted. | Only request decryption for Notes that were added with encryption. | note.get |
{not-implemented} | Requested feature is not yet implemented. | Check accompanying status for more details - if the situation persists contact Blues. | Any Notecard API request |
{not-ready} | Notecard is not ready for the requested operation. | Check accompanying status for more details - if the situation persists contact Blues. | Any Notecard API request |
{not-supported} | Request not supported due to Notecard hardware or incompatible with existing Notecard configuration. | Verify Notecard hardware and settings. If the situation persists contact Blues. | Any Notecard API request |
{note-exists} | A Note with the specified Note ID already exists in the Notefile. | Use a different Note ID, or update the existing Note with note.update. | file.changesfile.deletenote.addnote.changesnote.deletenote.getnote.update |
{note-max} | The number of Notes in the Notefile has reached the max value specified on a note.add request. | Reduce the number of Notes in the Notefile (by syncing, or by deleting Notes with note.delete), or increase the max value. | note.add |
{note-noexist} | Action cannot be performed on a Note that doesn't exist. | Validate that the Note exists before performing this action. | note.changesnote.deletenote.getnote.update |
{note-paused} | The _note_pause environment variable is set on Notehub to prevent a possible runaway device. | If device is not in runaway mode, delete this environment variable on Notehub. | note.addnote.templatenote.updatevar.set |
{notefile-bad-name} | Invalid Notefile name (e.g. may be using a reserved character). | Be sure the Notefile name does not include ,, contains exactly one ., and ends in a recognized type such as .qo, .qos, .qi, .qis, .db, or .dbs. | file.changesfile.clearfile.deletenote.addnote.changesnote.deletenote.getnote.update |
{notefile-exists} | Cannot add a new Notefile that already exists. | Use a different name for the Notefile you are trying to create. | file.changesfile.clearfile.deletenote.addnote.changesnote.deletenote.getnote.update |
{notefile-in-use} | Cannot delete a Notefile that is currently in use. | Wait for the current action on the Notefile to complete. | file.changesfile.clearfile.deletenote.addnote.changesnote.deletenote.getnote.update |
{notefile-noexist} | Action cannot be performed on a Notefile that doesn't exist. | Validate that the Notefile exists before performing this action. | env.getenv.modifiedenv.setfile.changesfile.clearfile.deletehub.sync.statusnote.addnote.changesnote.deletenote.getnote.updatevar.deletevar.getvar.setwebweb.deleteweb.getweb.postweb.put |
{notefile-queue-disallowed} | Specified operation not allowed on queue Notefiles. | Contact Blues for assistance. | file.changesfile.deletenote.addnote.changesnote.deletenote.getnote.update |
{notehub-connected} | Successfully connected to Notehub. | hub.statushub.synchub.sync.status | |
{notehub-disconnected} | Successfully disconnected from Notehub. | hub.statushub.synchub.sync.status | |
{notehub-open-failure} | General error while opening Notehub. | Check accompanying status for more details - if the situation persists contact Blues. | hub.statushub.synchub.sync.status |
{ntn} | Appended to the wireless registration status on a Notecard with integrated NTN (satellite) connectivity, for example {cell-registered}{ntn}. | card.statushub.statushub.sync.status | |
{ntn-connect-failure} | NTN module (Starnote) was unable to establish a connection to a satellite. Also reported when the Notecard has not yet synced with Notehub to negotiate the information needed for secure satellite communication. | Confirm the Notecard has completed at least one sync over cellular or WiFi, that the satellite antenna specified for your Starnote variant is fully seated and has a clear view of the sky, and that the device has adequate power during transmit. See Diagnosing Satellite Connectivity Issues. | card.transportcard.wirelesshub.sync.statusntn.status |
{ntn-connected} | NTN module (Starnote) has established a connection. | card.transportcard.wirelesshub.sync.statusntn.status | |
{ntn-connecting} | NTN module (Starnote) is establishing a connection. | card.transportcard.wirelesshub.sync.statusntn.status | |
{ntn-disconnecting} | NTN module (Starnote) is closing a connection. | card.transportcard.wirelesshub.sync.statusntn.status | |
{ntn-downlinking} | NTN module (Starnote) is actively receiving data over satellite. | ntn.status | |
{ntn-gps} | The NTN module's (Starnote's) own GPS is enabled. | ntn.gpsntn.status | |
{ntn-idle} | NTN module (Starnote) is powered but not actively communicating. | card.transportcard.wirelesshub.sync.statusntn.status | |
{ntn-initializing} | NTN module (Starnote) is initializing. | card.transportcard.wirelesshub.sync.statusntn.status | |
{ntn-need-location} | NTN module (Starnote) requires a location before it can transmit and does not yet have one. | Give the device a clear view of the sky so GPS can acquire a fix, or use ntn.gps to switch which GPS is used. | ntn.gpsntn.status |
{ntn-power} | NTN module (Starnote) is powered up and available. | card.transportcard.wirelesshub.sync.statusntn.status | |
{ntn-unknown-location} | NTN module (Starnote) is unable to acquire its location, either via its internal GPS or via its paired Notecard's GPS (depending on its configuration). | Use the ntn.gps API to switch between using Starnote's or Notecard's GPS. | ntn.gpsntn.status |
{ntn-uplinking} | NTN module (Starnote) is actively transmitting data over satellite. | ntn.status | |
{odfu-aux-mode} | Current AUX mode isn't compatible with using Notecard Outboard Firmware Update to update the host MCU via AUX. | Consult the Notecard Outboard Firmware Update docs to verify the proper card.aux request is in use. | card.dfudfu.statushub.sync.status |
{odfu-fail} | Failed to use Notecard Outboard Firmware Update to update the host MCU. | Attempt the DFU again and if the situation persists contact Blues. | card.dfudfu.statushub.sync.status |
{odfu-init} | Notecard Outboard Firmware Update feature initializing. | card.dfu | |
{port-in-use} | The port specified on a note.template request is already assigned to a different Notefile. | Choose an unused port number, or reuse the Notefile that already owns it. | note.template |
{product-noexist} | ProductUID does not exist. | Check that the Notehub project has a valid ProductUID. | hub.sethub.statushub.synchub.sync.status |
{receive-limit} | An inbound serial request exceeded Notecard's UART receive buffer. | Send a smaller request, or use card.binary for large payloads. | Any Notecard API request over serial |
{receive-timeout} | The most recent Notehub transaction timed out. | Check accompanying status for more details - if the situation persists contact Blues. | hub.synchub.sync.status |
{registration-failure} | Cellular Notecard unable to register with network. | Consult our guide on Diagnosing Cellular Connectivity Issues. | card.wirelesshub.sync.status |
{request-failure} | The Notecard sent a malformed or invalid request during a Notehub transaction (e.g. an invalid response message type or a request rejected by Notehub). | Check accompanying status for more details - if the situation persists contact Blues. | hub.statushub.synchub.sync.status |
{rts-not-necessary} | Request to Send (RTS) not required in current context. | card.aux.serial | |
{service} | General connectivity error reaching the Notehub service (e.g. Notecard could not resolve or reach a Notehub host). | Check accompanying status for more details - if the situation persists contact Blues. | card.dfudfu.statushub.statushub.synchub.sync.status |
{session-closed} | Notehub session is closed. | Check accompanying status for more details - if the situation persists contact Blues. | hub.statushub.synchub.sync.status |
{socket-closed-session} | TCP socket closed the session. | hub.sync.status | |
{socket-connect-error} | Unable to connect to Notehub socket handler. | If the situation persists contact Blues. | hub.sync.status |
{socket-connected} | Connection to Notehub service successful. | hub.sync.status | |
{socket-connecting} | Connecting to Notehub service. | hub.sync.status | |
{socket-disconnected} | Remote service has been disconnected. | hub.sync.status | |
{socket-dns-failure} | Unable to resolve Notehub IP address. | If the situation persists contact Blues. | hub.sync.status |
{socket-dns-success} | DNS lookup of Notehub service successful. | hub.sync.status | |
{socket-invalid-cert} | Invalid TLS/SSL certificate detected. | If the situation persists contact Blues. | hub.sync.status |
{socket-ip-init} | Network socket IP initialized. | hub.statushub.synchub.sync.status | |
{socket-ip-term} | TCP socket terminated IP address. | hub.statushub.synchub.sync.status | |
{socket-open-session} | Opening a session to Notehub service. | hub.sync.status | |
{socket-opened-notification-session} | Opening network notification socket. | hub.sync.status | |
{socket-opened-session} | Network socket session opened. | hub.sync.status | |
{socket-tls} | TLS successfully authenticated. | hub.sync.status | |
{socket-tls-connected} | Network socket connected over TLS. | hub.sync.status | |
{socket-tls-connecting} | Network socket connecting over TLS. | hub.sync.status | |
{socket-tls-error} | Unable to authenticate with Notehub socket handler. | Can occur sporadically in poor signal conditions - if the situation persists contact Blues. | hub.sync.status |
{softap} | JSON request not supported while Notecard WiFi is in SoftAP mode. | Press the SoftAP button, complete WiFi setup, or wait 5 minutes for SoftAP mode to time out automatically. | Any Notecard API request |
{suppress-rsp} | Request was processed successfully, but the operation is intentionally configured to not generate a response. | Any Notecard API request | |
{sync} | General sync status information (check accompanying status). | hub.sync.status | |
{sync-begin} | A sync with Notehub service is starting. | hub.sync.status | |
{sync-completed} | Data synchronization with Notehub completed successfully. | hub.sync.status | |
{sync-disconnecting} | Disconnecting a partially-opened session (likely was used by GPS). | hub.sync.status | |
{sync-end} | A sync with Notehub service has completed. | hub.sync.status | |
{sync-error} | An error occurred during sync with Notehub. | Check accompanying status for more details - if the situation persists contact Blues. | hub.sync.status |
{sync-get-local-changes} | Retrieving local (outbound) Notefile changes. | hub.sync.status | |
{sync-get-remote-changes} | Retrieving remote (inbound) Notefile changes. | hub.sync.status | |
{sync-local-error} | Potential local filesystem corruption. | If the situation persists reset filesystem with card.restore. | hub.sync.status |
{sync-remote-error} | Unable to merge Notefile changes on Notehub. | If the situation persists contact Blues. | hub.sync.status |
{syntax} | Syntax error in JSON request. | Verify request with Notecard API reference. | Any Notecard API request |
{template} | Notefile template-related status (check accompanying status). | card.location.trackcard.motion.trackhub.lognote.add | |
{template-incompatible} | note.add operation is incompatible with Notefile template. | Refer to the Note Template guide for assistance. | card.location.trackcard.motion.trackhub.lognote.add |
{ticket} | Transient error due to Notehub being restarted as part of update. | Check accompanying status for more details - if the situation persists contact Blues. | hub.statushub.synchub.sync.status |
{time-unavailable} | The request needs the current time, and Notecard has not yet acquired it. | Perform a sync with Notehub to set the time. | card.usage.getcard.voltage |
{tracker-exists} | Cannot add a new tracker that already exists. | Contact Blues for assistance. | file.changesfile.deletenote.addnote.changesnote.deletenote.getnote.update |
{tracker-noexist} | Action cannot be performed on a tracker that doesn't exist. | Contact Blues for assistance. | file.changesfile.deletenote.addnote.changesnote.deletenote.getnote.update |
{transport} | General transport status information (check accompanying status). | card.wirelesshub.sync.status | |
{transport-unreachable} | Unable to attempt a connection to Notehub. | Check accompanying status for more details - if the situation persists contact Blues. | hub.statushub.synchub.sync.status |
{unavailable} | Requested resource or service is unavailable. | If the situation persists contact Blues. | card.transportcard.wificard.wirelesshub.sync.statusntn.status |
{usb-disabled} | USB is disabled. | card.voltage | |
{usb-enabled} | USB is enabled. | card.voltage | |
{version} | Notecard's firmware build number is lower than the minimum build number the card.version request asked for. | Update the Notecard firmware, or lower the minimum build number your host requires. | card.version |
{wait-data} | Notecard has joined the wireless network and is waiting on the data connection (e.g. IP session) to become available. | card.wirelesshub.statushub.sync.status | |
{wait-gateway} | Notecard is waiting for WiFi or cellular gateway connection. | card.wirelesshub.statushub.sync.status | |
{wait-module} | Notecard is starting communications with the wireless module. | card.wirelesshub.statushub.sync.status | |
{wait-service} | Notecard is waiting for the wireless network service itself (e.g. cellular registration or WiFi association) to become available, prior to acquiring a data connection. | card.wirelesshub.statushub.sync.status | |
{web-payload} | Payload corruption was detected during a web request operation. | Check the host-to-Notecard connection integrity. | hub.statushub.synchub.sync.status |
{wifi-ap} | Notecard WiFi was not able to detect the configured SSID. | Check the current SSID with card.wifi and verify Notecard is within range of access point. | card.wificard.wirelesshub.sync.status |
{wifi-auth} | Notecard WiFi connection failed, most likely due to incorrect password. | Use card.wifi or SoftAP mode to configure the SSID and password. | card.wificard.wirelesshub.sync.status |
{wifi-config} | Notecard WiFi does not have an SSID configured. | Use card.wifi or SoftAP mode to configure the SSID and password. | card.wificard.wirelesshub.sync.status |
{wifi-disconnect-begin} | Notecard WiFi is disconnecting session. | card.wificard.wirelesshub.sync.status | |
{wifi-disconnected} | Notecard WiFi is disconnected. | card.wificard.wirelesshub.sync.status | |
{wifi-error} | Unspecified Notecard WiFi error. | Check accompanying status for more details - if the situation persists contact Blues. | card.wificard.wirelesshub.sync.status |
{wifi-fatal} | Unable to communicate with Notecard's WiFi module (possible hardware error). | If the situation persists contact Blues. | card.wificard.wirelesshub.sync.status |
{wifi-join-wait} | Notecard WiFi is waiting to join network. | card.wificard.wirelesshub.sync.status | |
{wifi-joined} | Notecard WiFi has joined network. | card.wificard.wirelesshub.sync.status | |
{wifi-softap} | Notecard is operating in WiFi soft access point mode. | card.wifi | |
{wifi-unavailable} | Use of card.wifi request on a Notecard that does not have WiFi hardware. | Only use this request on a Notecard with WiFi capabilities. | card.wifi |
