arm PELION Device Shadow bridge for Google CloudIoT
08/09/2021: updated bridge - better support for unified formatting of notifications/responses
08/08/2021: updated bridge - minor fixes and updates for AWS and Pelion
01/07/2021: updated bridge - minor fixes and dependency updates
08/31/2020: updated bridge - updated dependencies
02/29/2020: updated bridge - fixes for draft mode MQTT (token handling)
02/29/2020: updated bridge - updated for treasuredata support. minor marshalling fixes
02/25/2020: updated bridge - updated internal dependencies. bridge updates (Watson)
02/24/2020: updated bridge - final fixes for draft mode mqtt formatting
02/24/2020: updated bridge - resync with dockerhub
01/22/2020: updated bridge - reverted broken jetty websocket dependency updates
01/17/2020: updated bridge - internal dependencies updated
11/11/2019: updated bridge - internal dependencies updated
10/31/2019: updated bridge - minor udpates and fixes
08/29/2019: updated bridge - minor fixes/enhancements
08/23/2019: updated bridge - minor update for mqtt
08/20/2019: updated bridge - added key Pelion device attribute retrieval prior to twin creation
08/13/2019: updated bridge - webhook fixes
08/12/2019: updated bridge - numerous bugfixes and initial websocket notification callback support
07/25/2019: updated bridge - additional fixes and updates
07/23/2019: updated bridge - PUT content type fixes, TypeDecoder and GC enhancements
Container Bridge Instance Installation:
1). Clone this repo into a Linux instance that supports docker images
2). cd into the cloned repo and run: ./run-reload-bridge.sh
Once the container instance is live, you must configure the bridge and bind it between your mbed Pelion account and your PubSub Service in Google Cloud
1). In Google Cloud, create your project... your project will be named. Save this name
2). Create a PubSub instance in your project - enable the PubSub API.
3). In Google Cloud IAM, create a service account and authentication JSON for project. This will be your "IAM credential JSON"
4). Next go to https://os.mbed.com and create your mbed Account. You can then request a Pelion developer account using the same credentials at https://portal.us-east-1.mbedcloud.com
5). Once your Pelion account is created, you need to "Access Keys" to create a Pelion API Key/Token. Record the Token Value
Now that you have your:
- Google Cloud Project Name. Enter this as your "google_cloud_application_name" value
- Google Cloud Project IAM credential JSON. Enter this as your "google_cloud_auth_json" value
- Pelion API Key/Token generated
Go to: https://[[your containers public IP address]]:8234
- username: "admin" (no quotes)
- password: "admin" (no quotes)
Enter each of application name value, auth json value, and Pelion API Token
- Please press "SAVE" after *each* is entered...
- Once entered, press "Restart" to restart the bridge
Your Pelion bridge should now be configured and operational.
Additionally, a Google Cloud PubSub example has been published here:
- https://github.com/ARMmbed/GoogleCloudConnectorExerciser
This sample provide an example on how, from within Google Cloud, you can read and react to events and telemetry via the bridge.
Bridge source (Apache 2.0 licensed - Enjoy!): https://github.com/ARMmbed/pelion-bridge.git
Copyright 2018. ARM Ltd. All rights reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.