at the moment I am thinking the mdns daemon on the tessel is not responding to a particular packet, not sure how to debug that hypothesis yet.
I commented out the line in the t2-cli that said...
... and that gave me information, but not from the tessel (basically from my apple tv). I set the timeout to 120 (t2 list -t 120) and unplugged and plugged in the tessel again, this time the tessel showed, but said it was not provisisioned (which it is) so i think that is one step forward.
I found I could run...
DEBUG=mdns:* t2 list -t 120
and that gave me more information, which showed that the library sends a packet then waits. I assume that is a packet that is broadcast on the network asking for devices to respond, my hypothesis is the t2 is not getting that packet, or not responding correctly to it. My knowledge of bonjour/zeroconf is limited, and I do not know the protocol level at all. If any of the output of any of this is helpful let me know and I will post. At the moment I am trying to debug what packets are reaching the t2 and/or what the mdnsd daemon is doing about them, but again my knowledge of openwrt is limited and my options are not as wide spread as a general linux system.
I wonder if we can simply abstract the mdns library out into a wrapper, and perhaps use a different library depending on the platform/user preference? That might be a github issue at this stage, but I will get your thoughts on that before I attempt such a thing.