-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LoraGW Bridge #9
Comments
I figured it out, for anyone else looking into the same issue, here is what needs to be done: The script will not create in this case files: So first you need to copy the files to place from /opt/loragw/dev/packet_forwarder/mp_pkt_fwd Edit the file local_conf.json first:
} Also edit global_conf.json and change ( I assume this can be just added in local conf without editing global conf ) :
Ok now you need to install lora-gw-bridge on rPi (RPI zero W uses the armhf versions of packages, sadly for same reason the latest is 2.5.1 :-/ ) sudo wget https://artifacts.loraserver.io/downloads/lora-gateway-bridge/lora-gateway-bridge_2.5.1_armhf.deb sudo dpkg -i lora-gateway-bridge_2.5.1_armhf.deb Edit /etc/lora-gateway-bridge/lora-gateway-bridge.toml Edit your MQTT server, And there you go, secured connection to MQTT server, and GW is running all on rPI zero :D Don't forget to edit logrotate /etc/logrotate.d/lora-gateway-bridge /var/log/lora-gateway-bridge/lora-gateway-bridge.log { |
I'm trying to follow this deployment guide but I'm stuck a little, more confused though.
From what I gathered this deployment script does not count with using own Loara Server and does not install lora gateway bridge on the rpi, which would be more secure to let it talk to mqtt server directly ( with ssl and pass ).
Own installed loraserver will not give you: serv_gw_id and serv_gw_key
The text was updated successfully, but these errors were encountered: