[BUG] Cannot read properties of undefined (reading 'id')

[CurtisBlumer]

Describe the bug After installing Double Take in a Docker Container or in Home Assistant, an error is persistently shows and disappears in the bottom left corner stating Cannot read properties of undefined (reading 'id')

Version of Double Take v1.13.1-8e2728d

Expected behavior I expected no error messages

Screenshots

Hardware

• OS: Ubuntu 22.04 in LXC/Docker
• Browser (if applicable) Chrome and Brave

Additional context Fresh install, this happens bother before and after successful configuration

[Bug23451]

Same issue here.

Happens when using both Deepstack and compreface either one at a time or simultaneously.

Both detectors are still able to process images.

[rgriffogoes]

Looks same as this https://github.com/jakowenko/double-take/issues/313#issuecomment-1560064936

Issue on version check requests failing as latest release workflow logs got displaced by CodeQL runs.

Also same as #317

[Majestic7979]

I also have this issue.

[Knaackee]

I have the same issue. The Status of Double Take, Frigate and Deepstack is green though.

mqtt:
  host: 192.168.188.86
  username: ****
  password: ****
  
frigate:
  url: http://192.168.188.86:5000
  
detectors:
  deepstack:
    url: http://192.168.188.86:5050

[afternet]

yo igual, mismo problema. Hay alguna solución a esto?

[palletodap]

Same here. Fresh home assistant addon.

[kksligh]

same here

[Jens-Wymeersch]

same here

[townsmcp]

Clearly a lot of people couldn’t be bothered to read the threads listed above and switch to a maintained version

https://github.com/skrashevich/double-take

[Majestic7979]

Clearly a lot of people couldn’t be bothered to read the threads listed above and switch to a maintained version

https://github.com/skrashevich/double-take

What would've cost you to not be patronizing? People have varying levels of free time and responsibilities to juggle. If you have the time to read the entire internet, good for you. Many of us started using this when it was the only repository and didn't think it would be abandoned without a deprecation notice in the front page. I hope the developer is alive and well, but if he is, it's a complete dick move to walk away from something without giving notice, it costs absolutely nothing whatsoever apart from a minute or two to edit the readme and add a message saying that the project is no longer maintainer, which at least helps users find a fork.

Anyway, at least your message was useful in that you've provided a working alternative, thanks.