You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of problem:
I have an automation that notifies me via persistent_notification of new devices tracked. The iOS 2.0 beta app is currently using a long UDID for the device_tracker until backend changes are merged in 0.93 I guess. So the message is:
New Device Tracked: None (device_tracker.7b50aa345032439dacb17b31c3c08acb)
But this goes outside of the card width instead of wrapping to a second line.
Furthermore, you cannot seem to select this text and copy contents of a persistent_notification which seems like a super weird thing to restrict.
I had to open the Chrome inspector just to be able to copy the device_tracker entity id here, and most regular users are not going to know how to do that.
Possibly related to this issue with Home Assistant Cloud settings I reported a while back #2982. I am guessing it's a problem with all the cards then?
The text was updated successfully, but these errors were encountered:
Home Assistant release with the issue:
0.92.2
UI (States or Lovelace UI?):
Lovelace
Description of problem:
I have an automation that notifies me via persistent_notification of new devices tracked. The iOS 2.0 beta app is currently using a long UDID for the
device_tracker
until backend changes are merged in 0.93 I guess. So the message is:New Device Tracked: None (device_tracker.7b50aa345032439dacb17b31c3c08acb)
But this goes outside of the card width instead of wrapping to a second line.
Furthermore, you cannot seem to select this text and copy contents of a persistent_notification which seems like a super weird thing to restrict.
I had to open the Chrome inspector just to be able to copy the
device_tracker
entity id here, and most regular users are not going to know how to do that.Possibly related to this issue with Home Assistant Cloud settings I reported a while back #2982. I am guessing it's a problem with all the cards then?
The text was updated successfully, but these errors were encountered: