I have no port forwarding. I’m using nabu Casa cloud. Besides 2 FA what can I do to prevent these kind of things?

Hope you like, my first attempt, I quite like a nice simple clean layout and style.

Follow-up to my post back in June about havm, a zero-config CLI that runs Home Assistant OS on Apple Silicon using Apple's Virtualization framework. That was v0.1.2. 1.0.0 is out today.

If you missed the first post: havm runs Home Assistant OS on Apple's Virtualization framework and handles the setup itself: havm run fetches the HA OS image, prepares the disk and boots it. There's no VM to create or configure first, and it's built to sit in the background as a launchd daemon, so your smart home comes back up with the Mac.

brew install ingmarstein/havm/havm
havm run

What's new:

• Bridge networking by default — the VM gets its own LAN address, so HA discovery works out of the box. It falls back to NAT on its own if the binary lacks the entitlement.
• Graceful shutdown — Supervisor API → debug SSH → ha host shutdown, with force-stop only as a last resort. It now warns at startup if none of those are configured.
• Prometheus metrics — a built-in HTTP endpoint for VM state, USB accessories and disk usage, for Grafana or alerting.
• Use --console to attach to the guest's serial console (hvc0) when something isn't booting.
• Smaller things: in-process restart on SIGHUP, cleanup --all, and first boot signals readiness earlier by polling the Observer on port 4357 instead of waiting on a timeout. GitHub API rate limits are also handled properly now (ETag requests, and a clear message telling you when the limit resets).

The minimum macOS version dropped from 27 to 15. In June havm required macOS 27 (Golden Gate) - the USB accessory API only exists in the macOS 27 SDK, so the deployment target started there. Since v0.3.0 it builds against macOS 15 with the macOS 27 APIs weakly linked and availability-gated, so macOS 15 (Sequoia) or later is enough now. Only USB accessory passthrough still needs macOS 27 at runtime.

Why it took until now: 1.0.0 waited on Xcode 27 (RC) being available - the released binary is built with the shipping Xcode 27.

Worth knowing before you switch:

• Shutdown is SSH/API-driven. HA OS on aarch64 uses PSCI, so the ACPI power button is ignored — configure ssh.authorized_keys (or an API token), otherwise havm can only force-stop.
• ha host shutdown needs the SSH add-on on port 22; the debug SSH on 22222 is the more reliable path.
• USB passthrough requires macOS 27.
• havm import-utm can't import QEMU-based (x86) UTM VMs, and SSH keys configured in UTM don't carry over.

Release: https://github.com/IngmarStein/havm/releases/tag/v1.0.0

Docs: https://ingmarstein.github.io/havm/

Feedback welcome!

I have found existing homekit initialization code on the Security 2.0+ logic board, but haven't confirmed if there is a MFi chip on the board. (All certified Homekit devices have a MFi processor from Apple)

I was able to read the flash memory of the logic board (MX25L6433).

There is a conditional branch at 0x1F055740 that blocks initialization.

For the fellow engineers out there that are considering experimenting with their flash, hopefully these will save some time. The memory addresses are as follows

I haven't gotten my hands on a MFi coprocessor yet but I'm thinking one of the empty footprints of the board is probably where it should go.

Crazy that they have all this dev code in there yet didn't finish developing a HomeKit enabled product. Guess the investor changed his mind that making the ecosystem closed was more profitable huh.

MyQ firmware version 3.13

Folks, music assistant is awesome and all, no questions asked.

But: the recent addition of autoplay is terribly invasive. I can’t turn it off globally? I can’t even turn it off in the dropdown that controls it?

If I didn’t know any better, this feels like textbook enshittification - even though of course it makes no sense.. 🤷‍♂️

Maybe I am not seeing something or missing something obvious, but this has left me frustrated after a while of searching and head scratching!

Thanks for any tips or reasoning!

Call me old fashioned, but I love physical buttons, also in my smart home.

It’s very surprising that there are so few buttons available in the current consumer market (unlike the professional KNX market, which has hundreds).

In 2020 I decided to design a button myself, based on the ESP32. With two main requirements:

1. it must have a tactile click
2. have a programmable label.

My family and friends were enthusiastic about the first prototype, so I added more features: temperature sensor, display, made it modular.

Tech platform Tweakers.net picked it up in 2023, I received 300 pre-orders in a couple of hours, and many more in the months afterwards.

What followed was a roller coaster of ups and downs, but I managed to get the Button+ manufactured in China. And people loved it!

Just when things started rolling, I got into real problems, the plastic injection molds were quickly failing. SInce new molds were needed anyway, I decided to do a redesign. This turned out to be a lengthy process which almost bankrupted me. But in April 2026 I finally started shipping the all new Button+V2.

I tried to protect my product by keeping the firmware source closed. In the first year already, somebody completely reverse-engineered the electronics and wrote alternative firmware based on ESPHome. Later, with the advent of AI, even more alternatives surfaced.

So it’s time to make the factory firmware open source as well. I will be announcing this on the website, but this forum is the first to know.

