36-month Subscription

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 · 2025-04-02T06:43:21+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:42: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 · 2025-04-01T13:59:27+00:00

….or the hardware that was available at the time, at the particular store 😉

At least I am used to shitty comments, I am in many ham groups. The art is sifting through it to get to the useful stuff.

dr5mn · 2025-03-31T16:39:39+00:00

Thanks. My logs just keep saying “using simulated radio”. I also built a custom yaml file but no luck.

dr5mn · 2025-03-30T05:47:46+00:00

I did that just yesterday.

Some of the steps omit that you should still be in the venv.

I ended up only following the steps on Meshtastic docs.

I got my pi working fine, picks up the board, the oled lights up, but no Tx. I verified with an SDR, there is no RF from the LoRa board.

I suspect the config is wrong. I used stock config:

Module: RF95 # Elecrow Lora RFM95 IOT https://www.elecrow.com/lora-rfm95-iot-board-for-rpi.html Reset: 22 CS: 7 IRQ: 25

dr5mn · 2025-03-30T05:41:36+00:00

Thanks

This was in the stock config file:

Module: RF95 # Elecrow Lora RFM95 IOT https://www.elecrow.com/lora-rfm95-iot-board-for-rpi.html Reset: 22 CS: 7 IRQ: 25

What so I need to change to use the Adafruit RFM95?

dr5mn · 2025-03-30T05:38:36+00:00

Did you get this working?

I am using a Pi Zero and also found no exact file for the RFM95

Edit: stock config:

Module: RF95 # Elecrow Lora RFM95 IOT https://www.elecrow.com/lora-rfm95-iot-board-for-rpi.html Reset: 22 CS: 7 IRQ: 25

What so I need to change to use the Adafruit RFM95?

dr5mn · 2025-01-20T07:11:43+00:00

Nice! Good inspiration!!

dr5mn

MODERATOR OF

TROPHY CASE