@Dmitriy I’ve been doing a bit more testing on events and notifications and discovered an issue.
If you set-up an event, but don’t enable notifications for that event, then in C++ you can do this:
Blynk.logEvent("over_temperature_alert", String("Hello World"));
and it works fine, the custom description (“Hello World”) appears below the event name in the timeline…
But if you use the HTTPS API to do the same thing…
blynk.cloud/external/api/logEvent?token=REDACTED&code=over_temperature_alert&description=Hello%20World
then the API returns an error:
{"error":{"message":"Notifications are disabled"}}
So, the HTTPS API rejects the command because that event doesn’t have a notification enabled, but the same event is logged correctly when you use C++
The simple workaround is to enable notifications for the event but not add any recipients, but is it possible to remove the error checking that is preventing the HTTPS API from working in the same way as when its done via C++ please?
Pete.