Geschrieben February 6, 2026 at 04:586. Feb 2026 Mir ist die Meldung unten im Brickv auf dem macMini aufgefallen. Weiß nicht, seit wann das da steht. Beim MacBook taucht sie nicht aus. Ich bin mir nicht bewusst dass ich etwas umkonfiguriert habe. Eine Idee? Ich finde nichts an Berechtigungen für Brickv ... Werde mal neu installierenmacMini M1, macOS 26.2, neuester Brickv 2.4.26, gerade noch mal installiert.Cheers, Uwe
Geschrieben February 6, 2026 at 08:276. Feb 2026 Same here with Brickv 2.4.24. Weird, because version files seem to be fine here and here. Maybe a code signing thing with Apple?Update: it seems the developer certificate expired.
Geschrieben February 6, 2026 at 09:556. Feb 2026 Completely removed Brickv 2.4.24 using Tinkertool → Rebooted → Installed Brickv 2.4.26 → Still the same problem. bearbeitet February 6, 2026 at 09:576. Feb 2026 von Superp Resized images
Geschrieben February 6, 2026 at 10:236. Feb 2026 There are two different issues. We moved our servers to a new infrastructure and by doing that changed the root ca. Because of that brickv doesn't like to download from tinkerforge.com anymore. Additionally we need to renew the developer cert for the next brickv release, but that is a different issue.
Geschrieben February 8, 2026 at 07:218. Feb 2026 Autor Hmm, I'm pretty sure I run the same version of Brickv on the same version of macOS in my office. There everything runs as expected.
Geschrieben February 13, 2026 at 12:3513. Feb 2026 This morning I pushed an update that enables the Tinkerforge Ruby bindings to check firmware versions. To my surprise it immediately found a Bricklet with outdated firmware.For now it expects you to download latest_versions.txt yourself and put it in either ~/.config/tinkerforge/downloads or /etc/tinkerforge/downloadsThis is still somewhat experimental, your kilometrage may vary, etc. Feel free to port this code to your favourite programming language. bearbeitet February 13, 2026 at 20:0813. Feb 2026 von Superp Restored disappearing screenshot
Geschrieben February 13, 2026 at 14:4113. Feb 2026 Autor Am 6.2.2026 um 11:23 schrieb borg: Because of that brickv doesn't like to download from tinkerforge.com anymore. Please forgive my ignorance. Wouldn't that affect every running brickv running in the world out there? But on my Laptop I do not see this message. Am 6.2.2026 um 11:23 schrieb borg: Additionally we need to renew the developer cert for the next brickv release, but that is a different issue.I hate this traffic sign. Any idea when that release will come?
Geschrieben February 16, 2026 at 14:4316. Feb 2026 I cannot reproduce the download issue here, with two different MacBooks with macOS 15.5 and 26.1.It's not a general issue with our server, but with Python not being able to verify the HTTPS certifcate of our server. We are using Let's Encrypt now. I'm a little puzzled why it should not work. I suspect a problem local to the affected computer.Could you try running this terminal command on the affected computer and post it's output here:curl -v https://download.tinkerforge.comSame with Python please:python3 -c "from urllib.request import urlopen; print(urlopen('https://download.tinkerforge.com').read()[:100])"Yes, the code signing certificate used to sign that version of brickv is expired by now. But that's not a real issue, because the signature is timestamped and at the time brickv was signed the certificate was valid. This version of brickv is still properly signed. There is no issue to be fixed. There will not be a new brickv release just because of that. Apple decided to show this in a too dramatic way, making it look like an issue. This also has nothing to do with the download issue.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.