That’s what I thought. I’m pretty new to intents, and have pretty limited experience with this.
I found that page before, and tried just about every combination I could think of to no avail. Also, I don’t know where to find any logs to check to see if I’m even close.
I found a bunch of different references to com.google.android.deskclock, when referring to the Next Alarm sensor. Also when reading this I’m not sure if I should be sending AlarmClock.ACTION_SET_ALARM?
This is what I have that starts the SleepAsAndroid tracking.
I know I would need to specify the hours and minutes. I believe that would be set using group option under channel, but I’m lost as to what to put under the title, and the channel to interact with the base android alarm clock.
The first time I did it through Tasker, I believe it asked me if I wanted to set the alarm using the google app, or the SleepAsAndroid app.
I think I’m still doing something wrong. I am sending this, with nothing. The message is received by the phone (I can see it in the Notification History).
Could you help me remove the old alarms. I have a node red flow that sets my alarm from my google calendar work schedule. I would like to be able to remove the old alarm and set a new one if my schedule changes.
Thank you so much for your post dshokouhi you (and this link) have got me this far. Do you think you might be able to help me get the rest of the way?
I was able to add a new alarm as per the code in you previous post. But I am not able to enable/disable an alarm in Sleep as Android.
I have tested this code (and some other alternatives) but it isnt working
I get message: Not able to send activityintent. Please check format of command. Or something like that, I get the message in swedish
Hi, I was happily using this solution to set my daily alarm, but I think Android 13 broke it… Now I just see the “command_activity” notification as if it was a normal notification.
I tried the map example in documentation and it still works, so I think there’s something specific with this intent. Has anyone else experienced this issue with Android 13?