#homekit_controller specify IP address instead of relying on zeroconf

1 messages · Page 1 of 1 (latest)

digital widget
#

Is there a way to force homekit_controller not to discover the IP address for a HomeKit device via MDNS and use the IP address instead?

I have multiple WiFi thermostats (Sinope TH6250WF) that advertise themselves using their model number instead of their device name. They russian roulette themselves by adding -2, -3, etc. if they discover another of the same model on the network, but they don't keep the name. I am trying to get the manufacturer to fix the behaviour, but it's causing the homekit_controller integration to connect to random IP addresses, so pairing fails if HomeAssistant restarts or WiFi goes down.

For example the integration has now discovered six entries which it then randomly picks:

        "data": {
          "AccessoryIP": "192.168.8.31",
          "AccessoryIPs": [
            "192.168.8.31",
            "192.168.8.35"
            "192.168.8.32"
            "192.168.8.34"
            "192.168.8.30"
          ],
hazy quail
#

can you manually edit the config to specify the IP you want, or does that get overwritten?