Double take addon keeps stopping without error

[dragonsoul84]

I have the Frigate Addon installed and working. I have the Deepstack CPU Addon installed. I have MQTT configured and working with other devices. I set the initial configuration for Double Take and when I start the Double Take Addon and go to the config tab I can see the green dots next to Double Take, MQTT, Frigate, and Deepstack. The log shows:

info: Double Take v1.13.1-8e2728d
info: MQTT: connected
info: MQTT: subscribed to frigate/events, frigate/+/person/snapshot

Then the Double Take dot on the config page turns red and the addon stops. No other info appears in log.

Edit: Adding info from UI log

23-02-03 20:21:05 info: Double Take v1.13.1-8e2728d
23-02-03 20:21:06 info: MQTT: connected
23-02-03 20:21:06 info: MQTT: subscribed to frigate/events, frigate/+/person/snapshot
23-02-03 20:21:28 info: Double Take v1.13.1-8e2728d
23-02-03 20:21:29 info: MQTT: connected
23-02-03 20:21:29 info: MQTT: subscribed to frigate/events, frigate/+/person/snapshot
23-02-03 20:21:49 info: Double Take v1.13.1-8e2728d
23-02-03 20:21:50 info: MQTT: connected
23-02-03 20:21:50 info: MQTT: subscribed to frigate/events, frigate/+/person/snapshot

Edit: Add config.yml

# MQTT Settings
mqtt:
  host: [homeassistant_ip_address]
  user: [mqtt_user_name]
  password: [mqtt_password]

# detector settings (default: shown below)
detectors:
  deepstack:
    url: http://[homeassistant_ip_address]:5001
    #key:
    # number of seconds before the request times out and is aborted
    timeout: 15
    # require opencv to find a face before processing with detector
    opencv_face_required: false
    # only process images from specific cameras, if omitted then all cameras will be processed
    # cameras:
    #   - front-door
    #   - garage
    
# Frigate Settings  
frigate:
  url: http://[homeassistant_ip_address]:5000

[kdoh82]

Also seeing the same exact thing. Deepstack, Facebox, MQTT, and Frigate all working properly. Double-take just continually cycling. Supervisor logs show rate limit when trying to restart the container from what it appears.

23-04-06 01:29:27 INFO (SyncWorker_9) [supervisor.docker.interface] Cleaning addon_c7657554_double-take application
23-04-06 01:29:31 INFO (SyncWorker_9) [supervisor.docker.addon] Starting Docker add-on c7657554/amd64-addon-double-take with version 1.13.1
23-04-06 01:29:40 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.6:3000 ssl:default [Connect call failed ('172.30.33.6', 3000)]
23-04-06 01:30:06 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-04-06 01:30:08 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-19294' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:989> exception=AddonsJobError('Rate limit exceeded, more then 10 calls in 0:30:00')>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 1003, in watchdog_container
    await self._restart_after_problem(self, event.state)
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 144, in wrapper
    raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more then 10 calls in 0:30:00

[dragonsoul84]

I got so fed up with trying to make it work within HA, and not getting any assistance that I just spun up an Ubuntu VM and installed all 3 (deepstack, frigate, and double-take) in docker there. I am using the proxy Add-ons now and it seems to work ok.

[kdoh82]

I was able to get it to work by installing the container from my docker-compose seperate from HA. I suspect the issue is with my supervisor and all the complaining it’s doing about having unauthorized software, docker misconfigured, etc. I’m going to have to eventually set up HA on a separate system without anything else and see if that works but for now this is just the workaround.

[dragonsoul84]

I couldn't do a separate container because I am using HA OS and it doesn't let you manage the docker separate. I'm ultimately happier this way so now I have a docker setup for other things and I'm not putting that extra load on my HA VM.

[deepansteven]

I have found a solution by moving the "secret path" folder into /config/double-take. So copy the "secrets.yaml" file you have in the default "config" location of homeassistant to this folder where everything else is located (storage/config) then it won't crash . It must be a permission error ?

[henroFall]

To elaborate here a bit, cause I approached with a small buzz on... For Noobs... Go to the configuration tab of the add on and change the secrets path to /config/double-take , then use a file manager to download/upload the secrets.yaml file from /config to /config/double-take. Then you have joy.

[cureheaded]

I have found a solution by moving the "secret path" folder into /config/double-take. So copy the "secrets.yaml" file you have in the default "config" location of homeassistant to this folder where everything else is located (storage/config) then it won't crash . It must be a permission error ?

THANK YOU !!!