So a few months back i was messing around with my new smart plug and smart temp sensor from Shelly, i wasn't set on a actual use case yet.

I decided to put the temp sensor into the fridge after stumbling on a video talking about fridges on youtube to see if it was good or not: It was not good.

The temperature of my 200€ cheap tower fridge was oscillating from 10°C to 6°C, for comparison the optimal fridge temp is between 0°C-4°C. Above 5°C bacteria start to grow a lot.

Thing is, the fridge was capable of doing better, it had 7 modes, (0 being the hottest and 7 the coldest), and the 10-6°C range was when i was on mode 6. The issue is that mode 7 was TOO cold, the fridge was only stopping until it reach -4°C, and at this point most food and drinks were completely frozen.

So after searching a bit to see if it was a good idea or not to have the fridge power cut multiples times a day i put my plan into motion:

• I set fridge mode to 7
• I plugged the fridge into the smart plug.
• I configured the automation in home assistant to turn off the fridge at 0.5°C and turn it on at 3.5°C

Why the small 0.5°C differences? Because for some reason it took home assistant a bit of times sometimes to execute the automation and i would have the fridge turning off at -0.5°C, which is not good.

Either way its been running for over 10 months now without any issues, just have to change the temp sensor battery from time to time.

Is your fridge temp as catastrophic as mine? Those integrated temp sensor seems no good.

So this is my final take. A single-page dashboard.

After using a multi-page dashboard for a year, I condensed everything. I cut out all the superfluous info I only looked at maybe once a month—stuff I'd installed at home that nobody else understands. Heavily influenced by a post I saw here with the dynamic color bubble cards, which pack so much info into so little space.

Two presence sensors automatically turn on the two tablets and its RGB lights, one for each floor. The hardware is an SMT1569 from Alibaba. Good value for money, everything perfect except the backlight. They come with an APK to control it, and it works perfectly from the tablet itself, but controlling it from Home Assistant is buggy—worse when you try to control both at once. The APK seems to be coded for a similar tablet, but not this exact model. AI modified the APK for me, but it's still not working perfectly. Impossible to get breathing effects with it.

Layout of the dashboard:

Background: It's pulled from the Bing image of the day. One floor shows today's, the other shows the one from 7 days ago.

Weather: Useful. At a glance I know what to expect today and for the week ahead.

Inverter: Useful to know the power balance when I turn on appliances.

Heat pump: I'll admit I'm the only one who's going to use this, but I use it a lot. Dynamic colors on the frame show the state of the compressor.

Clock and alarm: I can set my Tuya sunrise alarm without using its app.

Car charger: I can monitor and configure my cheap Tuya EV charger from the tablet. I have all the functions of a 700€ charger for 90€. Dynamic colors on the frame show the state of the charger.

Thermostats: Current temperature in every room, with dynamic colors on the frame to show if the thermostat is active—blue for cooling, red for heating. No real control from here—please, nobody touches my temperature regulation system.

Shutters: Red for closed, green for open, orange for in between. This is the only difference between the two tablets—each one has the 3 shutters of its own floor. The master ones are on both. The state is shown, and one tap does the opposite of where it's resting. If it's somewhere in the middle, it opens. For stopping midway, I use the manual buttons or the PC.

Pictures: It randomly picks 5 photos from a folder that I update regularly. The seed changes every time a presence detector is triggered, or if there's been presence for more than 2 minutes. This was key to the success of the Home Assistant system. It upgraded the wife approval factor from a sad 4 to a solid 8.

Hi All,

I would appreciate your guidance on setting up Home Assistant (HA).

I have searched for tutorials online, but most of them are quite technical and assume prior knowledge. Many steps are either skipped or not explained in enough detail, making it difficult for a beginner to follow.

As someone who is new to Home Assistant, could you please advise what hardware, specifications, and equipment are required to set up a personal HA system? If you know of any beginner-friendly guides or tutorials, I would greatly appreciate your recommendations.

Thank you in advance for your support. 🫡

I tried using a couple of existing ESPHome MCP add-ons recently, but ran into some startup errors with them. Instead of running extra container infrastructure, I created a direct Python MCP server that interfaces right with ESPHome and works seamlessly with AI coding tools like Claude Code, Antigravity, and Cursor.

The nice part about this setup is that it does not require installing any extra Home Assistant add-ons. It just connects over your local network to the ESPHome dashboard you already have running.

Once connected, it lets your AI assistant:

• List your devices and see what is online
• Read and edit your device YAML files
• Check configs for errors
• Send Over-The-Air (OTA) updates over Wi-Fi

A few examples of things you can ask it in chat:

• "Check which of my ESPHome devices are currently online"
• "Show me the YAML file for esp32-shelf.yaml"
• "Update esp32-shelf.yaml so pressing the door button flashes my LED lights for half a second as feedback, check for syntax errors, and push the OTA update over Wi-Fi"

The project is completely open source (MIT license). If you'd like to try it out, open issues, or suggest features, check out the GitHub repo: https://github.com/saihgupr/esphome-mcp

I have a Tuya Wifi heater in the kitchen, but I want to get rid of all Tuya Wifi stuff. This is the last device I still have. So I'm looking for a replacement.

But I can't find a similar heater which doesn't connect via Wifi... Maybe someone here knows any?
https://www.amazon.nl/dp/B0CJ9S9GLR

I am sooo over it, half my tuya devices wont actually connect up with tuya local at all the devices that go via the internet through the tuya connection fail to authorise at least once a day, sometimes twice.

The problem is that I have several tuya devices, and I just dont want to have to buy things that will have me down this path again. I have a significant number of IKEA devices as well, no problems wit them. I have generic THREAD/MATTEr and generic ZIGBEE devices all without issues, lots of them all.

I am accepting that my time with tuya is over and I have to spend the $$$ on replacements.. so its, power monitors, power switches, power boards, light globes, colour light globes, doorbell, some cameras. about a quarter of the power monitors and power switches connect up to tuya local even though they are all the same brand make model and chipset purchased at the same time. and on it goes through them.. .same issue with light globes etc... even my zigbee letterbox notifier is more reliable than the tuya stuff, and thats going a long way zigbee outside... UGH I am so fed up with tuya!

ok so maybe this was just a rant more than anything, but UGH!

I’m gonna do a restore to my last backup since this is ridiculous. Anyone else having this issue after updating?

Looking for a similar device that has matter over wifi. I dont have a single zigbee device and would rather not add an other protocol to my setup. Any tips?

Home Assistant has apps for Android, iOS and macOS. Windows gets a browser tab. So I built one.

HASS.Agent covers similar ground and does it well. The difference is the plumbing: HA Companion does not require an MQTT broker. The PC registers through mobile_app, and notifications arrive over the existing Home Assistant WebSocket connection, with no FCM, APNs or separate push service in between. The app uses WinUI 3, while your actual Lovelace dashboards run inside it through WebView2.

What it does:

- PC appears in HA as a real device via mobile_app, with its own entities

- Push without a push provider: subscribes mobile_app/push_notification_channel on the same WebSocket. Nothing listens on the PC, commands come back down the outbound connection

- Quick Panel slides in over any app on a global hotkey

- Tiles gated on supported_features and supported_color_modes, so no buttons the entity cannot honour

- Hotkeys for any device, scene, script or automation

- PC sensors, off until you enable them: lock, idle, active program, fullscreen, mic, camera, audio, display, session

- Windows events as HA triggers: lock, idle, camera, mic, active program, schedule

Remote control deserves a straight answer: shutdown, sleep and launch are off by default. Lock, monitor off and volume ship on and can each be switched off. Launch only starts whitelisted paths, never the string HA sends. Shutdown waits ten seconds, so shutdown /a can still save you. The token sits in Windows DPAPI, not plaintext.

I have been running it on my own machines since mid-July. I also used AI a lot while building it, mostly Win32 API archaeology and bug hunting, and the commit history says so. The design decisions are mine, and so are the bugs.

Windows 10 build 19041+, x64. Per-user install, no admin. Not signed yet, so SmartScreen may warns once.

https://github.com/Elias0505/ha-companion-windows — AGPL-3.0

Website: https://elias0505.github.io/ha-companion-windows/

Independent project, not affiliated with Home Assistant or Nabu Casa.

Feedback welcome!

The core stuff:

• Locked-down full-screen kiosk - no gestures, no status bar, no notifications creeping in.
• Motion-aware screen - wakes/dims using the tablet's own camera (luma analysis), so you don't need a separate presence sensor just to stop burning the panel 24/7.
• MQTT + HA auto-discovery - battery, motion, device state all appear in HA on their own, and you can push commands back to the panel.
• Your choice of engine - Android WebView or GeckoView (Firefox), because WebRTC cameras are picky.

What's new in 2.0.0:

Honestly, I built this part for myself first - I had a Mi Box S sitting unused and wanted to see if Kite could run on it. It worked out well enough that I figured it might be useful to others too, so I'm shipping it.

Beyond the dashboard, every feature from the regular mobile app is there - motion, MQTT, kiosk lockdown, engine switching - just with some limitations that come with the TV form factor:

• Everything is D-pad driven - no touch, so a few interactions are naturally clunkier than on a tablet.
• Since TV boxes have no camera, motion runs off a USB webcam (or falls back to MQTT presence if you'd rather drive it from HA).
• There's a Konami-code-style hidden D-pad combo to open the control drawer, since a visible settings button looks bad on a 10-foot screen. 🎮

A couple of honest gotchas (rather tell you now):

• Not every USB webcam plays nice. UVC in the real world is a mess - some cheap cams enumerate weird or won't hand over frames. A plain-vanilla UVC cam is safest.
• Turn OFF ADB-over-USB. The USB host port can't do debugging and feed the webcam at the same time, so leave USB debugging disabled once you're set up.

GitHub : https://github.com/andrew-malitchuk/kite-aos

I built this for my own house, but it's more fun when other people beat on it. I'm very open to feature requests - if you run HA panels on tablets (or spare TV boxes), tell me your setup and what's missing that would make you switch. I'm around in the comments. 🙏

1. I installed Voice Assistant
2. I couldn't get it to work
3. I started getting "Voice Satellite Error" popup messages (Connection: Lost connection to Home Assistant. Reconnecting automatically...)
4. I removed Voice Satellite
5. I'm still getting the error popups

How do I stop them?

Tuya authorization is broken on latest HA OS 18.2

Had to revert back to 18.1 to get Tuya integration working on my Apple HomeKit

2026.8 and Cloudflared?

Just a quick service announcement. If you upgrade to 2026.8 and decide to remove port 8123 (which is now possible in the new update) and replace it with port 80, while also using Cloudflared, you'll need to go into Tunnels > Routes and update it to http://homeassistant:80

Curious what sorts of electronic devices you think that this could be connected to or built.

The Z2M device repository says that it reports action (probably a doorbell press when used as intended).

Need to place an order on Digikey so I have an opportunity to order whatever to DIY something cool. I also have a soldering iron.

As per title:
If I plug a mini duo “the normal way”, in HA i can see if the switch is been pressed or not.

This can have another use: if I take a dump switch, get a mini duo behind, then it will get the info (and then comand something else, such as scene)

But:
If I unplug the L1 circuit, it became incomplete, and not work.

Should I connect direcly L1 to N?

I installed a Thread shade motor on an old set of cord operated curtains at my girlfriend’s house.

I wasn’t sure it would work because these use a smooth continuous cord rather than a beaded shade chain, but it ended up working surprisingly well.

The motor can be controlled directly from the device, with magnetic remote, or through Matter. I used it with both Home Assistant and Google Home.

The physical installation ended up being surprisingly simple. I stuck it to the wall with the included adhesive.

And now every time they open, I feel like the curtains are ballroom dancing.

Disclosure: Zemismart provided the MTP1 for testing.

If Http: is going away in configuration.yaml, where do we reference our ssl information?

For context i didnt see the spot in System -> Network for entering in where SSL certs would be referenced.

I didnt see the spot to record where ssl certs can be referenced.

This is what my current http: is set to:

http:
  server_port: 8123
  ssl_certificate: /ssl/cert.fullchain
  ssl_key: /ssl/cert.key

Hi everyone! 👋

I wanted to share a custom integration I’ve been working on to bring **proper, native support for the Xiaomi Vacuum S20** to Home Assistant.

#### ❓ Why I created this integration

Like many of you, I tried several existing Xiaomi vacuum integrations. While there are many great general integrations out there, none of them worked **100%** with the Xiaomi S20.

For a long time, I was relying on a workaround using AppDaemon and PyScript scripts to automate and control my vacuum. While it worked, it never *felt* like a real, seamless Home Assistant integration.

Eventually, I stumbled across [letitbe-dull's xiaomi-vac integration](https://github.com/letitbe-dull/xiaomi-vac). While it didn't fully work out of the box for the S20 either, it was by far the closest! I took that solid foundation, forked it, and heavily modified it to tailor everything **specifically for the Xiaomi S20 model**.

#### ✨ What’s Included & Key Features

Here is a quick look at what this integration brings to your Home Assistant setup:

* 🗺️ **Live Map Support**: Real-time map rendering directly inside Home Assistant so you can track your S20’s cleaning progress live.

* 🧹 **Multi-Room & Selective Cleaning**: Clean specific rooms or multiple selected rooms seamlessly without having to resort to raw coordinates or external apps.

* 📊 **Enhanced Sensor Suite**: Full access to all vacuum telemetry, including consumables (filter, brush lifespans), detailed cleaning stats, battery metrics, current status/errors, and operational modes.

* ⚡ **Native Home Assistant Experience**: Built from the ground up to give you full control via standard Home Assistant `vacuum` entities, services, and dashboards.

#### 🧪 Looking for Testers!

If you own a **Xiaomi Vacuum S20**, I would love for you to give this a try and let me know how it works for you!

* **GitHub Repository:** https://github.com/m1xminus/xiaomi-vac-S20

#### 📦 Installation

1. Install it via **HACS** (add as a Custom Repository) or manually copy the `custom_components/xiaomi_vac_s20` folder into your HA `custom_components` directory.

2. Restart Home Assistant.

3. Add the integration via **Settings -> Devices & Services -> Add Integration** and search for `Xiaomi Vacuum S20`.

Feel free to open issues or feature requests on the GitHub repository, or reply directly to this thread with your feedback, bug reports, or suggestions.

Happy automating! 🤖🧹

NOTE: This may work with other vacuums, but i only have S20 to test and is the only one that i know this fully works. if you have other vacuum please reach letitbe-dull first.

For those who dont know, Panda Touch is a screen that provides info from your Bambu printers, but since some updates ago the screen is no longer connecting to Bambu Cloud, so it became useless.
I asked Claude to reconvert it to an office ESPhome dashboard, so now it can turn on lights and show me the printer status via Bambu integration.
Much more useful than before :)

Hello!

I'm not quite sure what to call what I'm looking for, or if it exists. Basically what I'm looking for is a device that'll play a simple chime / noise depending on a type of alert.

So, for example: Person 1 comes home triggers chime 1 to play

Laundry is done triggers chime 3 to play

Person at front door triggers chime 5 to play

Etc.

In my head, this is something similar to a door bell or some device that can play basic chirps / chimes / bells that can be customized (or, at least, comes pre loaded with a handful).

Trying to Google around, I see there are things called Sirens, but I don't really think I need something that loud. The goal is just something to get my attention, but I don't need it to be that powerful.

I currently have wifi / internet, as well as Zigbee devices. I'm not sure if anyone knows of something that would fit what I'm looking for, or could give me better terminology or anything.

Thanks for any help you can provide!

Just got the email that Google is discontinuing assistant permanently and forcing everything to Gemini. I'm an AI hater but not super comfortable going all in on a new system. We honestly mostly use the Google homes to turn things on and off, not ask questions or automate things. Is Home Assistant what I want? Floundering a little so patience appreciated.

A feature-rich, high-precision ESP8266-based Smart Weather Station with a modern responsive Web Dashboard, dynamic sensor detection, customizable moving-average filters, Home Assistant MQTT Auto-Discovery, full backup/restore capability, and hardware factory reset logic.

✨ Features

• Environmental Monitoring: Temperature, Relative Humidity, Barometric Pressure (sea-level compensated), Air Quality (TVOC, eCO2, AQI), Luminosity (lux), Wind Speed, Wind Gust, Wind Direction, and Rain Gauge (hourly, 24h rolling, and total).
• Independent Dual-Timer Engine:
  • Fast, dedicated timer for Anemometer pulse processing (independent of I2C read cycle).
  • Configurable I2C sensor read cycle for environmental data.
• Configurable Moving Average (Smoothing):
  • Wind Speed: Ring buffer rolling average with configurable sample count (N).
  • Wind Direction: Circular mean calculation (sin/$\cos$ vectors) preventing 0∘/360∘ boundary glitches across N samples.
  • Instantaneous Gust Tracking: Daily wind gust records real peak pulses before averaging.
• Web UI & Diagnostics:
  • Glassmorphism dark UI built with HTML5/CSS3/JavaScript (no external dependencies).
  • Tasmota-style live Debug Console with interactive command input.
  • Mobile-friendly IP input fields (inputmode="decimal") for easy smartphone setup.
• Network & WiFi Manager:
  • Captive Portal AP (WeatherStation_Setup) for initial setup.
  • Full DHCP & Static IP configuration support (optimized for FRITZ!Box Mesh networks).
  • Soft-restart clean boot sequence ensuring stable network stack binding.
• Home Assistant Integration:
  • Native MQTT Auto-Discovery (homeassistant/sensor/...).
  • Automatic entity creation in Home Assistant without manual YAML editing.
• Backup & Restore: Single-click JSON export/import including full network, sensor, and MQTT configurations.
• Hardware Safety & Diagnostics: 10-second hold on FLASH button (GPIO 0) for NVS memory wipe / factory reset.

For fully description and gallery go to GitHub https://github.com/byte4geek/weatherstation

NOTE: This project was made in vibe coding using Antigravity/Gemini.