HA Addon Crash/Stopping without error V1.7, V1.8, V1.9 and V1.10 [BUG]

Describe the bug I’ve been having this issue for a long time, all the way back to V1.7. Till this point I keep falling back to V1.6 as it works without error. I’ve installed Double Take as an HA add-on, it starts without error. I’m able to log into Double Take and navigate around, I can see some captured images. Config looks good, nothing much in the logs. After a few seconds Double Take stops, when I drop back to the add-on page, I can see the addon has stopped. I can click start, log in again, but a few seconds later, it again stops.

This behavour has been happening across multiple HA and HAOS upgrades.

supervisor log: 22-05-24 10:16:14 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.10:3000 ssl:default [Connect call failed ('172.30.33.10', 3000)]

Double Take log: 22-05-24 10:13:05 info: Double Take v1.9.0-24bdcef 22-05-24 10:13:05 verbose: { auth: false, detect: { match: { save: true, base64: false, confidence: 97, purge: 36, min_area: 1000 }, unknown: { save: true, base64: false, confidence: 40, purge: 8, min_area: 0 } }, time: { timezone: 'UTC' }, frigate: { attempts: { latest: 5, snapshot: 0, mqtt: true, delay: 0 }, image: { height: 500 }, labels: [ 'person' ], update_sub_labels: false, url: 'http://192.168.1.166:5000' }, mqtt: { topics: { frigate: 'frigate/events', matches: 'double-take/matches', cameras: 'double-take/cameras', homeassistant: 'homeassistant' }, host: '192.168.1.166:1883', username: 'MQTTDoubleTake', password: '********' }, logs: { level: 'debug' }, ui: { path: '', theme: 'bootstrap4-dark-blue', editor: { theme: 'nord_dark' }, logs: { lines: 500 }, pagination: { limit: 50 }, thumbnails: { quality: 95, width: 500 } }, server: { port: 3000 }, purge: { matches: 24, unknown: 24 }, detectors: { compreface: { det_prob_threshold: 0.8, timeout: 15, url: 'http://192.168.1.166:8000', key: '********' } }, storage: { path: '/config/double-take', config: { path: '/config/double-take' }, secrets: { path: '/config', extension: 'yaml' }, media: { path: '/media/double-take' }, tmp: { path: '/dev/shm/double-take' } }, version: '1.9.0-24bdcef' } 22-05-24 10:13:06 info: MQTT: connected 22-05-24 10:13:06 info: MQTT: subscribed to frigate/events, frigate/+/person/snapshot 22-05-24 10:13:10 verbose: 1653351175.291872-ay2fwo - car label not in (person) 22-05-24 10:13:10 verbose: 1653351175.291872-ay2fwo - car label not in (person) Version of Double Take V1.10

Hardware

• OS: HAOS 8.1
• HA 2022.5.5
• NUC generic-x86-64
• Running on bare metal, no VM

Additional context Issue looks similar to bug #173 reported back on v.1.7

[Haloooch]

And we are fixed!

In the new config for 1.11.0 I had the secrets setup like this: SECRETS_PATH: /config My main HA secrets.yaml did live in the /config folder.

I decided to move a copy of the secrets file to /config/double-take and updated the config to match. SECRETS_PATH: /config/double-take

Double-take has been running for 5 minutes and is capturing images as expected! 😃

[robert1993]

That solved the problem. I’ve just been able to install and launch 1.10.1, working as expected.

Op 25 mei 2022 om 17:43 heeft David Jakowenko @.***> het volgende geschreven:

TotaalHost reports: This sender is trusted. There is a new beta add-on with a fix. Are you able to verify this resolves your issue?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.