Everyware GreenEdge Frequently Asked Questions
Revision History
Revision | Date | Notes |
---|---|---|
1.0 | 30/05/2024 | First draft |
1.1 | 07/06/2024 | URL fixes |
AWS IoT Greengrass v2 troubleshooting
Q: How can I ensure that the connection and provisioning on AWS IoT Greengrass is successful?
A: One way to check that the provisioning went well is to check the ESF log. A message like this will appear
2024-04-29T13:22:08.480Z [INFO] (AwsEventLoop 4) com.aws.greengrass.mqttclient.AwsIotMqtt5Client: Successfully connected to AWS IoT Core. {clientId=XXXXXXXXXX, sessionPresent=false}
Q: Greengrass fails to connect to AWS IoT Core : how can I verify and recover from misconfigured data endpoints?
A: Check the correctness of the data endpoints. Using the AWS CLI or CloudShell, execute the AWS describe-endpoint commands already used for the user onboarding to find the AWS IoT data plane endpoint and the AWS IoT Credential Endpoint.
In Everyware Cloud edit the provisioning request for the device. In Additional Configuration find the properties aws.iot.data.endpoint and aws.iot.credentials.endpoint of the configuration com.eurotech.framework.addons.ztp.greengrass.GreengrassZTP and compare them to the previous one.
If there are differences you have two options:
- Contact the Eurotech customer support and provide them the above information.
Or
- Modify the endpoints in the EC Provisioning Template:
- Access the Everyware Cloud REST API, check the documentation REST API on how to use it.
- Authenticate:
- GET the token with
/authentication/user
. - Use it to authenticate in “Authorize”.
- GET the token with
- In the Bulk Provisioning Request section:
- GET the provided service: Service Id (example GGZTP) and Group Id (example Frankfurt_eu-central-1) in
/scopeId/provisionTemplates/default/providedServices
- Use the previous information in
provisionTemplates/default/providedServices/serviceId/groupId
to correct and POST the new endpoints values.
- GET the provided service: Service Id (example GGZTP) and Group Id (example Frankfurt_eu-central-1) in
Pricing questions
Q: Where can I find the pricing guide?
A: The pricing guide is published here
Q: I want to deploy 15 ReliaGATE 10-14 GE, which will consume 150 tokens. How is the final cost calculated?
A: 100 tokens are included in the Small tier. The additional 50 tokens will be billed monthly, so the final price will be : 12 x 50 x token price + Small tier price.
Q: I have seasonalities in my deployment, using my 20 ReliaGATE 10-14 for 3 months each year. How is the final cost calculated?
A: The ReliaGATE 10-14 GE that are not included in the small offer will be billed based on activation per calendar month. So, 10 devices are billed monthly. Let us assume that the devices become active on September 7th until November 30th. This counts as 3 (months) x 10 (devices) x 10 (token/device) = 300 additional tokens
Q: How I can move from, say, Small tier to Medium when I'm ready to grow?
A: Go to AWS marketplace, subscribe to the Medium tier, we'll take care of the pro-rated credit of the small tier. More information available on AWS marketplace documentation on contract upgrades
Q: How can I move from a standard tier to a private offer (e.g. I need more than 5000 tokens)?
A: Contact our Sales team, you will receive a private offer in your AWS account. For further information please check the AWS video explaining how to receive and accept a private offer