i am using version 3.9 of app and network server. i have added a Micro tektelic gateway using device profile LORAWAN 1.0.1 supporting B revision of regional params and used OTAA support. THAT gateway is not visible by the UI
gateway != device . gateway not using all that you described above. gateway using own gateway profile ( not device profile)
sorry i was mistaken. Device-profile mentions LoRaWAN MAC version and LoRaWAN Regional Parameters revision. Gateway does not depend on device-profile. When I entered gateway id,i got the message: Last seen=Never. Is that normal?
usually not.
but it depends from right packet-forwarder configuration “keepalive_interval”: , “stat_interval”:, chirpstack components availability from GW etc.
I am not sure what does that mean?
I am assuming that parameters “keepalive_interval”: , “stat_interval”: from gateway config
look into the /etc/default/config.json of your gateway
see the packet-forwarder message log also.
“keepalive_interval”: 10
“stat_interval”: 30
tail of packet forwarder log
May 1 21:45:16 kona-micro pkt_forwarder:
2020-05-01 21:45:16 GMT
May 1 21:45:16 kona-micro pkt_forwarder: ### [UPSTREAM] ###
May 1 21:45:16 kona-micro pkt_forwarder: # RF packets received by concentrator: 0
May 1 21:45:16 kona-micro pkt_forwarder: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 1 21:45:16 kona-micro pkt_forwarder: # RF packets forwarded: 0 (0 bytes)
May 1 21:45:16 kona-micro pkt_forwarder: # PUSH_DATA datagrams sent: 1 (183 bytes)
May 1 21:45:16 kona-micro pkt_forwarder: # PUSH_DATA acknowledged: 0.00%
May 1 21:45:16 kona-micro pkt_forwarder: ### [DOWNSTREAM] ###
May 1 21:45:16 kona-micro pkt_forwarder: # PULL_DATA sent: 3 (0.00% acknowledged)
May 1 21:45:16 kona-micro pkt_forwarder: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
May 1 21:45:16 kona-micro pkt_forwarder: # RF packets sent to concentrator: 0 (0 bytes)
May 1 21:45:16 kona-micro pkt_forwarder: # TX errors: 0
May 1 21:45:16 kona-micro pkt_forwarder: # BEACON queued: 0
May 1 21:45:16 kona-micro pkt_forwarder: # BEACON sent so far: 0
May 1 21:45:16 kona-micro pkt_forwarder: # BEACON rejected: 0
May 1 21:45:16 kona-micro pkt_forwarder: ### [JIT] ###
May 1 21:45:16 kona-micro pkt_forwarder: # SX1301 time (PPS): 3358298813
May 1 21:45:16 kona-micro pkt_forwarder: INFO: [jit] queue is empty
May 1 21:45:16 kona-micro pkt_forwarder: ### [GPS] ###
May 1 21:45:16 kona-micro pkt_forwarder: # GPS coordinates: latitude 0.00000, longitude 0.00000, altitude 0 m
May 1 21:45:16 kona-micro pkt_forwarder: ##### END #####
May 1 21:45:16 kona-micro pkt_forwarder:
JSON up: {“stat”:{“time”:“2020-05-01 21:45:16 GMT”,“lati”:0.00000,“long”:0.00000,“alti”:0,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:0.0,“dwnb”:0,“txnb”:0,“temp”:51,“cpur”:9.3,“memr”:11.5}}
May 1 21:45:36 kona-micro pkt_forwarder: INFO: host/sx1301 time offset=(1588366158s:58688us) - drift=16us
after I audit all gateway parameters,UI shows is has seen the gateway a few seconds go.This I assume is normal. When I restart my gateway,i get the message
listen udp 0.0.0.0:1700: bind: address already in use
The address I put in the gateway block is NOT 0.0.0.0. where does it take the address of 0.0.0.0:1700?
to exclude your previous experiments with local(gateway) chirpstack components
put gateway to factory defaults, without additional package installation and reconfigure packet forwarder with right server address and port.
@eugenev
I need to get from tektelic support values for regional service and device profile.I have read regional parameters doc but values for ADR was missed or I did not find it. The same goes for DR. Can you share the link for regional params ? I want to make sure I am reading the correct info.
here is my link: https://lora-alliance.org/sites/default/files/2020-01/rp_2-1.0.0_final_release.pdf
@eugenev
here is the message from tektelic support
Hi Alexander,
Thank you for contacting us. Kindly note that there is no way to perform factory reset on Kona Micro gateway. Also, we do not recommend it to our customers.
Thanks and Regards,
AP
Then remove all packages installed by you manually.
not for this purpose
@eugenev
I got lucky.I removed task/service from monit called lora-service-bridge and the bind error went away from pkt_fwd.log on the gateway. tail of the file looks like:
May 5 22:11:37 kona-micro pkt_forwarder: # PUSH_DATA datagrams sent: 1 (185 bytes)
May 5 22:11:37 kona-micro pkt_forwarder: # PUSH_DATA acknowledged: 100.00%
May 5 22:11:37 kona-micro pkt_forwarder: ### [DOWNSTREAM] ###
May 5 22:11:37 kona-micro pkt_forwarder: # PULL_DATA sent: 3 (100.00% acknowledged)
May 5 22:11:37 kona-micro pkt_forwarder: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
May 5 22:11:37 kona-micro pkt_forwarder: # RF packets sent to concentrator: 0 (0 bytes)
May 5 22:11:37 kona-micro pkt_forwarder: # TX errors: 0
May 5 22:11:37 kona-micro pkt_forwarder: # BEACON queued: 0
May 5 22:11:37 kona-micro pkt_forwarder: # BEACON sent so far: 0
May 5 22:11:37 kona-micro pkt_forwarder: # BEACON rejected: 0
May 5 22:11:37 kona-micro pkt_forwarder: ### [JIT] ###
May 5 22:11:37 kona-micro pkt_forwarder: # SX1301 time (PPS): 724158970
May 5 22:11:37 kona-micro pkt_forwarder: INFO: [jit] queue is empty
May 5 22:11:37 kona-micro pkt_forwarder: ### [GPS] ###
May 5 22:11:37 kona-micro pkt_forwarder: # GPS coordinates: latitude 0.00000, longitude 0.00000, altitude 0 m
May 5 22:11:37 kona-micro pkt_forwarder: ##### END #####
May 5 22:11:37 kona-micro pkt_forwarder:
JSON up: {“stat”:{“time”:“2020-05-05 22:11:37 GMT”,“lati”:0.00000,“long”:0.00000,“alti”:0,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0,“temp”:50,“cpur”:12.5,“memr”:8.8}}
May 5 22:11:37 kona-micro pkt_forwarder: INFO: [up] PUSH_ACK received in 26 ms
May 5 22:11:39 kona-micro pkt_forwarder: INFO: [down] PULL_ACK received in 20 ms
May 5 22:11:49 kona-micro pkt_forwarder: INFO: [down] PULL_ACK received in 20 ms
May 5 22:11:59 kona-micro pkt_forwarder: INFO: [down] PULL_ACK received in 22 ms
May 5 22:12:07 kona-micro pkt_forwarder:
2020-05-05 22:12:07 GMT
May 5 22:12:07 kona-micro pkt_forwarder: ### [UPSTREAM] ###
May 5 22:12:07 kona-micro pkt_forwarder: # RF packets received by concentrator: 0
May 5 22:12:07 kona-micro pkt_forwarder: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
May 5 22:12:07 kona-micro pkt_forwarder: # RF packets forwarded: 0 (0 bytes)
May 5 22:12:07 kona-micro pkt_forwarder: # PUSH_DATA datagrams sent: 1 (185 bytes)
May 5 22:12:07 kona-micro pkt_forwarder: # PUSH_DATA acknowledged: 100.00%
May 5 22:12:07 kona-micro pkt_forwarder: ### [DOWNSTREAM] ###
May 5 22:12:07 kona-micro pkt_forwarder: # PULL_DATA sent: 3 (100.00% acknowledged)
May 5 22:12:07 kona-micro pkt_forwarder: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
May 5 22:12:07 kona-micro pkt_forwarder: # RF packets sent to concentrator: 0 (0 bytes)
May 5 22:12:07 kona-micro pkt_forwarder: # TX errors: 0
May 5 22:12:07 kona-micro pkt_forwarder: # BEACON queued: 0
May 5 22:12:07 kona-micro pkt_forwarder: # BEACON sent so far: 0
May 5 22:12:07 kona-micro pkt_forwarder: # BEACON rejected: 0
May 5 22:12:07 kona-micro pkt_forwarder: ### [JIT] ###
May 5 22:12:07 kona-micro pkt_forwarder: # SX1301 time (PPS): 754168328
May 5 22:12:07 kona-micro pkt_forwarder: INFO: [jit] queue is empty
May 5 22:12:07 kona-micro pkt_forwarder: ### [GPS] ###
May 5 22:12:07 kona-micro pkt_forwarder: # GPS coordinates: latitude 0.00000, longitude 0.00000, altitude 0 m
May 5 22:12:07 kona-micro pkt_forwarder: ##### END #####
May 5 22:12:07 kona-micro pkt_forwarder:
JSON up: {“stat”:{“time”:“2020-05-05 22:12:07 GMT”,“lati”:0.00000,“long”:0.00000,“alti”:0,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0,“temp”:50,“cpur”:12.4,“memr”:8.9}}
May 5 22:12:07 kona-micro pkt_forwarder: INFO: [up] PUSH_ACK received in 24 ms
May 5 22:12:09 kona-micro pkt_forwarder: INFO: [down] PULL_ACK received in 19 ms
May 5 22:12:19 kona-micro pkt_forwarder: INFO: [down] PULL_ACK received in 27 ms
May 5 22:12:29 kona-micro pkt_forwarder: INFO: [down] PULL_ACK received in 23 ms
root@kona-micro:/var/log#
is this ok? what do I do now?
this log about nothing.
where from your log you can see that the packet-forwarder successfully connects to the chirp?
continue to configure packet-forwarder and chirpstack components from other side, to make them work together.
May 09 15:50:10 ip-172-26-0-174 systemd[1]: Started ChirpStack Gateway Bridge.
May 09 15:50:10 ip-172-26-0-174 chirpstack-gateway-bridge[23930]: time=“2020-05-09T15:50:10Z” level=info msg=“starting ChirpStack Gateway Bridge” docs=“Introduction - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server” version=3.8.0
May 09 15:50:10 ip-172-26-0-174 chirpstack-gateway-bridge[23930]: time=“2020-05-09T15:50:10Z” level=info msg=“backend/semtechudp: starting gateway udp listener” addr=“0.0.0.0:1700”
May 09 15:50:10 ip-172-26-0-174 chirpstack-gateway-bridge[23930]: time=“2020-05-09T15:50:10Z” level=info msg=“integration/mqtt: connected to mqtt broker”
May 09 15:50:18 ip-172-26-0-174 chirpstack-gateway-bridge[23930]: time=“2020-05-09T15:50:18Z” level=info msg=“integration/mqtt: subscribing to topic” qos=0 topic=“gateway/647fdafffe0088c1/command/#”
May 09 15:50:26 ip-172-26-0-174 chirpstack-gateway-bridge[23930]: time=“2020-05-09T15:50:26Z” level=info msg=“integration/mqtt: publishing event” event=stats qos=0 stats_id=4f48ac11-6d24-4be9-bd7a-a1b31c6330cc topic=gateway/647fdafffe0088c1/event/stats
May 09 15:50:56 ip-172-26-0-174 chirpstack-gateway-bridge[23930]: time=“2020-05-
09T15:50:56Z” level=info msg=“integration/mqtt: publishing event” event=stats qos=0
stats_id=9ba1cd2b-11a9-4425-96db-e750da4d7709 topic=gateway/647fdafffe0088c1/event/stats
May 09 15:51:26 ip-172-26-0-174 chirpstack-gateway-bridge[23930]: time=“2020-05-09T15:51:26Z” level=info msg=“integration/mqtt: publishing event” event=stats qos=0 stats_id=afb3f09f-ac42-4eee-8ce8-46276925ada1 topic=gateway/647fdafffe0088c1/event/stats
@eugenev here my gateway-bridge log that runs on AWS server. I think it is connected to mqtt. How do I query the device(kona home sensor)?
LoRa sensors are not queried, espicially Class A endnodes. They are joins to the network and send their data by some event or by schedule programmed into it, after successful join. Please do not ask additional questions not related to the topic. You may start another thread.