Check the result on the affected device

1. Confirm you wrote to the intended SB1000 and note any restart notice. Keep the phone correctly positioned until the NFC operation finishes.
2. Allow the device to apply the change and perform the app's optional verification rescan. A completed NFC write can be shown as saved before a matching apply receipt has been read.
3. If verification reports a stale revision, read a fresh snapshot, review the proposed changes again, and reapply only the intended edits. Another interface may have changed the configuration since the previous read.
4. If writes are disabled/locked, check the device's NFC settings and the installation's permitted configuration route. If the response is unsupported, check app/firmware compatibility. Do not repeatedly resend the same rejected payload.
5. If the setting changed but its effect is not visible, check restart requirements, the selected operating mode, and any changed network address. Verify through the applicable device interface.
6. If an error persists, record the app/platform version, SB1000 firmware, setting name, and apply status. A storage error or repeated invalid-payload result needs support evidence rather than repeated retries.

Passwords are intentionally not read back. A blank password field does not prove that the saved password is empty. Reusable templates also omit secret values or request them at application time.

The native app provides NFC configuration and offline help. Live RS485 scans and self-tests require the affected SB1000's web interface.

Expected result

A fresh read confirms the intended readable setting and, where supported, a matching successful apply receipt. Retain the status and transaction evidence if it does not.