Update docs

Change Python environment instructions from optional to recommended. Add warning box about potentially different cable colors for the LED button. Update instructions for blocking Witty Pi behaviour.

Author: maxsitt

docs/deployment/classification.md

@@ -24,54 +24,54 @@ for faster CPU inference. The classification results are added to the merged met
 If you followed the steps in [Local Setup](../software/localsetup.md#python){target=_blank},
 you already have [Python](https://www.python.org/){target=_blank} installed on your computer.
 
-??? info "Optional: Set up an isolated Python environment"
+???+ info "Recommended: Set up an isolated Python environment"
 
-    You can [create a virtual environment](https://virtualenv.pypa.io/en/latest/user_guide.html){target=_blank}
-    before installing the required packages for YOLOv5 to avoid version and dependency
-    conflicts of the packages, especially if you are working on different Python projects.
+     You can [create a virtual environment](https://virtualenv.pypa.io/en/latest/user_guide.html){target=_blank}
+     before installing the required packages for YOLOv5 to avoid version and dependency
+     conflicts of the packages, especially if you are working on different Python projects.
 
-    - Install [`virtualenv`](https://virtualenv.pypa.io/en/latest/){target=_blank}:
+     - Install [`virtualenv`](https://virtualenv.pypa.io/en/latest/){target=_blank}:
 
-        ``` powershell
-        py -m pip install virtualenv
-        ```
+         ``` powershell
+         py -m pip install virtualenv
+         ```
 
-    - Navigate to the `YOLOv5-cls` folder:
+     - Navigate to the `YOLOv5-cls` folder:
 
-        ``` powershell
-        cd YOLOv5-cls
-        ```
+         ``` powershell
+         cd YOLOv5-cls
+         ```
 
-    - Create a new Python environment (folder in your current directory):
+     - Create a new Python environment (folder in your current directory):
 
-        ``` powershell
-        py -m virtualenv env_yolov5
-        ```
+         ``` powershell
+         py -m virtualenv env_yolov5
+         ```
 
-    - Activate the environment by running:
+     - Activate the environment by running:
 
-        ``` powershell
-        .\env_yolov5\Scripts\activate
-        ```
+         ``` powershell
+         .\env_yolov5\Scripts\activate
+         ```
 
-        If you cannot run the activate script because of your Execution Policy
-        settings, open a new PowerShell as administrator and run the following:
+         If you cannot run the activate script because of your Execution Policy
+         settings, open a new PowerShell as administrator and run the following:
 
-        ``` powershell
-        Set-ExecutionPolicy RemoteSigned
-        ```
+         ``` powershell
+         Set-ExecutionPolicy RemoteSigned
+         ```
 
-        You can find more info [here](https://virtualenv.pypa.io/en/latest/user_guide.html#activators){target=_blank}
-        and [here](https://stackoverflow.com/questions/18713086/virtualenv-wont-activate-on-windows){target=_blank}.
+         You can find more info [here](https://virtualenv.pypa.io/en/latest/user_guide.html#activators){target=_blank}
+         and [here](https://stackoverflow.com/questions/18713086/virtualenv-wont-activate-on-windows){target=_blank}.
 
-    - Now all packages will be installed only in the virtual environment,
-      which you have to activate everytime you want to run a script that
-      depends on these packages.
-    - You can deactivate the virtual environment by running:
+     - Now all packages will be installed only in the virtual environment,
+       which you have to activate everytime you want to run a script that
+       depends on these packages.
+     - You can deactivate the virtual environment by running:
 
-        ``` powershell
-        deactivate
-        ```
+         ``` powershell
+         deactivate
+         ```
 
 - Create the new folder `C:\Users\<username>\YOLOv5-cls`.
 - [Download](https://github.com/maxsitt/yolov5/archive/refs/heads/master.zip){target=_blank}

docs/hardware/2024_buildinstructions_hardware.md

@@ -230,6 +230,13 @@ Put the sealing ring onto the thread of the button.
 
 ![Button Sealing Ring](assets/images/2024_button_sealing_ring.jpg){ width="600" }
 
+!!! warning "Different Button Types"
+
+    Please check the cable colors and their respective assignment for your
+    specific product on either the button itself or the button socket. Even if
+    the button looks identical, the cable assignments/colors can be different
+    depending on the producer or batch.
+
 Take a look at the socket and note the colors of the cables that are labeled
 with **C** and **NO**. In our case this is green for **C** and yellow for **NO**.
 We won't use the white cable labeled with **NC**.

docs/software/pisetup.md

@@ -103,9 +103,9 @@ More info:
     still stays on after 25 seconds, the button will not be responsive as the
     Witty Pi assumes that the RPi is still turned on. This can happen if the
     Witty Pi software is not yet installed or if there is a problem with the
-    GPIO connection (check for faulty solder joints). In this case, you will
-    need to unplug both batteries (USB-C and 3.7V) and connect them again to
-    reset the Witty Pi board.
+    GPIO connection (check for faulty solder joints). To make the Witty Pi
+    responsive again, press and hold the button for 10 seconds until the red
+    LED turns off.
 
 ---