• 0 Posts
  • 46 Comments
Joined 2 years ago
cake
Cake day: August 4th, 2024

help-circle





  • Any smart lock should work on an interior door, you may have to drill a deadbolt but its the simplest solution. Switchbot and U-tec both make smart locks with fingerprints and excellent Home Assistant integration. Ubiquiti also sells magnetic latches you could install for access control if you’re in their ecosystem.

    If you can give up on Home Assistant integration/smart features, however, there are oodles of push-button and even fingerprint door (without other connectivity features) knobs out there. Most of them are terrible quality and not secure but that doesn’t really matter to you and they are cheap.


  • Yeah but the problem is a LOT of common domestic door locks and padlocks are vulnerable to low skill attacks like raking or other simple bypasses that you can learn in a couple hours. The number of lock makers that cheap out and neglect even basic higher security features is shocking. Unless you really go out of your way and specifically go looking for a quality lock are you unlikely to find one with something like security pins and higher tolerances that resist picking.




  • What would dual Z axes on the mini achieve? The existing cantilever design is plenty stiff in my experience, I’m skeptical you’ll get any significant increase in print quality or speed, and I suspect at the cost of having to fiddle around a lot tuning settings to get it back to where it started as the existing firmware has a lot of tuning for the mechanical behavior of the exisiting design. So, if you’re not happy with the mini as is, I would be looking at a different printer rather than a dual Z mod.

    Having myself indulged in the temptations of homebrew 3D printer mods, I came to realize that not all mods out there actually improve performance, especially this type of serious mechanical overhaul of what is already a fairly sophisticated and optimized design. A decent part of the mini’s secret sauce is in the firmware, and this is going to break that.





  • Nah, unfortunately I watched this video a couple weeks ago and while it is a waste of time, there is at least a bit more to it than that. DNS is part of it but it’s more “I built a regular router”. The backstory is the OP’s apartment has some kind of shady wireless ISP as their only option. They build a router to hide connecting multiple devices behind NAT (which they barely even talk about), but they don’t do much else to actually hide devices. Honestly it’s really basic and could be achieved with a cheap travel router, though the 3D printed enclosure they built is pretty cool.

    Even if you’re not a Linux networking neckbeard and want to learn this video isn’t worth watching because it just glosses over the actual useful/interesting/complicated parts.



  • Not entirely sure about the de-google’d version of the Home Assistant companion app, but I know the regular companion app uses Firebase (and whatever the Apple equivalent is called, I forget) to deliver notifications, and it still would using Telegram as Telegram also uses Firebase. Apprise is a bit different as it can use multiple backends. Regardless, there are multiple ways to do things. Ntfy iphone and google app do not route your data through a third party server. I self host the ntfy server on my own machine and domain and my phone connects to it and receives data. It will deliver notifications wherever I am, not just in my LAN. It also provides a nice UI akin to Pushbullet I can use to send myself stuff privately.

    You can’t replicate all of what ntfy does with Home Assistant. There’s more to it than just delivering notifications, it’s the whole app frontend and persistent data etc. If it’s not clear to you what it’s for from my description you might have to go look into it yourself. Look at PushBullet, that’s most similar to what I primarily use it for.


  • Home Assistant notifications and almost all other notification services on phones actually route notifications through a cloud service like Firebase because Apple and Google try to railroad apps into their platforms. Ntfy lets you actually self host notifications without a third party, but also without killing your battery.

    That’s not the main thing I care about, though. Mainly I use it as a self hosted replacement for PushBullet, to share links and files with myself across machines and do some light alerting for servers and stuff (e.g. TrueNAS errors). Some of that could he done with HA, but ntfy is just better for some other uses with stuff like its web ui.

    Plus, apart from that ntfy is really easy to integrate with other stuff, like its easy to send a notification from a shell script or web hook so you can hack it into things that don’t otherwise support notifications (there are also lots of things that support ntfy natively, e.g. the arrs).