@robert-hh Thanks! :-)

@OSSART Il manque les captures d'écran... Si j'ai tout suivi, tu n'as qu'un seul LoPy4? Ça ne correspond pas au scénario décrit pour pouvoir observer du trafic: il faut un LoPy4 qui joue le rôle de passerelle (nanogateway), qui va recevoir des paquets et les transmettre à TTN via une connexion Wi-Fi/Internet, et un autre qui joue le rôle de terminal qui envoie les paquets. LoPy4 terminal <-- LoRaWAN --> LoPy4 gateway <-- WiFi/Internet --> TTN <-- Internet --> Serveur Avec un seul LoPy4, soit c'est une passerelle et il faut que quelqu'un d'autre passe par elle (mais comme c'est une "nano-gateway" qui n'écoute que sur une seule fréquence au lieu des 3 à 8 d'une vraie passerelle conforme, ça ne va vraiment fonctionner que pour des terminaux configurés de façon spécifique), soit c'est un terminal et il faut qu'il y ait une autre passerelle quelque part à portée.

@Livelock @robert-hh Update: In the mode EF98 I installed the CDC-Driver in zadig. Now device manager sees Expansion3 on COM5 This is also able to be chosen in the pycom upgrade tool. The error is gone and I was able to install it. I really hope they update their documentation. It is lacking. Thank you so much! Edit: For the second board, I only needed to reinstall it once. Now it sees the board.

@drgdhorler We added experimental support for this. Below is some example code to capture MAC addresses. from network import WLAN import ubinascii def pack_cb(pack): mac = bytearray(6) pk = wlan.wifi_packet() control = pk.data[0] subtype = (0xF0 & control) >> 4 type = 0x0C & control #print("Control:{}, subtype:{}, type:{}".format(control, subtype, type)) if subtype == 4: for i in range (0,6): mac[i] = pk.data[10 + i] print ("Wifi Node with MAC: {}".format(ubinascii.hexlify(mac))) wlan = WLAN(mode=WLAN.STA, antenna=WLAN.EXT_ANT) wlan.callback(trigger=WLAN.EVENT_PKT_MGMT, handler=pack_cb) wlan.promiscuous(True)

@catalin Was this fixed in newer versions of the PySense?

@dgerman It has been fixed

@Sudosu132 You will need the pull-up resistors. For testing with the provided 1m cable the soft-pullup's of the ESP32 may be sufficient. If there is a problem, you can lower the baud rate by increasing PULSE_SHORT and PULSE_LONG.

@robert-hh I just tried this, but it's still using the other frequencies. I have also tried powering it off fully, but again, no luck...

I would like to change my username, is that possible? Have not seen that option in edit / settings either.

@ferfersan6 Good intentions pave the way to hell and I had every intention to reply to this. I know this is WAY too late to reply this but may useful for any experiencing the same issues. If I remember correctly, I just held the pin high for as long as possible and went through the drudgery of reinstalling the proper firmware. Nothing sophisticated going on here! :)

@NickBoots boot.py and main.py share the same namespace. If you import pytrack in boot.py, you do not have to do that in main.py again. Actually that would be ignored. So either way is fine, but in your case does not matter much anyhow. boot.py and main.py are executed one after the other, with just a few ms time in between. So it is more a matter of software design than a difference in energy consumption.

@carver someone suggested screws here: https://forum.pycom.io/topic/4533/universal-ip67-case-feedback/3

@NickBoots Everything IoT would be too broad... But I agree, expertise from Pycom forum, various sub-reddits, micropython.org forum. Having a single place to go to would be nirvana. Maybe that's the next evolution of social networks?