Today, for the second time after the update, it happened that the custom alarm set to 06:40 ringed 10 minute later, as it was postponed. This time, I awaked by myself about 15-20 minute ahead the alarm time and I’m pretty sure I didn’t touch any button. DND was set from 22:30 to 07:30.

@Thibault-B. said in [Question] No stupid questions - ask anything here: Can we get current ZoneSense zone information? I have not found the key of such data. It’s not mentioned in documentation, but editor’s autocomplete shows there’s /Fusion/Ddfa input resource. I’m not sure how that value maps to zones. I struggle to make the “PREV INT” data slightly bigger (not as big as current rest/int data - which is sp-d-s -). “PREV INT” data is currently sp-d-xs for which I tried to override font size, rescale. Note that on simulator it might looks fine but not on the watch (can be bigger but then uses a default font which includes big spaces between numbers, etc). Watch has only a predefined set of font sizes (unless there’s been some improvements to font support). For numbers you should use one of the sp-d- CSS classes, those already cover the available font sizes. Documentation has this somewhat vague sentence: “The older watches do not support every possible font size and thus using the css classes for font sizes (shown below) can generally lead to less errors.” This hints that there might be better font support in some watches, but I don’t know what “older watches” means here. In any case, if you want to support all watches, you’re probably limited to sp-d- classes.