Tasker, Automate - Sleep as Android

Sleep tracking started …​ Sleep tracking stopped …​ Sleep tracking paused …​ Sleep tracking resumed …​ Snooze (alarm) the user has snoozed a ringing alarm Bedtime the bedtime has just occured Alarm started …​ Dismiss (alarm) the user has dismissed a ringing alarm AND solved the CAPTCHA if present. This event will also be fired when alarm has been dismissed while snoozed Snooze canceled alarm has been dismissed while snoozed ~REM the REM phase has been detected. More on REM phase detection here. Audio recognition Sleep as Android has detected one of the supported sounds: snoring, talk, coughing, laughter, baby crying. The maximum frequency of the event is once per 30s. Audio recognition has to be active for this event to work. Anti-Snoring Sleep as Android has detected snoring and executed an anti-snoring action (vibration or tongue click or both). Anti-snoring has to be active for this event to work. Smart period fires 45 minutes before smart period starts (to gather data for the smart period)

This is a companion discussion topic for the original entry at https://docs.sleep.urbandroid.org//services/tasker_automate.html

Instructions for Automate are missing, link is broken.

Tasker can read heart rate data and publish it as required. Would it be possible for SAA to accept a heart rate action trigger to incorporate into the sleep tracking timeline, without blocking sonar, sleep phaser or accelerometer readings?

I would like to trigger a Tasker action on some alarms but not on others, or better yet, trigger different actions for different alarms. Would it be possible to e.g. send the alarm name along with the trigger and check it in Tasker or at least have a checkbox in the individual alarm settings to enable or disable Tasker triggering?

On the automation page: https://docs.sleep.urbandroid.org/services/automation.html
It says that the event “alarm_snooze_canceled” passes on two variables, one of which is the “label” of the alarm. This should let you read that label in tasker. However I can’t get Tasker to see that parameter. It’s located in the Tasker docs here: https://tasker.joaoapps.com/userguide_summary.html#eventcontext.html

Has anyone gotten Tasker to see the event parameters (passed as %evtprm) in Tasker?