Tectelic Micro - Device Register No Response

Uri_Genin · April 21, 2020, 4:18pm

Hi

I am trying to register device through tektelic Micro. I can see packets coming to the network server but no packets going abck to gateway. The device that is trying to regsiter is of course configures in thw apllication server.
These are the logs I see. They talk about Gateway stats but no mention of Register request:

Apr 21 16:16:34 ip-172-31-88-102 chirpstack-network-server[27075]: time=“2020-04-21T16:16:34Z” level=info msg=“finished client unary call” ctx_id=945f4500-ac07-4e87-8d57-ab3275a323e4 grpc.code =OK grpc.ctx_id=fb2168c4-ca10-4ef8-b2e1-d509367ac486 grpc.duration=4.400393ms grpc.method=HandleGatewayStats grpc.service=as.ApplicationServerService span.kind=client system=grpc Apr 21 16:17:01 ip-172-31-88-102 CRON[27267]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 21 16:17:04 ip-172-31-88-102 chirpstack-network-server[27075]: time=“2020-04-21T16:17:04Z” level=info msg=“gateway/mqtt: gateway stats packet received” gateway_id=647fdafffe00811b stats_id =0562a4b6-6c3d-4746-b25c-81f3cee09543 Apr 21 16:17:04 ip-172-31-88-102 chirpstack-network-server[27075]: time=“2020-04-21T16:17:04Z” level=info msg=“gateway updated” ctx_id=0562a4b6-6c3d-4746-b25c-81f3cee09543 gateway_id=647fdafff e00811b Apr 21 16:17:04 ip-172-31-88-102 chirpstack-application-server[27033]: time=“2020-04-21T16:17:04Z” level=info msg=“gateway updated” ctx_id=43a71c92-188e-4065-b745-34d952b1fa6a id=647fdafffe008 11b name=TestMacroGW Apr 21 16:17:04 ip-172-31-88-102 chirpstack-application-server[27033]: time=“2020-04-21T16:17:04Z” level=info msg=“metrics saved” aggregation="[MINUTE HOUR DAY MONTH]" ctx_id=43a71c92-188e-406 5-b745-34d952b1fa6a name=“gw:647fdafffe00811b” Apr 21 16:17:04 ip-172-31-88-102 chirpstack-application-server[27033]: time=“2020-04-21T16:17:04Z” level=info msg=“finished unary call with code OK” ctx_id=43a71c92-188e-4065-b745-34d952b1fa6a grpc.code=OK grpc.method=HandleGatewayStats grpc.service=as.ApplicationServerService grpc.start_time=“2020-04-21T16:17:04Z” grpc.time_ms=4.082 peer.address=“127.0.0.1:41140” span.kind=server system=grpc Apr 21 16:17:04 ip-172-31-88-102 chirpstack-network-server[27075]: time=“2020-04-21T16:17:04Z” level=info msg=“finished client unary call” ctx_id=0562a4b6-6c3d-4746-b25c-81f3cee09543 grpc.code =OK grpc.ctx_id=43a71c92-188e-4065-b745-34d952b1fa6a grpc.duration=4.948012ms grpc.method=HandleGatewayStats grpc.service=as.ApplicationServerService span.kind=client system=grpc Apr 21 16:17:34 ip-172-31-88-102 chirpstack-network-server[27075]: time=“2020-04-21T16:17:34Z” level=info msg=“gateway/mqtt: gateway stats packet received” gateway_id=647fdafffe00811b stats_id =4ba30643-5c82-4975-b1e2-1df42c4a001e Apr 21 16:17:34 ip-172-31-88-102 chirpstack-network-server[27075]: time=“2020-04-21T16:17:34Z” level=info msg=“gateway updated” ctx_id=4ba30643-5c82-4975-b1e2-1df42c4a001e gateway_id=647fdafff e00811b Apr 21 16:17:34 ip-172-31-88-102 chirpstack-application-server[27033]: time=“2020-04-21T16:17:34Z” level=info msg=“gateway updated” ctx_id=d8f8061e-5b8e-4cdf-8052-abac7d0a9f2d id=647fdafffe008 11b name=TestMacroGW Apr 21 16:17:34 ip-172-31-88-102 chirpstack-application-server[27033]: time=“2020-04-21T16:17:34Z” level=info msg=“metrics saved” aggregation="[MINUTE HOUR DAY MONTH]" ctx_id=d8f8061e-5b8e-4cd f-8052-abac7d0a9f2d name=“gw:647fdafffe00811b” Apr 21 16:17:34 ip-172-31-88-102 chirpstack-application-server[27033]: time=“2020-04-21T16:17:34Z” level=info msg=“finished unary call with code OK” ctx_id=d8f8061e-5b8e-4cdf-8052-abac7d0a9f2d grpc.code=OK grpc.method=HandleGatewayStats grpc.service=as.ApplicationServerService grpc.start_time=“2020-04-21T16:17:34Z” grpc.time_ms=3.845 peer.address=“127.0.0.1:41140” span.kind=server system=grpc Apr 21 16:17:34 ip-172-31-88-102 chirpstack-network-server[27075]: time=“2020-04-21T16:17:34Z” level=info msg=“finished client unary call” ctx_id=4ba30643-5c82-4975-b1e2-1df42c4a001e grpc.code =OK grpc.ctx_id=d8f8061e-5b8e-4cdf-8052-abac7d0a9f2d grpc.duration=4.685536ms grpc.method=HandleGatewayStats grpc.service=as.ApplicationServerService span.kind=client system=grpc

