Learn which modules and command signatures are available on live micrOS devices. Use this after discovering a device, after its firmware or modules change, or when search_devices does not show an expected capability. Omit deviceTag to inspect all known devices, or provide a UID, IP address, or device name fragment to inspect matching devices. Use password when micrOS app authentication is enabled.

Find live micrOS devices on a local IPv4 /24 network. Use this during initial setup, when a device is missing from list_devices, or when its IP address may have changed. Omit networkPrefix to scan the active local network, or provide a prefix such as 10.0.1. By default, the tool also learns the commands available on discovered devices; set refreshFeatures to false when only device discovery is needed.

Show a quick inventory of known micrOS devices, including each device's UID, name, address, note, and module names. Use this to see what devices are known without checking whether they are currently online. Use search_devices when selecting a command target, finding a capability, or inspecting command signatures.

Run a micrOS command or a sequential command pipeline on one live device. Before using this tool, call search_devices to confirm the exact device and relevant command signature. Target the device by its exact UID, device name, or IP address.

Command syntax examples:

• No arguments: version

• Positional argument: conf webui

• Module function: dht22 measure

• Keyword argument: dht22 measure log=True

• String pipeline: rgb status <a> dht22 measure

• Array pipeline: ["version", "dht22 measure"]

For a string pipeline, <a> separates commands by default; separator can select a different delimiter. For an array pipeline, each array item is one command and runs in order.

Commands act on a real device and may change its state. Configuration reads such as conf and conf webui are allowed, but configuration writes such as conf webui true are rejected. Other commands are not automatically made safe, so use the least disruptive command that fulfills the request.

Find the right micrOS device and command syntax before run_command. Search by a device UID, name, IP address, note, module, function, or capability phrase. Results identify matching devices and show relevant modules with their complete function signatures and available documentation. Use fuzziness 0 for literal matching, 1 for conservative typo tolerance, or 2 for broader recovery. Set status to online or offline when live reachability matters. If a device or capability is missing, use discover_devices or discover_commands, then search again.

Read or save helpful context about one micrOS device, such as its location, attached hardware, purpose, or how its readings should be interpreted. Target the device by UID, IP address, or an unambiguous name fragment. Omit note or pass an empty string to read the current note. Provide a note with mode: "replace" to replace the current text or mode: "append" to add a new line.