New firmware release 1.6.7.b1 (LoRaWAN Nano Gateway with TTN example!!)

[robert-hh]

Hello @zmrzli,
no idea what you did, but this sequence works for me:
from network import WLAN

wl = WLAN(AP)
wl.init(mode=wl.AP, ssid="My_lopy", auth=(wl.WPA2, "This is a Test"))

It takes a while before the change gets visible on the other devices, if these do not scan the networks frequently. Sometimes on cycling Wifi Off/On helps.

[daniel]

@zmrzli the answer from @robert-hh is correct, it just works like that, but some devices take a while to scan for networks again or to update the ssid if the MAC address is the same. Try switching the WiFi of your iPhone on and off as suggested.

Cheers,
Daniel

[daniel]

@jmarcelino thanks for the suggestion! I'll include that on the next nano-gateway release along with the other planned improvements :-)

[JF002]

@daniel Congratulations for you and the whole team! I've just upgraded to 1.6.7.b1, and tried the examples (NanoGateway and OTAA node) and... it works like a charm! I'm currently sending my room temperature (from a DS18B20 sensor) on TTN using these examples!

For now, there is no TTN gateway at range at home, I have to move away from my home to find some signal. The possibility to create a "dev" nano-gateway that connects to TTN allows me to work on my projects from home, this is wonderful!

[johncaipa]

Very good news, we were expecting this !. Congratulations to the entire Pycom team.

[gertjanvanhethof]

This is really fantastic news. I immediately uploaded the code to by LoPy.
TTN Dashboards shows gateway is connected!
Now I have to test to send messages to it with my other LoPy.

[constantinos]

Daniel,

I lost the functionality of receiving messages from RFM95. It was working with firmware version 1.2.2 and now is lost.

I just receive nothing at all now.

[daniel]

@constantinos please try playing with the public argument in the constructor:

https://docs.pycom.io/pycom_esp32/library/network.LoRa.html#network.lora.init

Before the last 2 releases the default of True for the public sync word was not being honoured, and now it is. Set this value to False and that will most likely make the LoPy work with the RFM95 again.

[constantinos]

@daniel Thanks! It works!

[rskoniec]

@daniel Really nice update! NanoGateway and OTAA node works like a charm! Thank you Pycom Dev Team! :)

[daniel]

Thanks for the thumbs up!! :-)

[johncaipa]

Someone can help me with an example of how to use it on US or AU frequencies, I still can not do it on my own. Thanks

[robert-hh]

@daniel Hello Daniel, I do not want to impose any kind of pressure on you, since you are doing a great work in imroving the device, but at what time do you plan the next update of the github repository with the micropython files?

[daniel]

@robert-hh, no worries, our only focus from today onwards is code maturing and doing the migration to the MicroPython migration. We'll also update our own repo as we were sorting out the way to publish Sigfox libraries.

[daniel]

@johncaipa, for sure, I'll work on an example for US frequencies and will add to the same repo where the other are. We'll do our best to get it done today or tomorrow.

Cheers,
Daniel

[Colateral]

If Wipy WLAN is configured simply as STA-AP ... the ftp is not working.

from network import WLAN
wlan = WLAN(mode=WLAN.STA_AP, ssid='Cola', auth=(WLAN.WPA2, 'abc12345678'))
wlan.ifconfig(id=1, config=('192.168.10.1, '255.255.255.0', '192.168.10.1', '192.168.10.1'))

connect to 'Cola'
and ftp(with micro/python) is connecting on 192.168.10.1 but fails on root dir (/flash)

[livius]

@Colateral
I also wait for this but still do not know how to work with it
STA work but AP not able to connect
https://forum.pycom.io/post/4202

[robert-hh]

@Colateral: I tried your setting and it worked fine for both addresses (STA and AP), using command line ftp on Linux. Did you use passive mode? Active mode is not supported.

[Colateral]

@robert-hh Yes. It is passive mode. My environment is on Windows10. I tried with WinScp, TotalCommander and Windows10 ftp in passive mode. I saw that is working if I use the default 192.168.4.1 IP instead of the custom IP 192.168.10.1 .

[robert-hh]

@Colateral That sounds strange that 192.168.4.1 works, but not 192.168.10.1. The other thing that suprises me is, that you used command line ftp on WIndows 10 in passive mode. The one I have here does not support it. Do you have a special version?