Any ideas?

alexv · April 21, 2020, 10:14pm

I am trying to work with tektelic device as well. I installed all chirpstack servers on a singlr AWS system.Can you share your config?

Uri_Genin · May 7, 2020, 6:02am

I had to reinstall the server using instructions on the site and it worked

alexv · May 9, 2020, 4:09pm

@Uri_Genin

I am trying to get tektelic working but I cant get kona home sensor recognized.I think one of my problems with device-profile questions in UI.can you share what you put for answers to the following questions: The LoRaWAN MAC version supported by the device 1.0.0 or 1.0.1 or 1.0.2 or 1.0.3 or 1.1.0
LoRaWAN Regional Parameters revision A or B
class-b or class-C device
Maximum EIRP supported by the device.

Uri_Genin · May 10, 2020, 6:04am

Hi Alex

I use lorawan version 1.0.1 in the device porfile. It depened I guess on which library your firmware uses. Regional Parameter : A.
We use class A devices only.
Hope it helps

alexv · May 10, 2020, 6:03pm

It does. Thanks for the information

djfromla · May 10, 2020, 6:55pm

I just built a new server with Chirpstack and re-commissioned all of our Tektelic 6-1 sensors. They were reading correctly on the old LoRaServer NS and AS. When I placed them on the new server, I see a lot of activity on the Tektelic Micro and Micro-Lite, but the sensors still say “Last Seen N/A”.

They were working fine with these settings on the LoRaServer:
MAC Version: 1.0.0
Regional Parameters Revision: B
Max EIRP: 0

So should I change it on the Chirpstack server to:
Version 1.0.1
Revision: A

Using: Tektelic Kona Home Sensor / T0004885 RevD

djfromla · May 10, 2020, 6:58pm

Also,

I do not see any join requests from the sensors. I hope I dont have to reset the sensors?

eugenev · May 10, 2020, 7:31pm

Yes, You need to rejoin them.

FYI:
1.0.x versions compatible from top to bottom and differ in additional mac-commands and Class B support.
1.1.x versions has additional security.

djfromla · May 10, 2020, 7:40pm

Oh no, I guess I need to head over to the building and hit the reset button on every sensor.

djfromla · May 12, 2020, 5:55pm

I just got a message from Tektelic:

There are 3 ways to reset sensors and get them to re-initiate their network join procedure:

By sending the Over-The-Air command 0xF00001 on Port 100. This is only doable if the sensors are currently joined to a Network Server.
By using a pin to press the reset button on the front of each the sensor.
By power-cycling the sensor by removing the battery and replacing it.

I still have the old LoraServer running. Is there a way to send a mass download msg to all 60 sensors?

eugenev · May 12, 2020, 6:10pm

try this hint
turn your device profile to ABP on the new chirpstack
copy and paste existing activation data from old one server to the new
turn it back to OTAA

djfromla · May 12, 2020, 6:19pm

I will try this now. Thank you

djfromla · May 12, 2020, 6:51pm

Sorry Eugenev for being a noob at this. I do not see a place to enable ABP, just OTAA.

eugenev · May 12, 2020, 6:53pm

if OTAA unchecked that means the device is ABP

djfromla · May 12, 2020, 6:54pm

Got it, Thank you! I will try again.

djfromla · May 12, 2020, 7:38pm

Seems to work for the first sensor. Time to try another! Awesome! Thank you eugenev

djfromla · May 13, 2020, 1:40am

Worked Great! All sensors are online again on the new server.

djfromla · May 28, 2020, 4:55pm

So good news and bad news. The sensors are online and sending data now, but the uplink data is not correct… when base64 is decoded it comes back garbage.