You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,16 +37,18 @@ Users will then be unable to access the API `http://your-device:9090/v1/connect`
37
37
Alternatively, if you would rather have your backend use specified ports instead of the host network, you can change the `PWC_HOST` environment variable to `172.17.0.1` and access the API from `http://172.17.0.1:9090/v1/connect`.
38
38
39
39
## Changing the default network interface
40
-
By default, the first available Wi-Fi network interface available will be used. For the vast majority of cases there is only one Wi-Fi network interface (`wlan0`) and therefore this is no issue. Similarly, if you plug in a Wi-Fi dongle to a device without its own built-in Wi-Fi, the Wi-Fi dongle will be used by default. If however, you have a device with built in Wi-Fi and a Wi-Fi dongle, you will have a device with two network interfaces (usually `wlan0` and `wlan1`). For these instances, or on other occasions where you have a complex interface setup, you can specify which network interface you would like Py Wi-Fi Connect to use by setting the environment variable shown in the `docker-compose.yml` file:
40
+
By default, the first available Wi-Fi network interface available will be used. For the vast majority of cases there is only one Wi-Fi network interface (`wlan0`) and therefore this is no issue. Similarly, if you plug in a Wi-Fi dongle to a device without its own built-in Wi-Fi, the Wi-Fi dongle will be used by default.
41
+
42
+
If however, you have a device with built in Wi-Fi and a Wi-Fi dongle, you will have a device with two network interfaces (usually `wlan0` and `wlan1`). For these instances, or on other occasions where you have a complex network interface setup, you can specify which network interface you would like Py Wi-Fi Connect to use by setting the environment variable shown in the `docker-compose.yml` file:
41
43
42
44
````
43
45
PWC_INTERFACE: "wlan0"
44
46
````
45
47
46
-
To allow for automatic detection, set the variable to `false` or remove the variable from your `docker-compose.yml` file:
48
+
To allow for automatic detection, set the variable to `auto` or remove the variable from your `docker-compose.yml` file:
47
49
48
50
````
49
-
PWC_INTERFACE: false
51
+
PWC_INTERFACE: "auto"
50
52
````
51
53
52
54
This setting can also be controlled using the `/set_interface` endpoint.
@@ -170,9 +172,9 @@ Requests are returned immediately and then the process is executed. Otherwise us
170
172
171
173
By default the Wi-Fi network interface is auto-detected. If you need to specify a network interface, you can do so using this endpoint.
172
174
173
-
To set back to auto-detection, pass `false` as the value.
175
+
To set back to auto-detection, pass `auto` as the value.
174
176
175
-
Changing the setting will only last until the next restart of the container, when it will resort back to the default setting set by the environment variable in the container.
177
+
Changing the setting will only last until the next restart of the container, when it will resort back to the default setting set by the environment variable in the container or `auto` if there is no environment variable in the container.
0 commit comments