• 2 Posts
  • 49 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle
  • I’ll have to have a look when I’m next in the vacinity but I’m pretty sure I have an APC Easy UPS on mine and it works out of the box.

    Let me get back to you…

    Update: It’s an APC Back-UPS 850. No doubt the instructions banged on about requiring Powerchute but I just plugged it into the Syno and it worked fine. You do need to enable UPS support on the NAS itself of course, from Control Panel/Hardware & Power/UPS, and set it to USB UPS.




  • I have my dock plugged into a smart plug and the laptop set in the BIOS to turn on when it receives power. I have an NFC tag on my coffee machine that I bloop while I’m making my morning brew, and that turns the dock on so that everything’s ready when I move into the office.

    For turning things off I have HASS.Agent installed and sending state updates (locked, unlocked, etc, which is useful for other automations) and when that sensor goes unavailable for 15 minutes it turns the plug off. I find that’s long enough to allow it to reboot for updates and what not.

    The sensor does report shutdown, reboot, and sleep states but I found that it often happens too quickly to get the change sent, so the unavailable state is more reliable.


  • Unless you’re hosting VHDs and need maximum throughput (in which case use NFS), SMB is going to be the easiest to setup and maintain across those 4 platforms.

    The Linux SMB implementation is decent and supports the latest version of the protocol (or close to, at least) whereas NFS in Windows ain’t so great and is a bit of a pig to get working in my experience.



  • Z2M. I had a ZHA setup and I’ll give it to them, it was super easy to setup (barely an inconvenience). Then I bought a set of sockets with power monitoring but found that they used a non-standard way of reporting those stats.

    They were seemingly quite new and both ZHA and Z2M had ‘quirks’ submitted very quickly to make them work, but while the Z2M quirk was approved and added almost straight away, 2 or 3 months later I was still waiting for the ZHA one to be approved.

    Then, like you, I wanted to change the Zigbee channel and took the opportunity to switch to Z2M where the sockets and their power monitoring have been working perfectly ever since. It’s definitely more complicated to setup initially but you get more control overall and, at least from my experience, the overall device support is much better.

    Note: I did initially have loads of stability issues when making the switch, but it was due to me flashing the combined Zigbee+Thread firmware to my Sonoff stick. The fix was to turn off the OpenThread Border Router in the Silabs addon and then everything was stable again. I don’t have any Thread devices yet, of course.





  • This is the correct answer. Due to wear levelling, a traditional drive wipe program isn’t going to work reliably, whereas most (all?) SSDs have some sort of secure erase function.

    It’s been a while since I read up on it but I think it works due to the drive encrypting everything that’s written to it, though you wouldn’t know it’s happening. When you call the secure erase function it just forgets the key and cycles in a new one, rendering everything previously written to it irrecoverable. The bonus is that it’s an incredibly quick operation.

    Failing that, smash it to bits.


  • Very little. I have enough redundancy through regular snapshots and offsite backups that I’m confident enough to let Watchtower auto-update most of my containers once a week - the exceptions being pihole and Home Assistant. Pihole gets very few updates anyway, and I tend to skip the mid-month Home Assistant updates so that’s just a once a month thing to check for breaking changes before pushing the button.

    Meanwhile my servers’ host OSes are stable LTS distros that require very little maintenance in and of themselves.

    Ultimately I like to tinker, but once I’m done tinkering I want things to just work with very little input from me.


  • Gotta hold my hands up and admit that in my initial haste to confirm the price I fell victim to the Play Store putting sponsored results ahead of what you actually searched for and I installed some crap called minimalist launcher, which charges £70 for a lifetime license. That’s what my “insane” comment was based on.

    In comparison it’s nowhere near that bad for Niagara, but it is still pricey compared to most apps, and I balk at paying a subscription for software in general so that still stands.

    Might give it another go after all…


  • Reading the article and justification given I do actually get the idea of it. They want to levarage the parent company’s clout and connections in order to convince other app makers into implementing a way for Sesame, the universal search app/plugin, to pull results directly from those apps. For the parent company it would give them a USP in the analytics market.

    In short: Think of searching for a product from the launcher and rather than it opening Google, it returns results directly from the Amazon app, or eBay, or any other app that supports the functionality. Obviously there’ll be an affiliate kickback for any click-through and you’ve got a decent revenue source.

    It’s a good idea, I get it. Would I feel comfortable using it? I don’t know. On the one hand it just cuts out the middle-man of searching for and clicking through to products via Google etc. On the other hand, all of the concerns already raised in this thread!


  • I like Niagara but it’s insanely expensive, especially as a subscription. I don’t know how people justify it.

    Edit: The above was based on me getting duped by a Play Store sponsored search result and installing some crap that charges £70 for a lifetime licence. In comparison Niagara feels like much better value, but it’s still expensive compared to most apps and I still don’t like subscribing to software in general.