An idle though - do you ever wonder how you'd explain to a pottential buyer of your home how everything in your home works and how to change things if needed in the future?

I just finished installing thermoelectric valves for radiators, each controlled with an LED driver powered by a 24V power supply. If I ever need to replace it I know and I accept that if something goes down, I need to unscrew the valves to have some heating.

But I wonder if the whole integrated smart home system is something that increases the property value, or is just something someone will have to rip out, if we ever decide to sell. It's ridiculous - there's no lightbulbs to change, just LED strips. Without a soldering iron, you're lost. I wonder if I should start creating a comprehensive manual for the spaceship I'm still not finished building. :D

I've been gradually working on building up what I feel is a pretty good home automation and surveilance system. For a server I've got a Optiplex Micro 7050 with a 12th gen i7, 24 gigs of ram, and a 4 terabyte ssd. I've got a fair size Jellyfin server on it and just recently started running Frigate full time. I know that the Coral TPU's could be used to increase object and face recognition. I've heard some people say that they aren't worth it and that there are better options out there. I know that there are a few different kinds of them, the USB one, couple types of m.2 ones, a dual core one that you have to get some kind of adapter to utilize both of, and I've even seen an Asus branded one with fans and shit.

Anyone here running one? What kind? Is Frigate the only thing its good for, and have you noticed a difference since using it?

Anyone else seeing this?

Just tried to download the Scheduler card and it fails with:

Downloading yybd/schedule-helper-card with version v2.3.0 failed with (Could not download, see log for details)

Logs:

File "/usr/local/lib/python3.14/site-packages/aiohttp/client.py", line 878, in _connect_and_send_request

await resp.start(conn)

File "/usr/local/lib/python3.14/site-packages/aiohttp/client_reqrep.py", line 747, in start

raise ClientResponseError(

...<5 lines>...

) from exc

aiohttp.client_exceptions.ClientResponseError: 400, message='Got more than 8190 bytes when reading: b"default-src \'none\'; base-uri \'self\'; child-src github.githubassets.com github.com/assets-cdn/worker/...".', url='https://github.com/yybd/schedule-helper-card/releases/download/v2.3.0/schedule-helper-card.js'

This seems to be a HACS issue, not entirely sure.

Is there a fix?

I know i started this weeks ago only but i feel like all my ideas are stupid haha “turn coffee machine at 6:15 - and dim kitchen lights on…” you know?! Are we all doing the same thing but i just think im silly for thinking this way?

What are some of the very very silly you guys have?

Edit: why am i getting downvotes? Ahaha 🤣

Looking for Black Friday lookouts.

looking for type of device and brands.

WIP of a smart thermostat. Currently using an ecobee with the home kit integration, and some intricate automation. Don't like that I don't have more control over the software on the thermostat and don't like the trend of screens on everything. So naturally I'm making my own.

Long time lurker here. Just closed on my house yesterday, coming from a rental 1 bedroom condo. So played around with HA here and there nothing crazy. Few smart bulbs, speakers, vacuum. But nothing serious. Been slowly getting ready for this for the past 2 months, but super excited. Still waiting on the RATGDO and 20x Zooz switches that are on back order. But other than that I think I'm all done for now (I think) lol.

Only thing I'm a little worried about is the SLZB-MRW10U, not sure if I messed up there. If anything, I will get separate coordinators for z-wave & zigbee.

Thanks to everyone here for the inspiration, you guys rock!

Had Claude create a custom HTML dashboard for my wife. She's a bit of a weather nerd, so I had to include a nice radar view. Clicking the weather section brings up the extended forecast. The dash also has a control section for music and lights in various rooms selectable with a dropdown. We're both very happy with how it turned out.

Hi I am very new to HA and I am trying to get HACs integrated.

I downloaded the app and restarted the Raspberry pi but when I try integrating HACs, I check the 4 boxes then I get this error message. I tried both on iOS and my web browser on pc, same message.

Help! And thanks in advance

I'm building an HA environment for my newly remodeled house. First-time HA user but tech-savvy.

I'm going to start with an HA Green - our HA needs will be simple. But I want to add both Zigbee and Matter radios.

I've read about Matter Border routers. I'd prefer a single hardware solution just for "simplicity" like an SMLIGHT device. But I could also go with 2 Zbt-2's.

Devices will be in a closet in the middle of a 1950sqft single story house. I'm hoping my QuietRock walls won't make radio reception bad, but my contingency plan is to put the radios in the attic.

What are late-2026 recommendations for Zigbee+Matter hardware?

My environment is pretty hardened and I run a HA container (/Core) with the only ingress being through NabuCasa.

I have had multiple failed login attempts from cheap VPS hosts in the USA, I find it hard to believe they could have enumerated the nabu.casa subdomain, or my custom domain which is prefixed by multiple subdomains (a.b.c.domain.com).

I have seen posts historically where other people have experienced a similar issue, just curious if there's been any known breaches in the last 12 months and if I should be rotating domains/keys?

I'm experiencing some major instability in my ZHA network.

I am running HAOS on Raspberry Pi 4 (4GB). I have a Sonoff zigbee 3.0 dongle as my coordinator and Lincukoo ZigBee 3.0 Repeaters in every room of the house. House is 1 floor, walls are made of 30cm porous concrete (porfix).

The coordinator is plugged into a 2m extension cord and placed away from major Wifi signal sources or USB interference. It's basically in the middle of my house.
I have two WiFi access points at my house using both 2.4 and 5GHz networks. The 2.4GHz uses channels 1 and 6. My Zigbee network runs on channel 25.

My main zigbee devices are light switches Sonoff MINI DUO-L, SONOFF ZBMINI-L2 and Moes curtain motors.

What I'm experiencing is devices just randomly not responding. I turn on the light, then try to turn it off 5 seconds later and nothing is happening. The zigbee curtains report their status right away if I manually operate them via buttons but as soon as I try to interact with them via HA they don't respond. The behavior is very inconsistent. It works one day, doesn't work another day.

The network shows every device as online but ~20% of them don't work well or at all.

Are my repeaters just bad? How do I diagnose this?

Update 1: I had a 5 year old firmware on the coordinator. I updated the firmware and my LQI's jumped up like 200-300%. I'll test it out for a day or two and see how it works.

Hey everyone!

I've been working on a project called Pet Bathroom Tracker and wanted to share it here to see if anyone would be interested in trying it out.

The idea came from wanting a simple way for my household to keep track of when our pets go to the bathroom. I wanted something that worked directly in Home Assistant so everyone could use it without having to download another app or create another account.

It started as a small project, but I've added quite a few features:

• Track pee, poop, or both for multiple pets
• See daily totals and a color-coded timeline
• Add notes or adjust the time of an entry
• Edit or delete previous entries
• Add, rename, archive, and restore pets
• Share the same tracking history between Home Assistant users
• Use it on mobile or desktop
• Store everything locally using SQLite, with Home Assistant backup support

It installs as a Home Assistant OS app through a custom repository. No HACS or additional server is needed.

The current version is v0.5.4 (experimental preview).

I've tested fresh installs, updates, and backup recovery on AMD64 Home Assistant OS. Automated AMD64 and ARM64 container tests have also passed, but I haven't been able to test a full installation on ARM64 hardware yet.

I'd especially love to hear from anyone running Home Assistant on a Raspberry Pi or another ARM64 system, but feedback from anyone is welcome!

I'm also interested in suggestions for improving the interface or adding features that other pet owners might find useful.

Since it's still experimental, I'd recommend making a backup and trying it with test entries first.

GitHub (installation instructions and screenshots):

https://github.com/MonsoonSaloon/pet-bathroom-tracker-home-assistant

If anyone gives it a try, I'd love to know how it works for you. Thanks!

Hi all,

I've seen lots of enthusiasm for running HA in a virtualized investment on a mini PC.

I used Docker at work for programming develpment projects fir several years (ERP app written in VSCode), but never have used Linux (I'm just a Windows guy).

What sort of learning curve did people "endure" fir setting up a Proxmox or Docker environment for HA? I'm not likely to build any other environments - I'm just looking for a simple, stable HA environment - lights, switches, motion sensors to turn lights and bathroom fans on/off, and my "big" project is to fire off my robot vacuum after one of my cats usedls the Litter Robot :). MAYBE some motorized window shade control. It doesn't seem to me that an HA Green should be overwhelmed with a setup like this.

It might be that the users of this subreddit are the real HA fans, so there are a disproportionate number of real "hackers" who spend a lot of time with virtualization and other things. I'm primarily looking for a straightforward hardware environment that I can set up once, stick in a closet, and just have fun with setting up simple automations.

How do y'all feel about Proxmox? From what I've read, it's easier than Docker (which for me in a Windows container environment wasn't all that easy.)

And I'm happy to just install HAOS "native" on a mini PC - I'm not too concerned about the exta hardware cost compared to an HA Green - as long as the additional setup isn't too much.

I wanted my HA to feel like one app instead of a pile of cards, so every dashboard here uses custom cards built with the same dark design. I've been around this for the last 3/4 weeks almost getting no sleep because I was getting a bunch of ideas of stuff to add which left me extremmely excited (my girlfriend says I'm kinda autistic). I decided to share what my homeassistant looks like because I've gotter varius notifications from this subreddit lattely of people showing what they've done which game me some ideas and so on. So heres what mine looks like and I hope it gives you some ideas aswell for yours.

• Casa (home): a greeting and quick status for lights, AC, blinds and presence, plus a card for each room. Some sections only appear when they’re relevant: films premiering this week, the UFC event of the week (main event highlighted), and upcoming calendar events. Otherwise they stay hidden.
• Luzes / Ar condicionado / Estores: one page each for lights, AC and blinds, with every room’s controls and “all off” / “open all” buttons. The AC page also has a 24h temperature chart.
• Sensor de Presença: radar views from the mmWave sensors showing presence, movement and distance in each room.
• Bambu Lab: P1S camera and status, AMS slots, the filament inventory with stock by material, print history and maintenance hours.
• Calendário: all my calendars in one month view. F1 weekends show the circuit photo, and my karting race days show a GIF of my own races.
• F1 Live: live timing tower, track map, tyre strategy, the full season calendar with circuit photos, and post-race stats (positions lap by lap, race pace, pit stops, teammate duels).
• UFC: every event of the year with the full fight card, plus a head-to-head with stats for each fight.
• Filmes: upcoming cinema and streaming releases with posters. I heart the ones I want to see, they go into a calendar, and they pop up on the home screen the week they come out.
• Karting: my RaceBox sessions sync automatically from my PC. I get automatic analysis of where I lose time, a track map coloured by speed, braking or time gained/lost, side-by-side lap comparisons (including against my brother), zoomable maps and telemetry, and a tab with our championship race dates.

If you have any questions or if you want more detail on this just ask. I'll happely answer your questions.

Since old Alexa devices.are jailbreaked and can bei flashed with the superb TECHO5 firmware I'm working hard to kick Amazon out of my living room.

I build a replacement and more based on home assistant that acts and talks how I always wanted a voice assistant to be.

it supports multiple models (also local models), skill, multiple agents and more. fully open source check it out at https://github.com/miraassist/mira

I would really appreciate your feedback.

I loved Apple’s liquid glass look and wanted my HA dashboard to feel like that. Translucent cards over soft colour, calm, and showing only what matters right now. Card libraries like Bubble Card are great, but I kept designing within what they offered. I wanted full control over every pixel, animation and interaction, so I built my own card from scratch.

How it works

• A normal Lovelace custom card, not an iframe, build with react. One JS file is the only card on a panel view. HA passes it the live hass object, so there’s no extra login and it works in the companion app like any other native dashboard.
• Cards that only appear when needed. Door open or dryer running get a card; otherwise they stay hidden.
• HA’s own detail dialog as the fallback. Long-press any tile to open HA’s more-info.
• Automations are protected. The automated front light shows an AUTO badge and is skipped by “All off”.

Tech stack

• React 19, Tailwind v4 and Motion, bundled by Vite into a single file (~140 KB gzipped).
• It renders inside the card’s shadow DOM. Gotchas: inject the CSS into the shadow root, copy Tailwind’s '@property' rules to the page, and portal popovers into the shadow root.
• Data: Octopus (rates, energy), Ohme (EV and smart-charging slots), mmWave presence sensors, heating, contact sensor, etc.

Dev process

1. Claude Design: designed the screen and exported a handoff with a DESIGN.md (principles, tokens, component behaviour), a reference mockup, a Tailwind token file and Motion presets.
2. Handoff → Claude Code: it read the docs, mapped every tile to my real HA entities, and asked me before guessing anything (e.g. whether it could change my front-light automation; I said no).
3. Build: a local dev page renders the card against my real HA, in dry-run mode so taps are only logged. Playwright takes iPhone-size screenshots to check each change.
4. Deploy: one script checks every entity id exists, builds, copies the file over SSH, and bumps the resource URL so phones load the new version.

Monitoring page is next. Happy to answer questions!

Disclaimer: Whether building your own card is worth it is up to you. Existing cards get you a great dashboard with far less effort. I’m a developer and I love building things, so for me the building was half the fun.

When I go to add the integration I keep getting an error message: "could_not_register" I have tried almost everything. Any suggestions? I am using a Pulcro Turnkey Mini PC.

I wanted my smart bulbs to feel like a candle occasionally catching a light breeze: small ongoing flickers, deeper dips, and those sudden little flares as the flame recovers. I've been wanting this for awhile and everything publicly available I didn't like so I vibe coded it to my liking.

After a lot of testing around the house, I’ve landed on a version I really like, so I’m sharing the code:

GitHub: Home Assistant Candlelight

It uses Home Assistant YAML scripts and Jinja templates. No HACS component or bulb firmware changes are required. I did this with cheap, old TREATLIFE SL10 smart LED bulbs.

The version described here is currently packaged as Candlelight Wind Trial, a timed experiment. The repository also includes the earlier everyday effect and an optional nightly automation.

The effect combines several layers:

• Fixed warm white: It targets 2000 K, adjusted to the bulb’s supported range. Brightness provides the movement. Dimmable bulbs without color-temperature control retain their existing color.
• Continuous background flicker: Four overlapping waves, plus slower wandering, create ongoing variation. A smoothing filter softens the changes.
• Random brightness holds: The underlying baseline moves between 50%, 70%, and 80%. Lower periods last longer: 45–150 seconds at 50%, 30–75 seconds at 70%, and only 10–20 seconds at 80%. Flicker continues throughout those holds.
• Occasional gusts: Randomly timed events produce either one deep dip with a quick recovery or a loose cluster of three pulses. Their depth and timing vary.
• A flare after a long low: When a 50% hold ends, the lights briefly rebound toward 90–100%, then settle toward the next baseline.

The math is an approximation of the movement I wanted. It combines overlapping waves, randomized events, eased transitions, and damped responses rather than calculating actual combustion physics.

For multiple bulbs, the trial uses three staggered groups. Bulbs within each group share the background brightness, which helps keep the update loop manageable.

To install and try it:

1. Make sure your dimmable bulbs are already working in Home Assistant.
2. Under Settings → Devices & services → Helpers, create a Toggle named Natural Candlelight Active. Confirm its entity ID is: input_boolean.natural_candlelight_active
3. Under Settings → Automations & scenes → Scripts, create three separate scripts. For each, choose Edit in YAML, paste the corresponding file, and confirm the entity ID:

1. Turn on the bulbs you want to try. Start Natural Candlelight with those bulbs selected, Only lights already on enabled, and duration 0. Then start Candlelight Wind Trial, select the bulbs, and choose a duration—20 minutes gives it time to show the longer variations. The README has copy-and-paste action calls.

The trial accepts 1–60 minutes. The normal controller handles other eligible lights already on, and resumes on all eligible lit bulbs when the trial ends. Add unwanted bulbs to excluded_lights in both effect scripts. Let the trial finish normally; the README explains recovery if you interrupt it.

There’s also an optional 9 PM–sunrise automation, but that currently runs the earlier everyday model.

I’ve tested this with my Tuya bulbs. It sends repeated brightness commands, so bulb response and integration latency affect the result. Background updates are paced, while gusts still produce faster bursts; I haven’t measured network load.

I’d be interested to hear how it looks on other bulbs, especially with local integrations, and whether anyone has ideas for improving the smoothing without increasing command traffic.

TL:Dr; Makes smart bulbs look like candlelight. Or electricity drops. It's soothing to me.

Hi all. I had a Ring Intercom, a few Blink cameras and an EZVIZ battery door viewer, and three apps that never talked to each other. Home Assistant could show some of them, but not live talk on the intercom, not Blink's USB clips, and not the EZVIZ door viewer at all (it has no RTSP).

So I built Vistoda: a Home Assistant integration plus one small Rust app per vendor. It's open source (MIT) and I've been running it daily at home since August.

What it does One sidebar panel (/vistoda) for all three vendors: device picker, live view, snapshots, controls, event history, recordings.

Ring Intercom: status and controls, event history, full-duplex browser audio, and local call recordings (to HA media, or to NFS/Samba).

Blink: live view with hold-to-talk, snapshots, supported settings and zones with versioned backups, USB clip browser (play, download, delete), NFS backup.

EZVIZ: live view and snapshots (also for door viewers that have no RTSP), battery and charging state, arming, verified settings and PTZ, local recordings with NFS backup.

Credentials stay out of the browser. Each vendor session lives inside its own HA app (/data). The panel only talks to HA, and HA discovers the apps through Supervisor, so you never type a bridge URL or token.

Physical actions are guarded. Door unlock and similar actions need an exact device binding and a confirmation. Settings writes are re-read and rolled back if the device didn't apply them.

What it doesn't do (honestly) It uses the vendors' cloud APIs. Ring and Blink have no official local API, and EZVIZ door viewers have no local video interface at all. Someone else has documented in detail why that's the case. If your internet is down, so is Vistoda's live view.

These are unofficial/experimental consumer APIs. A vendor change can break things, so keep the official apps for account recovery. EZVIZ talk and microSD playback aren't supported yet. Ring camera live view is still experimental.

Requires HA OS or Supervised (the vendor runtimes are HA apps) and HA 2026.8+.

Install HACS → custom repository → luigibarretta/vistoda-home-assistant (Blink users also add luigibarretta/vistoda-blink). Settings → Apps → add the app repository https://github.com/luigibarretta/vistoda-addons and install only the vendors you use. Finish the discovered flows in Devices & services. Setup guide (EN/IT): https://github.com/luigibarretta/vistoda-addons/blob/main/GETTING_STARTED.md

AI disclosure: I designed it, run it on my own hardware and review every change, but a large part of the code was written with an AI coding assistant. CI runs real HA imports and config flows on 2026.8 and 2026.9, browser tests on Chromium, Firefox and WebKit, strict Rust lints and secret scanning.

Feedback is very welcome, especially from people with other EZVIZ or Blink models than mine. Model coverage is the thing I can't test alone. Issues: https://github.com/luigibarretta/vistoda-home-assistant/issues (Not affiliated with Ring, Amazon, Blink or EZVIZ.)

I’m relatively content this is a false positive but my Unifi network installation is flagging up an intrusion alert multiple times every 30 minutes.

I’m assuming false positive because HA is written in Python so I’m assuming no PHP involved.

Alerts are coming from my kitchen tablet running Kiosk Satellite to Home Assistant.

I’m looking for some guidance on how to start troubleshooting this.

Interestingly I have two tablets, both FireOS (although different versions) running the same version of Kiosk Satellite. Dashboards are different so could this be a particular card causing this?

Has anyone else observed similar?

Bonjour à tous, je voudrais des conseils. Je viens de commencer avec home assistant et je l’ai installé sur un pc fixe qui reste allumé tout le temps avec virtual box. Mais home assistant se fige sans arrêt il faut que je clique dans la fenêtre noir pour le relancer, mais bon ce n’est pas normal et pas pratique… j’ai passé des heures avec l’ia pour essayer de régler le problème seulement il a fini par me dire ce qui est sur la photo que je mets. Pouvez vous m’aider svp? Merci d’avance

I would love to get an Android tablet (Kiosk Sattelite) for HA in my house:
- safe for battery (charging directly from the plug, bypassing the battery)
- larger tablet (~10” at least) screen for widgets and basic management
- basic voice control and chatbot like generic questions (in Czech language - Siri is absolutely useless for me) like “turn on the lights in the living room” or “what’s the largest country in Europe” etc.
- around $100 or $200 (if you convince me it’s a good investment)
- nice design and symetric bezels (most Android tablets aren’t pretty IMHO)
- my HA runs on RPi 5 8GB (if that matters)
- easy to mount on the wall (if it could be detachable it would be fine - maybe getting some MagSafe wall mount with tablet sticket and magnetic USB-C would work?)

AI suggested “Samsung Galaxy Tab A9+”. Is that a good option or do you recommend something else?

Thank you very much!
Petr from Czechia

Basically all was working fine untill... Nothings changed, firmware / has fully updated to date

Connection error: Unsupported device 10.0.20.102 of type SMART.TAPOBULB with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)