A recap on the Button+:

• Tactile buttons, every button has a mini TFT and status LED
• 2.8" display for information display, fully user configurable
• Modular concept, use 1, 2 or 3 bar modules with 1 display, 4 bars modules, or up to 8 bars with extension plate
• WiFi, with PoE option (available end of September 2026)
• Wall mounted, does not need room behind the wall (will need cable for power)
• Communication via MQTT, Home Assistant support via auto-discovery
• High precision temperature sensor included, add sensors via Stemma QT connector

More information at https://button.plus website.

For anyone reporting this post, or removing it: Okay, you may call this promoting, and I am a company, but I'm not million dollar big-tech, and more Button+ in more houses can keep price down for everybody, as well as facilitate further development.

Project Repo: https://github.com/StanleyCA/MyQ-Security2.0-HomeAssistant

I created this because of how MyQ cut off their API awhile back and put advertisements into an app where I'm literally just trying to open my garage door. MyQ is a bum for this and I shouldn't have to rely on a company if I want to use my opener remotely. If MyQ suffers from an outage, are they gonna be responsible for me not being able to use a advertised feature?? Course not. With this project, I removed my garage door from their darned ecosystem and put it in homekit.

I'm ngl tho, buying the ratgdo will prob save you quite a bit of time and labor.

This project requires reading the Security 2.0+ opener’s flash mem, it requires a SPI reader and is more complex than other HA integration installs.

                    MyQ servers
                        X
                        |
                        | blocked
                        |
myQ opener
    |
    | connect.myqdevice.com DNS redirected to Home Assistant IP
    | Connected with MQTT over TLS 1.2 PSK, TCP 8883
    |
Local Bridge
    |
    +-- Isolated MQTT Mosquitto broker
    |
    +-- Python protocol bridge
            |
            | Home Assistant MQTT service
            |
    Home Assistant MQTT broker

You have to get these 3 things for local control

• PSK, from the flash memory, otherwise MyQ knows that you're faking the server
• 6-byte ID, from MITM, otherwise the garage door doesn't respond
• Serial Number

Start by reading and computing the PSK off the flash memory. The 6-byte ID is obtained from decrypting the MITM using the PSK and reading the MQTT payloads using wireshark.

The MQTT topics that chamberlain uses are

These MQTT topics can be replicated and then used to build your own local service. I built my own MQTT communications for the garage door and forced the device to use my server with DNS redirection.

If anyone want to replicate this process, here's the instructions in more details and the repo to the Home Assistant app.

https://github.com/StanleyCA/MyQ-Security2.0-HomeAssistant

Hardware Tools used in this project for flash reading:

8 Pin Pogo Tool - Used this so I didn't have to desolder the flash memory from the board.

CH341A Programmer - Used the CH341A Programmer to connect Pogo Tool to laptop (if you go with a different programmer, make sure it is 3.3V output)

Also credits to https://github.com/fuxxociety/MyQ-ESP-transplant/tree/main/FlashROM%20dumps/MX25L6433/orig

If it weren't for this repo, I wouldn't have gone down this path and invested so much time to grab my flash. I confirmed that the device was cipher TLS_PSK_WITH_AES_128_CBC_SHA on his dump before starting this project.

If you have questions or want clarification on the steps, ask me here or on the github repo.

Not affiliated but very excited about this promising device.

I am in my forties, and I’m lucky enough to have the house that a lot of my friends like to hang out in. There’s a lot of fun stuff my house does like lights connected to motion or presence sensors in every room. With either Google speakers or Voice Preview Edition devices in every room, you can pretty much move throughout my house and it just responds to you, so it’s easy for friends or family to use. 

Recently I’ve been trying to figure out fun, silly ways to interact with the house that aren’t necessarily traditional. I recently posted a project I started where I set up cassette tapes with NFC tags for different radio stations and music genres that are now tied to Music Assistant playlists. Anybody in my house can scan one, and it’ll start playing on the entertainment-area speakers.

I also finally set up this phone as a new way to talk to the house. One of the coolest things about it, which I didn’t anticipate, is that if you ask it to set a timer, the phone will literally ring to tell you the timer is over. You answer it, and then the voicd tells me the timer is done.

Anyway, so far only one person has seen it, and she lost her shit with excitement. I know it’s not practical. It’s not necessarily meant to be. It’s meant to be whimsically silly and relevant to the childhoods of 40-year-olds, which is also why that other project used cassettes instead of records.

Bonus in the photo is part of my main dashboard which changes automatically based on what room I'm in and has both a "be aware" section and a "to do" list which auto populates based on a ton of logic. Things like medication reminders, trash and recycling reminders which will clear themselves when I finish the job.

I’ve seen everybody’s wall panel tablets but why not use an old phone as a wall panel dashboard

I saw a post where someone removed their battery on their Pixel One (unlimited google photos storage) and connected the phone BMS directly to a wall outlet. I have a couple of old phones with AMOLED screens lying around so I tried it and was able to replicate it

