@robert-hh Works like a charm, thank you so much!

@robert-hh thanks. ill try and sort out some VM's and give that ago.

Following-up … if I add an exception handler and keep trying to connect, I get a bunch of different error numbers: Uncaught exception: -17168 Uncaught exception: -10368 Uncaught exception: -10368 Uncaught exception: -10368 Uncaught exception: -1 Uncaught exception: -32512 Uncaught exception: -29312 Uncaught exception: -16 Uncaught exception: -10368 Uncaught exception: -4480 Uncaught exception: -19840 Uncaught exception: -4480 Uncaught exception: -16912 Any advice on how / where to look those up? Cheers, Tim

@brewnut The RTS pin is not used by the firmware, but driven by the UAB/UART bridge. But you can also use another pin, like P6.

Stupid mistake, I thought I had checked the pinout... thanks! Set it to None and now it works.

Any news?

@robert-hh Es läuft jetzt. Ds Update ging nicht weil ich das Board für den Fipy überbrückt habe das es im batterie Modus läuft. nach entfernen des kabels ging auch das Update. Jetzt kann es weiter gehen. Danke für deine Mithilfe.

@zahary-momchilov Yes. You can use WiFi. However it is advisable to have a generic USB/UART adapter with 3.3v output as second option. Any adapter with 3.3V output level will do. The latter sorts out most Arduinos.

And one more: File "urequests.py", line 54, in request OSError: [Errno 9] EBADF which might be #define EBADF 9 /* Bad file number */ I have a gc.collect() after the upload, but no .close on the connection. Adding this now to see how things go. -- Martin

@robert-hh I just connected power drectly. That works, now I have to do some soldering in order to check if it works together with the level-shifter. Thx so far!

In case someone else comes along looking for a solution to this problem. Simply add this callback before the while loop: def char_notify_callback(char): char_value = (char.value()) print("Got new char: {} value: {}".format(char.uuid(), char_value)) And update the char condition: if ((char.properties()) & (Bluetooth.PROP_NOTIFY)): characteristic.callback(trigger=Bluetooth.CHAR_NOTIFY_EVENT, handler=char_notify_callback, arg=None)

@sealyons I made a test with the calibrated temperature mesurement device: Calibrated device: 21.7 21.8 DS18B20: 21.9 21.9 DHT22: 21.8 21.9 SI7021: 21.7 21.8 BMP085: 22.4 22.5 BME280: 21.8 21.9 Besides the BMP085, all devices were on the spot = within 1 digit variance. That status was stable for 5 hours testing. Only the BMP085 was always ~0.6 °C above, but still that at the limits of it's spec.

@robert-hh Hi, sorry for my insistence on this topic. I 'm not able to use thread but I read about it and I think that it's better for my code if I use them . So do you know if is it possibile to use thread to read from two I2C through the code that I posted before? thank you.

@modellhaus I suggest you two things for help, the first is to modify your post and please enclose your code in correct code balise ( </> tool in line above )to help reading . The second thing is to post the error message and line number where it happen to help analysis.

@robert-hh Thank you @robert-hh. Your help is making a steep learning curve a lot easier.

@robert-hh Thank you, much appreciated.

@svonbentzel Thank you very much. I appreciate it.

@jimmie glad that copy and paste is your biggest problem :)