Thanks for explaining that, @pe1uca@lemmy.pe1uca.dev
mike_wooskey
joined 1 year ago
Thanks for the help, @pe1uca@lemmy.pe1uca.dev.
I do still have my old server (I'm posting this from it). The new Lemmy server is using a different domain.
Thanks for the assistance, @iso@lemy.lol.
My new server uses a new domain. I do still have the old data (in fact, the old server is still up - that's where I'm posting this from).
I installed both Lemmy servers via Docker. It would be nice if I could rsync my account data (including post/comment history) from the old server to the new server, but I'm now wondering if my changing domains would make the old account not work at all in the new server.
I see the import/export settings in my new server (0.19.3) but not in my old server (0.18.3). But it sounds like exported account settings don't include post/comment history. Thanks, though, @willya@lemmyf.uk.
Congratulations! And thank you.
From what I understand, a timer's duration is the amount of time the timer was set to run for when it was started - the total time, not the time remaining.
If you're wanting to determine the time remaining in an active timer, you need something like:
{% set finish_time = state_attr('timer.timer_entity_id', 'finishes_at') %}
{{ '00:00' if finish_time == None else (as_datetime(finish_time) - now()).total_seconds() | timestamp_custom('%H:%M', false) }}
Or this version, which breaks hours and minutes into speakable parts:
{% set finish_time = state_attr('timer.timer_entity_id', 'finishes_at') %}
{% set hours, minutes = ('00:00' if finish_time == None else (as_datetime(finish_time) - now()).total_seconds() | timestamp_custom('%H:%M', false)).split(':') | map('int') %}
{{ '' if hours == 0 else hours ~ ' hour' if hours == 1 else hours ~ ' hours' }} {{ ' and ' if hours > 0 }} {{ minutes ~ ' minute' if minutes == 1 else minutes ~ ' minutes' }}
I currently use Photo structure, which is good, but its not open source and the one guy behind it, Matthew, is quite slow with progress. He's super friendly and helpful, and bug fixes are pretty quick. But feature additions are glacial.
I was considering switching to photoprism but was turned off by the attitude of some of the developers. The product looks prery good, though.
I'm pretty sure I'm going to switch to Immich, which is also really good.
A friend uses Piwigo which is decent and has good features, though I find it's very ugly regardless which skin you use.
I recently installed TrueNAS in Proxmox in this interesting Ouroboros-like configuration. So far it's been great.
Smart Home Junkie's method worked perfect! And it was quite easy and quick. Thanks for the referemce @paf@jlai.lu!
I forgot to mention that I had also renamed one of my automations in the hope that I'd be able to find the original name in my log files when whatever was trying to turn it off could no longer turn it off. But I can't find anything in the log files containing the original name.
I have a Dreametech L10s Ultra vacuum that HA recognizes via the Xiaomi Miot Auto integration. I'm trying to add a custom:xiaomi-vacuum-map-card to a dashboard, and the vacuum is recognized but the camera (which I guess is the map) isn't working due to "Invalid calbiration". But the calibration is whatever was automatically set by the card when I chose the vacuum. Hmmm.
I have the camera/map set in configuration.yaml as follows:
camera:
- platform: xiaomi_cloud_map_extractor
host: !secret xiaomi_vacuum_host
token: !secret xiaomi_vacuum_token
username: !secret xiaomi_cloud_username
password: !secret xiaomi_cloud_password
draw: ['all']
attributes:
- calibration_points
- charger
- cleaned_rooms
- country
- goto_path
- goto_predicted_path
- goto
- ignored_obstacles_with_photo
- ignored_obstacles
- image
- is_empty
- map_name
- no_go_areas
- no_mopping_areas
- obstacles_with_photo
- obstacles
- path
- room_numbers
- rooms
- vacuum_position
- vacuum_room_name
- vacuum_room
- walls
- zones
This vacuum has not been Valetudo-ed - it's in new condition from the vendor.
Does anyone have any suggestions?
view more: next ›
Thanks, @iso@lemy.lol.