LoRa gateways are now able to communicate (using the LoRa Gateway Bridge) with the Cloud IoT Core service (using the MQTT bridge). This can be seen as an alternative to running your own MQTT broker (e.g. Mosquitto). Apart from scalability, this also makes it possible to manage the gateway authentication to the network using the web-based GCP Cloud IoT console.
Cloud Pub/Sub
LoRa Server is able to use Cloud Pub/Sub to communicate with your gateways (though the Cloud IoT Core) E.g.:
Also LoRa App Server is able to forward data to a Pub/Sub topic, as an alternative to a MQTT broker. This means that device data can directly be used with other GCP services.
Thanks for this GCP integration tutorials. However in terms of IoT end to end product this setup looks bit clumsy. Is there any way we can use GCP IoT core to handle LORWAN end device? end devices can be bound to gateway and then data can be published on pub/sub directly per device ? can that possible ?
I am trying to setup LORAWAN end device on google-cloud-iot under registry and devices which is bound to gateway.
LoRaWAN specifies security keys: NwkSKey, AppSKey and AppKey. All keys have a length of 128 bits. however google-cloud-iot requires the following keys,
Create a device in registry XXXXXXXX. Public key format RS256 ES256 RS256_X509 ES256_X509
has anyone used LORAWAN end device directly with google-cloud-iot ? How can we setup LORAWAN end device bound to Gateway supporting LORAWAN ? We are using LorixOne as Gateway.
I am just curious here. How much could expect the costs to be? Say for example with 1 gateway and like 22 devices mostly “pubbing” like 10 times a day.
Great News, However i was wondering if a user is hosting with google, on a managed cloud hosting provider, does that mean he can too bear the fruits of this integration?