@Dave Flowerday We don't "actively fight" it. The user guide says pretty much exactly that - it's not supported, we don't recommend it, and if you absolutely have no choice it gives some advice.
I stand corrected. I assumed (more than I should) based on the observation that the display doesn't show IP address when attached over wifi and neither have I seen the display listed in TM on a PC.
But I have since verified that I can at least add the display IP manually to TM and then it works
@Dave Flowerday There's nothing magical about the Pi Zero W.
Not really magical, just different - ARMv6 vs ARMv7 on newer PIs, and when some SW gets compiled for v7, no dice on Pi Zero. Since the docs explicitly specify "2 or 3B", I assumed. My bad.
@Dave Flowerday We've had TM running on it for a long time. The problem is, we've tested it and we do not feel it performs acceptably (it uses the same microprocessor as the original Raspberry Pi). Plus, it does not have a wired network interface, which means most people would try to use it wirelessly. And, as we keep telling everyone, that's not a great idea.
I hear you. We will get those wires there somehow. And I do have Pi 3B to use for that.
Thanks for making TM available for RPi and sorry if I sounded little too offensive.
Sometimes, it's about managing expectations (and I understand given my track record above I am disqualified from giving suggestions, but consider this):
"Use TM on RPi3B. Yes, it would run on Pi 0, but you won't like the performance."
"Yes, it is technically possible to use WiFi, but especially on 2.4GHz, it would interfere badly with your robots"
We drive the students to ask questions. We teach them to not take "It won't work" for an answer. To seek understanding and test boundaries. Yes, they can be annoying asking their "why"s afterward :-)