@jcaron Thanks for the info!

Finally, my problem is Solved : With pygate, no need to register the device EUI, just create one from scratch ! (and edit config.json accordingly) as the doc says

Okay this has answered my question! Looking forward to test the border router functionality.

Fair enough, I did quite a bit of reading on TTN about Gateways, Nodes, Applications, etc... I think once I can muster up some more funds for an actual Gateway; I will convert this to a Node. This PyCom LoPy4 is really a learning experience for me. The idea of using MicroPython is all new to me. Cheers,

@dan Thank you!

@robert-hh that did it! router.us.thethings.network was the key! Nowhere do I see that URL on TTN gateway config, so you really saved my bacon there. Thank you!

hi @Harish-kumar , we released here Lora-Mesh, that I thought it will help you. Well, mesh-network over LoRa, has a specific protocol (Thread), and probably it's not implemented neither in Arduino, nor Multitech. This would work if all 3 devices would be Lopys, the last one (gateway) would be registering itself to TTN as gateway, and forwarding data from the first Lora (sensor), thru the second one (the repeater, which does this automatically, being a Mesh node - router role).

Thanks @jmarcelino. Thus the encryption part is not something you get for free... At this point, would it still make sense to prefer LoRaWAN over LoRa-MAC for a standalone network?

@mj SInce the for string for pack contains only two fields, it must be written as: _LORA_PKG_FORMAT = "Bf" pkg = struct.pack(_LORA_PKG_FORMAT, DEVICE_ID, D) But besides that, the receiver must contains a lora_sock.recv(64) call, in order to get something. Please have a look at the simple examples in the documentation on how the code structure has to be set up.

@seb Thank you for your reply, YES true that compute module does not have wifi or BT , so only we go with UART connection, and i have connected the fipy and RPI compute module via UART. But how shall ssh to RPI compute module and access the RPI file structure. After the serial connection now i want to send data within the RPI compute module to server. How to do this?? Thank You

@jmarcelino said in US915 OTAA - Cannot communicate with packet forwarder: LoRaWAN network server Hi @jmarcelino. Thanks for your help. I'm using the brocaar's one network server https://www.loraserver.io/ I have copied below the docker-compose config file content: version: "2" services: app: build: . expose: - "8090" ports: - "8090:8090" volumes: - .:/app depends_on: - gatewaybridge - loraserver - appserver - postgres - mosquitto - redis postgres: image: library/postgres:10.2 volumes: - ./db/pgdata:/pgdata ports: - "54322:5432" environment: - POSTGRES_PASSWORD=loraserver - POSTGRES_USER=loraserver - POSTGRES_DB=loraserver - PGDATA=/pgdata command: -p 5432 elasticsearch: image: elasticsearch:2.4 container_name: elasticsearch environment: - cluster.name=docker-cluster - bootstrap.memory_lock=true - "ES_JAVA_OPTS=-Xms512m -Xmx512m" ulimits: memlock: soft: -1 hard: -1 mem_limit: 1g volumes: - esdata1:/usr/share/elasticsearch/data ports: - 9200:9200 # # STARTS BROCAAR SERVERS # loraserver: image: loraserver/loraserver environment: - DB_AUTOMIGRATE=true - LOG_NODE_FRAMES=true - NET_ID=010203 - BAND=US_902_928 - REDIS_URL=redis://redis:6379 - GW_MQTT_SERVER=tcp://mosquitto:1883 - GW_SERVER_JWT_SECRET=verysecret - POSTGRES_DSN=postgres://loraserver_ns:loraserver_ns@postgresql_ns/loraserver_ns?sslmode=disable - JS_SERVER=http://appserver:8003 appserver: image: loraserver/lora-app-server ports: - 8080:8080 environment: - DB_AUTOMIGRATE=true - REDIS_URL=redis://redis:6379 - POSTGRES_DSN=postgres://loraserver_as:loraserver_as@postgresql_as/loraserver_as?sslmode=disable - MQTT_SERVER=tcp://mosquitto:1883 - JWT_SECRET=verysecret - HTTP_TLS_CERT=/etc/lora-app-server/certs/http.pem - HTTP_TLS_KEY=/etc/lora-app-server/certs/http-key.pem - AS_PUBLIC_SERVER=appserver:8001 gatewaybridge: ports: - 1700:1700/udp image: loraserver/lora-gateway-bridge environment: - MQTT_SERVER=tcp://mosquitto:1883 postgresql_ns: image: postgres:9.6-alpine ports: - 5432 environment: - POSTGRES_PASSWORD=loraserver_ns - POSTGRES_USER=loraserver_ns - POSTGRES_DB=loraserver_ns postgresql_as: image: postgres:9.6-alpine ports: - 5432 environment: - POSTGRES_PASSWORD=loraserver_as - POSTGRES_USER=loraserver_as - POSTGRES_DB=loraserver_as redis: ports: - 6379 image: redis:4-alpine mosquitto: ports: - 1883:1883 image: eclipse-mosquitto volumes: esdata1: driver: local Then, once the docker servers are running I config the lorawan platform through the web admin ui like this: Device profile Service profile Gateway configuration Not sure if that's enough @jmarcelino . Let me know if you need some extra data. Thanks!

@juan-narvaezb95 1.17.0.b1 see https://forum.pycom.io/topic/2734/new-firmware-release-v1-17-0-b1-completely-new-lte-class/39

Hello @jmarcelino I have currently set up a nano gateway and several nodes (with LoPy) on the 868MHz using the EU868. From what I understand, AS923 is supposed to be used, but there are no strict regulations on the frequencies around 868MHz as of today. It would be better to work on the 923MHz frequency, thus I am currently wondering if anyone has gotten any success on 923MHz, or AS923. When I tried to replicate the EU868 to the AS923, I couldn't get the TTN to display any values other than a random value to pop up only once. I was wondering if anyone with success or failures can share their experience.

I'm trying to use nano-gateway with loraserver.io but I can not downstream messages just upstream. Can you share if you had the same problem?

@jmarcelino Any update on this? or suggestion?