The Visibility Feature, is something I've known for in a while, and I know exactly how it works, but I haven't ever used it :D I think I have to make something like this too. Good job man.
Really nice. Of course, you misspelled "humidity" in the mini grid. I still also believe that headings are basically superfluous and a waste of space, except possibly when there's any possibility of confusion, like inside/outside temps.
I agree with the title being a waste of space but it can come in handy sometimes. For instance I have a Lights section only and always showing quick access to the 2 main light groups I use on a daily basis. This section has a title (Lights ^^) that lets me navigate to my full lights view (which is a hidden subview). On the right of the title, it also shows how many lights are on at any given time (if any).
Hunidity....nice. Thanks for catching that. As for the headings, that is one of those things that some people will love and others will see no need for. The feels like temp is something I don't need in my face but is nice when it differs from the actual temp so it gets displayed in the heading only when it differs.
Nice layout. I'm migrating from Homekit infused but one thing I'm missing is the great notification slider from HKI. How do you deal with notifications on your dashboard?
I have a video on using sections. It shows most of the basics and this dashboard update is a continuation of that first (and second) video. ua-cam.com/video/LF_qY2vmZng/v-deo.html
@mostlychris, do you like your Tempest? I ended up getting rid of mine as the humidity sensor kept messing up about every 4 months or so. It would show negative humidity. The only fix was to climb the roof and reset it. Finally got rid of it and went to an ecowitt. The Tempest had a lot more sensors than the ecowitt but nothing I can't live without I guess.
For the mini graph card vertical spacing issue... I found that you can set grid_options: rows: 2.3 and it works fine. Strangely it seems like you can use decimal values only for the rows, not columns.
Right after watching the video, I was just about to post the same thing ! :) I use decimals even with normal cards, to keep sections that are next to each other, exactly the same size. Because some of my cards are unchangeable in size. For example, the "clock-weather-card". So on the sections next to it, I use decimals to keep them exactly the same height. :) Moreover, in Home Assistant, as standard, you can now select "Precise Mode" to technically "cut" the columns in half for more precise sizes. Really neat. :)
I usually limit it to 1 or zero. Just haven't done that with the mini graph cards yet. The sensor sends two decimals for those, but check out this for the wet bulb resolution: 67.5500392038427
@@r7boatguy No expert, I dont use mini cards, but isnt there a way to use "round" (or even force it to be an "int") when you specify the entity in those cards? I have a Markdown card with: {{states('sensor.fan_energy')|round(0)}}
@@r7boatguy I have just added some graphs on a new "sections" view. When you click the graph, a little popup shows with the details of the single entity. When you then click the gear icon, there is a setting for "display precision" I set it to (64) for a humidity entity, but neither the graph nor the entity on a seperate entities card actually uses the set precision. What I said yesterday works on a Markdown card. As disapointed as you. 🙂
Thanks!
The Visibility Feature, is something I've known for in a while, and I know exactly how it works, but I haven't ever used it :D
I think I have to make something like this too. Good job man.
Good Job Chris 👍👍👍
Really nice. Of course, you misspelled "humidity" in the mini grid. I still also believe that headings are basically superfluous and a waste of space, except possibly when there's any possibility of confusion, like inside/outside temps.
I agree with the title being a waste of space but it can come in handy sometimes.
For instance I have a Lights section only and always showing quick access to the 2 main light groups I use on a daily basis. This section has a title (Lights ^^) that lets me navigate to my full lights view (which is a hidden subview). On the right of the title, it also shows how many lights are on at any given time (if any).
who cares
Hunidity....nice. Thanks for catching that. As for the headings, that is one of those things that some people will love and others will see no need for. The feels like temp is something I don't need in my face but is nice when it differs from the actual temp so it gets displayed in the heading only when it differs.
Nice layout. I'm migrating from Homekit infused but one thing I'm missing is the great notification slider from HKI. How do you deal with notifications on your dashboard?
Amazing, thanks 🙏
Do you have a video showing how to build this from scratch?
I have a video on using sections. It shows most of the basics and this dashboard update is a continuation of that first (and second) video. ua-cam.com/video/LF_qY2vmZng/v-deo.html
@mostlychris, do you like your Tempest? I ended up getting rid of mine as the humidity sensor kept messing up about every 4 months or so. It would show negative humidity. The only fix was to climb the roof and reset it. Finally got rid of it and went to an ecowitt. The Tempest had a lot more sensors than the ecowitt but nothing I can't live without I guess.
I just saw mini-graphic-card have a PR with sections compatibility coming.
For the mini graph card vertical spacing issue... I found that you can set grid_options: rows: 2.3 and it works fine. Strangely it seems like you can use decimal values only for the rows, not columns.
Interesting. I didn't know decimals were allowed. Thanks for the tip!
Right after watching the video, I was just about to post the same thing ! :)
I use decimals even with normal cards, to keep sections that are next to each other, exactly the same size.
Because some of my cards are unchangeable in size. For example, the "clock-weather-card".
So on the sections next to it, I use decimals to keep them exactly the same height. :)
Moreover, in Home Assistant, as standard, you can now select "Precise Mode" to technically "cut" the columns in half for more precise sizes.
Really neat. :)
Can you please show that govee banner and how that is setup. Are you using mushroom chips inside an entity card?
I am using a bubble card. Here is the yaml for that. github.com/mostlychris/homeassistant/blob/master/goveebuttoncardsettings
Hi. Can I disable the Overview dashboard from guests/kids? Else it is pointless to share hassos
Thanks
How can i see my dashboard and edit it on a pc? I have the app on my phone but its too difficult to setup everything vbia phone
Just wondering did you mean for Hunidity? 🤔
same
I was just coming to say something. My OCD is killing me :)
For what?
Can't unsee that... 😱
Never knew how much triggering a misspelled word causes. I've fixed it so y'all can sleep well knowing there is no more Hunidity. 😂
Hehe.. might want to change Hunitity to Humidity....... at around 3.00 in.
Yup. Second notice 😀
Wonderful, wonderful.
But what I never understand is why people show Temperature and Humidity with 2 decimals. Your sensor isn't that good.
I usually limit it to 1 or zero. Just haven't done that with the mini graph cards yet. The sensor sends two decimals for those, but check out this for the wet bulb resolution: 67.5500392038427
@@mostlychris I am so sorry, Chris. It's a personal pet-peeve.
I have my temp & humidity sensor set to 0 decimal places, but those mini cards always display the decimals, can't figure out why
@@r7boatguy No expert, I dont use mini cards, but isnt there a way to use "round" (or even force it to be an "int") when you specify the entity in those cards?
I have a Markdown card with:
{{states('sensor.fan_energy')|round(0)}}
@@r7boatguy I have just added some graphs on a new "sections" view.
When you click the graph, a little popup shows with the details of the single entity.
When you then click the gear icon, there is a setting for "display precision"
I set it to (64) for a humidity entity, but neither the graph nor the entity on a seperate entities card actually uses the set precision.
What I said yesterday works on a Markdown card.
As disapointed as you. 🙂