@floriandotorg i think that’s a totally different issue to the one I’ve flagged above.
I believe that the Online and Offline system events are special, and that their usage via either the Blynk.logEvent or HTTPS API are blocked for good reason.
However, it does raise another issue that @Dmitriy might be able to help with…
Blynk Legacy had the ability to send server-side notifications when a device dropped off the radar (went offline).
At the moment, it’s not possible to enable the Notification tab on the offline system event. Is it possible change this please, so that a behaviour similar to Blynk Legacy can be enabled?
Having the ability to send a notification when the online event is triggered may also be useful, but you can workaround this by triggering a user defined event when a device first connects, but that isn’t an option for offline notifications, which have to come from the server.
Also, this isn’t something that can be done with automations either, as online/offline aren’t selectable in a device state automation.
Pete.