| 11 Sep 2025 |
 @saiko:knifepoint.net | can you make the dashboard proxy the info instead of requiring the client to access the devices directly, or set non-mdns names for the devices? | 15:48:04 |
| @saiko:knifepoint.net | otherwise if this can’t be changed I would really just use openvpn or some othe tap tunnel | 15:48:32 |
| @saiko:knifepoint.net | and then it should just work | 15:48:39 |
 toonn | K900: Do you have a way of getting mDNS to work over Tailscale? | 15:48:42 |
 ghostbuster91 | I don't think so. The info pages use websockets to propagate realtime information | 15:49:34 |
| ghostbuster91 | Yeah that would work | 15:49:52 |
| @saiko:knifepoint.net | because this still sounds like you will need mdns queries to work, which fundamentally rely on broadcast to work
GPT told me that I need to propagate have something that will answer DNS queries and respond with mDNS entries
any way I could interpret this ranges from “might work but forbidden by the spec” to “might work but extremely sketchy”. but let’s see what K900 says, he is the tailscale guy
| 15:59:37 |
| @saiko:knifepoint.net | In reply to @saiko:knifepoint.net
can you make the dashboard proxy the info instead of requiring the client to access the devices directly, or set non-mdns names for the devices?
domain (Optional, string): Set the domain of the node hostname used for uploading. For example, if it’s set to .local, all uploads will be sent to <HOSTNAME>.local. Defaults to .local.
is this related? I have no idea what it’s talking about with “uploads” but if so, you could actually change the domain suffix from what it looks like to something that can be resolved everywhere https://esphome.io/components/wifi/
| 16:04:24 |
| @saiko:knifepoint.net | people are also saying you can use static IPs but 👎 | 16:05:55 |
| ghostbuster91 | hmm nice finding! I will look into this | 16:05:57 |
