@gruia-nichita You don’t need the deep sleep shield on the Pysense/Pytrack, that functionality is built in.

Hi @seb Thanks that clears things up a lot! I didn't know I could list the methods in each module either, useful to know... That would be fantastic if you could add this sort of extra detail in the documentation, I'm sure that will save me a lot of time! Thanks again.

@alidaf Alternatively you can use ampy from Adafruit or rshell fro Dave Hylands (look of it on Guthub) to transfer files using USB.

@jmarcelino Thank you for noting the issue and acting on it.

Hi @livius, yes mailbox! here is the text in the documentation of the CCS811 chip: Programming Model: For flexibility and software driver maintenance simplification the CCS811 does not support direct addressing of registers over the I2C bus. Instead it supports single byte mailboxes identifiers that behave as proxies for registers with specific functionality and data sizes. To access a register an I2C transaction must be issued with the target address on the CCS811 being equal to the intended mailbox, this by way of proxy opens access to the register's functionality. In this manner the programming model is rigidy fixed while allowing the underlying firmware to be inherently flexible, extensible and configurable. That's chinese for me! Jiemde

@Xykon Working now :D Thanks for the support!!

I do not know but it may depend on fw version. Also no idea whether stored data survives fw update or not. I'm missing methods get number of total/used indexes get list of keys Also there are some smaller issues with retrieving data with non existing keys, etc.

Aha, LoPy 1.7.8-b1 micropython 1.8.6-724 loran 1.0.0 Alright I'm going to update the lot. Maybe some hints in the doc like micropython does with the different versions....

This is the server I am using. You can get a trial account. I am trying to either use the MQTT Websockets or MQTT TCP/IP with mosquito as the broker.

@jmarcelino you could have pushed the sigfox binaries to a separate branch (without history) and then made that branch the default branch. that way you wouldn't have broken anyone's git remote or pull requests while still hiding the history :)

I personally hate it when people cancel last minute for an event, been in that position as organizer more than once, but I simply have to make some calendar choices for this Saturday. It is one of those “busy parents with busy children and full schedules” kind of things. So I won't be seeing all of you in Eindhoven. Sorry guys :(

@PiAir Thanks for the link, I will check it out.

Just to bring it back on the workbench ;-) What are the plans to implement this feature? Cheers, Thomas

@YazIdo I think this may be an error associated with an accumulating number of open sockets. I got the same OSerror: 23 after running the MQTT example for the 8th time and beyond. A soft reset does not clear this, but powering on/off does clear it - and it works again, at least for the first 7 times. I fixed this problem by adding one line at the very end of the MQTT example. client.disconnect()

@bucknall I am able to corrupt the file system pretty easily. Running 1.7.6FW ATM. It seems to be when the program has a file open and an error occurs. What is the file system running on these boards? It doesn't appear to be a journaling file system. It is way too easy to corrupt the file system and have it erase the whole flash. I am developing a BT application that can update any file on the device and really need protection against this type of failure. I'm already doing a double buffer approach with the file writes so I have a good copy of the target file before deleting the original and renaming the file. The issue is resetting the board in the middle of a file write causes any manor of flash corruption. Before someone says "don't do that", I try very hard to design my system to recover from any type of errors. The cardinal rule is that there should be no way to brick a unit doing an update. To that end, I test every kind of failure during updates to make sure the device remains in a operating state.