Wiring: other scenarios
Beyond IR and serial, a proxy can switch pins and act as a Bluetooth remote.
Projector screen / lift (gpio.out or serial)
Section titled “Projector screen / lift (gpio.out or serial)”Motorised screens are either dry-contact (up/down/stop relays) or RS-232.
- Dry contact: drive a small relay board from
gpio.outpins; wire the relay contacts to the screen’s trigger terminals. - RS-232: wire as in serial and use the Screen driver.
For the dry-contact case, a gpio.out pin drives a relay module (its own transistor and flyback diode keep the coil off the ESP32), and the relay’s isolated COM/NO contacts close the screen controller’s trigger terminals.
12 V trigger in/out (gpio)
Section titled “12 V trigger in/out (gpio)”- Out: a GPIO through a transistor/relay can pulse a 12 V trigger to power an amp on with an activity.
- In: an opto-isolator from a 12 V trigger into a GPIO lets reMaestro react to another device turning on.
An opto-isolator is the safe way to read a trigger: the 12 V side lights an LED inside the package, a phototransistor on the other side sees it, and there is no electrical path between them — so nothing can put 12 V onto a 3.3 V pin.
Bluetooth HID (bt.hid)
Section titled “Bluetooth HID (bt.hid)”The ESP32 can pair to a TV/streamer as a Bluetooth remote and relay navigation with no IR and no vendor API — driven by the HID proxy driver. No extra wiring; just power the ESP32 near the device and pair.
Bluetooth remote in (bt.host)
Section titled “Bluetooth remote in (bt.host)”The same radio works the other way. In bt.host the board pairs to a Bluetooth remote and relays what it
heard; the hub decides what it meant, so the remote drives activities from a room the hub itself can’t hear.
Like bt.hid it needs no pins — power the ESP32 within range of the remote and pair.