search

helium / gateway-rs

The Helium Gateway
Apache License 2.0
280 stars 110 forks source link

trying to onboard dragino LPS8 #180

Closed dvdadie2 closed 2 years ago

dvdadie2 commented 2 years ago

In the LoRa Gateway window, all four status areas have a green checkmark. In the Helium IoT window, the gateway_key.bin file is loaded with version (helium_gateway 1.0.0-alpha.21), the hotspot key is right, and the animal name is right.

In Helium Explorer, the unit was added to the blockchain 7 days ago, the location was asserted 4 days ago, red dot hovering over activity, no beacons, no data, no rewards.

In HeliumStatus.io, the unit listed, the status is offline, the helium api status is offline. I have tried to test the connections with several different IP addresses and ports, nothing works.

In the Putty window, this is the output after a gateway reset:

Sun Jan 23 16:01:58 2022 daemon.info helium_gateway[26005]: INFO starting server, key: 14UcAh3dvphbbh6JPyp54GhJcn5VsS1KVEe1qnmwyBgrUALkzAf, version: 1.0.0-alpha.21 Sun Jan 23 16:01:58 2022 daemon.info helium_gateway[26005]: INFO starting, module: gateway Sun Jan 23 16:01:58 2022 daemon.info helium_gateway[26005]: INFO starting, module: dispatcher Sun Jan 23 16:01:58 2022 daemon.info helium_gateway[26005]: INFO default router, uri: http://54.176.88.149:8080/, pubkey: 1124CJ9yJaHq4D6ugyPCDnSBzQik61C1BqD9VMh1vsUmjwt16HNB, module: dispatcher Sun Jan 23 16:01:58 2022 daemon.info helium_gateway[26005]: INFO using gateway, uri: http://52.49.199.40:8080/, pubkey: 11tk4zzbyfMPYYHYda255ACoqfYFVdrUSoCWrCYfn8BoyuYrERK, module: dispatcher Sun Jan 23 16:01:58 2022 daemon.info helium_gateway[26005]: INFO starting, module: updater Sun Jan 23 16:01:58 2022 daemon.info helium_gateway[26005]: INFO starting, listen: 127.0.0.1:4467, module: api Sun Jan 23 16:01:59 2022 daemon.info helium_gateway[26005]: INFO starting, oui: 16, uri: http://13.37.13.24:8080/, pubkey: 11afuQSrmk52mgxLu91AdtDXbJ9wmqWBUxC3hvjejoXkxEZfPvY, module: router Sun Jan 23 16:02:00 2022 daemon.info helium_gateway[26005]: INFO starting, oui: 13, uri: http://46.246.38.248:8080/, pubkey: 115ZS5of9wsV3M5sH3mePp9NVnKayUXG7qT2W7Sn4KJLMzd3eMr, module: router Sun Jan 23 16:02:00 2022 daemon.info helium_gateway[26005]: INFO starting, oui: 12, uri: http://54.219.236.122:8080/, pubkey: 112ewJNEUfSg3Jvo276tMjzFC2JzmmZcJJ32CWz2fzYqbyCMMTe1, module: router Sun Jan 23 16:02:00 2022 daemon.info helium_gateway[26005]: INFO starting, oui: 9, uri: http://86.99.197.230:8080/, pubkey: 11w77YQLhgUt8HUJrMtntGGr97RyXmot1ofs5Ct2ELTmbFoYsQa, module: router Sun Jan 23 16:02:00 2022 daemon.info helium_gateway[26005]: INFO starting, oui: 4, uri: http://54.193.165.228:8080/, pubkey: 11263KvqW3GZPAvag5sQYtBJSjb25azSTSwoi5Tza9kboaLRxcsv, module: router Sun Jan 23 16:02:00 2022 daemon.info helium_gateway[26005]: INFO starting, oui: 2, uri: http://54.176.88.149:8080/, pubkey: 1124CJ9yJaHq4D6ugyPCDnSBzQik61C1BqD9VMh1vsUmjwt16HNB, module: router Sun Jan 23 16:02:01 2022 daemon.info helium_gateway[26005]: INFO updated routing to height 1194869, module: dispatcher Sun Jan 23 16:02:01 2022 daemon.info helium_gateway[26005]: INFO starting, oui: 1, uri: http://52.8.80.146:8080/, pubkey: 112qB3YaH5bZkCnKA5uRH7tBtGNv2Y5B4smv1jsmvGUzgKT71QpE, module: router Sun Jan 23 16:02:05 2022 daemon.info helium_gateway[26005]: INFO no update found, module: updater Sun Jan 23 16:02:11 2022 daemon.info helium_gateway[26005]: INFO new packet forwarder client: MacAddress(A8:40:41:21:D7:BC:50), 127.0.0.1:45469, module: gateway

Can someone please help me? I have spent days on this and I am not getting anywhere.

Thanks in advance.

lthiery commented 2 years ago

Things I can see from the logs are that the packet forwarder is connected to helium_gateway so that's good.

However, I don't see any radio frames in your logs. How did you configure the channel plan of the packet forwarder (ie: global_conf.json)? Have you double checked that the LPS8 channel plan matches?

And with which LNS is the LPS8 registered?

dvdadie2 commented 2 years ago

@lthiery thank you for the reply.

i found my global_conf.json file and it originally said: { "SX130x_conf": { "full_duplex": false, "spidev_path": "/dev/spidev0.0", "lorawan_public": true, "clksrc": 1, "clksrc_desc": "radio_1 provides clock to concentrator for most devices except MultiTech. For MultiTech set to 0.", "antenna_gain": 0, "antenna_gain_desc": "antenna gain, in dBi", "radio_0": { "enable": true, "type": "SX1257", "freq": 904300000, "rssi_offset": -166.0, "tx_enable": true, "tx_freq_min": 902000000, "tx_freq_max": 928000000 }, "radio_1": { "enable": true, "type": "SX1257", "freq": 905000000, "rssi_offset": -166.0, "tx_enable": false }, "chan_multiSF_0": { "desc": "Lora MAC, 125kHz, all SF, 903.9 MHz", "enable": true, "radio": 0, "if": -400000 }, "chan_multiSF_1": { "desc": "Lora MAC, 125kHz, all SF, 904.1 MHz", "enable": true, "radio": 0, "if": -200000 }, "chan_multiSF_2": { "desc": "Lora MAC, 125kHz, all SF, 904.3 MHz", "enable": true, "radio": 0, "if": 0 }, "chan_multiSF_3": { "desc": "Lora MAC, 125kHz, all SF, 904.5 MHz", "enable": true, "radio": 0, "if": 200000 }, "chan_multiSF_4": { "desc": "Lora MAC, 125kHz, all SF, 904.7 MHz", "enable": true, "radio": 1, "if": -300000 }, "chan_multiSF_5": { "desc": "Lora MAC, 125kHz, all SF, 904.9 MHz", "enable": true, "radio": 1, "if": -100000 }, "chan_multiSF_6": { "desc": "Lora MAC, 125kHz, all SF, 905.1 MHz", "enable": true, "radio": 1, "if": 100000 }, "chan_multiSF_7": { "desc": "Lora MAC, 125kHz, all SF, 905.3 MHz", "enable": true, "radio": 1, "if": 300000 }, "chan_Lora_std": { "desc": "Lora MAC, 500kHz, SF8, 904.6 MHz", "enable": true, "radio": 0, "if": 300000, "bandwidth": 500000, "spread_factor": 8 }, "chan_FSK": { "desc": "disabled", "enable": false }, "tx_lut_0": { "desc": "TX gain table, index 0", "pa_gain": 2, "mix_gain": 9, "rf_power": 12, "dig_gain": 2 }, "tx_lut_1": { "desc": "TX gain table, index 1", "pa_gain": 2, "mix_gain": 9, "rf_power": 13, "dig_gain": 1 }, "tx_lut_2": { "desc": "TX gain table, index 2", "pa_gain": 2, "mix_gain": 10, "rf_power": 14, "dig_gain": 2 }, "tx_lut_3": { "desc": "TX gain table, index 3", "pa_gain": 2, "mix_gain": 10, "rf_power": 15, "dig_gain": 1 }, "tx_lut_4": { "desc": "TX gain table, index 4", "pa_gain": 2, "mix_gain": 10, "rf_power": 16, "dig_gain": 0 }, "tx_lut_5": { "desc": "TX gain table, index 5", "pa_gain": 2, "mix_gain": 11, "rf_power": 17, "dig_gain": 1 }, "tx_lut_6": { "desc": "TX gain table, index 6", "pa_gain": 2, "mix_gain": 11, "rf_power": 18, "dig_gain": 0 }, "tx_lut_7": { "desc": "TX gain table, index 7", "pa_gain": 2, "mix_gain": 12, "rf_power": 19, "dig_gain": 0 }, "tx_lut_8": { "desc": "TX gain table, index 8", "pa_gain": 2, "mix_gain": 13, "rf_power": 20, "dig_gain": 0 }, "tx_lut_9": { "desc": "TX gain table, index 9", "pa_gain": 2, "mix_gain": 14, "rf_power": 21, "dig_gain": 0 }, "tx_lut_10": { "desc": "TX gain table, index 10", "pa_gain": 2, "mix_gain": 15, "rf_power": 22, "dig_gain": 0 }, "tx_lut_11": { "desc": "TX gain table, index 11", "pa_gain": 3, "mix_gain": 11, "rf_power": 23, "dig_gain": 1 }, "tx_lut_12": { "desc": "TX gain table, index 12", "pa_gain": 3, "mix_gain": 12, "rf_power": 24, "dig_gain": 0 }, "tx_lut_13": { "desc": "TX gain table, index 13", "pa_gain": 3, "mix_gain": 14, "rf_power": 25, "dig_gain": 0 }, "tx_lut_14": { "desc": "TX gain table, index 14", "pa_gain": 3, "mix_gain": 14, "rf_power": 26, "dig_gain": 0 }, "tx_lut_15": { "desc": "TX gain table, index 15", "pa_gain": 3, "mix_gain": 14, "rf_power": 27, "dig_gain": 0 } }, "gateway_conf": { "server_address": "router.us.thethings.network", "serv_port_up": 1700, "serv_port_down": 1700, "servers": [ { "server_address": "router.us.thethings.network", "serv_port_up": 1700, "serv_port_down": 1700, "serv_enabled": true } ] }

}

