When accessing the next alarm sensor on a Samsung device that has enabled the sleep mode schema, the companion app picks the sleep mode start time rather than the actual clock alarm.
Anyone also having this problem?
1 Like
Anyone who uses a Samsung app with the next alarm sensor will have the issue. Samsung apps are known to misbehave here .
It was not a problem until one of the family members discovered the sleep mode āfeatureā recently.
Poor design not to use a separate counter for the sleep mode and re-use the alarm counter 
This time I could mitigate with a time condition in the automation and thereby ignore the sleep mode next_alarm start time.
yea samsung and xiaomi apps are particularly bad about this, some of their apps even set alarms for the calendar.
1 Like
My long term solution has been to check the source of the alarm, and use that in a template sensor
sensor.erikas_mobil_next_alarm is the HA Companion sensor used as an input
% if is_state_attr(āsensor.erikas_mobil_next_alarmā,āPackageā,ācom.google.android.deskclockā) %}