The Macs at North Attleboro are on the wired network, Wi-Fi and the Dante networks at once, and Bonjour lists every network MIDI session once per network. On 2026-10-20 the Vista Cues senders on NA Ingest were set to Wi-Fi addresses (Tracks 10.6.9.193, Companion 10.6.3.222), so the lighting MIDI ProdDash listens to rode Wi-Fi. Those addresses were corrected to the wired ones by hand; this makes the admin page catch it next time.
What changes
New setting, "Wired network" (Vista Cues → This machine). One network like 10.1.0.0/16, or several with commas. Empty, the default, changes nothing.
With it set, any of these turns the admin status line red and names the sender:
a sender typed as an address outside the wired network ("Tracks (10.6.9.193) is not on the wired network: use its address on 10.1.0.0/16");
a sender typed as a name ("Tracks is set by name (NA-Tracks.local)"), since a name resolves to whichever network answers first;
a session that joins ProdDash from outside the wired network.
The tile's sender chip turns red too, with the reason in its tooltip.
The flagged sender still joins, so the cue lists keep showing mid-service. This is a warning, not a block.
127.* (Companion on the same machine) is always fine.
A typo in the setting fails the module in /admin with a plain message, as the module guide asks.
Version 1.0.1 → 1.1.0.
Tested
node modules/vista-cues/vista.test.js: 15 passed, including two new tests (network matching; a by-name sender still joins and the health says so).
tools/*.test.js all pass.
Ran ProdDash locally against tools/vista-midi-mock.js with a sender at an unroutable test address (192.0.2.10): the admin card shows the red line and the new field sits under This machine.
After merging
On NA Ingest: update Vista Cues from the admin page, then set Wired network to 10.1.0.0/16. The status panel's MIDI key already flags the same problem from its side.
## Why
The Macs at North Attleboro are on the wired network, Wi-Fi and the Dante networks at once, and Bonjour lists every network MIDI session once per network. On 2026-10-20 the Vista Cues senders on NA Ingest were set to Wi-Fi addresses (Tracks 10.6.9.193, Companion 10.6.3.222), so the lighting MIDI ProdDash listens to rode Wi-Fi. Those addresses were corrected to the wired ones by hand; this makes the admin page catch it next time.
## What changes
- **New setting, "Wired network"** (Vista Cues → This machine). One network like `10.1.0.0/16`, or several with commas. Empty, the default, changes nothing.
- With it set, any of these turns the admin status line red and names the sender:
- a sender typed as an address outside the wired network ("Tracks (10.6.9.193) is not on the wired network: use its address on 10.1.0.0/16");
- a sender typed as a name ("Tracks is set by name (NA-Tracks.local)"), since a name resolves to whichever network answers first;
- a session that joins ProdDash from outside the wired network.
- The tile's sender chip turns red too, with the reason in its tooltip.
- The flagged sender **still joins**, so the cue lists keep showing mid-service. This is a warning, not a block.
- `127.*` (Companion on the same machine) is always fine.
- A typo in the setting fails the module in /admin with a plain message, as the module guide asks.
- Version 1.0.1 → 1.1.0.
## Tested
- `node modules/vista-cues/vista.test.js`: 15 passed, including two new tests (network matching; a by-name sender still joins and the health says so).
- `tools/*.test.js` all pass.
- Ran ProdDash locally against `tools/vista-midi-mock.js` with a sender at an unroutable test address (192.0.2.10): the admin card shows the red line and the new field sits under This machine.
## After merging
On NA Ingest: update Vista Cues from the admin page, then set **Wired network** to `10.1.0.0/16`. The status panel's MIDI key already flags the same problem from its side.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
christian
added 1 commit 2026-10-20 13:15:11 -04:00
The Macs at NA are also on Wi-Fi and the Dante networks, and Bonjour lists each MIDI session once
per network. On 2026-10-20 the Tracks and Companion senders were set to Wi-Fi addresses, so the
lighting MIDI ProdDash hears rode Wi-Fi. With "Wired network" set (This machine; e.g. 10.1.0.0/16,
several with commas), a sender typed as a name or as an address outside it, and a session that
joins us from outside it, turn the admin status line and the tile's sender chip red, naming the
sender. It still joins, so the cues keep showing. Empty (the default) changes nothing; a typo in
the setting fails the module in /admin with a plain message.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
The Macs at North Attleboro are on the wired network, Wi-Fi and the Dante networks at once, and Bonjour lists every network MIDI session once per network. On 2026-10-20 the Vista Cues senders on NA Ingest were set to Wi-Fi addresses (Tracks 10.6.9.193, Companion 10.6.3.222), so the lighting MIDI ProdDash listens to rode Wi-Fi. Those addresses were corrected to the wired ones by hand; this makes the admin page catch it next time.
What changes
10.1.0.0/16, or several with commas. Empty, the default, changes nothing.127.*(Companion on the same machine) is always fine.Tested
node modules/vista-cues/vista.test.js: 15 passed, including two new tests (network matching; a by-name sender still joins and the health says so).tools/*.test.jsall pass.tools/vista-midi-mock.jswith a sender at an unroutable test address (192.0.2.10): the admin card shows the red line and the new field sits under This machine.After merging
On NA Ingest: update Vista Cues from the admin page, then set Wired network to
10.1.0.0/16. The status panel's MIDI key already flags the same problem from its side.🤖 Generated with Claude Code