Replies: 1 comment
-
|
Absolutely yes, it requires more communication https://discord.gg/Znd68HA8 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi knoop,
I've been testing your project on multiple displays around my home and loving it for the most part. I have a local-ish setup with my local network connected p2p thru ipsec with a remote network where homeassistant is running in kubernetes.
Everything has been very stable, however this type setup still has some limitations. One of which was using all the android poe screens as actual assist and ble satellites which your project enables! An important second one however is device discovery. Since the infrastructure homeassistant is running on is remote to the IOT network (+ipsec), mDNS traffic is not generally forwarded.
Since there are many android displays worth of "compute" already available. I was wondering if possibly you would be open to collaborate on a feature that adds a configurable mDNS repeater to Ava. This service could then very easilly be paired on the remote homeassistant network with a companion service, instantly enabling remote discovery of local devices.
It is not yet clear to me if any of this is even possible on android, but if it is, remote discovery over vlans seems like a very old and unresolved issue with no easy or generic solution other than "you should just run homeassistant locally". I think adding mDNS repeater capability to Ava in addition to BLE could benefit the project immensely.
Beta Was this translation helpful? Give feedback.
All reactions