• 5 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle



  • The router polling integration is probably a bit superfluous for devices that have the companion app installed.
    Although, it’s still helpful for other devices like guests’ phones, or non android/ios devices.

    Not sure how helpfully to your use case these will be, but a few ideas…

    It’s been a while since I tinkered, but I think you can also assign multiple devices to a person and track the person’s presence instead of a specific device.
    You can also create a group of persons, which is handy for some use cases.

    As an example, I have a group.us which contains person.me and person.mypartner. The group’s status is home if either of us are home and only changes to away if neither of us are home.

    Similarly, I have a group.guests which contains guests who sometimes spend the night.
    If any guests are home, my goodnight automation ignores the bathroom and the guest bedroom lights.

    group.guests:

    entity_id:
      - input_text.manual_guest_tracker
      - person.guest
      - person.fren
      - person.otherfren
      - person.olefren
      - person.stepbro
      - person.nephew
      - person.cousin
      - person.niece
    order: 3
    icon: mdi:bag-carry-on
    friendly_name: Guests
    

    I have an input boolean that changes input_text.manual_guest_tracker to home/not_home if we wanna enable “guests mode” without having to track a device.

    Single person with multiple trackers:
    person.fren:

    editable: true
    id: fren
    device_trackers:
      - device_tracker.applewafren
      - device_tracker.iphonefren
    friendly_name: Fren
    
    

  • In the companion app, where you choose the update interval, there’s a banner of text that explains it.
    Some sensors update instantly (such as connected WiFi SSID), others update on an interval (such a battery level or pressure sensor).
    The maximum update interval applies to non-instantaneous sensors.

    Sensors will update either instantly or on a defined interval. If the sensor supports instant updates then it will always receive instant updates. View the sensor details to learn which sensors update instantly.
    If the sensor does not support instant updates then it will update based on one of the below selected options
    You must restart the application when you make any changes to this setting

    When you select which sensors to enable you can see whether it’s an instantly updating one or one on a timer



  • Thanks for taking action and letting us know.

    edit: Why the downvotes?

    No one can really answer that other than the people who clicked the buttons.
    I sincerely have no hard feelings here, but I have to point out the irony of questioning the downvotes you received but not those you cast yourself on kersploosh’s polite request.

    PS: FWIW, neither of your 2 downvotes are from kersploosh or myself but rather from random users.

    Anyway, thanks for making content and contributing to making this is one of the more interesting communities.






  • I use different things for different edges.
    Most of my hard working tools end up with a convex edge, I like them better for chopping stuff like wood and asklemmy posters bones and its good durability doing so.
    So that’s either automotive sandpaper in various grits, or 3M’s paperless abrasive sheets (easier on curvy stuff). Slap a thin foam sheet or two on your work surface, choose your paper grit, work it, change to a figer grit, repeat until happy.
    What I like about those is they’re huge and easily replaced. I’ve done flat edges with them too by simply not using the foam.

    For more traditional flat edges, I’ve mostly been using a pair of DMT’s dual sided butterfly thingies, so that’s indeed 4 different grits. That’s what I use because that’s what I got ages ago and got used to them. They’re ok. Nothing amazing, but it works and it’s small enough to sit in the kitchen drawer.

    I also have a fancy kit that clamps on the blade with a metal arm that keep the tiny stone a the same angle and whatnot but it’s kinda annoying to setup.
    It’s probably more consistent than anything I do by hand, but I never bother using it because it’s clunky.

    In the end, whatever you actually use is gonna be better than anything that sits in storage.




  • Right, while it technically has a user-level solution, you’re right that a brand new user would simply not know about any of this.
    I stumble upon a few now and then when they try and report stuff from there.
    So… something like autoblocking the instance on user creation… which might make more sense than outright defederation. A bot could probably be made to do that and send them a DM with instructions on how to change it off they so wish.

    Thanks for your input





  • A1: probably, although that’s more processing power. The tool I used to fix it would have outputted a second image file if the extra data had been an image, which is then a weird case to handle. (Upload both? Make 2 links?) Certainly, it could output a better error message though.

    A2: Should be lemmy-wide, although technically a malicious server could disable that somehow, which I think would only affect their local users. ie: don’t make an account on a server you don’t trust.

    A3: It is a server specific setting. It’s easy enough to change the setting. Bigger limits uses more storage which costs money

    A4: Possible, I would think. No idea if that’s ever on the devs’ roadmap. I think that would be added to the pict-rs code which is then used by the lemmy server.
    Both are open source projects, so an instance implementing this could then share the code so it’s eventually a feature for everyone.

    I’ve ran into bugs before on some public image host I don’t remember where it wouldn’t strip metadata if you uploaded an album. It’s probably a good practice to strip metadata before uploading, although much less convenient. I double-check that it still works here from time to time, doubly so after upgrading versions.