Can't figure out how to get to Settings > Advanced Options on device #172

Activity

1. BrettKinny

   added

   bugSomething isn't workingSomething isn't working

   needs-triageAwaiting triage (see docs/agents/triage-labels.md)Awaiting triage (see docs/agents/triage-labels.md)

   status:activeReady to start, not blockedReady to start, not blocked

   area:docsREADME, docs/, assetsREADME, docs/, assets

   on Jul 11, 2026
2. BrettKinny commented on Jul 11, 2026

   

   BrettKinny

   on Jul 11, 2026

   Owner

   More actions

   This was generated by AI during triage.

   Thanks for reporting this — you are not missing a gesture. I checked the current firmware and the quickstart instruction is incorrect: the Setup app has Wi-Fi, device, hardware-test, account, and firmware-update entries, but no Advanced Options screen or editable OTA URL field.

   There is also a broader onboarding defect: the current release binary compiles an installation-specific OTA URL, so correcting the navigation wording alone would not make a fresh third-party install work. I have labelled this as an active onboarding bug. We need to update the provisioning path and quickstart with a real, reproducible way to set the server address.

   For now, please do not keep searching the device menus; that option is not present in this firmware.
3. jonjon1123 commented on Jul 12, 2026

   

   jonjon1123

   on Jul 12, 2026

   Author

   More actions

   Is there any workaround that can be done until the issue is fixed?
4. BrettKinny commented on Jul 12, 2026

   

   BrettKinny

   on Jul 12, 2026

   Owner

   More actions

   This was generated by AI during triage.

   Immediate documentation mitigation is in draft PR #173: it removes the nonexistent on-device Advanced Options instruction, explains the optional browser SoftAP Advanced tab, warns that fw-v1.3.3 is maintainer-LAN-specific, and documents the reliable source-build CONFIG_OTA_URL path. Regression tests guard all onboarding surfaces against reintroducing the false menu instruction.

   The durable portable provisioning/build workflow remains open work; this documentation change does not claim the generic prebuilt is portable.
5. jonjon1123 commented on Jul 12, 2026

   

   jonjon1123

   on Jul 12, 2026

   Author

   More actions

   I am not sure I fully understand the changes in PR #173. The quickstart.md is changed and says to set the CONFIG_OTA_URL="http://<XIAOZHI_HOST>:8003/xiaozhi/ota/" as described in SETUP.md. I've cloned https://github.com/m5stack/StackChan.git, set the CONFIG_OTA_URL, CONFIG_WIFI_SSID & CONFIG_WIFI_PASSWORD, built and flashed the firmware, yet I am still seeing the onboarding flow on the device (the "Welcome! Let's get started." screen).
6. BrettKinny commented on Jul 16, 2026

   

   BrettKinny

   on Jul 16, 2026

   Owner

   More actions

   This response was prepared with AI-assisted source inspection and diagnosis.

   Thanks for the exact steps—you found three separate problems in our guide:

   1. https://github.com/m5stack/StackChan.git is the upstream tree, not Dotty's released firmware fork. Please use:

      git clone --recursive https://github.com/BrettKinny/dotty-stackchan.git
      cd dotty-stackchan/firmware/firmware

   2. CONFIG_WIFI_SSID and CONFIG_WIFI_PASSWORD are not defined by the pinned firmware, so setting them has no effect. Wi-Fi is stored in NVS and provisioned through the Xiaozhi hotspot.

   3. “Welcome! Let's get started.” is expected after a fresh flash. It is the StackChan app-configuration wizard controlled by an NVS flag; seeing it does not mean CONFIG_OTA_URL was ignored.

   The source-verified flow is now:

   • set CONFIG_OTA_URL in sdkconfig.defaults;
   • if you already generated sdkconfig, update it with idf.py menuconfig or regenerate it, then verify with grep '^CONFIG_OTA_URL=' sdkconfig;
   • build and flash;
   • tap Skip on the welcome screen;
   • if the launcher remains visible, open SETUP and use its home control to leave it;
   • join the temporary Xiaozhi-* Wi-Fi network and open the URL shown on the robot (normally http://192.168.4.1);
   • choose your 2.4 GHz Wi-Fi. The browser portal's Advanced tab can confirm or override ota_url.

   The corrected guide is in draft PR #173, commit fc960b6. This path is verified against the pinned source and covered by regression tests; I have not yet claimed clean-device bench verification, so I am leaving this issue open until that is completed and the documentation lands.
7. BrettKinny commented on Jul 16, 2026

   

   BrettKinny

   on Jul 16, 2026

   Owner

   More actions

   Hey @jonjon1123, real Brett here.
   Thanks for reporting the issue. Sorry you were responded to multiple times by AI, that is honestly rude and was not my intention. It got picked up in ai-review sweeps. This project is at the point where it needs more time with me bench testing which I just don't have at the moment, but I'm hoping over the next month I will get this stable. My goal for this now is to not add any more features and just get it working well for my kids. I appreciate the assistance.

   ❤️React with ❤️1Reacted by Nodeswitch
8. jonjon1123 commented on Jul 16, 2026

   

   jonjon1123

   on Jul 16, 2026

   Author

   More actions

   Hey @BrettKinny, no worries sir. I've just started getting into customizing firmware for xiaoshi-esp32/StackChan. I am getting a better feel for how it all works the more I go on. From what I have learned, the not show the base firmware onboarding flow (i.e. "Welcome! Let's get started." screen) will require more firmware changes than just setting the wifi and OTA URL.