Inspired by ciotlosms gauge card I created a similar card which shows two gauges at once.
I’m using completly new CSS because the styles in the ciotlosms version weren’t suitable for a second gauge - and because I like fiddling with CSS sometimes
It’s still a bit “work in progress” but I already use it “productiv” for my own climate controls.
Installation works as usual: copy dual-gauge-card.js to your www directory and add the url to the resources section of your lovelace config. (detailed instructions may follow if requested)
I hope someone has a use for this and I’d love to get some feedback!
That’s one of the reasons I call it work in progress
There is a css-variable for the width of the card as a whole and all other values are relative to this. This must be set statically in pixels, thats why the card doesn’t scale dynamically.
this is my most favorite custom card by far. Great work!
Quick question: I am using this card to display temperature and humidity of a room within one card. This saves space in lovelace because I have a lot (> 10 temperature/humidity sensors spread all over the house) and looks really nice too. Right now I use a custom sensor template for each sensor to round the temperature and the humidity value to one decimal place in order to avoid overlapping of the left and the right sensor text in the dual gauge card. Is there a trick to round/display to only one decimal place, e.g., by using “attribute” without having to define a custom sensor template?
Great card! Exactly what I was looking for! I need to move the inner and outer labels as I am using this to measure watts of my power usage and input of my solar, so the values are 4 digits and the label name itself. I have tried CSS but I may be doing it wrong. Can you help me move this with CCS? AN example would be great. Also, I want to compare the values of the inner and outer that change the color if the inner value becomes greater than out value. Thanks in advance.
@Rocka84 do you have any plans to update this card with the fixs on github, i used to use this quite a bit in my config and would be nice to have the real HACS version instead of my hacked JS file.
Good News everybody!
I recently began to take care of this card again. Sorry for being absent for such a long time. I won’t go into detail but work, family and other hobbys kept me from being active in the home assistant community for some months.
My home assistant setup wasn’t quite up to date as well (I upgraded from 0.103 to 0.108 last weekend) so I didn’t experience all the bugs myself. In other words: it worked for me
Sorry about that.
@dacorn Could you open an issue over at github? Maybe we can figure something out together.
Yes, unfortunately. As I mentioned before I opened a pull request to get off that list yesterday but when and if that is accepted is beyond my control.
Looking on the HACS discord channel I believe from Ludeeus statement this should be able to be unlocked by you. I don’t know if it is true, just passing on what I read. I it is not, I’ll comment back in the discord as Ludeeus is usually very responsive.
fun fact, all publishers have write access (at least for now) to the "default" repo, when 3 approve (and CI passes) anyone can merge, this way it's not locked to just me
If a PR needs a retrigger of the CI, just add the "recheck" label to it