Florian Echtler

I think the problem is that the nRF24L01+ can at most receive 32 bytes of a BTLE message, but most phones send noticeably longer messages (~48 bytes or so). It...

I would suggest you start with the temperature example (https://github.com/floe/BTLE/blob/master/examples/temperature/temperature.ino) and change the UUID to the one for humidity (should be in the BTLE specification UUID list).

INFORMATION_SERVICE won't work for humidity, that's something entirely different. 0x2A6F seems to be correct, see also here: https://github.com/NordicSemiconductor/Android-nRF-Connect/issues/52

I think the code you posted actually looks pretty correct (apart from the humidity UUID). What does e.g. the nRF Connect app show for your device when all 3 parameters...

OK, then you're running out of space in the advertisement, for the nRF24, you can only have at most 21 bytes of payload. Try setting the name to "" (empty...

Could you try a recent Android phone to see if it shows up there? You could also try a second Arduino with the receive example in parallel.

Keep in mind that this is abusing the Bluetooth spec pretty hard, I've seen a lot of issues where some specific combination of Arduino model and phone model works, and...

Just for the record, the guy from #16 used an Arduino Uno, and it worked in both directions there (using a Galaxy Note 5).

@ardyesp very interesting, thanks for sharing. That would explain why this behaviour seems so entirely random (and if certain channels work better than others on de-tuned modules, that would also...

Wow, weird. What Android device(s) did you test with?