This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/krisniem on 2026-06-06 16:33:37+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Flameknight on 2026-06-06 15:51:59+00:00.

Hello plant lovers!

It's been a couple of months since I last posted about Adaptive Plant, and a lot has changed under the hood. v1.2.1 just shipped, jumping from v1.0.5 the last time I posted here — that amounts to 8 releases of features, fixes, and a fairly significant cleanup pass.

For the majority of you who didn't see my other posts: Adaptive Plant is a fully local HA integration for tracking your plants, with adaptive watering logic that learns from how you actually care for them — water early consistently and the interval shortens; snooze consistently and it lengthens. No cloud, no APIs, no subscriptions, and no I don't ask for money this is purely a passion project. The integration comes bundled with a card and a task reminder automation blueprint allowing for the full replacement of apps like Planta that force you to pay for all the features and API access.

https://preview.redd.it/zqk62v71po5h1.png?width=896&format=png&auto=webp&s=5c8aec528e3609b0d44947572f3afab762f14809

If you're catching up and want to see my prior posts:

• v1.0.3 — original post

• v1.0.5 — moisture sensor fixes, blueprint improvements, card picker discovery

**What's new since v1.0.5 (high level — full notes on GitHub):**

https://preview.redd.it/41wcawgb6k5h1.png?width=2912&format=png&auto=webp&s=e4600af9b44d071fb813b5d4291f5ad17c0d4196

• **Autoinstall for the card and blueprint.** Based on a recommendation from frenck on the pending HACS approval PR, the companion card and task reminder blueprint are now registered automatically when the integration loads. No more manual resource setup or blueprint import — install the integration, restart HA, done.

• **Repotting tracking.** New optional feature with a last-repotted date sensor, Mark Repotted button, and a date input field if you want to backfill a past repotting event.

• **Latin name field.** Optional scientific name per plant, displayed in italics under the plant name on the card.

• **Major card performance pass.** The card used to rebuild itself on every HA state change anywhere in the system. It now only re-renders when something it actually cares about has changed — over 95% reduction in re-renders on a typical busy install.

• **Card theming.** Configurable card background color and active tab color via the visual editor.

• **MDI icons by default.** Card now ships with Material Design Icons out of the box instead of emoji.

• **A lot of bug fixes and polish.** Optional text fields can now be cleared from Configure (this took more digging than expected), health select no longer silently resets the check-in clock, the Confirm Health button background now renders correctly with any CSS color, and a handful of latent bugs got cleaned up in the options flow.

• **HTML escaping across the card.** Defense-in-depth against any future scenario where untrusted text could reach the card markup.

**GitHub with full readme and install instructions:** https://github.com/Big-Xan/adaptive_plant

Install via HACS as a custom repository for now, HACS inclusion coming soon™!

**While I have your attention — other cool plant projects worth checking out:**

I want to spotlight a couple of other HA plant projects I've come across that are doing really interesting work:

