umail and RMT interrupts

[smhodge42]

Hardware: ESP32-S3 DevKitC-1-N32R16V, firmware 3.4.0, Micropython v1.25.0.

I am able to send an email using the MicroPython <umail.py> package, using a gmail server and all the standard settings in the example code (port 465, ssl=True). However, I also use the NeoPixel on the DevKit with the <neopixel.py> MicroPython package, for various things, and after successfully sending an email the code crashes with a "E (116281) intr_alloc: No free interrupt inputs for RMT interrupt (flags 0xE)" error when it subsequently attempts to use the NeoPixel.

A little web research indicates that might indeed happen, and, in fact, if I comment out the NeoPixel action all continues to run smoothly after sending multiple emails but, of course, without the NeoPixel action.

Is there a work around for this issue? I tried deleting the NeoPixel object before creating the SMTP object and then re-creating the NeoPixel object after the email was successfully sent, but that did not fix it.

[davefes]

I have using uMail for years. Just a suggestion do you disconnect the WiFi after sending the email?

[davefes]

I dropped this into Google is there a wifi deinit in micropython? I don't use it and also recall comments that maybe it was not necessary, but maybe ...

[smhodge42]

I still need WiFi when not sending email, for ESP-NOW. The issue is connected with the NeoPixel driver (which I also need when not sending email), because when I comment out the NeoPixel use it works just fine, From: Dave Festing ***@***.***> Sent: Saturday, December 13, 2025 3:54 PM To: micropython/micropython ***@***.***> Cc: smhodge42 ***@***.***>; Author ***@***.***> Subject: Re: [micropython/micropython] umail and RMT interrupts (Discussion #18568) I dropped this into Google is there a wifi deinit in micropython? I don't use it and also recall comments that maybe it was not necessary, but maybe ... - Reply to this email directly, view it on GitHub<#18568 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2XPQKVSJEHF57VPGAI2Y5D4BSRKXAVCNFSM6AAAAACO6RCZS6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRUHA4TMOI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>