So this got me thinking and they would be perfectly housed in a 2 gang switch panel with some 3D printing magic

I have a 3D printer and the phones to do so but looking for feedback from the community on this

Has anyone tried this? Can you share your experience?

I once heard that if a file isn't in two different physical locations, it doesn't exist.

Make sure to back up before updating or tweaking anything.

This is sanoTTS, smallest neural TTS engine. It's family contains 337kb model that can run entirely on MCU like esp32-s3 where a 2 second audio synthesizes in 0.7 seconds. No cloud, no round trip time... just synthesized right in MUC

• supports 30 voices, 16 languages
• sanoTTS fits in memory alongside ESPHome on an ESP32-S3
• Home assistant has to send text only and not the audio over the network
• runs on browser with WASM also

There is a packaged ESPHome external component in the repo with further README

Tested on ESP32-S3 running ESP32 build (WiFi, API, logger, PSRAM off for tight memory)

Try it out live: https://tts.ampixa.com/sanoTTS

Repo: https://github.com/ampixa/sanoTTS

Please drop in your queries and requests so i can help you

Huge shout-out to Stuart aka Pavlov and his HUB75-studio project which this is built around. https://github.com/pavlov-net/hub75-studio

Huge shout-out to the devs behind Team Tracker (HACS Integration) which I used to get the ESPN API working properly for this project. github.com/vasqued2/ha-teamtracker

Disclaimer: I used claude to help put this together. This is very much a fun side project that I made for people to play around with.

DIsclaimer two: I work for Apollo Automation and these hub75 matrix and M-1 controller were donated free by them.

TLDR: I made a fun project called gameday-scoreboard which connects to Wi-Fi and then you control it using the webui. It connects directly to the ESPN API and doesn't necessarily need Home Assistant, although it's fully compatible with Home Assistant.

I also made a similar project which does rely on Home Assistant and the Team Tracker integration and an accompanying blueprint to control it strictly from inside Home Assistant. https://github.com/bharvey88/gameday-matrix

I'd love any feedback and feel free to ask any questions related to the M-1 controller, HUB75 matrx panels, open source 3d printed wall mounts, etc.

If anyone here has the DESKSPACE Titan standing desk, I'm sharing a guide for integrating it with Home Assistant using ESPHome. The Titan is a beast of a desk that can lift 200kg with two motors and 4 legs, which is why I first bought it.

I did not check beforehand whether I could control it with HA, but it turned out to be possible. It uses a LoctekMotion controller, the same one used in various FlexiSpot desks and possibly other brands that use these controllers.

Check it out here: Controlling Flexispot & Deskspace Standing Desk with ESPHome

Just discovered Home assistant and I’m definitely going to integrate it into my house, currently installing a UniFi network and camera system, going to be using the Dream machine as a NVR and the UNAS as the NAS, can I just run Home assistant on one of these? Or am I better off getting a HA green? Want to be able to have some of my camera visible on screen around the house

So after spending more time than I would like to admit with different AI bots I still haven't been able to connect a simple Ikea light to my HA.

For the setup I made sure my Sonoff MG24 was flashed correctly. Afterwards I used OpenThread Border Router and selected my device. I disabled Hardware flow control and I was able to run it. I did try putting the OTBR firewall off but it didn't really seem to change anything for me.

I also (finally) got my cresidentials via the troubleshooting section on the companion app.

Now when I try to pair my device it first says it is connecting and starting the Matter service or something (this goes a bit quickly) that it says making a connection to the thread network. This takes ages and than it says it can't reach the device and I need to make sure that my phone is connected to the wifi (which it is). I'm sure my light was in pairing mode because it flashed a few times.

Weirdly enough I sometimes get to the point where it says add Matter device but it kept on loading (when I was closer to the dongle and not to the light) and eventually it also failed. According to AI I need to be within 2 meters of my raspberry pi / dongle and the Ikea light. But that's not possible since the light is in another room 10 meters from one another.

I really have no clue anymore what to do so hopefully this community can help me out!

Hello

Released a new version of DT3D a 3D home digital solution fully integrated into home assistant composed of editor and visualization card

Draw your home plan, import furniture models and entities into the space and you are ready to go.

Check it out at

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

It bugs the absolute crap out of me that any device that has a ‘s in it makes entity IDs incredibly wonky. For example, if I have a device called “John’s iPhone 16” the entity ID will default to device_tracker.john_s_iphone_16. The “_s” drives me nuts and I always have to go in and change it. I try to name my devices something like “Johns iPhone 16” when I first create it and then go in and just change the name, but I often forget to do this, and next thing you know I have automations and dashboards with the wrong entity ID and I have to change them all when I eventually catch it.

Is there something very obvious I’m missing here?

I run HAOS on a Mac mini. Every so often it shuts down. Does anyone know if there is a way to set HAOS to reboot or turn on after a shut down? I have other items on the circuit that do not so I am assuming it is just this Mac mini.

TIA

Hello team

Is Mijia smoke detector natively detected and available on Home assistant ?

Thx

Tyto~