that last part didn't look right because i am not a part of the things network, so i changed it to:

"gateway_conf": { "server_address": 127.0.0.1, "serv_port_up": 1680, "serv_port_down": 1680, "servers": [ { "server_address": 127.0.0.1, "serv_port_up": 1680, "serv_port_down": 1680, "serv_enabled": true }

i restarted the helium gateway and the logread read this:

Mon Jan 24 12:23:48 2022 daemon.info helium_gateway[26675]: INFO starting server, key: 14UcAh3dvphbbh6JPyp54GhJcn5VsS1KVEe1qnmwyBgrUALkzAf, version: 1.0.0-alpha.21 Mon Jan 24 12:23:48 2022 daemon.info helium_gateway[26675]: INFO starting, module: gateway Mon Jan 24 12:23:48 2022 daemon.info helium_gateway[26675]: INFO starting, module: dispatcher Mon Jan 24 12:23:48 2022 daemon.info helium_gateway[26675]: INFO default router, uri: http://54.176.88.149:8080/, pubkey: 1124CJ9yJaHq4D6ugyPCDnSBzQik61C1BqD9VMh1vsUmjwt16HNB, module: dispatcher Mon Jan 24 12:23:48 2022 daemon.info helium_gateway[26675]: INFO using gateway, uri: http://35.84.173.125:8080/, pubkey: 11pUovhssQdXzrfcYMTUrNNTQossgny8WqhfdbprrAVFyHcmvAN, module: dispatcher Mon Jan 24 12:23:48 2022 daemon.info helium_gateway[26675]: INFO starting, module: updater Mon Jan 24 12:23:48 2022 daemon.info helium_gateway[26675]: INFO starting, listen: 127.0.0.1:4467, module: api Mon Jan 24 12:23:54 2022 daemon.info helium_gateway[26675]: INFO no update found, module: updater Mon Jan 24 12:24:15 2022 daemon.info helium_gateway[26675]: INFO new packet forwarder client: MacAddress(A8:40:41:21:D7:BC:50), 127.0.0.1:34321, module: gateway Mon Jan 24 12:25:58 2022 daemon.info helium_gateway[26675]: WARN gateway error: Service(Rpc(Status { code: Unavailable, message: "error trying to connect: tcp connect error: Operation timed out (os error 145)", source: Some(tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 145, kind: TimedOut, message: "Operation timed out" })))) })), module: dispatcher Mon Jan 24 12:26:03 2022 daemon.info helium_gateway[26675]: INFO using gateway, uri: http://3.38.70.101:8080/, pubkey: 11yJXQPG9deHqvw2ac6VWtNP7gZj8X3t3Qb3Gqm9j729p4AsdaA, module: dispatcher Mon Jan 24 12:26:04 2022 daemon.info helium_gateway[26675]: INFO starting, oui: 16, uri: http://13.37.13.24:8080/, pubkey: 11afuQSrmk52mgxLu91AdtDXbJ9wmqWBUxC3hvjejoXkxEZfPvY, module: router Mon Jan 24 12:26:04 2022 daemon.info helium_gateway[26675]: INFO starting, oui: 13, uri: http://46.246.38.248:8080/, pubkey: 115ZS5of9wsV3M5sH3mePp9NVnKayUXG7qT2W7Sn4KJLMzd3eMr, module: router Mon Jan 24 12:26:04 2022 daemon.info helium_gateway[26675]: INFO starting, oui: 12, uri: http://54.219.236.122:8080/, pubkey: 112ewJNEUfSg3Jvo276tMjzFC2JzmmZcJJ32CWz2fzYqbyCMMTe1, module: router Mon Jan 24 12:26:05 2022 daemon.info helium_gateway[26675]: INFO starting, oui: 10, uri: http://54.228.141.195:8080/, pubkey: 11YmZtwTPEuMSFGxze1x9TfDfGezN7vXevLu71iJe9FBbvNRAgk, module: router Mon Jan 24 12:26:05 2022 daemon.info helium_gateway[26675]: INFO starting, oui: 9, uri: http://86.97.7.188:8080/, pubkey: 11w77YQLhgUt8HUJrMtntGGr97RyXmot1ofs5Ct2ELTmbFoYsQa, module: router Mon Jan 24 12:26:05 2022 daemon.info helium_gateway[26675]: INFO starting, oui: 4, uri: http://54.193.165.228:8080/, pubkey: 11263KvqW3GZPAvag5sQYtBJSjb25azSTSwoi5Tza9kboaLRxcsv, module: router Mon Jan 24 12:26:05 2022 daemon.info helium_gateway[26675]: INFO starting, oui: 2, uri: http://54.176.88.149:8080/, pubkey: 1124CJ9yJaHq4D6ugyPCDnSBzQik61C1BqD9VMh1vsUmjwt16HNB, module: router Mon Jan 24 12:26:05 2022 daemon.info helium_gateway[26675]: INFO updated routing to height 1196176, module: dispatcher Mon Jan 24 12:26:05 2022 daemon.info helium_gateway[26675]: INFO starting, oui: 1, uri: http://52.8.80.146:8080/, pubkey: 112qB3YaH5bZkCnKA5uRH7tBtGNv2Y5B4smv1jsmvGUzgKT71QpE, module: router Mon Jan 24 12:29:28 2022 daemon.info helium_gateway[26675]: INFO updated routing to height 1196182, module: dispatcher Mon Jan 24 12:30:05 2022 daemon.info helium_gateway[350]: INFO starting server, key: 14UcAh3dvphbbh6JPyp54GhJcn5VsS1KVEe1qnmwyBgrUALkzAf, version: 1.0.0-alpha.21 Mon Jan 24 12:30:05 2022 daemon.info helium_gateway[350]: INFO starting, module: gateway Mon Jan 24 12:30:05 2022 daemon.info helium_gateway[350]: INFO starting, module: dispatcher Mon Jan 24 12:30:05 2022 daemon.info helium_gateway[350]: INFO default router, uri: http://54.176.88.149:8080/, pubkey: 1124CJ9yJaHq4D6ugyPCDnSBzQik61C1BqD9VMh1vsUmjwt16HNB, module: dispatcher Mon Jan 24 12:30:05 2022 daemon.info helium_gateway[350]: INFO using gateway, uri: http://52.49.199.40:8080/, pubkey: 11tk4zzbyfMPYYHYda255ACoqfYFVdrUSoCWrCYfn8BoyuYrERK, module: dispatcher Mon Jan 24 12:30:05 2022 daemon.info helium_gateway[350]: INFO starting, module: updater Mon Jan 24 12:30:05 2022 daemon.info helium_gateway[350]: INFO starting, listen: 127.0.0.1:4467, module: api Mon Jan 24 12:30:07 2022 daemon.info helium_gateway[350]: INFO starting, oui: 16, uri: http://15.188.63.152:8080/, pubkey: 11afuQSrmk52mgxLu91AdtDXbJ9wmqWBUxC3hvjejoXkxEZfPvY, module: router Mon Jan 24 12:30:07 2022 daemon.info helium_gateway[350]: INFO starting, oui: 13, uri: http://46.246.38.248:8080/, pubkey: 115ZS5of9wsV3M5sH3mePp9NVnKayUXG7qT2W7Sn4KJLMzd3eMr, module: router Mon Jan 24 12:30:07 2022 daemon.info helium_gateway[350]: INFO starting, oui: 12, uri: http://54.219.236.122:8080/, pubkey: 112ewJNEUfSg3Jvo276tMjzFC2JzmmZcJJ32CWz2fzYqbyCMMTe1, module: router Mon Jan 24 12:30:07 2022 daemon.info helium_gateway[350]: INFO starting, oui: 10, uri: http://54.228.141.195:8080/, pubkey: 11YmZtwTPEuMSFGxze1x9TfDfGezN7vXevLu71iJe9FBbvNRAgk, module: router Mon Jan 24 12:30:08 2022 daemon.info helium_gateway[350]: INFO starting, oui: 9, uri: http://86.97.7.188:8080/, pubkey: 11w77YQLhgUt8HUJrMtntGGr97RyXmot1ofs5Ct2ELTmbFoYsQa, module: router Mon Jan 24 12:30:08 2022 daemon.info helium_gateway[350]: INFO starting, oui: 4, uri: http://54.193.165.228:8080/, pubkey: 11263KvqW3GZPAvag5sQYtBJSjb25azSTSwoi5Tza9kboaLRxcsv, module: router Mon Jan 24 12:30:08 2022 daemon.info helium_gateway[350]: INFO starting, oui: 2, uri: http://54.176.88.149:8080/, pubkey: 1124CJ9yJaHq4D6ugyPCDnSBzQik61C1BqD9VMh1vsUmjwt16HNB, module: router Mon Jan 24 12:30:08 2022 daemon.info helium_gateway[350]: INFO updated routing to height 1196182, module: dispatcher Mon Jan 24 12:30:08 2022 daemon.info helium_gateway[350]: INFO starting, oui: 1, uri: http://52.8.80.146:8080/, pubkey: 112qB3YaH5bZkCnKA5uRH7tBtGNv2Y5B4smv1jsmvGUzgKT71QpE, module: router

lthiery commented 2 years ago

@dvdadie2 i don't see any radio frames coming in yet. can you restarted your end node to confirm that data gets this far?

Also, please let me know which LNS you've registered this LoRaWAN Device with. UUID is also helpful if you've used Helium Console.

dvdadie2 commented 2 years ago

@lthiery in the configuration screen, there is a menu called "lorawan" with four options (1) lorwan - semtech udp (2) lorawan - basic station (3) helium iot and (4) and loriot. i registered the gateway with "the things network". i got everything working so that the TTN console was showing live activity. however, when i went back to the helium iot option, the gateway-rs status was not connected, the hotspot key was missing, and the hotspot animal name was missing. as soon as i reload the gateway_key.bin file to get the helium information back, it kills the lorawn - semtech udp / ttn connection.

IoTThinks commented 2 years ago

Data-only hotspots are always shown as offline in the Helium explorer. You can not keep both TTN and Helium connection at the same time for LPS8. Make sure the "region=XXXXX" is on the top of settings.toml or you need to modify it in default.toml.

First join to Helium will take 3-4 hours.

Humancell commented 2 years ago

I'm actually having the same problem with the Dragino LPS8. I've got everything configured and it appears to be connected, my gateway is added and shows in my wallet, and I've got HNT and DC balances.

There does appear to be some error in the config though as I'm not seeing packets. When I reviewed my global_conf.json it also showed:

"gateway_conf":{
   "server_address":"router.us.thethings.network",
   "serv_port_up":1700,
   "serv_port_down":1700,
   "servers":[
      {
         "server_address":"router.us.thethings.network",
         "serv_port_up":1700,
         "serv_port_down":1700,
         "serv_enabled":true
      }
   ]
}

I changed it to be:

    "gateway_conf": {
        "server_address": "127.0.0.1",
        "serv_port_up": 1680,
        "serv_port_down": 1680,
        "servers": [ {
            "server_address": "127.0.0.1",
            "serv_port_up": 1680,
            "serv_port_down": 1680,
            "serv_enabled": true
        } ]
    }

Now I see this in the logs:

Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: Starting Packet Forwarder at 20220213232929
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ found global configuration file /etc/lora/global_conf.json, parsing it
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ /etc/lora/global_conf.json does contain a JSON object named SX130x_conf, parsing SX1301 parameters
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ lorawan_public 1, clksrc 1
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ no configuration for LBT
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ antenna_gain 0 dBi
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Configuring TX LUT with 16 indexes
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ radio 0 enabled (type SX1257), center frequency 904300000, RSSI offset -166.000000, tx enabled 1, tx_notch_freq 0
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ radio 1 enabled (type SX1257), center frequency 905000000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Lora multi-SF channel 0>  radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Lora multi-SF channel 1>  radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Lora multi-SF channel 2>  radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Lora multi-SF channel 3>  radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Lora multi-SF channel 4>  radio 1, IF -300000 Hz, 125 kHz bw, SF 7 to 12
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Lora multi-SF channel 5>  radio 1, IF -100000 Hz, 125 kHz bw, SF 7 to 12
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Lora multi-SF channel 6>  radio 1, IF 100000 Hz, 125 kHz bw, SF 7 to 12
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Lora multi-SF channel 7>  radio 1, IF 300000 Hz, 125 kHz bw, SF 7 to 12
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ FSK channel 8 disabled
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ /etc/lora/global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ server hostname or IP address is configured to "127.0.0.1"
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ upstream port is configured to "1680"
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ downstream port is configured to "1680"
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ packets received with a valid CRC will be forwarded
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ packets received with a CRC error will NOT be forwarded
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ packets received with no CRC will NOT be forwarded
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ found local configuration file /etc/lora/local_conf.json, parsing it
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ redefined parameters will overwrite global parameters
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ /etc/lora/local_conf.json does not contain a JSON object named SX130x_conf
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ /etc/lora/local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ gateway MAC address is configured to A840411D1FF44150
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ server hostname or IP address is configured to ""
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ upstream port is configured to "0"
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ downstream port is configured to "0"
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ downstream keep-alive interval is configured to 0 seconds
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ statistics display interval is configured to 30 seconds
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ upstream PUSH_DATA time-out is configured to 0 ms
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ packets received with a valid CRC will NOT be forwarded
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ packets received with a CRC error will NOT be forwarded
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ packets received with no CRC will NOT be forwarded
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Beaconing period is configured to 0 seconds
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Beaconing signal will be emitted at 869525000 Hz
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Beaconing datarate is set to SF9
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Beaconing modulation bandwidth is set to 125000Hz
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Beaconing TX power is set to 14dBm
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: INFO~ Beaconing information descriptor is set to 0
Sun Feb 13 16:29:29 2022 daemon.info lora_pkt_fwd[28501]: ERROR~ [up] getaddrinfo on address  (PORT 0) returned Name does not resolve
Sun Feb 13 16:29:29 2022 user.notice iot_keep_alive: Internet Access OK: via eth1
Sun Feb 13 16:29:29 2022 user.notice iot_keep_alive: use WAN or WiFi for internet access now

I can't tell if the local_conf.json is somehow confusing the packet forwarder? I also had it all working fine on the The Things Network, but it's not working on Helium.

lthiery commented 2 years ago

@lthiery in the configuration screen, there is a menu called "lorawan" with four options (1) lorwan - semtech udp (2) lorawan - basic station (3) helium iot and (4) and loriot. i registered the gateway with "the things network". i got everything working so that the TTN console was showing live activity. however, when i went back to the helium iot option, the gateway-rs status was not connected, the hotspot key was missing, and the hotspot animal name was missing. as soon as i reload the gateway_key.bin file to get the helium information back, it kills the lorawn - semtech udp / ttn connection.

@dvdadie2 Sorry for not following up sooner. I am not sure how Dragino implements these "lorawan" options. Based on what you are saying, it seems like the four LoRaWAN options are mutually exclusive as they connect the packet forwarder to TTN/loriot OR helium iot (ie: gateway-rs). I imagine they are connecting the packet forwarder to one of the network applications you are selecting; alternatively, option (1) seems to just be a bare packet forwarder that you then connect to whatever you want.

lthiery commented 2 years ago

@Humancell do you have logs from gateway-rs/helium_gateway to share? dvdadie's logs showed a good connection from this log line

Sun Jan 23 16:02:11 2022 daemon.info helium_gateway[26005]: INFO new packet forwarder client: MacAddress(A8:40:41:21:D7:BC:50), 127.0.0.1:45469, module: gateway

Are you also using the Dragino menu to do these installations?

Humancell commented 2 years ago

Hello ... I can't find those logs anywhere. What is the log file name? helium_gateway is installed, and I can run it ... but don't see specific log files for it anywhere. :-(

lthiery commented 2 years ago

Hello ... I can't find those logs anywhere. What is the log file name? helium_gateway is installed, and I can run it ... but don't see specific log files for it anywhere. :-(

I am not sure as it all depends on how Dragino integrated things. Maybe @dvdadie2 can share where to get them?

Humancell commented 2 years ago

@dvdadie2 I'm trying to get my LPS8 working also, and everything appears to be configured and working ... except as you had I'm not seeing packets. There are several things I'm unclear about:

  1. When I edit the global_conf.json like you did, and then I reboot, my edits are lost. How did you get them to persist through the reboots?
  2. Where did you find or extract the helium_gateway logs? Was it through the web ui? Or via a ssh session?
  3. Were you able to resolve your issues and get it working? If so, what did you do?

Thanks in advance!

lthiery commented 2 years ago

@Humancell @dvdadie2 I reached out to Dragino and they just now updated their Wiki and firmware to make this configuration easier

https://wiki.dragino.com/index.php?title=Notes_for_Helium#Forward_the_data_to_the_secondary_server

Can you try it out?

dvdadie2 commented 2 years ago

I started to install this new firmware but I stopped midway because it said it was going to reset settings to factory default. I reset to factory settings about a week ago and I lost everything. I had to abandon my old hotspot animal name, get a new name, and reassert my location. Thanks for the update though.

On Tue, Feb 15, 2022 at 8:25 PM Louis Thiery @.***> wrote:

@Humancell https://github.com/Humancell @dvdadie2 https://github.com/dvdadie2 I reached out to Dragino and they just now updated their Wiki and firmware to make this configuration easier

https://wiki.dragino.com/index.php?title=Notes_for_Helium#Forward_the_data_to_the_secondary_server

Can you try it out?

— Reply to this email directly, view it on GitHub https://github.com/helium/gateway-rs/issues/180#issuecomment-1041091699, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXNY4QNECFT255SFX2LYNK3U3MRMVANCNFSM5MTRKSIQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

-- enter through the narrow gate

Humancell commented 2 years ago

@lthiery thank you! I just downloaded the new firmware and will give it a try!

@dvdadie2 did you back-up the gateway key file? You should have done that, and then been able to restore/upload that file to restore the identity of the gateway. I believe that would have saved you from having to abandon the prior identity.

Humancell commented 2 years ago

Ok ... this is kind of insane. Is this a Dragino fatal flaw?

I backed up my gateway key, and then after applying the firmware update it DOES appear the gateway has a new key and animal name. So I then restored my key and rebooted ... and it still has the new key and animal name.

UGH!! How am I supposed to update the firmware and NOT wipe out my gateway? It looks like I have to pay again to add my gateway and assert it? Is this really the case?

Or how do I recover my gateway? A firmware update should NOT cause it to become a new gateway, right?

dvdadie2 commented 2 years ago

@humancell sorry I just saw your messages and questions. Yes, things are working for the most part now. In the dragino software interface there is a “reboot “ option. That seems to help things quite a bit. After that you want to log into your ssh session and type “/etc/init.d/helium_gateway restart” (no quotes). Then type “logread | grep helium _gateway” (no quotes). That is how I was accessing those logs. The dragino interface also has an option to read the Lora logs. You can look at those to find errors and warnings.

The dragino software is seriously lacking and only provides a fraction of what is needed. I haven’t found good, up to date documentation anywhere.

If you haven’t seen it, there is absolutely amazing series of videos on YouTube from a guy called “mobilefish”. There are 60 videos on lorawan from soup to nuts.

I believe that the global_conf.json file and the local_conf.json files cause about 70% of my lps8 problems. At first it was fun to try to solve the problems. Now it is just frustrating and way too time consuming.

Good luck.

On Sat, Feb 19, 2022 at 12:01 PM Scott C. Lemon @.***> wrote:

Ok ... this is kind of insane. Is this a Dragino fatal flaw?

I backed up my gateway key, and then after applying the firmware update it DOES appear the gateway has a new key and animal name. So I then restored my key and rebooted ... and it still has the new key and animal name.

UGH!! How am I supposed to update the firmware and NOT wipe out my gateway? It looks like I have to pay again to add my gateway and assert it? Is this really the case?

Or how do I recover my gateway? I firmware update should NOT cause it to become a new gateway, right?

— Reply to this email directly, view it on GitHub https://github.com/helium/gateway-rs/issues/180#issuecomment-1046093105, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXNY4QKNBBE6X2B3QAFXH4TU37ZKPANCNFSM5MTRKSIQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

-- enter through the narrow gate

dvdadie2 commented 2 years ago

closing this because the unit is up and running. thank you @Humancell and @lthiery

dvdadie2 commented 2 years ago

Ok ... this is kind of insane. Is this a Dragino fatal flaw?

I backed up my gateway key, and then after applying the firmware update it DOES appear the gateway has a new key and animal name. So I then restored my key and rebooted ... and it still has the new key and animal name.

UGH!! How am I supposed to update the firmware and NOT wipe out my gateway? It looks like I have to pay again to add my gateway and assert it? Is this really the case?

Or how do I recover my gateway? A firmware update should NOT cause it to become a new gateway, right?

i had other problems with the unit so i went ahead and upgraded the firmware. same result - lost everything, including the hotspot animal name and hotspot key. tried to load several old backups of the gateway_key.bin file but none of them worked. now i get to onboard and assert the "new" hotspot (again)...

madninja commented 2 years ago

You should be able to just put back your gateway_key.bin file in the right place and have it recover the original key/name. If not and your other units are working fine, maybe this is a dud?

Either way this does not appear to be related to gateway-rs and more with Dragino. Could you take it to their discord/support instead of here?

dvdadie2 commented 2 years ago

@madninja thanks again. yes, i agree. i SHOULD have been able to use my old backups but they didn't work. i will stop commenting here. cheers.