@moewex The 4095 is the highest value of the 12 bit ADC. So you could try to call apin.value() instead of just apin, which seems to return the voltage value, which has to be calibrated beforehand. The noise and fluctuation will always be large. So you have to add some kind of lowpass or averaging. For the moisture application with ist slow change, using a digital lowpass filter/averaging is surely appicable. And you do not have to care for absolute precision, just consistency.

... forgot duplicate CLIENT_ID in config.py... Problem solved!

@Tschili take a look at https://docs.pycom.io is full of examples. The bluetooth paring needs for you to create a server on Wipy, but usually you may want more than a simple paring. About the: Send data over the mobile phone to internet (webserver) I don't think that this forum is the adequate for mobile apps questions, but if you mean communicating to Wipy using wifi, for sure you will find and example on the documentation.

@tschili There's a similar issue being discussed here: https://forum.pycom.io/topic/3436/expansion-board-3-0-battery-power-not-enough-juice It seems it's related to the Expansion Board 3.0 rather than the WiPy in that case, not sure if it's the same problem you have.

I realize this post is super old, but I was also wondering the same thing. Did you find a way to make it work? I'm having trouble importing python's ecdsa module. It can't find the SigningKey module inside keys(dot)py for some reason. Though it's really slow, I'm aslo considering the following: https://github.com/jfindlay/pure_pynacl

@dan Yep I have never put anything in boot.py, have always had main.py run without intervention.

@jmpratt I cannot believe that you have the same code on both WiPy's. Please reload the code to both devices, reset them and try.

@ade-ro You can use WLAN.init() it accepts the password in the auth parameter.

@jmpratt I don't think so, because the pin is hardwired to the antenna switch internally. This has been a problem for us, too. I would advise against using P12 for anything anyway, because it also selects the boot mode. Therefore it will force the device into safe boot if P12 is for some reason high while it is booting.

I know this is an old topic I started but it seems like there is even less documentation now on this topic of using the BLE device as a peripheral. It would be nice if the documentation better represented common functionality and how the functionality is intended to be used with this device. I tried to use those links that had reference to using the BLE device as a peripheral but the link was broken.

@zaphodbb I think the issue is that the code uses a long (128 bit) UUID instead of the short 16-bit UUID, so there's a very short limitation on the max URL size. Try replacing the value of uuid with [0xaa, 0xfe] or 0xfeaa, it should give you 14 more bytes for your URL (haven't tried it).

@jmpratt Since there is no configuration data on a WiPy that could get lost, you could try to make a complete erase using esptool.py and then reload the firmware.

@charly86 and while there at it they can also mention that p8 must not be pulled up when you want to flash the firmware. because if you don't it wont get into download_boot mode but instead into HSPI_FLASH_BOOT mode and will start a reset loop. we also had that problem.

@robert-hh The hearbeat LED flashes when the board and code are working properly. If I notice that the data is not updating, I'll go look at the board and the heartbeat LED won't be flashing. I'll hit the reset button on the board and everything will work normally again. I think I'll setup an identical rig but power the USB power port from a variable DC supply. Then I can turn the voltage down and see what happens.

@xykon Thank you, it worked out.