Thank you for contacting SunFounder technical support, and for describing the issues in such detail.
First, one practical note that may help you a lot going forward: OpenClaw is updated very frequently, and its actual behavior often runs ahead of the official tutorial and FAQ. We have already seen cases where the skills directory structure was changed and the documented steps no longer matched. So if some steps in the tutorial don’t work on your current version, it is quite likely not a mistake on your side — the documentation simply hasn’t caught up yet.
Because of that, our recommended approach is: just ask OpenClaw directly in natural language and let it diagnose and answer for you. The CLI input not displaying and the file path issues both fall into the category of things it can work out itself, and that will be much faster than following the tutorial step by step. To be candid, once you are in the AI-assisted stage, our own development experience becomes less reliable as a reference — many of these behaviors are the AI doing something different from what we expected while still achieving the intended result, and tracing that really depends on the AI itself.
On your specific points:
Setting up hooks: We suggest telling OpenClaw in plain language what you want to achieve and where you are currently stuck, and letting it give you the correct approach for your current version.
Missing picarx-control directory: Glad to hear you already resolved this one, so we won’t go into it further.
Terminal input not displaying: This means the terminal state has been altered by some process (for example, echo has been turned off). Two quick things to try first: type reset and press Enter, or run stty sane; you can also simply close and reopen the terminal. If it is still abnormal, describe the symptom to OpenClaw and let it check which process changed the terminal settings.
Sound file path: The /path/to/sound.wav in the command is a placeholder and needs to be replaced with an audio file that actually exists on your system. As for which path to use, we suggest simply asking OpenClaw — for example, tell it “I need a usable audio file path to play a notification sound; please find the audio files already present on my system and give me the full path.” It will answer based on your actual system, which is more reliable than us giving you a fixed path.
If anything is still unresolved after trying the above, please send us the full output (or error messages) from OpenClaw and we will look into it with you. Thank you for your patience and cooperation.