- Mais recentes
- Mais votos
- Mais comentários
Thanks for explaining your use case.
The mqtt settings you mentioned in the post seem find to me. Just to confirm one thing, did you also pass in the device thing name as client ID?
Also what error messages do you get?
Thanks,
Hui
Hi omki12,
Correct me if I understand wrong. You have 2 devices in your setup. One is a windows machine running Greengrass (core device). The core device is able to connect to AWS IoT successfully. The second device is set up to connect to the core device, but it failed to.
I have a few questions based on this assumption.
- Were you able to add the second device to the Greengrass group and successfully deploy the group to the core device?
- Can you provide the logs from Greengrass core device? You can find the Greengrass logs here https://docs.aws.amazon.com/greengrass/latest/developerguide/greengrass-logs-overview.html#gg-logs-local
- How did you initiate the connection from the second device to core device? Can you provide the output of it? Have you tried to use device SDK and what version did you use?
- I'm assuming you're running Greengrass in a docker container, because windows is not currently supported. Which version of Greengrass are you running?
Hi there,
thank you for your reply.
- I added the second device in GG group and deployed the group successfully.
- If I use AWS IoT device SDK , I am able to connect to core device (GG).
I tested the GG using basic Discovery Example provided by amazon: https://github.com/aws/aws-iot-device-sdk-python/blob/master/samples/greengrass/basicDiscovery.py
But the issue is I cannot use AWS IoT Device sdk on the actual device. let's suppose I am using the MQTT-paho library on actual device. is it possible to connect to AWS GG using an mqtt-paho library, given all the certificates and topic is valid as mentioned in the GG group? - yes, I am using docker on windows and using the latest version of Greengrass. GG is up and running. tested using "Basic Discovery Example" provided by amazon.
Maybe something like
https://vixtera.com/software-appliance/
will translate your payloads to something that AWS GG can understand.
yes.. that was the issue. I was passing a random client id.
instead, I passed "Device name" as client id and it worked.
thank you.. :D
Conteúdo relevante
- AWS OFICIALAtualizada há 3 anos
- AWS OFICIALAtualizada há 2 meses
- AWS OFICIALAtualizada há 3 anos
- AWS OFICIALAtualizada há 2 anos