I had an automation where a dashboard was casted to a google nest hub max (which is turned off part of the time on purpose) when it changes from unavailable. I moved the Google Nest Hub Max onto a different vlan (IOT) than HA but have cross communicaiton of all protocols including mDNS. Ever since I moved it to the separate vlan the automation no longer works.
essentially - the “media_player.basement_google_nest_hub_max” never changes FROM unavailable. What am I missing in my network configuration?
Tip that may help - in chrome, the Google Nest Hub Max does not appear when I use the cast button to select a device - unless I pull the power cord from the Google Nest Hub Max - and then when it boots up I am for only a short while it does appear in the cast menu and I am able to cast to it from a chrome browser running on a PC on the other subnet (vlan). When doing the smae thing and monitoring the “media_player.basement_google_nest_hub_max” status - the whole time the google nest huib max is booting up, it stays unavailable (from within HA runniong on a RPI on the other subnet/vlan). I do have firewall rules set upo first blocking everything from one vlan tothe other, and then additional higher prioriy ruiles allowing certain kinds of sommunicaitn across… It’s just that I am missing something in my network configuration… ?