Skip to content

Getting Started

Get started with ScriptO Studio and pyDirect.

pyDirect Setup

pyDirect Setup Tool

The pyDirect Setup tool at pydirect.com provides a unified workflow for all device scenarios. Connect your ESP32 via USB and choose from four options:

Scenario Description
New Device Flash fresh firmware onto a blank ESP32
Forgot Credentials View saved hostname and password
Change WiFi Update network settings on existing device
Re-provision Generate new certificates for HTTPS

New Device Setup

If you have a brand new ESP32 chip without firmware:

  1. Go to pydirect.com
  2. Connect your ESP32 via USB
  3. Click Connect Device
  4. Select New Device when the chip is detected
  5. Flash the firmware (automatically selected for your chip)
  6. Configure WiFi when the network modal appears
  7. Select your network from the list (shows signal strength in dBm)
  8. Enter the WiFi password
  9. Device connects and saves settings
  10. You're returned to the scenarios screen
  11. Select Re-provision Device to generate certificates
  12. Certificate is generated and installed
  13. Device resets and connects to WiFi
  14. Accept the security warning modal and click to open device
  15. Accept the browser security warning (click Advanced → Proceed)
  16. Set an access password on the device's web interface
  17. You'll be redirected to ScriptO Studio
  18. When ScriptO Studio prompts for connection, use the same password you set in step 10

[!IMPORTANT] The password you set during provisioning is used both for the device's local web interface AND for ScriptO Studio connections. Remember this password!

Existing pyDirect Device

If you already have a device running pyDirect firmware:

  1. Go to scriptostudio.com
  2. Click Connect
  3. Enter your device's IP address or hostname (e.g. pydirect-xxxx.local)
  4. Enter the access password (set during initial provisioning)
  5. Click Connect

Forgot Credentials

If you can't remember your device's hostname or password:

  1. Go to pydirect.com
  2. Connect via USB and click Connect Device
  3. Select Forgot Credentials
  4. Your device's hostname, password, and WiFi SSID are displayed

Change WiFi

To update network settings on an existing device:

  1. Go to pydirect.com
  2. Connect via USB and click Connect Device
  3. Select Change WiFi
  4. A modal shows available networks with signal strength (dBm)
  5. Select your network and enter the WiFi password
  6. Device connects and you're returned to scenarios

[!NOTE] Change WiFi only updates network settings. If you need new HTTPS certificates, select Re-provision Device afterward.

Re-provision

To generate new HTTPS certificates:

  1. Go to pydirect.com
  2. Connect via USB and click Connect Device
  3. Select Re-provision Device
  4. New certificate is generated and installed
  5. Device resets and connects to WiFi
  6. A modal explains the security warning you'll see
  7. Click Connect to [hostname] to open device in new tab
  8. Accept the browser security warning
  9. Set a new password on the device's web interface

Connection Requirements

  • Browser: Chrome, Edge, or Opera (WebSerial/WebRTC support required)
  • Device: ESP32-S3 or ESP32-P4 with pyDirect firmware
  • Network: Device and browser on same network for ScriptO Studio

Accepting the Security Certificate

pyDirect devices use HTTPS with a self-signed certificate generated during setup. When you first connect:

  1. Browser shows "Your connection is not private" warning
  2. Click Advanced (or "Show Details" on Safari)
  3. Click Proceed to [device-hostname] (or "visit this website")
  4. The certificate is now trusted for this device

This only needs to be done once per device per browser.

Next Steps

Troubleshooting

Can't connect from pydirect.com?

  • Check USB cable supports data (not charge-only)
  • Install USB drivers if needed (CP210x or CH340)
  • Put device in boot mode (hold BOOT, press RESET, release BOOT)

Can't connect from scriptostudio.com?

  • Verify device is powered and on the network
  • Check the IP address is correct
  • Make sure you're using the password set during provisioning
  • Accept the self-signed certificate warning first

See Troubleshooting Connection for more help.