Q:After enabling Sound Monitoring, why does it work sometimes but not others?
A:[Cause/Principle] Sound Monitoring is not executed locally on the watch. After the parent taps Sound Monitoring in the app, the command must first be sent to the watch via 4G/Wi‑Fi; the watch then uses the SIM to actively call back the set number. Therefore, any instability in the watch's network signal, mobile data, SIM calling function, VoLTE, or number format may cause the occasional failure to call back.
[Normal Range] In weak-network locations such as underground garages, malls, deep indoors, or on a moving network, remote commands may be delayed or fail to deliver; the watch may also need time to recover right after powering on or regaining network. A single failure to call back immediately can be retried once and observed.
[Standard Test/Troubleshooting] 1) Confirm the watch is currently online and the app can refresh positioning normally; 2) Confirm the SIM can make regular calls; 3) Check that the callback number in Sound Monitoring is correct; 4) Disable modes such as Night Power-Saving and Sleep that may restrict networking; 5) Place the watch where 4G signal is good; 6) Re-send the Sound Monitoring command and wait about 30 seconds to observe the callback; 7) Test 2–3 times consecutively; 8) If it remains unstable, cross-test with another SIM confirmed to have working voice and 4G data.
[Abnormal Determination] If the watch network is stable, regular calls work, and other remote commands such as app positioning work normally—but Sound Monitoring consistently fails to call back or has a markedly low success rate—further investigate it as a Sound Monitoring command-delivery / voice-callback function abnormality.