Yes, imagine apple or Microsoft request you to read all the new change logs every week they roll an update, as I told you, I love the work, but new features should never overwride settings in previous versions.
I have already fixed the issues, didn’t take long, but for futre upgrades, I thing it would make a better user experience for your code if you kept that in mind. Yo can’t expect all users to read the change log every new weekly update, as well as you can’t expect anyone to read al the terms and conditions of every form they fill online.
Anyway, I mean to say this as a constructive comment, not as a criticism.
As I said, Keep it up! you guys rock for making this Outstanding great card!
Its free and open source work for an enthusiast crowd. There is nothing professional about it. My time is limited and what I spend it on is thankfully entirely my choice.
I’m ready to review your pull request to document the changes better. I will add it to the release notes for 2.0 to make the next person have an easier path than you did. This were a 2.0 release, so a breaking change release, that requires you to read through the changelog and documentation before you upgrade, or just don’t upgrade.
4 Likes
Did you clear your browser cache? What device/browser is it? Can you open the devtools console in the browser to look for errors?
It were added for alignment with the native thermostat controls. But I agree, it might as well be optional to show it.
1 Like
I kind of see things a little differently … sometimes structural changes in code syntax are required as best practise and standards develop or as developers gain experience. The developer makes the add-on available for free, is receptive to feature requests, and to be fair I believe that in this case the release notes did contain a warning that there would be breaking changes for most users.
Think I figured it out. I updated sensors to the following:
sensors:
- attribute: hvac_action
name: State
- attribute: fan_action
name: Fan
- entity: sensor.6900_kitchen_last_changed
name: Changed
Updated to the new formatting (missed this in my initial re-read of the docs).
The issue I was having iabove is that preset_mode has the value ‘null’ - which looks like it breaks the card entirely and causes it not to display.
FWIW, I’m NOT using this attribute on my current card, but as an FYI, believe the old card allowed a value of ‘null’ to display, and appears the 2.x version might have issue(s) with attributes returning null
1 Like
Hi,
How to remove this new things in the red circle:
Thank you.
Ho can I fix the mobile issue?
Displays properly in computer / tablet, not that nice on mobile up.
Sin the column format make the card too bulky.
I tried card mod in the past, but it didn’t have any effect on the iOS app
+1
Same question here: How to get rid of the additional hvac mode
At the moment you can’t, this attribute is shown as it is shown in the HA Core climate-card. It would need some programming to disappear. I suggest you create a feature request in the github.
A new beta release is out with an entirely new way to deal with sensors by using templates.
Would love feedback on, well, everything about it 
See the Github release and the documentation for the new format
You can’t combine old/new sensor configs, thus specifying the version. The old format for sensors will be removed in the future at some point as this approach is far more flexible and actually in a sense simpler on the code side for the card as well.
(Oh, yes, it allows you to fix your issue @nightfever @spider7611 )
3 Likes
Hello. I was intrigued that it is possible to create your own card in Lovelace. I would like to ask if it is possible to create more advanced cards, such as the attached picture. So that the buttons on the display are interactive and can switch thumbnails with other functions. Thank you
2 Likes
If the button card can be implemented in the image card so that there are more button cards on one image card, then it might be possible, but I strongly doubt that. I don’t think it’s possible.
Off topic for this thread, but yes you can develop as crazy complicated and uniquely looking cards as you want if you want to build a completely custom card.
There is a getting started documentation over here if you know your JS+HTML+CSS.
Hi everyone, I am stucked at the very begnning use of Fully Kiosk Browser on Huawei Mediatab T3 with this Simple thermostat card, it looks like it doesnt recognize the card that anyway is correctly displayed on a PC browser.
Anyone can advice me how to fix it? It looks like an old issue, can’t find much info about
I’ve made it work, using version 3:
sensors:
- label: State
id: state
template: "{{hvac_action}}"
This was a slightly better way that handles localizations too.
sensors:
- id: state
label: State
template: '{{hvac_action|translate(''state_attributes.climate.hvac_action.'')}}'