Chronometer fails if parameter 'when' is given a float

[harmpter]

Home Assistant Android app version(s):
2025.1.2

Android version(s):
14

Device model(s):
Google Pixel 5

Home Assistant version:
2025.1.4

Last working Home Assistant release (if known):

Description of problem, include YAML if issue is related to notifications:
Chronometer fails if parameter when: is given a float. The notification still posts, but without chronometer.

action: notify.mobile_app_dd
data:
  message: test
  data:
    chronometer: true
    when: "{{ now()|as_timestamp }}"

Companion App Logs:

Screenshot or video of problem:

Additional information:
Probably irrelevant, but a float ending in .0 like 1738267025.0 seems to pass as an integer and results in a working chronometer timeout.

I hope this issue can help fill a to-do list with many many checked items and make someone feel very productive 🚀😄

[dshokouhi]

hmm we actually expect an integer value here so maybe we need to update the docs

https://github.com/home-assistant/android/blob/master/app/src/main/java/io/homeassistant/companion/android/notifications/MessagingManager.kt#L1023

if you check the log you will see the error message that we catch

https://github.com/home-assistant/android/blob/master/app/src/main/java/io/homeassistant/companion/android/notifications/MessagingManager.kt#L1042

[harmpter]

I think rather than updating the docs, casting to an integer would make more sense and be way more convenient for the user. Or is that not as easy as I think? It would make sense because now().timestamp() returns a float and that's what is most likely used there.

EDIT: I checked the logs but did not see it. But I'm not too worried, I'm only appending the logs in case they are useful to you.

01-30 21:36:05.519 29083 14147 W FirebaseMessaging: Unable to log event: analytics library is missing
01-30 21:36:05.519 29083 14147 D FCMService: From: <<>>
01-30 21:36:05.520 29083 29083 D MessagingService: Creating notification with following data: {when=1738269365.193415, webhook_id=<<>>, message=test, chronometer=true, server_id=3}
01-30 21:36:05.523 29083 29083 D MessagingService: Show notification with tag "null" and id "-1192389361"
01-30 21:36:08.282 29083 29083 I ImeTracker: io.homeassistant.companion.android:a683856e: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT
01-30 21:36:09.476 29083 10064 D LogcatReader: Read logcat for pid 29083

[dshokouhi]

sorry a long is actually expected here which is why our conversion reverts to 0 if it is unable to convert to a long value at that point we dont set up the chronometer at all: https://developer.android.com/reference/androidx/core/app/NotificationCompat.Builder?hl=en#setWhen(long)

you should be able to cast to int in your template to fix this today, personally i use {{ as_timestamp(now()) | int }} in my automations that use a chronometer

[harmpter]

Okay this makes sense, and thank you for the fix, that's what I'm using too. I was just thinking it could make sense to have it accept a float too. If it isn't the easy quick fix as I imagined then we can of course close this issue. And thanks for your fast replies :))