in fact they were sort of doing that already, but not fully asleep, so the guy just gave up on the shoes so that the wardens could take the whole "bunch" without disturbing the bats too much. 🦇 To quote the classic, "it was the Batman".

www.ekologia.pl/wiadomosci/z...

I like this story a lot. Some dude in Warsaw called the "eco-patrol" about bats on his balcony, and the approx. 20 bats were literally filling the old sneakers he left on said balcony. They were taken to the city forest where they'll be able to peacefully hibernate

Drexciya Special w/ Unité Centrale Records (06.11.2025) 2 hours of Drexciyan music and everything around James Stinson (RIP) and Gerald Donald, straight from Unité Centrale's bins and cruising through the whole thing: Drexciya obviously and Clarence, Trans

soundcloud.com/lyl_radio/dr...

an absolute must for those who know #drexciya #dopplereffekt #japanesetelecom #arpanet #313ctr0

OK cool! 😊

so... how to get a wallpaper then? 🙃

yeah, that seems to be VPN. no problem at all on my regular machine.

I am using a VPN, I will try later from my own machine and let you know.

I honestly don't mind people doing whatever when they're already in that line. That's moving forward, one way or the other. What really grinds my gears, though, are damn zombies walking around as if it was some kind of interactive self-service commerce museum, wondering what all this stuff is 😵

creatinglightly.art/pages/gallery
creatinglightly.art/collections/...
creatinglightly.art/en-eur/pages...

all these are returning 403. I know that there are some Cloudflare outages today but this doesn't seem like it. It's like various redirections on the site return this.

Hmmm, I would love to have a wallpaper like this but how? So: I went you your website and signed up for the newsletter. But when I click on, say, Artwork or Store, I get the 403 error. What am I doing wrong? 🤔

On the plus side, I got some first code for RP2350 with Embassy. @raspberrypi.com Pico Debug Probe + @seeedstudio.com Xiao Expansion Board are a great combo for some #rustlang tinkering 🦀

wifi transmission works and what exactly is happening. Maybe one day, but for now the idea of sending data to REST API from my Rust-y ESP32 is still at a very early beta stage. It works, but then it stops and I have no clue, why. But maybe some sort of a watchdog is the solution?

Well, I really like my #rustlang contraption, sending SEN54 data to my small webapp, but I have no clue how to fix the issues it's having with random frequency. It's all about WiFi, at some point I get the RX_QUEUE_FULL warnings from the esp_hal crate, but I don't understand how this whole

Don't fake the funk or yer nose will grow, they say. but this guy, he ain't fakin' it! #jamiroquai The Heels of Steel 2025 tour, Milan. Super groovy!

right... 🥸 nah, I have two smaller ones, B/W and a smaller tri-color with red. just need to get to work on that.

IKEA hack part 🙃 One thing VINDSTYRKA has and my contraption doesn't is a display, but this is going to be the next step, some nice ePaper. Stay tuned.

It turns out that Sensirion SEN54 sensor is used in the IKEA's VINDSTYRKA air quality monitoring device. A common hack is to put an ESP32 inside, connecting the exposed I2C points to push the sensor data to some website etc. So without really trying I sort of replicated this device, skipping the

Lowering the frequency to 100 kHz did the trick. I also thought about doing something like this:

let sda = Output::new(peripherals.GPIO5, Level::High, OutputConfig::default().with_pull(esp_hal::gpio::Pull::Up));

but I can't pass this to .with_sda().

Thanks! I will see how it goes, but I can tell from my little REST API that it's been working fine with that "additional sensor hack". Definitely need to try combining lower bus speed with pullups turned on, etc.

Yeah, that's something I need to look into. Thanks, I did suspect it had something to do with the hardware side of things, but couldn't really figure out how 😀

github.com/esp-rs/esp-h...

I believe the answer is somewhere here, I leave the Config::default but of course there are settings for the pins, which I happily ignored, but in this particular case they might be needed 🙃

Seeed Xiao ESP32C3 and C6, and Adafruit QtPy ESP32C3. Usually I attach devices via Xiao expansion board or the Grove Shield, and those have additional 4.7K pull-ups for the I2C.

Well this does make sense. I usually attach I2C devices to these boards using some carrier board with connectors, and those have additional pull-ups. And I didn't do any particular setting for the I2C, leaving the defaults, so that could be insufficient 🤔

That's kind of what I was thinking. But in theory the "helper board" should provide that: learn.adafruit.com/adafruit-sen...

@adafruit.com have you ever encountered this issue/had any feedback regarding this?

What kind of sorcery is this? 🤔

for actually starting the fan and the laser of the SEN54, but no, it's not it. And it's not the I2C. And it's not the code, because it does work. Why does it work with this dummy sensor connected, but not without it? I don't even start the sensor, I just initialize the I2C interface of its driver.

This started every time without issues, so I tried adding the LPS22 to my WiFi code, and it works. But not just with the sensor connected to the helper board, but also initialized. This makes zero sense to me: I thought maybe it was something about power supply, like maybe there was not enough

I tried moving the whole sensor setup code at the very beginning to make sure it all starts before anything else, and nothing, 9/10 attempts it just wouldn't start. So I tried the code where I was just testing I2C without WiFi, and there I had another sensor connected to the helper board, an LPS22

Now here's the weird part:
The sensor is connected via this helper board: www.adafruit.com/product/5964... and then with a Qwiic cable to the ESP32. I tried different cables, I tried adding quite long wait times between various steps of the code (setting up the I2C, initializing the sensor etc.),

This is not a number sent by the driver (crates.io/crates/sen5x...) when it doesn't know what the sensor returned, no. This is a value sent by the sensor when it doesn't know what to say, so to speak. The sensor device itself works, it correctly initialized and returns the serial number, etc.