@Captain_Morgan and @NickF1227 Apologies for that previous post, I realize I worded that confusingly and more importantly forgot the link!
I got HA mDNS discovery working once, about 18 months ago in Cobia, by disabling Truenas mDNS in global config. That seems like not an ideal solution. I ran it for an hour and turned mDNS back on for Truenas (causing HA to no longer work). I have never had home assistant device discovery working outside of that brief test, trying to reproduce it now I cannot get it to work at all. I think I may have been using the TrueCharts app.
The second part was a quote from another user who currently has it working. @tannisroot in this thread:
Was able to get it working recently using this network code section.
services:
homeassistant:
...
networks:
homeassistant:
ipv4_address: 192.168.0.242
...
networks:
homeassistant:
driver: macvlan
driver_opts:
parent: br0
ipam:
config:
- subnet: 192.168.0.0/24
ip_range: 192.168.0.240/29
gateway: 192.168.0.1
aux_addresses:
host: 192.168.0.241
So unfortunately I am unable to help others outside of scouring forums and gathering information. I would like to test the custom container YAML at some point this summer, but I will be bumbling through that as I have not done anything related to network bridges previously (and I’m not entirely sure if the bridge is needed?). Maybe Tannisroot can answer additional questions as needed, maybe that code section provides enough detail.