Voice Network Diagnosis & the "Internet Connection Failed" Error
Want to know which Wi-Fi network Kachaka is on and whether the connection is healthy? You don’t need to dig through the App’s settings — just ask Kachaka out loud. And when the App shows “internet connection failed” on startup, this voice diagnosis is also the fastest first step to figure out where the problem lies.
Ask for the connection status by voice
Say to Kachaka:
“ねぇカチャカ、ネットワークの診断”
Kachaka will report the result by voice based on its current Wi-Fi connection state. Keep the wake word and command in the original Japanese — it is the fixed phrase the robot recognizes.
How to read the three results
Kachaka’s reply falls into one of the following three states. Match it to the action below.
- Normal (online): It reports “Normal, connected to ○○○”, where ○○○ is the name (SSID) of the Wi-Fi it is on. Both the Wi-Fi and the internet connection are fine — nothing to do.
- Offline (Wi-Fi connected, but no internet): It reports “Error. Wi-Fi is connected but the internet cannot be reached. Connected to ○○○.” Kachaka did join that Wi-Fi; the problem is that the router/hotspot itself is not connected to the internet.
- Not connected to Wi-Fi: It reports “Error. Not connected to Wi-Fi.” Kachaka has not yet joined any Wi-Fi.
When the App shows “internet connection failed”
If the App shows “internet connection failed” on startup, first run the voice network diagnosis above, then act on the result:
- If Kachaka reports case 2, “Wi-Fi connected but the internet cannot be reached”, the problem is the router: confirm that the router or hotspot is actually online (for example, open a web page on a phone on the same network to test), and adjust its settings so it can reach the internet.
- If it reports case 3, “Not connected to Wi-Fi”, redo the Wi-Fi setup first — see Setting Up and Changing the Wi-Fi Connection; if setup gets stuck, see Wi-Fi Setup Fails or Cannot Connect After Setup.
- If it reports “Normal” but you still can’t connect, or the situation is none of the above, it is most likely a communication problem with the server. In that case, contact Sigma for assistance.