Environment State

The system continuously monitors key components to ensure stable operation. Each check runs automatically and reports a status that reflects the current state of the system. By reviewing these results, you can quickly identify setup issues, connectivity problems, or performance degradation before they cause service interruptions.

Reading the State

In the state overview, each check displays:

Status (OK / Warning / Error / Unknown)
Category - The general category of the environment state
Type - The type of the environment state
Name - A short name of the state
Description - A detailed description
Additional Info (provides details when the state is not OK)

Use the "Additional Info" field as your first resource for troubleshooting—it often contains diagnostic details such as missing endpoints, failed connections, or current counts (e.g., "Only 3 APs detected").

Understanding System States

Every check can return one of the following states:

Status	Meaning	Typical Action
OK	The system component is functioning normally.	No action needed.
WARNING	The component is operational but may be partially degraded or misconfigured.	Review details in Additional Info and verify setup.
ERROR	The check has failed—a key service or configuration is not working.	Immediate attention required. Follow troubleshooting notes and review details in Additional Info.
UNKNOWN	The system was unable to determine the state (e.g., due to timeout or missing data).	Check network connectivity and wait a few minutes.

Categories and Checks

The monitoring system groups checks into categories for clarity. Each category focuses on a specific aspect of system functionality.

`SETUP` Category

These checks verify that the system environment is correctly configured and ready for operation.

Name	Type	Description	Possible Causes	Recommended Action
Access Point not found	`ACCESS_POINT_NOT_FOUND`	Checks whether access points are discovered in the environment.	Access points are not yet configured in the environment.	Ensure all deployed APs are configured and placed in the environment
At least 5 Access Points deployed	`AT_LEAST_5_ACCESS_POINTS_DEPLOYED`	Confirms that at least 5 APs are available to guarantee reliable positioning and coverage.	Fewer than 5 APs are online or properly configured.	Verify AP installation count and ensure all are registered in the environment.

`COMMUNICATION` Category

These checks ensure that your system can communicate with internal and external services required for proper operation.

Name	Type	Description	Possible Causes	Recommended Action
Routing between APs	`CELL_COMMUNICATION`	Verifies network routing between access points.	Access points are powered off, not yet deployed, not configured in the environment, or outside network range.	Ensure all APs are powered, configured in the environment and connected to the same network segment as the system.
LoconIQ API available	`LOCONIQ_API_COMMUNICATION`	Ensures that the system can reach the LoconIQ API endpoints (`api.loconiq.com`, `edge-upstream.loconiq.systems`).	Internet outage, firewall blocking, or incorrect DNS configuration.	Verify outbound internet access and allow the required domains through your firewall.
Monitoring Services available	`MONITORING_COMMUNICATION`	Checks whether monitoring and logging endpoints (e.g., `logging.googleapis.com`) are reachable. Stable connectivity is required (≥ 1 Mbps upstream).	Internet connectivity issues, restricted outbound access, or bandwidth limitations.	Confirm internet access, firewall configuration, and sufficient uplink bandwidth.
USB Connection	`USB_CONNECTION`	Monitors the local USB connection status.	Faulty cable, disconnected device, or power issue on USB port.	Reconnect the USB device or use a powered USB hub if instability persists.

`LOCALIZATION` Category

These checks ensure stable and precise localization in the environment.

Name	Type	Description	Possible Causes	Recommended Action
Amount of APs Connected	`AMOUNT_OF_APS_CONNECTED`	Indicates how many APs are currently connected to the localization network.	APs are out of range, APs are powered off, too few APs are deployed, or configuration errors exist.	Check AP power, verify if all APs are online and properly configured, or add more APs.
AP Constellation	`AP_CONSTELLATION`	Displays the spatial distribution and positioning of APs used for localization	Poor AP constellation or Tag is out of the localization zone.	Verify AP constellation Best Practices for Access Point Placement, add APs, move Tag inside the localization area, or increase the localization area.
Signal Strength	`SIGNAL_STRENGTH`	Indicates the received signal power between APs and Tags.	Obstructions between APs and Tag or excessive distance between devices.	Remove obstructions, reposition APs for better coverage, or add more APs.
Ranging Error	`RANGING_ERROR`	Represents the estimated accuracy of distance measurements between tags and APs	AP Positions may be set incorrectly, obstructions between APs or Tag, poor AP constellation.	Verify if APs are placed correctly, remove obstructions, and verify AP constellation Best Practices for Access Point Placement.
Localization Latency	`LOCALIZATION_LATENCY`	Shows the average elapsed time between two position computations.	APs are too far apart, not enough APs installed, obstructions between APs, or too many Tags are active	Add APs, reduce the distance between APs, remove obstructions, or reduce the amount of active Tags.
Ranging Latency	`RANGING_LATENCY`	Measures the time delay for communication between APs and Tag.	APs are too far apart, not enough APs installed, too many Tags active.	Add APs, reduce the distance between APs, or reduce the number of active Tags.

Unknown or Missing Data

In some cases, the system may report UNKNOWN for any check if it cannot reach a Loci, times out, or fails to parse data. This typically indicates that the system is still initializing, the network is temporarily unstable, or monitoring services are restarting. /

API

The states are available both via On Premises and Cloud API:

On-Premise
- Get Environment State
Cloud
- Get Environment State
- List Environments

LoconIQ App

In the app, you see in the upper right corner the environment state. Depending on the overall state, it is red, yellow, green, or gray if the state is unknown. By clicking on it, you'll receive further information on the underlying issues.

Next Steps

If multiple checks in the Communication category show errors, the root cause is often related to network or firewall configuration. If only the Setup category reports problems, verify the physical installation and registration of devices.

For persistent issues, export the monitoring log and contact your system administrator or support team with the timestamp and reported state details.