AlarmClockElapsed sensor state change not processed

[Ayuus]

Hello,

For my Gaggenau Steam Oven (BS474112), the integration creates a sensor AlarmClockElapsed of type enum (Off, Present, Confirmed).
When I set an alarm, and the alarm ends, the sensor state changes from Off to Present, and the oven starts beeping.
So far so good.
However, when I confirm the alarm on the oven, sensor state is not updated. I would expect it to change state to Confirmed, or back to Off.
Only at 3:30 am, when everything is reset (why, I do not know), sensor state switches back to Off.
So in practice, I can use this sensor once a day.

I do not know if this is a gaggenau thing or not.
The integration also creates a sensor number.stoomoven_bsh_common_setting_alarmclock, which changes to 0 after confirmation on the oven (which is too late to warn:-( )
Maybe this could be uses to reset AlarmClockElapsed to Off?

Best regards,
Ronald

[Meatballs1]

I'm guessing the AlarmClockElapsed is an event, and you have events_as_sensors configured?

Events are essentially event driven notifications for the mobile app to display when the alarm has gone off, so don't behave like a proper sensor.

No-one's reversed how to send a 'confirm' response back to the oven (which you would do when you accept/close the notification on your mobile). I dont know if confirming them physically acts the same as via the mobile app, it may be worth trying to see if you confirm it via the normal app if the behaviour stays the same?

I dont have an alarm clock on any of my devices so haven't seen how these react.

[Ayuus]

Confirmation of the alarm clock is done on the device itself.

Strange that the alarm clock on my cooking how works as expected; after confirmation on the device, sensor state goes bak to off. So, either devices Oven/Cooking Hob function differently, or the handling of the events is different. Could the latter be the case?

Yes, events_as_sensors is switched on. Should I switch that off?

[Ayuus]

any news on this?