Issue
After replacing a SwiftReader with a SwiftVision or SwiftReader X device, the following symptoms were observed:
Address Mismatch: The intercom screen displayed an incorrect default address after the initial Access Point (AP) assignment.
Connectivity Instability: The device functioned briefly before moving to an "Offline" status.
Logging Failure: No activity logs were being captured for PIN entries, face unlocks, or intercom calls.
Unresponsive Reboot: Performing a remote reboot from the dashboard failed to fix the issues.
Troubleshooting Steps
To isolate and resolve the issue, the following steps were taken:
Firmware Update: Initiated a firmware update via the CC. This successfully updated the on-screen address, but activity logs remained missing.
AP Settings Verification: Checked backend configuration settings for the specific Access Point.
Settings Refresh: Performed a manual refresh of the AP settings by toggling the configuration options multiple times and saving the changes.
Resolution
The device returned to full functionality after the Access Point settings were re-saved.
Device status remained stable (Online).
Correct address information persisted on the display.
Activity logs (PIN, Face Unlock, and Calls) began generating and recording correctly in the activity feed.
Root Cause
The issue was caused by a configuration sync failure in the backend database.
When the SwiftVision was registered to an Old Access Point previously used by a SwiftReader, the backend did not automatically trigger a full update of the device-specific configurations required for the newer SwiftVision hardware.
Manually re-saving the AP settings forced the database to push the correct, updated configuration profile to the device.