Fix Office Occupancy Sensor Not Active for Butlr Systems

Firmware and device configuration

• Open the Butlr dashboard or management app and confirm the device firmware version.
• If firmware is outdated or shows a failed update, schedule or re-run the firmware update per Butlr guidance.
• Verify device settings such as site assignment, time zone, and reporting intervals; incorrect configuration can appear as inactivity.
• If available, review device logs to identify boot or sensor errors recorded after the restart.

Power and wiring checks

• Confirm the power source: for powered units check PoE or adapter output; for battery units check battery orientation and contacts.
• Measure voltage at the device if possible to ensure stable power delivery.
• Replace faulty power supplies, cables, or batteries and re-test the sensor.
• Check any inline power controllers, UPS devices, or switches that may isolate the sensor when in low-power or maintenance modes.

Network connectivity and firewall

• Ensure the sensor can reach the network: verify SSID and Wi-Fi credentials for wireless devices or link status for wired devices.
• Confirm DHCP assignment and that the sensor has a valid IP address; reserve the IP if required for stability.
• Check firewall rules, VLAN configurations, and any port restrictions that might block the sensor from reaching Butlr cloud endpoints; open required ports per Butlr documentation.
• Run ping/traceroute from a local host to the sensor and from the sensor to Butlr endpoints if remote debugging tools are available.

Cloud, account and site assignment

• Log in to the Butlr cloud dashboard and confirm the device appears under the correct organization and site.
• Verify licensing or subscription status; expired or misconfigured accounts can prevent devices from reporting.
• If the device is unassigned or listed as offline, reassign it to the correct site and trigger a reconnect or reprovisioning workflow if available.
• Contact Butlr support with device identifiers and logs if cloud-side errors or provisioning failures are suspected.

Verification and testing

• After making changes, verify the sensor reports live occupancy by observing dashboard timestamps and recent events.
• Run a local test: walk through the sensor field to confirm detection and check for expected occupancy entries.
• Use device diagnostics and logs to confirm stable connectivity, successful data transmissions, and absence of recurring errors.
• Document the actions taken and results so future incidents are faster to resolve.

Preventative maintenance and best practices

• Schedule periodic firmware updates and device health checks to catch issues early.
• Monitor device status with alerts for offline sensors or stale data to enable faster response.
• Keep spare power supplies, batteries, and replacement sensors on hand for critical spaces.
• Maintain network documentation, IP reservations, and firewall rules required by Butlr to reduce configuration-related downtime.

Conclusion

Resolving an inactive Butlr occupancy sensor typically involves a systematic check of power, network connectivity, firmware, and cloud configuration. Start with quick restarts and physical inspections, then proceed through power and network diagnostics, firmware updates, and cloud verification. If the issue persists after these steps, contact Butlr support with device logs and site details for advanced troubleshooting.