unsafeHTML() called with a non-string value

[Mariusthvdb]

Checklist

• I updated the card to the latest version available
• I cleared the cache of my browser

Describe the bug
A clear and concise description of what the bug is.

after the latest update to 400 dev5 (might have been earlier in the dev version, but didnt notice) a button using:

custom_fields:
  notification: >
    [[[ return Math.round(states['sensor.pond_buiten_sensor_temperature'].state); ]]]

throws

and doesnt show.

Commenting that makes the card appear

Version of the card
Version:
4.0.0.dev-5

To Reproduce
This is the configuration I used:

on another card I just found the same things happens when using

 custom_fields:
   notification: >
     [[[ return entity.attributes.current_position; ]]]

Screenshots
If applicable, add screenshots to help explain your problem.

no card:

without the notification field:

showing a default state value.

Expected behavior
A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

• Browser [e.g. chrome, safari] Any
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[RomRider]

Can you try with [[[ return Math.round(states['sensor.pond_buiten_sensor_temperature'].state).toString(); ]]] as it says it needs to be a string ?

[RomRider]

Ok, I think I found the bug. Odd it didn't trigger before as this code is there forever...

[Mariusthvdb]

yes, its odd indeed, as my butto has been there for ever too ;-)

btw, can this be caused by the same thing?:

got nowhere to look without anything further

[github-actions]

🎉 This issue has been resolved in version 4.0.0-dev.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[RomRider]

btw, can this be caused by the same thing?:

Probably, but I don't know for sure

[Mariusthvdb]

so I have a template error, that narrows it down....
just odd there is no originator here in the error

btw the other one was also fixed by using:

custom_fields:
  notification: >
    [[[ return entity.attributes.current_position.toString(); ]]]

but I dont get it, why do we need strings in those notifications? they are numbers and we need numbers...

[Mariusthvdb]

I found the template_error in connection.js....

it's not you ;-)
it was me in a card-mod-theme template. sorry about that.

[Mariusthvdb]

so still seeing this same html errors, but now also on:

name: 1

where indeed the name is the number of a spot. Have quite a few of those, and for ages, so he new update frustrates that now somehow.

I can change it into

name: '1'

which makes it a string. silly really, otoh it does make sense somewhat ?

this is still ok:

        name: Terrace - 2

as that obviously isnt a number..

[RomRider]

I'll look further into that... very strange :)

[RomRider]

4.0.0-dev7 will fix that, please let me know if you see some other strange behaviors because of the fix.

[github-actions]

🎉 This issue has been resolved in version 4.0.0-dev.7 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[Mariusthvdb]

just to conform all issues above are fixed in b7:
no more need for:

• toString() on those notification custom fields
• quotes around the numbers on name

so far so good!

[Mariusthvdb]

believe we can safely close this? I havent seen it any more since that fix..

[RomRider]

It's going to close automatically on stable release, no worries

[github-actions]

🎉 This issue has been resolved in version 4.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