Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Send event notification after successful device/gateway auto-provisioning
See original GitHub issueThis is to extend support to send an empty notification event with content-type as application/vnd.eclipse-hono-device-provisioning-notification once a device or gateway is successfully auto-provisioned. For more information refer to the discussion thread and documentation on device provisioning notification.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Device Provisioning :: Eclipse Hono™
After successfully sending a device provisioning notification, the corresponding device registration is updated with auto-provisioning-notification-sent as ...
Read more >Event notifications for AWS IoT Wireless
Event notifications are published when certain events occur. For example, events are generated when your Sidewalk device is provisioned. Each event causes a ......
Read more >Event Notification Engine | CyberArk Docs
The Event Notification Engine (ENE) sends email notifications about Privileged Access Security solution activities automatically to ...
Read more >TR-069 - Broadband Forum
1: Multicast Download support, 10 AUTONOMOUS. TRANSFER COMPLETE event,. AutonomousTransferComplete method, additional Download fault codes, interoperability ...
Read more >Configure Enrollment Options - VMware Docs
Automatically Select Based on User Group - This option only applies if ... Device Enrolled Successfully - Send an email notification when a ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Currently I am working on documentation. After that we can close this issue.
@kaniyan I think undoing an auto-provisioned device also may have another unwanted side-effect: the benefit of auto-provisioning feature is that devices just start sending new messages without having to register the device first. Say at the time the very first message is sent, the connection to the messaging network in Hono is interrupted. Then the device would get an error. Probably it would try to redeliver the message. In case of MQTT those retries can be pretty “aggressive”, so we may end up creating and removing the device all the time which may increase load on the database of the device registry in use.