Tasmota autodiscovery + Homekit in docker

Hi all,

I’m having some issues with my Home Assistant install (0.99.1 running in a docker) where my devices published to homekit go missing whenever I restart the docker container for an update or server restart and I have to restart my tasmota devices in order to trigger the autodiscovery, and in turn push the devices back out to Homekit again. They do not seem to have the same problem with a simple restart using the internal controls.

Each devices retains is configuration in home assistant (although shows as unavailable) but is completely lost in homekit, thus breaking any automatons I have set up there.

Can anyone suggest where I should start looking to remedy this?

Do you have your volumes mapped correctly, and rw? Sounds like the.homekit.state file might be getting wiped out at container restart.

root@vault:~# ls /mnt/user/appdata/home-assistant/.homekit* -lah
-rw-r--r-- 1 root root 450 Jul  7 14:29 /mnt/user/appdata/home-assistant/.homekit.state

Based on the edit date I don’t think this is the case.

Here is what my permissions look like and those are the same as the rest of the config files. I had the same thought as you but i’m not sure how to troubleshoot it.

Hmm, not sure where to go from there. I’d suggest turning on debug logging for homekit component to see if the logs reveal anything new.

# Write flat log file
logger:
  default: info
  logs:
    homeassistant.core: debug
    homeassistant.components.homekit_controller: debug
1 Like

Thank you!

I will try this.