- Newest
- Most votes
- Most comments
Hi,
I see that your custom component running on the core device is unable to receive the latest shadow update. Looking at the policy attached to the certificate, it seems correct to me, as permission for the the iot:GetThingShadow is provided for all resources.
To further investigate the issue, I would need to take a look at the greengrass logs generated pertaining to this specific issue. You can create a technical case using AWS Support console and share us all the logs generated under /greengrass/v2/logs directory[1].
References: [1] https://docs.aws.amazon.com/greengrass/v2/developerguide/monitor-logs.html#access-local-logs
I DID start a tech support question. I also tested further by testing a different core device. That performed the same. I also tested named shadows vs classic shadows. It would appear that the classic shadow syncs but named shadows do not. I think it looks like some kind of bug.
Hi @flycast, Sorry, we couldn`t reporduce the error from our side. Could you provide more logs before the error, especially the greengrass.log? We want to double check if the deployment and sync success. Also, to better reporduce it, could you also provide the OS, nucleus version, and shadow manager version?
I have had a support ticket open for 18 days at AWS now. I will post an "answer" on this thread as I can't fit it all in a comment.
Hi @flycast, Thanks for providing this info, and sorry for taking so long to handle it. It seems like some communication issues happen between the support engineer and our team. Back to this issue, I remember this support ticket. In this ticket, the related teams already follow up and provide some further requests to the support engineer. I believe the support engineer will reach out to you ASAP.
Can I include you in the support ticket somehow? Reading the support ticket it looks like all the communications are being funneled through one first tier support engineer to yourselves (I'm calling you second tier support) and me. There seems to be a few days lag every time that happens. I can't tell if that is because of first tier or second tier support. At any rate I supplied ALL the configurations, code, shadow names in my very first support request on 9/30. I was just asked last Friday 10/14 for the EXACT same information again as if I had never supplied it. Getting frustrated waiting.
As mentioned I have had a support ticket open for 17 or 18 days now and it is getting nowhere slowly. I just did some troubleshooting this morning. I created a named shadow named "Sussing" on the core called "PrecoGG1" and then edited the shadow. No information showed up in the PrecoGG1 greengrass.log file.
I then edited the classic shadow and I do see the following entries showing up:
2022-10-17T13:56:16.017Z [INFO] (pool-2-thread-25) com.aws.greengrass.shadowmanager.sync.strategy.BaseSyncStrategy: sync. Executing sync request. {Type=LocalUpdateSyncRequest, thing name=PrecoGG1, shadow name=} 2022-10-17T13:56:16.071Z [INFO] (pool-2-thread-25) com.aws.greengrass.shadowmanager.ipc.UpdateThingShadowRequestHandler: Successfully updated shadow. {service-name=aws.greengrass.ShadowManager, thing name=PrecoGG1, shadow name=, local-version=2} 2
So we know that the classic shadow is syncing.
I went back and edited the named shadow and nothing showed up in the greengrass.log file at all.
My shadowManager configuration looks like this: Shadow Manager:
{
"reset": [],
"merge": {
"strategy": {
"type": "realTime"
},
"synchronize": {
"coreThing": {
"classic": true
},
"namedShadows": [
"test",
"Sussing"
],
"direction": "betweenDeviceAndCloud"
}
}
}
Relevant content
- Accepted Answerasked 2 years ago
- asked a year ago
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
What shadow are you updating in the cloud, and what specifically are you updating?
How are you checking the shadow on the device? Are you sending multiple requests to getThingShadow, or are you subscribed to shadow changes?
I added answers to your questions above in my post edit.
hey @flycast. We are still looking into this, thanks for your patience.