-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
card_binary_sensor and card_binary_sensor_alert not displayed after HA Core 2023-11 #1398
Comments
setting ulm_show_last_changed to false solved the issue |
For me as well both mentioned cards are not working afer the update from 1.3.6 to 1.3.7 of Minimalist. But for me no error is visible only blank card. I tried as @wokkeltje13 suggested and changed ulm_show_last_changed to false but but still same. Looks like a problem on this cards in the new relase code for one of my cards:
below screenshot how it look like: |
Same issue as @wokkeltje13 after updating UI Lovelace Minimalist to Version 1.3.7. |
I was also having the same issue as @wokkeltje13. I did set ulm_show_last_changed to false and it did get the card working again but I noticed ulm_card_binary_sensor_name was no longer working. What ended up fixing both my issues was the following: Change: Looks like the documentation for the binary sensor card needs to be updated https://ui-lovelace-minimalist.github.io/UI/usage/cards/card_binary_sensor/#description |
I'm still on 10.5 core not sure if this is relevant for me why it is not working. It stopped working for me after 1.3.7 update |
Can't find any traces of |
Sorry for not being clear. Didn't mean to imply that Updating the card with Here is the code i'm using incase it helps.
While writing this I realized I'm using the binary_sensor_alert card and was referencing the binary_sensor card. Apologies there. |
But it's not working as it is supposed, to cause |
I found the source of the problem Lines 80 to 94 in 3438d15
|
After I updated to core 11.0 it started working same as @wokkeltje13 mentioned when |
What will be the breaking change? Currently it is already broken. |
Can also confirm same issues noted by @wokkeltje13 after updating to 1.3.7 & core 11.0 - cards on |
Any idea how and when this issue can be solved without a rollback? |
Same here. Would appreciate a fix. |
Same issue, have applied, workaround as below, but now missing any value for last_changed, so will look forward to the fix 👍 ulm_show_last_alert_changed: true
ulm_show_last_changed: false
ulm_card_binary_sensor_alert: true |
Should be fixed with release https://github.com/UI-Lovelace-Minimalist/UI/releases/tag/v1.3.8 Note the breaking change to the card configs to apply the fix 😉 |
Applied the fix. Lgtm. Thanks! |
Tnx, fixed the issue |
Thanks for this fix! I just hit this issue after the upgrade, but glad I could find the fix here |
This issue also seems to affect generic cards when you have an entity with a device class of timestamp as well, e.g. the in-built uptime sensor. I've done some debugging and it looks like it's an issue with the translation code with the |
After 1.3.7 most of the issues are resolved since the HA 2023-1 upgrade but I still have issues with the binary sensor cards
This is my yaml code
The text was updated successfully, but these errors were encountered: