Events
This tutorial will help you with creating Events in Device Templates
Last updated
Was this helpful?
This tutorial will help you with creating Events in Device Templates
Last updated
Was this helpful?
Events are used to track, log, and work with important events that happen on the device.
Events are also used for notifications which can be sent over email, delivered as push notifications to the user's smartphone, or sent as an SMS.
Events are pre-configured in Blynk.Console and can be triggered with a Events Firmware API from the device or using Events HTTP API.
Examples of an Event:
Log a moment when a temperature reaches a certain threshold and send a notification to selected users
Track the total working hours of the device. If it approaches or goes beyond a maximum value, you would need to notify technical support so that they can replace the device or provide warranty service
There are three types of Events in Blynk:
System Events: Default Blynk platform events, like "OTA Update"
Custom Events: Events you can create and configure for your needs
Content Events: Informative events that are shown separately in the app
You can't delete the system events or edit them.
This is a system event to track firmware updates. It can't be configured.
These are Events you can configure based on what your device does. Read these articles to start logging events and sending notifications:
Go to Developer Zone -> My Templates -> Select a template -> Open the "Events & Notifications" tab.
Click Edit Template
Click + Create Event
Name the first event with the name Hello
Click Create (the event will appear in the Events tab list)
Repeat the previous step for the second event with the name Error
Click Save to save and apply the changes made (select Update active device this time)
Note that each event hasEVENT_CODE. This event code will be used in firmware API or HTTPS API
Create a new Event named High temperature with code high_temp
Use the Blynk.logEvent(event_code) firmware API command to trigger a new event:
When this code works, an Event will be logged and the system will act accordingly to the Event setup (render on the timeline, send notifications, etc.)
Don't log an event too many times to avoid hitting daily limits. You can use timers or flags to mark the already-sent events. Check this article on how to avoid spamming the server with events
The current limit is 100 events per device per day. This limit could be increased for business clients to fit their needs.
You can change the description of the event when it's rendered on the timeline in Blynk.Console and in Blynk.Apps. For example, you can include the current data
Make sure you enabled Timeline recording in the Event Settings to see the result in the apps
To log an event via GET request:
To add a custom description to the event, use this GET request
Example:
You can test the Event creation by sending it from Device using Blynk.Edgent firmware API, or with REST API.
Blynk.logEvent("event_code", "optional message");
For this tutorial, you would need to use hello as a name. Here is a pseudo-code:
Optionally, you can send a custom description of the event. This description will be rendered on Device Timeline.
Navigate to the Device
Click on its name
Open the Device Info tab
Find Auth Token there and click on the icon to copy it to the clipboard
Now make an HTTP request with the tools you use for that. Make sure to change the AuthToken to the one you copied in the previous step.
You can even use your browser for that. Just put it in the URL field and press Enter.
Repeat the same with code=error
First of all, check Device Timeline by going to Device -> Timeline tab
You should see 2 events on the timeline! If you set up notifications, they should have been delivered as well.
You can send only 100 events per device per day (Adjustable in Business Plan)
When the limit is reached you'll see the notification on the UI in the Device Timeline section
The maximum description length for the event is 300 characters
