It ‘works’, albeit without the flexibility of having that behaviour optional.
(And yes, I use that template elsewhere for buttons that are not ‘radio buttons’ so I’d really like it!)
Is this your own card? Or is this something available? It looks really good, I’m not sure I would trust HA to run my sprinkler system (what if it crashes while a zone is on?) but I do have it linked to my rachio account so that I can mess with the zones, which worked well for when I installed sod last year.
That card is a piece meal card. He’s using a series of cards to configure that. It’s not a single custom card that you can install, if that’s what you’re asking.
As for letting HA run your irrigation, I have been doing it for two years (summers only ) with no problem. In fact it is probably why I found HA, and stayed.
Search for garden irrigation on here and you’ll find plenty of people doing it. You might even find my effort which I’m currently re doing. Hence the new UI.
Hi @petro, could you share your code for counting the number of lights? Right now I have a separate automation just for counting the lights on per group …
@petro I think you are there Man
I am trying since some days now to have a button with some other sensors embedded in.
The idea is bulb (big) plus triggering / related elements smaller at the corners (motion sensor ,illuminance, switch) dynamic (ie with corresponding state live)
Tried that with custom fields in button card
No luck
Just new one example then I walk alone
Please create a new thread or ask this in the custom button card thread. This thread is about the differences between the button card and lovelace gen.
@petro, I was just looking at your configuration and it’s given me more than a few ideas!
I’ve also been using lovelace_gen and jinja2 macros to generate some portions of my lovelace UI (though still mostly just getting started.) One thing that you might consider when using jinja2 macros to generate the YAML configuration is that JSON-style syntax works just fine inside of YAML files. So you can mostly just ignore the whitespace indentation issue completely, and have the macro emit JSON in the place that it’s invoked.
I made a post about this about a year ago that lays this out. This approach might simplify things a bit.
I knew about that before hand, the problem is if you make mistakes it’s much harder to see the unformatted json. I made the yaml things, so I can quickly copy and paste the entire templates into the template editor to see the results printed in a nice fashion.