wendy net configure
Update selected Wendy Net settings
Syntax
wendy net configure [flags]Examples
wendy net configure --helpArguments
No positional arguments are declared in the command synopsis.
Flags
Flags below include inherited options. Types and defaults come from the CLI source. An empty default means no value is configured.
| Flag | Type | Default | Description |
|---|---|---|---|
--ble | bool | false | Connect over Bluetooth Low Energy |
--ble-links | uint32 | 0 | Lite: limit simultaneous Bluetooth mesh connections |
--ble-mode | string | (empty) | BLE radio profile: off, normal, coded-s2 or coded-s8 (Lite profile changes restart the device) |
--device | string | (empty) | Target device host (hostname, IP, or host:port); 'wendy run' accepts a comma-separated list to deploy one build to several devices (needs a remote build host and --detach). Defaults to $WENDY_DEVICE, then the saved default device |
--ethernet | bool | false | Discover local net peers over Ethernet |
--infrastructure-wifi | bool | false | Discover local net peers over infrastructure Wi-Fi |
--json | bool | false | Output in JSON format |
--max-links | uint32 | 0 | Lite: limit simultaneous mesh connections |
--nan | bool | false | Connect over Wi-Fi Aware (NAN) |
--nan-links | uint32 | 0 | Lite: limit simultaneous Wi-Fi Aware mesh connections |
--participate | bool | false | Join and relay Wendy Net (false leaves the mesh; saved connection settings are retained) |
--roam | bool | false | Use Wendy Net Internet when an independent uplink is unavailable |
--share-uplink | bool | false | Share this device's own Internet connection with Wendy Net |
--wifi-links | uint32 | 0 | Lite: limit simultaneous infrastructure Wi-Fi mesh connections |
Output
Output depends on the operation and selected target. Use the command help for additional guidance..
JSON output
The global --json option requests machine-readable output. The CLI also selects JSON mode when no interactive terminal is attached. Support and payloads are command-specific; this flag does not guarantee a single JSON document for commands that stream logs or invoke build tools. Consult Details before parsing command output.
Exit codes
The CLI entry point returns 0 on success and for its user-cancelled or default-cleared results. Other returned errors exit with 1 and print a diagnostic to stderr. Some operations may terminate through subprocess or signal handling; do not infer application health from the CLI exit code alone.
Common errors
Check argument values and flag combinations against the synopsis above. For discovery, build, port, and readiness failures, see deployment troubleshooting. Command-specific constraints are in Details.
See also
Details
Use the command help for additional guidance.