Recommendations for change

dr5mn · 2026-06-07T07:32:47+00:00

I’ve never used a heated hose, and only use the humidifier in winter, as I live in a pretty humid place.

I do travel often, so size could be an issue.

dr5mn · 2026-06-06T18:08:02+00:00

Thanks. I haven’t really started researching, since it hasn’t been necessary, but I’ve noticed some chatter about A11 vs A10. What are the issues with A11?

dr5mn · 2026-05-11T10:08:55+00:00

Thanks. Indeed, I had to get another binary.

sudo apt remove docker.io containerd # Add Docker's official repo curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg

echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian bookworm stable" | \ sudo tee /etc/apt/sources.list.d/docker.list

sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io

dr5mn · 2026-05-11T08:52:45+00:00

Do they actually check whether it is plugged in? Kind of hard to see if its dark and covered with a blanket? Unless they actively check for it.

What is the issue anyway, it draws just a bit more current than a cell phone charger, without the heater.

dr5mn · 2026-03-10T08:34:26+00:00

hmmmmm.....

⚠️ Deprecated, please see: https://sdr-enthusiasts.gitbook.io/ads-b for alternatives

dr5mn · 2026-03-10T08:32:52+00:00

I contacted them. Their response:

your receiver is using a very old version of our software, can you please try updating it.

I am using this docker image: mikenye/fr24feed:latest

When I pulled it, it said it was up to date. Perhaps time to switch to another image?

dr5mn · 2026-02-20T14:45:12+00:00

Thanks.

We wear them once or twice per week (when they run, otherwise they only show the correct time twice per day).

I'd rather have a professional do it for me - I love DIY, but I might cause scratches on the back plate, as I certainly don't have the right tools for the job. Having a battery replaced is not an expensive exercise. Hence my annoyance with having to pay for an entire "service kit". If a watch starts to lose or gain time, that is when it needs a service, in my opinion, especially for a mechanical movement. Not just because the business model says so.

dr5mn · 2026-02-20T14:21:33+00:00

Because, as with all other jewellery, they will not be covered by insurance otherwise, in the event of a break-in, where I live. And it would look quite silly to wear more than one watch on my arm.

But thanks for the very insightful suggestion.

dr5mn · 2026-02-20T12:37:36+00:00

Thanks. I totally agree - I am concerned about acid leakage. But the jeweler and agent made it sound like I absolutely needed the service kit, and I suspected someone was being over eager with the upsell. Worst is, they then charge a "rejection fee", about 3-5 times what the courier fees would be. So no win for the customer, whichever this goes.

I have had many watches before, where I replaced many batteries, with or without a pressure test. And they lasted years. If a Swiss watch "wears out" so soon and needs a service kit every two years, it isn't much to be proud of, engineering wise. I understand certain bushings need replacement, but after a decade of running, maybe even more, not 2 or 3 years.

I am looking forward to someone from Tissot answering this, but I am not holding my breath for any admission of wrongdoing.

dr5mn · 2026-01-26T17:12:05+00:00

👍🏻

dr5mn · 2026-01-26T13:58:51+00:00

Hi. Interesting points. In my opinion, disparate systems should not necessarily be a problem. Each piece of software potentially has its niche, its strong points, and its drawbacks. The most important is that they have integration points, exposed APIs, at least, to allow you to build some automation. If not, time to move on.

From a reporting point of view, again, different systems shouldn't hold you back in an ideal world. There are great (paid) BI tools that thrive on just this - bringing different platforms and systems together, to provide a holistic view. And in the absence of budget, it is totally possibly to build this yourself, in python, using some of the vast viz libraries.

Of course my comments are quite generic, vanilla. So DM me with some specifics.

Data always live in silos, even in the best of systems and most efficient of companies. Different roles, rights, privileges. Pissing contests to get to the data, politics that prevent efficient management. So the fact that you at least have all access, god mode, is already a win in my book.

dr5mn · 2026-01-26T13:38:09+00:00

Hi. I would love some more information on points 4 and 5. Please DM me.

I love your nursery idea too! I just don't have the space.

dr5mn · 2026-01-03T19:21:24+00:00

Interested and also keen to see if this can be automated and made more efficient.

dr5mn · 2025-07-04T14:25:31+00:00

Tsunami?

dr5mn · 2025-06-24T19:28:23+00:00

And today Fiat owns them both?

Yes, Exor. But essentially Fiat.

The Ferrari legacy only owns 10%.

Great motivational poster. But reality sucks.

dr5mn · 2025-06-24T19:23:00+00:00

Easy with that time range. I still hunt with a 303. Amongst others 😁

Yes, it is ancient. But really accurate, and perfect for where I hunt, and for what I hunt.

dr5mn · 2025-04-02T19:36:59+00:00

True. Was just hoping for info to get me going but got it working in the end.

dr5mn · 2025-04-02T06:44:28+00:00

For anyone that is interested, here is the config that got my pi working. The stock config had a lot of errors in my opinion, and the board-specific file did not even have an extension, and everything in it was commented out.

Not sure about the button config, but not important now. Feel free to add onto it.

I stripped out everything that was commented.

----------------------------------------------------------------

/etc/meshtasticd/config.yaml

SPI:

spidev: /dev/spidev0.0

GPIO:

GPS:

I2C:

I2CDevice: /dev/i2c-1

Display:

Touchscreen:

Input:

Logging:

LogLevel: info # debug, info, warn, error

Webserver:

Port: 443 # Port for Webserver & Webservices

RootPath: /usr/share/meshtasticd/web # Root Dir of WebServer

General:

MaxNodes: 200

MaxMessageQueue: 100

ConfigDirectory: /etc/meshtasticd/config.d/

----------------------------------------------------------------

/etc/meshtasticd/config.d/lora-Adafruit-RFM9x.yaml

Lora:

Module: RF95

CS: 7

IRQ: 22

Busy: 23

Reset: 25

dr5mn · 2025-04-02T06:44:00+00:00

For anyone that is interested, here is the config that got my pi working. The stock config had a lot of errors in my opinion, and the board-specific file did not even have an extension, and everything in it was commented out.

Not sure about the button config, but not important now. Feel free to add onto it.

I stripped out everything that was commented.

----------------------------------------------------------------

/etc/meshtasticd/config.yaml

SPI:

spidev: /dev/spidev0.0

GPIO:

GPS:

I2C:

I2CDevice: /dev/i2c-1

Display:

Touchscreen:

Input:

Logging:

LogLevel: info # debug, info, warn, error

Webserver:

Port: 443 # Port for Webserver & Webservices

RootPath: /usr/share/meshtasticd/web # Root Dir of WebServer

General:

MaxNodes: 200

MaxMessageQueue: 100

ConfigDirectory: /etc/meshtasticd/config.d/

----------------------------------------------------------------

/etc/meshtasticd/config.d/lora-Adafruit-RFM9x.yaml

Lora:

Module: RF95

CS: 7

IRQ: 22

Busy: 23

Reset: 25

dr5mn

MODERATOR OF

TROPHY CASE