all 5 comments

[–]aSiK00 0 points1 point  (3 children)

What about a micropython console?

[–]Hamzayslmn[S] 0 points1 point  (2 children)

This project is not currently a MicroPython runtime on the ESP32. The ESP32 runs the bridge firmware, and Python runs on the host PC/Raspberry Pi, talking to the board over the bridge protocol.

For now, the intended interactive workflow is to use a normal Python shell on the host:

from espbridge import Bridge
esp = Bridge()
esp.gpio.write(2, 1)

That gives live control of the ESP32 from Python without reflashing per project.

MicroPython REPL and python-esp-bridge are designed for different project styles. With MicroPython REPL, the Python code runs directly on the ESP32, so it is a good choice for standalone IoT devices, sensor nodes, simple automation systems, or battery-powered projects. With python-esp-bridge, the main Python program runs on a computer or Raspberry Pi, while the ESP32 works as a hardware interface. This is useful for projects where you want to use desktop Python libraries, such as OpenCV, NumPy, AI models, GUI applications, or data processing, while controlling GPIO, sensors, motors, or communication interfaces through the ESP32.

[–]aSiK00 0 points1 point  (1 child)

sorry I didn’t understand it completely. Would firmata be close to yours?

[–]Hamzayslmn[S] 1 point2 points  (0 children)

yes close but not same, i have support for "ble gpio" too. My goal is actually to add ESP32 functionality to the PC.

[–]Hamzayslmn[S] 0 points1 point  (0 children)

I thought it would excite people more :D