-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Fan modes button error when HVAC is in Dry Mode #987
Comments
Hi! There is not much that I can do "by default" because I guess that some types of climate entities handle that differently. But you can add a simple template, in the editor, go to Styling options > Custom styles / Templates then add this to show it only when needed: /* Replace "1" if needed to match your sub-button and replace "climate.your_entity" */
.bubble-sub-button-1 {
display: ${hass.states['climate.your_entity'].attributes.hvac_mode !== 'dry' ? '' : 'none'} !important;
} This should works as you want 🙂 |
Thanks for the response. This does not fix it though.
This does disable the button, but only if the fan_modes button does not exist at all. I made a gif to demo it. Also worth noting that home assistant really does not like this. I sometimes get kicked out of editor mode and returned to the entry page, or the entire panel stops being displayed. To get it working again, I have to change the HVAC mode back to cool and refresh the page. The first card:
2nd card:
3rd card is the mushroom climate card, just for reference. |
From the home assistant log:
|
I notice it has been marked as wontfix. I guess I had wrongly assumed this was a simple missing null check based on the log. I would love to understand more about why this is something that is non-trivial to fix. I had thought Sensibo was one of the biggest smart HVAC services. The climate documentation explicitly states that both fan_mode and fan_modes can be None, so I don't think there is any unusual behaviour going on here. |
You're right, I will have to take a look at this 👍 |
This should be fixed in the next release! |
- [x] Fan modes button error when HVAC is in Dry Mode #987 - [x] Enhancement: Add Box-Shadow Customization to Bubble Card. Fix added for PR #1009 by @flobiwankenobi - [x] Better color handling for lights, now if the light doesn’t supports RGB it will take the accent color instead like the default Home Assistant behavior. #692 - [x] Templating .bubble-name is now instant. #975 - [x] Fixed an issue where some entity_picture url were not displayed. - [x] New pop-up trigger system based on the same conditional system that Home Assistant use. Not to be confused with the visibility conditions. Note: This is NOT a breaking change, if you previously added a trigger in a pop-up, it will still works, but the editor will not display it anymore and it will be visible in YAML mode only. Then if you decide to use the new system, it will be used instead of your previous trigger. This new feature is based on the code from @MrBearPresident, so thanks again to him for this great new possibility! #332
This issue should be fixed now! 🤞 |
I appreciate you looking at this, but unfortunately the error has just changed location.
|
Could you try the latest bèta and report back if this solves your issue? |
No need, I haven't worked on this issue in the lastest beta. But I will do my best for 2025 👌 |
I've worked on this new issue but I'm still unable to try this use case. Could you try this version? You need to remove Bubble Card from HACS first, then install it with the "Without HACS" method. Once installed, clear your cache then check in the editor if you see v2.3.4. 🤞 |
Still shows an error I'm afraid.
|
Thank you for your answer! I will try again! 🫠 |
Steps:
I'm using Sensibo for my climate integration. When I inspect the climate entity, the attribute 'fan_mode' gets set to 'null' when the device is in dry mode. (Fan modes are not adjustable in that mode)
Changing the HVAC mode to Cool or Heat allows the card to work again.
Ideally the fan sub-button would just disappear when it is not a valid option.
The text was updated successfully, but these errors were encountered: