u/sendcodenotnudes

https://preview.redd.it/x27m51a8ndbh1.jpg?width=946&format=pjpg&auto=webp&s=964a9d646090c24906db364b69e777a24064d859

I have a EX40 and noticed that, when in cruise control, thee are three distinct curved lines showing up. What do they mean?

I presume that the central orange-ish one is the speed that is set (50 km/h here) -- mirroring the digital `50` above the current speed indicator.

The twe other ones (most let and right, white-ish) seem to be connected, summing up to the set speed. I think that the rightmost one always show up (to mirror the current speed (I am not sure, I never look there. I do not understand what the leftomost one is for -- is it just "set speed - current speed"? If so it is not very useful, borderline distracting.

When I was using dsnmasq I had the possibility to map a name to a MAC: every time this MAC was being offered an IP, the built-in DNS was mapping my chosen name to that IP. In other words, the IP was floating, but each device had a wel-defined name.

I cannot find this feature in technitium. The only thig I found is to fix the current IP that the device got, and then manually map this IP to a name in the DNS section.

Is there a better way?

I need advice on setting up a relatively complex DNS resolution.

My home LAN is on 192.168.10.0/24. Addresses are served by Technitium (running in a container on 192.168.10.2) and the DHCP offer includes the DNS resolver, namely itself (192.168.10.2).

I have a public domain (example.com) which is resolved on Internet to a public IP (there is a wildcard entry for *.example.com). In the LAN Technitium has an example.com zone with a wildcard entry pointing to 192.168.10.2 → split horizon DNS.

All of this works fine: a client on internet accessing https://a.example.com will get resolved to the internet IP, which then is served by Traefik on 192.168.10.2 (this is my main an unique "server"). A client on the LAN will see https://a.example.com resolved to 192.168.10.2.

Now arrives Tailscale to shake all this up. It is installed on all clients, and the clients use MagicDNS.

If I do not set up anything special for example.com in Tailscale:

• on Internet, for a generic client (not mine), the resolution is OK (public IP)
• on Internet, for a client of mine (with Tailscale), the resolution points to the public IP (which is OK)
• on my LAN, the resolution also points to the public IP (which is not good, there should be a split DNS resolution to 192.168.10.2)

Now, after setting up in the Tailscale split DNS the domain example.com to point to 192.168.10.2 and fd7a:X:X::X:X:

• in the LAN: aaa.example.com correctly resolves to the LAN address 192.168.10.2.

• on Internet, it fails:

> nslookup aaa.example.com
Server:  magicdns.localhost-tailscale-daemon
Address:  fd7a:115c:a1e0::53

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to magicdns.localhost-tailscale-daemon timed-out

Note that the server address fd7a:115c:a1e0::53 is different from the one set up in Tailscale

Is there a way to solve these two problems?

Je voudrais donner mon corps à la science après ma mort -- surtout pour des raisons financières mais aussi pourquoi pas pour aider la science et l'éducation des médecins.

Je m'en fous complètement de ce qui se passe avec mon corps à condition qu'ils soit récupéré rapidement avec un minimum de formalités et qu'ils en fassent ce qu'ils veulent sans embêter ma famille après.

Sur le papier tout va bien (d'après le site administratif). Ma question est: à quel point est-ce que c'est efficace. Je présume qu'ils peuvent dire au moment de ma mort "non, pas besoin" et ma famille se retrouve avec un problème. Est-ce que c'est courant?

Je cherche des réponses de gens qui ont eu des experiences là dessus (ou travaillent directement avec le service). Merci.

EDIT: au vu des commentaires -- s'il vous plaît, je suis intéressé strictement par l'efficacité du service, pas si c'est bon ou pas et ce qui se passe avec le corps après

---

Ou bien est-ce qu'il y a un moyen de réduire au minimum l'impact sur la famille (et accessoirement les frais, mais c'est secondaire)

I am looking at the Serve Stale feature:

> Enable the Serve Stale feature to improve resiliency by using expired or stale records in cache to respond when the DNS Server is unable to reach the upstream or authoritative name servers to refresh the expired records before the Max Wait Time configured below.

Specifically, I am inclined to set Serve Stale Max Wait Time to 0 with the assumption that the clients will receive a reply that is likely to be correct, and that that the stale record will be fixed anyway.

The last part is what worries me (in my assumption). Let's say a client requests a.example.com, which is in the cache but stale, and immediately receives 10.10.10.10 as the answer. When would a.example.com be checked again for the correct record at the authoritative server's?

La question fait suite à https://www.reddit.com/r/AskFrance/s/rB9iC4WYP3

​

Est ce que vous connaissez un endroit à disons 1 ou 2h de route de Paris où je pourrais faire un peu de marche (disons 3 ou 4 heures), un bivouac dans la nature et revenir à la voiture?

​

Pas besoin de folies, ce serait pour partir avec mes (grands) enfants pour un moment ensemble en automne

To cybersecurity forensic experts: is there anything to recover from an SSD today?

​

HDDs have slack space, addressable with a read (i.e. you can reach out to blocks on disks). Not SSDs.

​

Are there any techniques (short of probably flashing a specific firmware)?

I am testing a Forerunner 165 (after having a Amazfit before). It is just great for my needs (beginner). I am considering the Viva 6, we will see.

Anyway, my question is about pool laps. I went yesterday to the pool and started the swimming exercise. This is in a 50 m pool.

Back at home, I had a look at my incredible results (I am joking, but I see that having a watch psychologically pushes you forward, which is good for a lazy beginner). And here, surprise: the circuits are not 50 m each. Some of them were aggregated into 100 or 250 m blocks.

My wild guess is that laps are not monitored at all, only circuits are. And a circuit is a continuous exercise time, split by rest time.

This is annoying (also the fact that it does not detect the kind of swimming (freestyle, ...))

Am I doing something wrong?

---

As a side note: I was expecting to have on my main display the number of laps, but got less useful information (something about the time spent resting etc.). As I was pressing here and there I discovered that by scrolling though the views I had one with the total distance. This is acceptable (though I am more used to laps but I can live with that). In the meantime I pressed something that made me loose a lap.

I messed up by letting Immich update itself and I have an error about a previously executed migration file missing.

 [Nest] 7  - 06/05/2026, 8:55:56 AM     LOG [Microservices:WebsocketRepository] Initialized websocket server
 [Nest] 7  - 06/05/2026, 8:55:56 AM     LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for clip_index of 57206 rows
 [Nest] 7  - 06/05/2026, 8:55:56 AM     LOG [Microservices:DatabaseRepository] targetLists=1, current=1 for face_index of 67195 rows
 [Nest] 7  - 06/05/2026, 8:55:56 AM     LOG [Microservices:DatabaseRepository] Running migrations
 [Nest] 7  - 06/05/2026, 8:55:56 AM   ERROR [Microservices:DatabaseRepository] Migrations failed: Error: corrupted migrations: previously executed migration 1773242919341-EncodedVideoAssetFiles is missing
 Error: corrupted migrations: previously executed migration 1773242919341-EncodedVideoAssetFiles is missing
     at #ensureNoMissingMigrations (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/migration/migrator.js:487:23)
     at #getState (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/migration/migrator.js:439:40)
     at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
     at async run (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/migration/migrator.js:409:31)
     at async /usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/kysely.js:569:32
     at async DefaultConnectionProvider.provideConnection (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
     at async #migrate (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/migration/migrator.js:268:20)
     at async DatabaseRepository.runMigrations (/usr/src/app/server/dist/repositories/database.repository.js:340:36)
     at async /usr/src/app/server/dist/services/database.service.js:110:17
     at async /usr/src/app/server/dist/repositories/database.repository.js:393:27
 microservices worker error: Error: corrupted migrations: previously executed migration 1773242919341-EncodedVideoAssetFiles is missing, stack: Error: corrupted migrations: previously executed migration 1773242919341-EncodedVideoAssetFiles is missing
     at #ensureNoMissingMigrations (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/migration/migrator.js:487:23)
     at #getState (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/migration/migrator.js:439:40)
     at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
     at async run (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/migration/migrator.js:409:31)
     at async /usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/kysely.js:569:32
     at async DefaultConnectionProvider.provideConnection (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
     at async #migrate (/usr/src/app/server/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/migration/migrator.js:268:20)
     at async DatabaseRepository.runMigrations (/usr/src/app/server/dist/repositories/database.repository.js:340:36)
     at async /usr/src/app/server/dist/services/database.service.js:110:17
     at async /usr/src/app/server/dist/repositories/database.repository.js:393:27
 microservices worker exited with code 1
 Killing api process

Is there a way to recover from that?

I have backups going back about a year so I could use that, but this will probably conflict with the photos loaded in the meantime (?)

Today I moved from Pihole to Technitium after some 10 years on Pihole. The transition was seamless and I like what I see in Techninium (except for the name which I always type wrong).

I do not understand what the "protocol" graph in the dashboard mean. Since I choose the protocol in the settings (DNS-over-UDP, DNS-over-TLS, ...), it will always be 100% this protocol, right? (in my case, 100% UDP)

> Select a protocol that this DNS Server must use to query the forwarders specified above

So why is it there?

I have a working SnapRAID setup with a wrapper that manages the execution and results. I was occasionaly getting errors becaise of a file that changed mid-snap so I decided to exclude the whole directory.

I added

root@srv ~ # grep deluge /etc/snapraid.conf
exclude /mnt/25ddb329-a622-443a-92f9-348480101f0c/media/deluge/

I still get the same occasional errors:

Unexpected time change at file '/mnt/25ddb329-a622-443a-92f9-348480101f0c/media/deluge/in_progress/XXX' from 1778807435.522289102 to 1778807456.782665550.
WARNING! You cannot modify files during a sync.
Rerun the sync command when finished.
Unexpected time change at file '/mnt/25ddb329-a622-443a-92f9-348480101f0c/media/deluge/in_progress/XXX

What is wrong with my exclusion?

---

Side note: as I am re-reading the message, I am realizing that this may not actually be a snap-stopping event, but just an information about this specific file (and the snap continues normally). In that case this is not such an issue, except for the notification I get in such cases. But I could silence it in the wrapper.

I bike to the office and, somewhere on the way, there is a place where I have to walk (to climb up a very steep road).

I start the trip by switching on the bike mode -- what is a reasonable approach to handle this walking part?

• switch to walking (is it possible to switch between activities?)
• just let it run
• pause (I would prefer to avoid this one because I will forget to switch it back)

First of all: apologizes if this is not the best subred (I know this is not the best one but people who are here are likely to have met the issue with HA)

I bought a few Tuya plugs - I just have one other Tuya device (a wall switch) which has been going strong for 5 or 6 years (with tuya-local). This and a nice price tag and here I am, owner of 3 new plugs that also measure the power consumption.

After a lot of horror stories, I ended up with a clean setup: Tuya Local + the Tuya IoT platform and I see all my devices (the old switch and the plugs). The plugs started to gather data and I was happy.

This until I realized that after working fine for 2 or 3 hours, the plug went offline -- both in HA and in the cloud platform. Smart Life also sees it as offline, but tries to (successfully) connect with BT (which does not help much except to say that the plug "works").

My question: do you have any experience with Tuya plugs going offline? If so is there a solution to prevent this? Or should I just taken the WiFi or Zigbee ones I use in other places because this is how Tuya is 😐?

I am trying to clean up my HA installation (it's been years and years) and hunting the warnings and errors in the logs. Some of them I will have to live with, but some I need to fix because they are constantly added to the log stream

hass-1  | 2026-04-27 14:39:00.409 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities calendar.martin, calendar.michael are missing or not currently available
hass-1  | 2026-04-27 14:39:00.536 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities weather.forecast_home, weather.pirateweather are missing or not currently available

calendar.martin and calendar.michael come from the Google Calendar integration. They are old, have never been used, were unavailable in the integration and I deleted them. So the integration is clean.
weather.forecast_home and weather.pirateweather are from integrations I was testing to rate them against the national one. They are gone now.

But the entities are still used somewhere. My question: how can I track down the places they are still used?

Note: Spook does not see them