I’m perfectly aware of this. I have enabled a firewall rule in my router that blocks all outgoing traffic from my Daikin. And I have also made a total of reset of my Daikin. By that any existing connection is killed and no new one can be established. So hopefully this will solve my issue.
It’s really annoying not knowing what service my Daikin communicates with. And what triggers my Daikin to establish a connection to this unknown service. Probably I will never learn how. But if this band aid fix will make my Daikin remain silent, I can live with that.
When I started my Home Assistant career 1-2 months ago, I made my first attempt with Hassio in a virtual machine on my Windows machine. I tried some automations triggered by energy price. However, I switched to a dedicated Rpi server quite soon, and this has been my Home Assistant platform since then.
Today I noticed my VM was up and running. A few days ago, I started my Windows machine and unfortunately automatic start of my VM was enabled. I think this was when my problem showed up again after my Daikin had been silent for 5 days. It is far more likely it is my first automation attempt that causes this behaviour than a magic Daikin function…
So now I have killed the VM, and disabled automatic start on boot. Hopefully my Daikin will remain silent from now on…