• [/u/Maximum-Sleep8048's plant card](https://www.reddit.com/r/homeassistant/comments/1ts1bty/comment/oounnhf/?context=3) — a different visual approach to plant dashboards, very polished

• [/u/degeneratedvirginape's plant monitoring setup with ESP32+Miflora](https://www.reddit.com/r/homeassistant/comments/1rw6uen/i//_built//_a//_plant//_monitoring//_setup//_with//_esp32/) — full DIY hardware-side build for soil/light sensing, journaling, and an AI assistant.

If you're into the plant-tracking-in-HA space these are worth a look. There's room for a lot of different approaches here and I love seeing what other people are building.

Happy to answer any questions. And as always, if you've got feature ideas or hit any bugs, please drop a comment under the most recent release or open an issue/feature request on GitHub — the roadmap is shaped by what people ask for.

Cheers 🌱

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Famous-Car4493 on 2026-06-06 07:42:11+00:00.

I’ve been slowly adding more smart home stuff, and the funniest part is realizing that automated doesn’t always mean properly configured.

My recent example is a dreame X60 Max Ultra Complete robot vacuum. I bought it a few months ago and mostly just let it run with the initial map. I didn’t really know much about robot vacuum mapping beyond it scans the house and cleans. So for a while I thought it was a strong vacuum with slightly questionable judgment. It would clean well, but the way it understood rooms, rugs, and certain areas didn’t always match how I thought about the space.

A friend came over a few weeks ago, saw my setup, and immediately realized I had basically never edited the map. He helped me split and merge rooms, clean up the zones, adjust carpet settings, and set some room-specific cleaning preferences. The difference was honestly kind of embarrassing. Same robot, same apartment, but suddenly it felt much more like an actual smart home device instead of just a vacuum on autopilot.

Now I’m still poking around the settings and trying not to over-tinker. Curious if anyone else has had a similar moment where a smart device became way better once someone showed you the obvious setup step you had completely ignored.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/hometechgeek on 2026-06-06 14:05:10+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Hardi_333 on 2026-06-06 11:12:19+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Nerdaxic on 2026-06-06 09:59:54+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Empty_Requirement940 on 2026-06-05 21:48:51+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/OpportunityNaive1754 on 2026-06-05 14:18:35+00:00.

After months of development: OpenPublicTransport — a Home Assistant integration that brings live transit departures from 28 providers across Germany, Switzerland, Austria, Sweden, Ireland, and worldwide into your smart home.

The camera entity renders a classic yellow-on-black station departure board that you can cast to a wall tablet:

Camera board

Or use the Lovelace card in table, compact, or trip layouts:

Table layout

Compact layout

Trip planner

What you get per stop:

• Real-time delays, platform changes, disruption notices
• Walking time filter (departures you can't make disappear)
• Binary sensor for delay alerts → automate your lights/notifications
• Calendar entity for each departure
• A-to-B trip planning with transfer risk assessment
• TTS announcements ("S6 to Essen Hbf, 3 minutes, platform 3")
• Statistics entity for punctuality tracking

28 providers, most need no API key: VRR, BVG, HVV, MVV, SBB, ÖBB, Trafiklab, NTA, Transitous, and more. Setup takes under 2 minutes via config flow — no YAML.

HA 2026.6 compatible.

GitHub (integration): https://github.com/NerdySoftPaw/openpublictransport GitHub (card): https://github.com/NerdySoftPaw/openpublictransport-card Docs + provider map: https://openpublictransport.net/

If your provider isn't listed — open an issue, adding one is straightforward.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/msapple on 2026-06-06 00:01:14+00:00.

I built a HACS integration that lets you use any IR remote as a Home Assistant automation trigger — no MQTT, no custom code

Home Assistant 2026.6 quietly introduced a new infrared entity platform, and as far as I can tell this is the first integration outside of the official LG one to actually use it.

I've been using a SideClick remote attached to my Apple TV to trigger Hue light scenes in Home Assistant for about a year now. The setup worked, but it was a mess — ESPHome flashed to an IR receiver, MQTT bridging signals into HA, and a pile of custom automation logic just to map button presses to scenes. Every time something broke I had to dig back into the whole stack.

With 2026.6's new infrared platform I was able to build a proper HACS integration that replaces all of that. You point your remote at an ESPHome IR receiver, hit "Add button" in the HA UI, press the button twice to confirm, give it a name, and that's it — HA fires an event entity you can use as an automation trigger. No MQTT, no custom code, no manual fingerprinting.

It also handles double-click detection, has a manual code entry path if you already have a command map, and includes tuned ESPHome configs for both ESP32 and ESP8266.

Still early (v0.4.0, I'm the only tester so far) but it's been working reliably for me. Would love feedback from anyone else running IR remotes with HA.

GitHub: https://github.com/dhruvb14/hacs

Sideclick Inside HomeAssistant

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/kobebrain on 2026-06-05 20:15:20+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/DR_Kroom on 2026-06-06 02:43:51+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/wanderingjoker on 2026-06-05 19:45:03+00:00.

The backstory (the whole reason this exists)

I live directly across from an elementary school, community center, and library on the backside on a street with no stop signs and no speed calming, and people absolutely rip through it. It's almost set up like a race track. So, I requested a speed study from the county back in 2022 (outside of city limits). They did one and the 85th-percentile speed of 25 mph, averaged 20mph so they basically said speeds were within limits and nothing would be done. This same study has been the answer every time I've asked for a stop sign or a speed bump since. I got two little kids who love to play outside and it's just crazy how people will drive 40mph+ like it's nothing.

In my opinion though, there were two major problems with that study:

1. It used one of those portable counters with the big black tube/box sitting in the lane. Drivers would it and slow down as they approach it so it functioned like a temporary speed bump. So it actually measured the one behavior you don't get the other 364 days a year. If they just would have left it, it probably would have solved my problem.
2. It ran for maybe 24 hours and in the summer while school was out. Way too short to capture normal traffic and none of the school traffic obviously

So I "built" my own radar detector that is permanent, basically invisible, runs 24/7 locally, and I own the data.

Hardware

• OmniPreSense OPS9243-A-PE — 24 GHz Doppler radar, the Ethernet/PoE variant
• Connected and powered off a UniFi USW-Flex 2.5G (PoE) that lives in my garage
• Weatherproof run: USBFireWire RR-125320 double-ended outdoor cable, with an RR-125310 adapter to break back out to the Flex in the garage.
• HA itself runs as a VM on Proxmox, with a local Mosquitto broker

Mounting

Had to buy this mount off Amazon and design and print a plate for it since it uses standard 1/4" connections. Plate just screws into the back of the radar detector then goes into the plate I printed.

The data pipeline

The OPS9243 publishes JSON over MQTT to a single topic (<serial>/json). Quick shoutout to OmniPresence for providing all the needed documentation on how to get this to point locally and not to their cloud. Anyway, two message shapes land on that same topic:

• Per-detection messages with DetectedObjectVelocity and direction
• Periodic TimedSpeedCounts summaries

On the HA side I've got template sensors for current speed and direction, plus a running speed log that keeps the last 50 detections as a list of dicts and renders them on a markdown card just so I can just keep that up and watch as I work during the day lol.

Aiming matters — and mine cheats in my favor

Doppler radar only measures the velocity component along its boresight, so a steep mounting angle introduces cosine error and reads low. I aimed mine nearly parallel to the road to keep that error tiny, and verified it by driving past at a known speed in my own car. It tracks scary accurate. Usually reports about 1mph under my actual speed.

Here's the part I love for my situation: any small error that does remain is always in the under-reading direction. It never reads high. So nobody at the county can accuse me of inflating the numbers. If anything, the real speeds are worse than what I'm logging.

Why local-first

No cloud dependency means it keeps running when the internet doesn't, nothing phones home, and the data is mine to do with as I please. Same reason the rest of my setup (UniFi + ESPHome + HA on Proxmox) avoids the cloud wherever it can.

What's next

More automations? I have one that alerts me when a speeder is going 35mph so I can grab the clip from the G6 180 and back it up to my NAS and add the speed they were going. Probably can automate the rest of that out.

Hue lights out front doing a red/blue light cop effect when a certain threshold is met?

Also, building proper speed histograms and time-of-day breakdowns so I've got a real dataset, not a cherry-picked 24-hour snapshot, to take back to the county. Long enough collection window that it can't be waved off as a fluke.

Honestly though, my new favorite thing is sitting on the driveway with neighbors at night, having a drink and yelling at speeders in real time. lol.

https://preview.redd.it/jo4icam0qi5h1.jpg?width=3024&format=pjpg&auto=webp&s=aad72385386c85e554348d213f3ff4e9a19d4159

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Squeeech on 2026-06-05 12:22:38+00:00.

Wall Mount for Guition ESP32-S3 4848S040 – A smart home panel for your entrance that even the cat sitter can use

Hey everyone! Long-time lurker, first-time poster here – wanted to share a little project that started with a very specific frustration: every time someone else needs access to our flat – the cat sitter, a family member, an Airbnb guest – I'd end up writing a two-page instruction manual for the smart home. Not ideal.

The solution I landed on is a wall-mounted panel right at the entrance, combining a touch display with a hidden NFC reader. Hand someone a card, they tap it on the way in, and the right things just happen – lights turn on, the heating adjusts, whatever scene you've set up in Home Assistant. No app, no login, no explanation needed.

The hardware side of things

The enclosure is a custom-designed PLA print that fits the Guition ESP32-S3 4848S040 touch display and hides everything behind the wall plate. The bottom compartment houses a Mean Well IRM-05-5 AC/DC power supply – mains voltage in, clean 5V/1A out. No power brick, no USB cable creeping down the wall. The display connects via a 4-pin MX1.25 connector (PIN1 = GND, PIN4 = +5V), and the ATOM Lite for the NFC reader gets its power from a second 4-pin socket in the same compartment.

The NFC reader sits behind the top panel, completely invisible from the outside but close enough to scan reliably. It's based on the excellent "No Soldering DIY NFC TagReader" project – if you haven't seen it, definitely worth a look. The idea is simple: you hand out pre-programmed NFC cards to whoever needs them. The cat sitter gets a "cat sitter card" that triggers exactly the automations she needs – nothing more, nothing less. No fumbling with apps, no accidentally turning off the heating.

Software

The display runs ESPControl (an ESPHome-based project by jtenniswood) paired with Home Assistant. Fully local, no cloud dependency, and fast enough that it actually feels responsive to the touch. The NFC side is handled entirely within Home Assistant automations – each card has its own tag ID and triggers whatever scene you've assigned to it.

Assembly

The enclosure prints in PLA and goes together with 4× M3 heat-set inserts and 4× M3×8 hex screws. Solid wall mount, no glue, no friction-fit guesswork.

Files are available on Makerworld: https://makerworld.com/de/models/2892428-combined-display-mount-for-the-guition-4-display#profileId-3231998

Happy to answer questions in the comments – and curious whether anyone else has gone down the "NFC for guests" rabbit hole!

Quick safety note: this build involves mains voltage (230V AC). If you're not comfortable working with line voltage, please have a qualified electrician handle the wiring.

https://preview.redd.it/0eipqyxsig5h1.png?width=1860&format=png&auto=webp&s=54adda54a2a688ab187438e8723c589d4aacbddf

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/chingy_meh_wingy on 2026-06-05 15:12:15+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/mr-samd on 2026-06-05 11:15:38+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/qaddodi on 2026-06-05 10:31:11+00:00.

Hey everyone, I made a small web tool for building Home Assistant floorplan dashboards:

https://qaddodi.github.io/ha-floorplan-editor/

Heavily vibe coded, I admit (busy life it's tough to find time to actually code it manually, if it works it works).

It lets you visually add and position entities on a floorplan instead of manually editing SVG/CSS/YAML every time. You can upload your floorplan assets, then add lights, sensors, cameras, or generic entities, move them around, adjust hitboxes/glow areas, labels, icons, and preview how things will look.

For lights, it can create the masked “lights on” glow areas and supports dimmable/color-capable lights. For sensors, it can add icons/text for things like doors, windows, motion, leak, temperature, etc. I was able to get two images of "Light_on" and "Lights_off" PNGs, see attached of my apartment, and dim between them for lighting (I have a previous post about this). I generated the PNGs using chatGPT/gemini.

When you are done, it exports the three pieces needed for a Home Assistant floorplan card:

• SVG
• CSS
• YAML card config

The idea is to make floorplan editing less painful, especially when you are adding or moving entities and do not want to hand-edit coordinates and masks manually.

Still rough, but it works for my use case.

https://preview.redd.it/dhwllsiiyf5h1.png?width=3322&format=png&auto=webp&s=e24cfd5bd5e9150e475e3c8b69c85f17d05631a3

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/ElementZoom on 2026-06-05 09:18:36+00:00.

This is a showcase of FluxUI, my Home Assistant dashboard design system. It continues from my previous MD3 dashboard and introduces a major improvement: a unified YAML structure where mobile and tablet layouts share around 90% of the same configuration. This makes the dashboard much easier to maintain, scale, and iterate on.

Overview Page

At the top of the dashboard, I’ve designed a compact overview section that focuses on real-time awareness and quick access.

• I start with weather alerts, alongside key system notifications like Alarmo status and a notification counter so I can immediately see if anything needs attention.
• Next is the person section for both myself and my wife, showing individual location tracking. This includes a live map view that integrates with Google Maps routes from Home Assistant, displaying real-time travel paths between home and workplace with live traffic updates.
• Below that is a running text ticker, showing the next 2 hours of weather forecast in a smooth scrolling format for quick glance information.
• I then use a tabbed control section that groups key controls together:
• Climate and temperature control
• Swipeable toggles for quick actions like booleans, automations, and other switches

Event calendar tab for upcoming schedules

Another tab focuses on active states, showing what’s currently running in the home, such as active lights, or any open doors and windows.

Hidden Pop-ups & Alerts

There are also layered pop-up cards that only appear when needed:

• Weather alerts, including earthquakes, volcano updates (if any), rainfall forecasts, and radar overlays
• Priority notifications such as appliance timers (washing machine, dryer), garage door status, and live camera feeds when something is left open or triggered

This is just the first page of the dashboard. I am building the Github page and hopefully can be finished sometime next week.

I want to sincerely thank the Home Assistant community. So much of what makes this dashboard possible comes from the open work, ideas, and support shared by others. I’m grateful to be able to learn from it and contribute in my own way.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Nusuthoid on 2026-06-05 08:13:56+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/duohad on 2026-06-05 04:36:05+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/ankzel on 2026-06-04 19:57:05+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/Routine_Yesterday_61 on 2026-06-04 19:42:31+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/dichron on 2026-06-03 15:46:49+00:00.

It's only $110, it's Matter compatible, and has 4 buttons. Seems like it has a lot of potential. Anyone going to buy one and tinker with it?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/PearlJam3452 on 2026-06-03 07:41:04+00:00.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/wivaca2 on 2026-06-04 04:39:21+00:00.

Just about any time I'm looking at something in HA, I want to know what time something happened or when it will happen, but I need to know more than just rounded hours. I want to see it happened at 7:26 and if I want to round that, I can easily convert in my head "oh, that was about 2 hours ago".

What I CAN'T do is know something happened at precisely 7:26 when the time is 9:54 and it says "2 hours ago".

Why are we getting this maddening imprecision on our dashboard? Yes, I know I can write a helper to make it show up precisely, but why must we burn clock cycles making it vague, then more entities created and code to execute to get back to what we started with?

As if time wasn't bad enough, "5 days ago" is pretty vague. I'm just surprised once it goes past 7 days, it doesn't literally say, "Uh, I think that was last week, maybe?"

If I wanted a rounded guess, I'd ask someone without a watch. Am I missing some global configuration flag I can change to get rid of this?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/AbbreviationsFit6561 on 2026-06-04 03:34:28+00:00.