Your email isn't shown to other users other than forum administrators

@bucknall I do not create another topic... really little bug - "Forum Guidelines & Rules" are wrongly linked to docs.

I think there is only little freedom. Floating point operations always allocate memory. Integer operations do not allocate memory as long as the result fits into 30 bit. Then memory must be allocated to store the result. Example on a LoPy: >>> f2 = 2 >>> for _ in range(32): ... f1 *= f2 ... print(_+1, end = " ") ... gc.mem_free() ... 1 37408 2 37408 3 37408 4 37408 5 37408 6 37408 7 37408 8 37408 9 37408 10 37408 11 37408 12 37408 13 37408 14 37408 15 37408 16 37408 17 37408 18 37408 19 37408 20 37408 21 37408 22 37408 23 37408 24 37408 25 37408 26 37408 27 37408 28 37408 29 37408 30 37344 31 37312 32 37280

Hi I'm having the same issue with DHT11 I ordered dht22 I'll check if it is related to the why DHT11 is being read Since normal the function stop all concurrence and threads this might be related to this

@robmarkcole Ok brilliant! So you'll be interested in send HTTP requests to the IFTTT Channel and you'll probably want a simple HTTP library so what I would suggest is urequest (https://github.com/micropython/micropython-lib/blob/master/urequests/urequests.py). You can use this to send HTTP request to IFTTT's server to trigger the 'Maker' channel :) I'll put together an example for you but it might be next week before I get a chance to!

@dchappel bit left shift << same for bit right shift >>

@jmarcelino Certification is an interesting point. First of all it is available only for 868MHz end devices, but nor for gateways, network servers, etc. Also even if you have a certified product you can reconfigure without hacking to be out of compliance. In the Microchip stack you can do nearly the same config changes as in RN2483 but you can not fully blow it up.

indeed :) probably in the future we'll do a plugin for the NodeBB forum

@Erica-Galindo Hi there, I can confirm we are fixing many of the issues and have been working with the web design company to make this a priority. We should have many fixes this week. Best wishes Fred

@Mike-K Did you select the correct country in the firmware flasher when flashing your lopy? This will determine if you get the 868 or 915 firmware version and thus which frequencies you can use. From the docs: "frequency accepts values between 863000000 and 870000000 in the 868 band, or between 902000000 and 928000000 in the 915 band."

Can you post your main.py for us please @iotmaker? Might help to work out what's happening! Thanks, Alex

@zmrzli Make sure you are sending the correct length and AD types according to the ADVERTISING AND SCAN RESPONSE DATA FORMAT (page 2081 on the Bluetooth 4.2 Core Spec - you can access the specification here https://www.bluetooth.com/specifications/adopted-specifications ). If you're looking to use BLE advertising packets to send your data you probably want to use AD type 0xFF (Manufacturer Specific Data) followed by the 2 company identifier octets. So your format should be 1 byte length + 0xFF + <2 bytes company identifier> + your data then filled with 00 until the 31 byte limit. You can't read improperly formatted advertising data.

For C embed there are a couple of libraries could be interesting. So being able to call them make sense.

@daniel Thank you. :o)

@crankshaft Thanks. We are looking at adding some blurb around that under each product as suggested. We have also now heard back from Espressif that the main missing features in the IDF such as ULP and Deep sleep modes will be made available to us next week. We are therefore working towards getting you all the new features by early march after which we mature the code all throughout March.

Thanks looks like it is doing good now

@Ricardo-M I boot my sipy in safe mode and i connect pc and sipy by telnet (using Putty) and i carry out a factory reset to the filesystem (reset flash filesystem) and now my sipy is like new