SayCyberOnceMore

  • 35 Posts
  • 1.39K Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle






  • Yeah, really I’m just wanting to tie Alexa into HA’s ability to control relays, etc and turn things on & off… but I still want it to work when Amazon pulls the plug on Alexa’s APIs (not heard anything, just my guess at future enshitification) - she listens to the “radio” on Alexa a lot, so - at the moment - it’s not the smart speaker part I’m too worried about - unless of course the Pine Speaker could host HA too :)





  • Considering it - appears - to also need Google Play services then I don’t know how that will affect degoogled phones.

    I’ve disabled all the Google services on my phone, and I’m able to restart them if necessary, but I don’t have a google account (which has to be tied to a physical phone number?), so it’s all waaay to sketchy for me.

    And the API that connects to? Is that auditing anything else of mine? Capturing yet more data?

    Not happy, me.











  • Kinda already covered by others here, but my summary:

    You won’t have partitions nicely numbered from 1~3 unless you start again.

    1 - Backup

    2 - Check the backup

    3 - Boot from GParted Live (feel free to use another live distro with gparted on)

    4- Delete sda1, sda2, sda3 & sda4

    5- Move sda5 to the beginning of the drive and resize down to 512MB

    6- Slide sda6 & sda7 down next to sda5. I like to have 1MB gap between all partitions to deal with future issues (sometimes restoring a partition might nip the next one)

    7- resize /home to fill the rest of the drive

    8- redo another backup

    If you wanted, you can apply each of those steps and then reboot to check it’s all working, then you’ll gain confidence in what’s happening for the future.

    I also advise doing a health scan of your drive to check it’s SMART parameters. Something like smartmontools (with gsmartcontrol if you like a GUI). Then you’ll know if the drive’s going to die during all that data moving…