Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
This relates to AWS IoT Core.I'm running into a situation where the bridge-workaround [0] is not optimal any longer.The next step is to look at AWS IoT custom authorizers, but it would be helpful to know whether there are plans from Meraki to support...
Documentation: https://developer.cisco.com/meraki/api-latest/#!generate-device-camera-snapshotEndpoint: /devices/{serial}/camera/generateSnapshotI have been trying to build a flow around MQTT events and requesting snapshots.via the API.What troubles ...
@noname11 unfortunately not. The workaround is to delay requests by a sufficient amount of time. I'm intently vague on a value as it's by trial-and-error.
I have gone down the path of using an AWS IoT Custom Authorizer, and I'm 99% of the way there. The last thing I'm unable do via the Meraki console is to specify an ALPN [0] value as required by AWS IoT Custom Authorizer protocols. [1], [2], [3].The f...
OK, I'm not sure I'm on the same page.I'm using the v1 API, calling /devices/:device-id/camera/generateSnapshot, which returns a JSON response indicating the URL from where to fetch the snapshot.The URL looks like https://spn2.meraki.com/stream/jpeg/...
