1. Latency and timing accuracy of smart switches
Commenters repeatedly questioned how quickly a command from the app translates to the switch actually turning on/off, and what jitter this introduces for precise photographic exposures.
- “I always assumed … there would be too much jitter in the actual timing … how stable is the delay from the app sending a command until the switch operates?” — arnarbi
- “I'd probably put the typical smart switch hardware/software stack at around 0.25 seconds. Maybe you can … but I don't think I'd try to rely on anything much faster than that.” — alnwlsn
2. Darkroom‑specific display requirements
The discussion emphasized that the UI must use a red‑on‑black (or similarly safe) palette to avoid exposing photographic paper, while also noting the need for readability outside the darkroom.
- “Isn't it more than a nod, and actually a hard requirement to be considered for use in an active darkroom?” — baoooooooooooo
- “I get that red‑on‑black color scheme is a nod to the red lighting of a dark room, but the contrast is so low I can hardly read the example screenshots.” — pimlottc
3. Hardware implementation choices
Several users weighed using stock smart‑switch hardware against flashing custom firmware (e.g., ESP8266/ESP32) or employing OLEDs to achieve low latency and proper spectral output.
- “If you did, I would go in the custom firmware for the smart switch direction. A lot of them are just an ESP32 inside …” — alnwlsn
- “It’s not a nod. It’s required to not ruin the paper during use. A specific yellow would also work but phone screens often output more than just the desired color. Red is the safest.” — guax