History points all the way back to a commit 8b98789a from
February 2, 2023: Add "noeboard" board type to play via web UI
That commit changed startup from only skipping hardware in --enable-console mode to skipping hardware whenever board-type = noeboard. Before that change, dgtpi=True would still start DgtPi(...) unless console mode was used. After that change, no-eboard became effectively web-only, including no internal clock. The help text still says noeboard is “for basic web-play only” in configuration.py (line 392), which matches the code but not the DGTPi fallback expectation.
The fix we could do is:
- Start/register DgtPi whenever args.dgtpi is true, even in NOEBOARD.
- Only start DgtHw/serial board when board_type != NOEBOARD.
- Guard the I2C CLOCK_VERSION path so it does not start the serial board in no-eboard mode.
That should restore “always show something on the internal DGTPi clock” while keeping no-eboard web play behavior. It would make the following combination work where you have DGTPi with clock display, no eboard, and play using a web client.
- dgtpi = True
- board-type = noeboard
- web-server = 80
I will open a issue for this. This is easy to fix.
-- Johan