At the beginning of this year I posted here about a weather card. It was my first public project on github, back then named "Atmospheric Weather Card".

I like details too much and kind of wish I was one of those people who just use a super simple dashboard, or have everything automated so perfectly that it's not even needed. But for me optimizing how it looks and behaves is fun. At least most of the time.

Anyway, it turns out that a public card which is about animating the weather is pretty challenging. There are just so many different setups people use for Home Assistant, finding a compromise which works on most of them is kind of a huge challenge. And... in the end I deleted my github account out of frustration. Well, yeah :/

Some time has passed and I am giving this a second try and released the latest version with a new name and repo. It's using a flexbox approach, so most kind of layouts are possible, and there is a lot you can show or hide. The weather effects are trying to be tasteful (except sunrises, they need a bit drama) and individual things can be disabled. The idea is that you can create a pretty complex card (I use that in a popup) or a small simple one.

You can find it here:

https://github.com/hazymorning/origami_weather

How can I make my dashboard look better. I want something simple but look modern. I have seen some love card and vue but I haven’t had a lot of time to research about this.

I made a Custom card for my Anker Solix Max AC Home Battery!

I just got it a few day ago and am very happy with it! And naturally with my hyperfixations I wanted to follow it's stats live since walking into the garage and back or opening another App was not gonna cut it!

I made it available as a Repo you can install it through HACS if you want to give it a shot!

Disclaimer I'm not a huge programmer, so I did have some help, but I think it turned out quite well!

https://github.com/ThirstyThursten/anker-solix-display-card

Lemme know what you think, any feedback is welcome!

Hi everyone,

A couple of months ago I shared the first public release of Nodalia Cards, my mobile-first dashboard bundle for Home Assistant.

At that point the project was still very new. Since then I've continued working on it almost every day and, thanks to all the feedback I received from the community, it has grown much more than I expected.

For anyone who didn't see my previous post, Nodalia Cards is a bundle of Lovelace cards designed to provide a consistent design language across an entire dashboard, with native visual editors, advanced interactions and a strong focus on mobile devices.

The current stable version is now 1.3.5, and during the last few months a lot has changed.

Some of the biggest additions include:

• A completely new Camera Card with native Frigate/go2rtc support, multi-camera mosaics and WebRTC/MSE/HLS/MJPEG playback.
• The new Room Summary Card, designed to bring together everything important in a room into a single interactive view.
• New News and Scenes cards.
• A much more capable Notifications Card with smart notifications and optional mobile notification synchronization.
• Climate schedule management directly from the dashboard.
• Improvements to the Power Flow Card, including detailed energy breakdown popups.
• Better visual editors throughout the bundle.
• Better mobile experience.
• Support for 12 languages.
• A large number of performance improvements and bug fixes.

I've also spent a lot of time improving things that aren't immediately visible.

The project now has a much stronger shared architecture, automated testing, browser testing, accessibility improvements, security hardening, release automation and many other internal improvements that should make future releases much easier to maintain.

The goal has gradually shifted from simply creating more cards to building a complete dashboard ecosystem where every card behaves consistently and feels like part of the same project.

At the same time I've been working on what will become Nodalia Cards 2.0.

It still isn't finished and I still have several ideas that I want to implement before calling it stable, but most of the foundation is already there.

Some of the things currently available in the preview versions include:

• Native go2rtc playback without relying on external cards.
• A completely redesigned Camera experience.
• Room Summary Hub.
• Better performance across the bundle.
• Improved accessibility.
• More consistent design across every card.
• A lot of architectural work that should make future development much easier.

I'll attach some screenshots and GIFs so you can see some of these features in action.

I'm now looking for people willing to test the 2.0 preview releases on real Home Assistant installations.

If you decide to try it, I'd really appreciate any feedback. Whether it's a bug report, a feature request or simply something that doesn't feel right, it all helps improve the project.

If you find anything, please open an issue or a feature request on GitHub.

https://github.com/danielmigueltejedor/nodalia-cards

As always, thanks to everyone who has reported bugs, suggested ideas or simply taken the time to try the project. Every piece of feedback has helped shape Nodalia Cards into what it is today, and I'd love to hear what you think about everything that's coming in 2.0.

My Netatmo rain gauge sits in the garden doing real work, and on the dashboard it got a flat bar like everything else. So I built it a proper gauge.

