Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| members:sparky:plans [2026/01/10 23:28] – created Sparky | members:sparky:plans [2026/03/11 22:16] (current) – Sparky | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| ### TODO | ### TODO | ||
| - | - [ ] Set up DNS for the Raspberry Pi API endpoint | + | - [X] Set up DNS for the Raspberry Pi API endpoint |
| - Current: `http:// | - Current: `http:// | ||
| - Goal: `transit-tracker.int.dma.space` (int.dma.space is for member projects not on the services rack) | - Goal: `transit-tracker.int.dma.space` (int.dma.space is for member projects not on the services rack) | ||
| - | - [ ] Set up DNS for the display device UI | + | - [X] Set up DNS for the display device UI |
| - Current: `10.20.110.197` | - Current: `10.20.110.197` | ||
| - Goal: `transit-display.int.dma.space` | - Goal: `transit-display.int.dma.space` | ||
| + | - [X] Set up static IP for the display device UI | ||
| + | - Current: `10.20.110.197` | ||
| + | ## WhereTrain (ESP32 Transit Tracker) | ||
| + | |||
| + | ### TODO | ||
| + | - [ ] Integrate with the Raspberry Pi transit-tracker API (`transit-tracker.int.dma.space`) instead of calling OneBusAway directly | ||
| + | - Currently the ESP32 polls OneBusAway API directly from `main.c` | ||
| + | - Goal: Point it at the existing transit-tracker API so all transit data flows through one source | ||
| + | - Reduces redundant API calls and centralizes API key management on the Pi | ||
| --- | --- | ||
| + | |||