Mike Wadsten

I would suggest that you reach out to 1NCE for support on this, since as you mention, the request works fine when using LTE-M, but fails with NB-IoT. My guess...

The MicroPython garbage collector is very conservative, so a small "memory leak" while in an execution loop isn't really concerning, as long as the GC is able to collect that...

As of a few months ago, Heroku switched the default Python runtime for newly created apps from Python 2.7 (which is what this application is compatible with) to Python 3.6....

> Because of Python 3.6 in Heroku I have removed wsgiref==0.1.2 I would recommend you change the `requirements.txt` file back to the master branch version, and simply try adding the...

Something seems to have gone wrong with the application deployment. You should get a webpage that looks like https://xbeewifi.herokuapp.com Run the following commands, then see if the app is working...

Can you run the following command and tell me the output? ``` git remote -a ``` The intent of that `git checkout` command is to revert the state of those...

> out put of git remote -a Thanks. Can you run the last set of commands I added to my previous command (`git remote add` and `git fetch`), then try...

> git remote add " what I have to give here " Run these commands: ``` $ git remote add origin https://github.com/digidotcom/xbeewificloudkit $ git fetch origin ``` then you should...

It seems like you may need to purge the build cache (see https://help.heroku.com/18PI5RSY/how-do-i-clear-the-build-cache)... so run the following commands, then attach the deploy_log.txt file to a reply here: ``` $ heroku...

Based on that log file, it does appear that the static asset build (done by JavaScript during the deploy) is succeeding. However, there is this message: ``` remote: -----> Python...