Sorry about the delay. I was in a hurry here and didn´t have enough time to come back to this thread. AFAIK, there´s no way to connect via browser to this gateway AFTER it´s running. If you want to change some parameter, you have to reset it, connect to it via WiFi and go the configuration screen pointing your browser to 192.168.4.1. It would be nice if this feature was deployed by Heltec.
In the beginning, we were worried that DHCP would take up MCU resources and affect the message queue of LoRaWAN, which would increase the packet loss rate.
I’m trying to setup my new HT-M01S to connect to The Things Stack (TTS).
Tried following the instructions from Heltec on TTN but got stucked after getting the gateway connected to my wifi network. I’m able to get an IP address assigned to the gateway.
I proceeded to add this gateway from TTS console, but the status seems to be always disconnected.
Is there any good documentation that I can refer to?
Did you tell the gateway where TTN lives? As far as I know the Heltec images still point to V2 so for V3 you might need to manually configure the backend. (something like eu1.cloud.thethings.network, depending on where on the globe you are)
Unfortunately, V1.3 connected to V3 does not work with me:
Heltec HT-M01S firmware Rev V1.3
NET MODE : ETH
SERVER ADDR : eu1.cloud.thethings.network
PORT UP : 1700
PORT DOWN : 1700
INTERVALS : 10
REGION : EU868
LOGIN PASS : heltec.org
TIME ZONE : UTC+2
ETH Started, Connecting…
ETH Connected
IPv4: 192.168.0.53, FULL_DUPLEX, 100Mbps
MDNS responder started
HTTP server started
get time from : europe.pool.ntp.org
Maybe you are right. But the network works with all other devices (including some other gateways) and I have no idea where I should change something in the settings of the HT-M01S
Refer to the log printed by HT-M01S, everything works well but in the last step, the system can’t get the IP address of eu1.cloud.thethings.network. But when I tested the HT-M01S with the TTN server at my side, it’s working normally.
Can you please try with another router? Or via the Wi-Fi method?
Thank you for your answer. Now it works, too. The problem was that the TTN address had invisible spaces at the beginning and the end. After removing them, the gateway connects. Maybe you add a cleaning step into the program…
Now I only have the problem with the HT-M00 where I am not able to enter the license after upgrading (HT-M00 -> Please provide a correct license! or License activation - LoRa Node - Heltec Automation Technical Community ) where I did not get an answer for a long time
Sorry, because the HT-M00 has updated the license algorithm in the V1.8 firmware, please send your ESP32 chip ID to support@heltec.cn, and we will generate a new license for you.
I just upgraded mine to 1.4 via the web and it initially came up with a blank screen - I had to go through the license process through the serial port to get it to work again.
Has anyone been able to use a Adafruit RFM95 module and a RP Pico to send data through this gateway? I also tried a UNO/HopeRF and a Mega/HopeRF module and could not get them to connect either. All of these continuously try to join and it fails each time.
I have only had luck connecting to this gateway through a Heltec ESP32LoRa 32 (V2).
That really needs to be its own question or attach to a thread on the pi pico, since it’s strictly about getting such a node to implement LoRaWAN with TTN settings and has absolutely nothing to do with which gateway is being used; gateways all behave the same way, unless they’re broken. The actual “conversation” is between the node and the TTN servers.