yayitazale

E-Ink Hub has moved to GitHub: https://github.com/yayitazale/eink-hub Nothing breaks for existing installs: registry.gitlab.com/yayitazale/eink-hub keeps getting every release. The template now uses ghcr.io/yayitazale/eink-hub:latest, which is the image to use from now on. To switch, edit the container and set Repository to ghcr.io/yayitazale/eink-hub:latest, then apply. Your data in /data stays as it is. Issues and ideas now go to https://github.com/yayitazale/eink-hub/issues

E-Ink HubSelf-hosted control center for e-ink photo frames, with Immich integration. A single container with a mobile-friendly web UI. Supported frames - BLOOMIN8 E-Ink Canvas (local) - SwitchBot AI Art Frame (cloud, not tested) - Frames running TRMNL firmware: TRMNL, Waveshare PhotoPainter, reTerminal… (local, not tested) - Your own ESP32 / Raspberry Pi frame through an open protocol (local, not tested) Features - Exact previews with smart crop, manual crop, border or blurred background - Collections from uploads or Immich (albums, people, favourites, smart search, "on this day") - Schedules with active hours, battery-friendly pull mode, Bluetooth wake for BLOOMIN8 Links - Documentation: https://yayitazale.github.io/eink-hub/ - Unraid guide: https://yayitazale.github.io/eink-hub/guide/unraid - Source code and issues: https://github.com/yayitazale/eink-hub - Changelog: https://github.com/yayitazale/eink-hub/blob/main/CHANGELOG.md - Image: ghcr.io/yayitazale/eink-hub:latest Install 1. Search eink-hub in Apps and click Install. 2. Set LOCAL_URL to your Unraid LAN address and port, e.g. http://192.168.1.10:8080. Frames use it to reach the hub, so it can't be "localhost". 3. Open the WebUI, choose an admin password and add your frames (or a Simulated Canvas if you have no hardware yet). Tailscale The template is ready for Unraid's Tailscale integration. Install the Tailscale plugin, edit the container and turn on Use Tailscale. Serve on port 8080 and the state folder are already set. After you approve the login link from the container log, the hub is available at https://eink-hub.<your-tailnet>.ts.net. The hub detects that address by itself and uses it for the QR code shown on the frames. You also get https, which the phone's Bluetooth wake needs. Please use Serve, not Funnel: Funnel makes the whole hub public, admin page included. If you need SwitchBot (the only frame that requires a public address), see the docs to expose only the pictures. Network Bridge is enough: add frames by IP or with "Search the network". For mDNS discovery, use br0 so the container gets its own LAN IP, and use that IP in LOCAL_URL. Asking for help Please include: - Your Unraid version - Your frame model(s) - The container log, or Settings → Server logs in the web UI Bugs and feature requests are also welcome as issues on GitLab.

@ It seems like everything is back to normal. All my templates disappeared for a while—I don't know why. I haven't heard back from any administrators...

No idea why, thanks for letting me know, I will check what happened...

You have some config issues, I reccomend you to startup with a minimal config...

You'll need to reinstall the app from scratch to use the new template, since many changes have been made. You can do this using your current folder and database, so you won't lose anything, but there are significant changes regarding ports (port 5000 is no longer used) and other changes that require the use of the updated template.

Sorry for the late reply; I was on vacation. The logs do not show the loaded model; if it starts up without errors, you should be using the model described. You will be able to observe changes in system metrics, inference time, and resource consumption.

Okay, this is useful for a very small percentage of deployments. In any case, if this is really that useful, I think it would be better for you to contribute these features to the main Frigate development branch—not as a separate project—since that’s what a Free Software project created and maintained by a community is for. https://github.com/blakeblackshear/frigate

This is pretty much useless in an UnRAID environment, where the OS already has a built-in system for periodically moving files from the cache pool (designed for use with SSDs) to the disk array (designed for use with HDDs)...

I think the problem resides on the Unraid side, not on the container side.

Did you created a V9 model?

Not sure but I think you don't need this: providers: - CUDAExecutionProvider cuda_graphs: false https://github.com/blakeblackshear/frigate/discussions/23546#discussioncomment-17412679

https://docs.frigate.video/frigate/installation#ports 8971 Authenticated UI and API access without TLS. Reverse proxies should use this port. EDIT: You're right, https://docs.frigate.video/configuration/tls, so I just modified the template so that future new installations will use HTTPS by default for the web UI. Thanks

I cannot help you without more info, can you share a screenshot of the configuration of the container and the configuration file (config.yaml) created during the initial startup?

From your logs, I notice that Frigate is starting successfully, but I don't see any specific detector initialization logs that would indicate whether the YOLOv9 model is loading correctly. The logs show the detector process starting but don't show model compilation or loading details. Check your config file and check if the model file is in the correct place.