You can find some of my favorite recipes and dashboards in the Home Assistant category. If you are not happy with the limited optionality and compatibility of Apple HomeKit and Google Home, definitely look into Home Assistant. With Docker, it is much easier – I can keep an eye on RAM requirements (Home Assistant can be a very memory-intense application depending on your use case), update the container when a new version comes out and restart it when things go wrong. I initially ran Home Assistant on my Mac, but it was always cumbersome to monitor, restart or update the instance. It is a local platform and such relies on your local hardware instead of some cloud capability.

inspide of I can see it in my Network with the specific Mac Address and IP.Home Assistant is a very powerful open source home automation platform with a large community around it. I tried to create MacVlans with success but when I deploy the Docker container, I can't reach it. For example, For HA, I would like to create 3 virtual interfaces (One per Vlans) with for each one, a specific Mac Address and a specific IPV4. I know I can do this by using MacVlan but I have not sufficient competences to do that. I would like to install HA and other stuff (Adguard, PLEX etc.) on Docker (easy to do) BUT with a direct access to Vlans (ex: HA must communicate with CORE, IOT and SEC, PLEX only the Vlan CORE etc.) I have also an Unifi network with different Vlans (CORE, IOT, SEC) and the server OMV is installed on the CORE Vlan but connected to a Trunk port where the Vlans CORE + IOT + SEC are available. This server have only one physical network interface (enp7s0).

I have an OMV server on which one run Docker/Portainer.

Docker adguard