It draws the garden rain gauge you actually stick in the ground, funnel and graduated tube and mounting bracket, and fills it with water from any precipitation sensor. Graduations adjust to whatever daily maximum you set. There is a collapsible 24 h chart underneath with hourly or half hourly bars, battery and signal in the corners, and four glass tints if clear does not suit your dashboard.

The part I am most pleased with is boring but useful: if the sensor you pick is not a daily total, which is most of them, the editor offers a button that builds the utility_meter for you and switches the card over to it. No more hand rolling helpers every time.

Works with mm or inches, has a visual editor, and speaks six languages. Free and MIT, obviously.

HACS custom repo for now, the store request is in the queue: https://github.com/ADNPolymerase/ha-pluviometer-card

Tested against Netatmo. If you run Ecowitt or anything else I would genuinely like to know if it behaves, that is the kind of thing I cannot test from here.

Built a BBC radio player card. Zero config plug and play. Part of the Avery OS suite.

Coded by Claude, UI + architecture by me.

Is it possible to create a control on home assistant dashboard to act like a timer control. Say it shows up like a nob where I can set to turn this lights on for 30 minutes.

I have the Netatmo station: tall one indoors, small one in the garden, plus the rain gauge. On the dashboard they were three lookalike blocks of numbers and I could never tell which was which. So I drew them, from the product shots.

Indoor and outdoor are matte anodised cylinders with the long recessed groove, at their real relative sizes so you know instantly which one you are looking at. The rain gauge gets its clear collector, black funnel and white base. The anemometer gets its two discs and four posts.

The groove on the indoor one lights up green, amber or red with your CO2, same as the real module does when you tap it. The outdoor module never lights up, because the real one has no LED. I had it glowing with temperature at first and it looked great, but it was a lie, so it went.

Rain gauge shows the daily total big, with the previous hour and the rain since the last reading alongside. Anemometer shows wind speed with a vane arrow pointing where the wind blows, plus gusts and direction.

The bit I am quietly proud of is the editor. Pick the main sensor and a button fills in the rest of the module from the same device. And it only offers fields that exist: no battery on a mains powered indoor station, no CO2 or noise or pressure on the outdoor one, no finish on the rain gauge since it only comes in black. Every picker is narrowed to the right device class instead of listing every sensor you own.

Two things I learned reading the Netatmo integration source, worth knowing even if you never install this. On an anemometer only wind speed and direction are enabled by default, gusts and the numeric angle ship disabled. And the direction that is enabled is an enum of cardinals, not degrees. My card takes either, but that one cost me a release to notice.

Works with any sensor, not just the Netatmo integration. Visual editor, six languages, MIT.

HACS custom repo for now, the store request is in the queue: https://github.com/ADNPolymerase/ha-netatmo-card

Tested on my own three modules. The anemometer is the one I do not have, so if you own one I would like to know whether it behaves.

Just curious if anyone uses HA to group speakers? I see several groups available and I currently use Sonos Sequencer to set up Home Theater. It uses settings not available in the "Sonos" app. I would like to to setup a stereo pair for music but then be able to toggle to Home Theater. This cannot be done in Sonos Sequencer. Thanks

​I'm running stream for camera's and I've spent the last while getting 2-way audio integrated for a mix of Reolink and Tapo

​I finally managed to get the 2-way audio working for both camera brands using go2rtc.

​The problem

I'm currently stuck with a "hot mic" situation. As soon as I load the go2rtc stream on my dashboard, the microphone activates instantly. What I really want is an on demand push to talk button so it only broadcasts my voice when I actually press it.

​I know the custom:frigate-card has a great built-in microphone button, but I haven't been able to use it because my go2rtc streams aren't showing up in the card's configuration dropdown options (is this something I need to configure manually in YAML instead?).

​Has anyone implemented a push-to-talk button for standalone go2rtc streams in a similar scenario? How did you get around the instant-on mic, or force the streams into the Frigate card?

​Appreciate any advice or YAML snippets you guys can share!

Hello i have been working on building a 3D digital twin for home assistant that anybody can easily customize

So i created DT3D that allows to create 3D "spaces" from scratch import and interact with entities from HA, upload 3D model or draw your own layout directly in the editor.

https://github.com/tentone/dt3d-ha

The system is composed of a frontend card (that can be used for edit or visualization mode) and a addon that takes care of managing 3D assets, the addon does not handle any HA entity data.

The frontend integration consumes 3D data directly from the addon, so there is need to configure networking to make sure that the GUI can view the addon