DigiH

No worries, or you can also let me know your OTA set up, as I am always doing OTA updates as well though PlatformIO. Might be something obvious. Either way,...

Thanks for the further tests. I have uploaded some changes with the unit bit set to what i think it might be, but for a final decoder it would really...

@jpmorrison > LaCrosse-TX141THBv2 and TFA-303221 are also gone Did you also try the development version? I'm getting the LaCrosse-TX141THBv2 fine with it, with it occasionally being mis-recognised as TFA-303221. Which...

> It's a CC1101. Also with a CC1101 here, and using the development branch from about two weeks ago. As I do not recall any issues with the 1.7 release...

> Same at my side, with Beta it seems to work . I am using esp32dev-rtl_433. > Too early for celebrating, it stopped working after some time Which frequency have...

> My frequency is 433.92 MHz. Any improvement with the Lacrosse-TX141W reception with 1.7.0 when tweaking the frequency a bit in either direction? Any possible mis-recognitions of the Lacrosse-TX141W as...

My above suggested Nearby Info Continuity BLE advertising data, looking at the data length and the relevant octet being "98" or "18" clearly identifies it is an Apple Watch AFAIK,...

Hi @stefanPilz, From what I have found out about this device so far, is that it doesn't change its freely broadcast advertisement data at all, so very likely not containing...

Hi @BertrumUK, Just FYI, you do not necessarily need a separate ESP32 to use the Theengs Decoder decoding of your Amazfit T-Rex Pro, you can also use the [Theengs Gateway...

Thanks for this, I didn't know it yet. Not having a Mopeka myself either, it's always relying on others with the devices to help with the decoders. Some user data...