Superp

Maybe AYCT–303, or Trust AYCT–102 ? Also see this list of devices that work but are not documented by Tinkerforge.

For those using Tinkerforge with Ruby and Tinderfridge: the Tinderfridge repository has moved from Github to Codeberg.

That looks very promising, thanks for bringing this to our attention again. I don't suppose it is possible to tempt you to create a binary for Raspberry or Mac OS ?

See also: LED Strip Bricklet 2.0 max voltage

See the thread Brick Daemon 2.4.6 not working for a discussion of the problem instructions for downgrading to brickd 2.4.5 (fix) a preview of brickd 2.4.7 (alternate fix)

It works here.

@zbindenp That is exactly what I did. Thanks for sharing the write up. This would be an excellent opportunity for reviving the near-dead blog. Write two lines informing us about the (avoidable) problem and the fix. RSS is our friend.

Hello, I have upgraded four of our systems from brickd 2.4.5 -> 2.4.6, and brickd stopped responding on all of them: <I> <main_linux.c:385> Brick Daemon 2.4.6 started (architecture: arm, pid: 25228, daemonized: 1) <I> <main_linux.c:391> Running on Linux system (sysname: Linux, release: 6.1.21-v7+, version: #1642 SMP Mon Apr 3 17:20:52 BST 2023, machine: armv7l) <I> <bricklet.c:274> Found supported HAT product_id 0x084e in device tree, using default HAT Brick config <I> <bricklet.c:315> Found Bricklet port A (spidev: /dev/spidev0.0, driver: gpio, name: GPIO23, num: 23) <I> <bricklet_stack_linux.c:87> Using spidev backend for Bricklets, because Raspberry Pi without BCM2835 detected <I> <bricklet.c:315> Found Bricklet port B (spidev: /dev/spidev0.0, driver: gpio, name: GPIO22, num: 22) <I> <bricklet.c:315> Found Bricklet port C (spidev: /dev/spidev0.0, driver: gpio, name: GPIO25, num: 25) <I> <bricklet.c:315> Found Bricklet port D (spidev: /dev/spidev0.0, driver: gpio, name: GPIO26, num: 26) <I> <bricklet.c:315> Found Bricklet port E (spidev: /dev/spidev0.0, driver: gpio, name: GPIO27, num: 27) <I> <bricklet.c:315> Found Bricklet port F (spidev: /dev/spidev0.0, driver: gpio, name: GPIO24, num: 24) <I> <bricklet.c:315> Found Bricklet port G (spidev: /dev/spidev0.0, driver: gpio, name: GPIO7, num: 7) <E> <bricklet_stack_linux_spidev.c:263> Could not find line GPIO7 <I> <main_linux.c:579> Brick Daemon 2.4.6 stopped These systems are all Raspberry Pi 3 Model A Plus Rev 1.0 with a HAT Brick. Downgrading to brickd 2.4.5 fixed the problem on all four systems, for now. Is this a known issue?

Your photo does not show the motor type, but it shows "moons". Go to the moons website, look up the motor, click "recommended options" for cables etc. example

Moritz, In my experience, the Outdoor Weather Bricklet + TH-6148 is the best choice when you want reliable reading of ambient temperature and humidity. I have 4 of these sensors running, indoors and outdoors, all communicating wirelessly with the same Outdoor Weather Bricklet and can recommend it without reservations. Any T/H sensor inside a computer case will always give a reading that is off, because the temperature inside the box will be higher than the ambient temperature. The difference (inside box vs ambient) will change depending on conditions such as ventilation, room temperature, load of your CPU, etc. so is difficult to compensate for. The TH-6148 is electrically isolated from your system, and you can more easily experiment with its location. Location matters a lot for T/H sensors. The TH-6148 can also be read by anybody, directly, because it has its own display, which always works, no software needed. Many people appreciate this. Good luck!

Unfortunately, AFAIK, the individual values can not be accessed in any way; the calculation of the IAQ is a black box: I can recommend the CO2 Bricklet (unfortunately, this has become quite expensive) and the Particulate Matter Bricklet.

Hi, The context (hardware, software, ...) of your question is not clear to me. Maybe you are using a Warp charger? There isa separate forum for that.

Fixed. Multiple resets and reboots did not fix this; unplugging the system from power fixed it. Interesting. Solved!

Hello, I am having a small problem with the GPS Bricklet 2.0 (FW 2.0.7). When I set the fix LED configuration to 4 (PPS) this effectively switches the LED off. With a GPS Bricklet 3.0 this works as expected: the LED blinks once per second. Both Bricklets have a fix. What am I doing wrong?

Thanks.

Hello, The LED Strip Bricklet 2.0 can be connected to the DC power supply line for the LEDs it controls. What is the maximum DC voltage the Bricklet can safely handle? I can't find this in the docs.

Or use a short ribbon cable to put the Pi and the HAT next to each other, instead of on top of each other.

Sigvald, Could it be that your hardware does not supply enough power? If that happens, the GPS Bricklet can seem to work normally, but it never finds satellites.

Can you be any more specific? Will this be days, or weeks?

Hello, This morning I wanted to order some parts including the HAT Brick, but the HAT Brick is listed as "out of stock". Will it be available again, or will it be replaced with something else? And is there a timeline for this? Any info would be welcome.

That was my point @borg, kind of, but I obviously did not make myself very clear. Thanks for responding and Happy tinkering!

Thanks, I know, I use both.

FWIW, the shop page and the documentation for the GPS Bricklet 2.0 both still say: "Supports GPS and GLONASS simultaneously (later Galileo through software update)"

The shop lists the Ethernet Master Extension (with PoE) as "in stock". But further down the page: My emphasis. Can somebody clarify?

Good to see you're back. So...what can you tell us about the dome? What is it made of? How big is it? How is it sealed? How did you mount it?