I see there are a few performance comparisons, but I wonder how this compares to ty. I guess it may be a while before we can really compare the two since they’re both in alpha/beta.

Maybe I’m not picking up on the different models correctly, but the first link I sent was about Z-Wave.

Can I use the Assure Lock 2 with my Z-Wave Hub?

The Assure Lock 2 supports the following Z-Wave modules:

• Z-Wave 500 Series (version 1.8.1)
  • Module Part Number: AYR-MOD-ZW2-USA
• Z-Wave 700 Series (available at a later date)

I know some people, like yourself and the commenter thelordzer0, have had success using the lock without a Yale account or app. I’m not sure why you’ve been able to but others are reporting differently. I was just commenting to help OP out in case they’re one of the other people who were forced to create an account and/or use the Yale app to initialize their lock.

Ah, you’re right about 800 mesh and LR.

I’ve seen multiple reports online about the lock requiring an account though and Yale’s documentation stating that it only supports 500 series. Below are just a few examples of reports indicating that a Yale account is required for setup. Is yours the same model?

• https://reddit.com/r/homeautomation/comments/xuy0iv/those_interested_in_the_yale_assure_2_beware/
• https://community.home-assistant.io/t/yale-assure-lock-2-with-fingerprint-sensor-and-z-wave/789555
• https://github.com/zwave-js/zwave-js/discussions/5391

This lock requires a Yale account to register/setup the lock though, correct? In other words, while you can use the lock locally, it first needs to be associated with a Yale account.

Additionally, if I remember correctly, its Z-Wave module is a 500 series using the Security 0 (S0) standard instead of the more modern 800 series and/or Security 2 (S2) sandard. The 800 series (introduced in 2021) should provide much better reliability and range while the S2 standard (introduced in 2017) should make your connection more secure and less chatty. However, the 800 series does not operate as a mesh network and is still working through the final legislative approvals in Europe.

Unfortunately, I don’t think there is a one-size-fits-all, perfect solution. I believe the only Z-Wave lock that addresses the two items in my comment is the Philips 4000 Series deadbolt. One issue with that lock is I believe you have less control over the combinations without the Philips app (eg: cannot specify date/time ranges when a code will work, can only add codes while physically at the device, etc.).

I’m not too sure - I’m not too familiar with any of these services (including PinePods 😂). I know this type of feature is a common request for any audio related services though. I imagine that this is something that could be added at some point, but I’m not sure what the effort would be.

I don’t see anything about it on the roadmap for v1 or anywhere else on Pinepods’ issues. Perhaps the developer/maintainer @madeofpendletonwool@lemmy.world can chime in or an issue on Github can be created with more information about this feature request?

The biggest benefits are likely:

• Single service for all your podcasting needs (ie: searching, storing, playing, tracking, and syncing podcasts + listening history)
• Multi-device, cross-platform support (I know this can be somewhat accomplished through the process that you mentioned, but you would need separate apps for iOS and desktop/web)
• (speculation/assumption) It may be easier to get newer features added to Pinepods (especially those that you or the community contributes and/or for server-related features) since the project is focused on just podcasts
• I’m not aware of a similar all-in-one podcast server + client service. As Pinepods matures, it can offer features/services that may not be easily included in the services you mentioned. For example, searching by transcript across all downloaded podcasts or summarizing/combining multiple podcasts (which may be helpful if you listen to multiple daily/weekly/monthly “news” podcasts of a similar topic).
• Supporting a newer project and open source community

The first two may not apply to you in particular, but I’m sure if you have other users that use the services you support then I’m sure they would appreciate having to learn/use a single app/interface for podcasts instead of having to learn one for searching/downloading (if they care about that at all), one for listening on mobile, one for listening on web, and another for managing their download/play sync.

Thanks for the response!

Sorry to hear about the frustrations regarsing F-Droid, but glad to hear it will at least be on IzzyOnDroid. Excited to check it out once it’s available on there!

Excited to see the app develop over time. I bet Pinepods will be able to meet all my podcasting needs sooner than I can imagine.

Thanks for the update! Really appreciate all of the work that has gone into this.

A few quick questions:

• Will the Android app be available on F-Droid? It looks like it should/will be, but I don’t see it on F-Droid at the moment.
• Is it possible to download episodes from a Pinepods server to a local device via a Pinepods client so the episodes can be stored on something externally, like a USB drive or old MP3 player? If so, can all/multiple episodes on the server for a podcast be downloaded without having to manually select each episode? The only download options that I have seen are for the server to download the episodes from the podcast’s source.

I think that any guides you find for Gitea + Renovate should work still for Forgejo + Renovate.

I believe the process is:

• Create Forgejo instance
• Create a user for Renovate within Forgejo
• Using the CLI on your local machine (or another tool to complete this step), create an SSH public/private key for the Renovate user
• Log into Forgejo using the Renovate user and configure the previously created SSH keys and separately generate a Forgejo token
• Create a Renovate instance with settings for at least RENOVATE_GIT_PRIVATE_KEY (SSH private key value), RENOVATE_TOKEN (Forgejo token value), RENOVATE_PLATFORM (gitea), RENOVATE_ENDPOINT (Forgejo API base URL), and any other Renovate settings that you may find helpful/necessary to configure (eg: GITHUB_COM_TOKEN, RENOVATE_AUTODISCOVER, etc.)
• Depending on how you want things to work, you may need to give the Renovate Forgejo user access to individual repos

uv

It is made by the Astral team, who made ruff and are working on a static type checker. They’re making great Python tooling and uv is no exception.

Congrats on getting everything working - it looks great!

One piece of (unprovoked, potentially unwanted) advice is to setup SSL. I know you’re running your services behind Wireguard so there isn’t too much of a security concern running your services on HTTP. However, as the number of your services or users (family, friends, etc.) increases, you’re more likely to run into issues with services not running on HTTPS.

The creation and renewal of SSL certificates can be done for free (assuming you have a domain name already) and automatically with certain reverse proxy services like NGINXProxyManager or Traefik, which can both be run in Docker. If you set everything up with a wildcard certificate via DNS challenge, you can still keep the services you run hidden from people scanning DNS records on your domain (ie people won’t know that an SSL certificate was issued for immich.your.domain). How you set up the DNS challenge will vary by the DNS provider and reverse proxy service, but the only additional thing that you will likely need to set up a wildcard challenge, regardless of which services you use, is an email address (again, assuming you have a domain name).