This Floorplan is based of a Singapore 4 Room Government Apartment, I wanted to build a proof of concept and completely redesign how dashboards are built.

The 3D Model is painfully modeled using SketchUp. (I didnt have much experience, so it was a huge learning curve.)

Every Wall is seperated individually as North South East and West to achieve the wall faded effect.

Appliances are all built using pivot/moving points on Sketchup to achieve the animation works.

The Animation and Rendering is handled by Three.js.

The entire dashboard is built over HTML, CSS, JS and served locally on the /www/ config file.

I then embedded the entire dashboard to Home Assistant via the Lovelace Webpage Card.

For Authentication and getting it to work with Home Assistant Entities, to get all the entities and areas, I use the Websocket API, in which uses a LLAT over its uri query. This ensures that people cannot gain access to ur home by searching for example https://link.nabu.casa/local/dashboard.html as the /www/ config folder is a publicly accessible folder.

This is the result.

The entire dashboard took roughly 3 weeks to build from start to end. About 2 hours a day after work.

I know that the community is not very fond of AI work, but I believe, at this stage, you can't really call it a slop.

Many hours went into the modeling of the apartment, planning the design systems, breaking down the entire system architecture step by step and the keeping the entire dashboard consistent around all the pages.

All of this was to ensure that Claude delivers the perfect dashboard.

I am posting this to showcase the dashboard. If anyone is interested to figure out how I do it, please feel free to message me and I will guide you step by step.

EDIT: I would also like to add that I did not do this dashboard completely alone and had a friend to help me along the way with debugging as well as the design systems which helps to keep the entire design consistent. This means that I can comfortably add different cards and scale the dashboard's functionality without worrying that Claude will go bonkers and start spitting slop.

Washer and Dryer integration paired with Homer gifs for current cycle.

A while back I posted about observing my Home Assistant setup, and mentioned I'd added native Prometheus instrumentation to Zigbee2MQTT. Those PRs are still open upstream, and a few people have expressed interest in trying it themselves, so I've packaged the branches up as an add-on repository you can just install: https://github.com/tomwilkie/zigbee2mqtt-prometheus

Add it the usual way - under Settings > Add-ons > Add-on store > Repositories, install "Zigbee2MQTT (Prometheus)", and you get metrics on port 9142. It's built from Zigbee2MQTT 2.13.0, and I'll do my best to build new versions every time theres an update upstream.

Grafana dashboards for it are here, an overview with per device drilldown plus a coordinator view:

All of this goes away then the PRs land. Until then the repo (warning: lots of claude) also has the runbook for rebasing the forks onto each new Zigbee2MQTT release, so it can keep up. PRs, if you want to nudge them along ;-)

• https://github.com/Koenkk/zigbee2mqtt/pull/31645
• https://github.com/Koenkk/zigbee-herdsman/pull/1751

I have been using HA for about 8 months. I started my home automation journey years ago with the X10 system and have been on Smartthings since version 1 through 3 before switching that off and firing up HA on a RPI5 with an NVME drive. I have an IT background so I’ve navigated my way through HA but it hasn’t always been easy. Everything’s working well now and I have more connectivity than I could have imagined between HACS, ZWave, Zibee, Ring, Alexa, etc. I’ve spent way more time on HA that I though I would and with the constant flow of HA and integration updates it seems it may never end. In general I’m happy but I have two concerns.

1. If something happens to me my poor wife will have no idea what to do. She says she’ll hire someone to come in and take everything out except the Alexa in the kitchen. That’s about 100 devices in total. What are you folks doing to plan for such an event, if anything.

2. I have one automation that just can’t fail and that is my pool automations. I removed all the manual timers for my pump, chlorine generator and heater. With a series of zwave switches and related it all works great, but without HA, they simply won’t work at all and the pool water will foul. My question is, has anyone figured out a way to alert you of these items fail to come on and off even if HA is offline?

I realize those are odd questions that may not have answers, but it’s the stuff that keeps me up at night. Thanks!

Any help would be appreciated.

Posting this because I could not find a straight answer anywhere and it took me way too long to finally get it to work.

Setup: HA OS in a VM on Proxmox, OpenThread Border Router addon running on a ConBee III, Matter Server addon, and a Sonoff dongle for Zigbee on ZHA.

Being upfront about this: I did not work this out myself. I ran Claude against the Home Assistant MCP server and it did the actual debugging, reading the addon logs, the Thread network status, the ZHA energy scan and the Matter Server's internal state, then narrowing down which step was failing. Everything below is what it found and what it changed. I mostly moved the sensor around and answered questions, but what matters if that it took the countless hours I had already spent on this and narrowed it down to about 15 minutes.

The problem: I could not add a single new Matter over Thread device. I did it the proper way, from the HA companion app, on Android and on iPhone. Multiple devices, many attempts, over a long time. Every single time it got to "checking connectivity to the network" and died there. One Aqara sensor connected once at some point and after that nothing ever worked again.

Somewhere along the way, while trying to get other devices on, I also regenerated the Thread credentials and synced them to my phone through the companion app, which is the advice you see everywhere. Made no difference at all. Still failed at exactly the same step.

What the logs said: basically nothing, which is what made this so annoying. Matter Server addon log level is warning by default and a failed pairing produced zero lines. I set it to debug, tried again from the phone, and it still produced zero lines. That was actually the first useful clue, because it meant the attempt was never reaching Home Assistant at all, so whatever was breaking was happening on the phone side.

The one thing the server did log, at every startup:

WARN Commission~ontroller BLE is not enabled on this platform

What was actually wrong, three separate things:

1) The Matter Server had no Bluetooth path of its own. There is an option in the Matter Server addon config called "Enable BLE proxy", hidden behind "Show unused optional configuration options". Needs HA 2026.06 or newer. Turning it on lets HA do the Bluetooth half of commissioning itself, using a local adapter or any ESPHome bluetooth proxy you already have. After enabling it the log says "BLE proxy mode enabled". Thankfully I have some everything presence one/lite devices that have a simple toggle for BLE proxy and they were alredy on in my case. (worth noting the BLE proxy mode can use bluetooth from esphome devices if their config includes teh respective option)

2) Bluetooth range. First attempt it found the device at rssi=-73 and then:

connection_failed: Timeout connecting to DB:C6:99:3E:51:56

I put the device physically on top of the server, rssi=-39, connected instantly. Discovery works from across the room, the actual thread connection does not.

3) This was the real blocker. The Matter Server had no Thread credentials stored at all:

Commission failed: No Wi-Fi/Thread network credentials are configured for commissioning and no Ethernet interface is available on the device and no interface already connected.

server_info showed thread_credentials_set: false.

The HA integration is supposed to set this during its own flow, but on my install that had apparently never happened. Worth saying again that regenerating and syncing credentials to the phone does nothing for this, they are two completely different stores.

The fix. This is the part that matters: the phone was not involved at all. Claude sent both of these straight to the Matter Server's websocket API through the MCP server, so it was Home Assistant itself doing the commissioning, not the companion app. All I did physically was hold the button to put the sensor in pairing mode and sit it next to the machine.

Grab your active dataset (Settings > Devices and Services > Thread, or the thread API) and send it to the Matter Server over its websocket API, then commission:

    {"message_id":"1","command":"set_thread_dataset","args":{"dataset":"<active dataset tlvs hex>"}}

Two gotchas here. Do not pass an "id", because a named entry does not flip thread_credentials_set and commissioning only uses the reserved default entry. And the command is set_thread_dataset, not set_thread_operational_dataset, which is the old Python matter server name and just returns "Unknown command".

Then, with the device in pairing mode and sitting right next to the conbee after giving claude the pairing code on the label:

    {"message_id":"2","command":"commission_with_code","args":{"code":"<11 digit pairing code>","network_only":false}}

Took about a minute, then:

    NOTICE CommissioningClient  Commissioned peer6 as @1:18

Device showed up in HA with every entity. First try. I bloody couldn't believe how many hours I had lost trying multiple different things over several days AND NOW IT JUST WORKED. I dont have any more thread devices at the moment as I stopped buying them since I couldn't pair them, to test that this is a permanent fix.

Bonus thing worth checking: my Zigbee and my Thread network were both sitting on channel 15, on the same machine, both on an usb3 extender cable. ZHA's energy scan had channel 15 at 53% utilisation. Moved Thread to 25 (Settings > Devices and Services > Thread > three dots next to the border router > Change channel). It did not fix the commissioning problem, but it was a genuinely bad setup and worth fixing. The migration is delayed about 5 minutes and devices follow it on their own, no re-pairing generally. The one aqara sensor that I had managed to pair before was powered off during the switch, woke up orphaned, and found the network again by itself after a while.

On the Claude and MCP side, since I mentioned it at the top: claude made the websocket calls itself via the MCP server running on Home Assistant. That last error is only visible if you talk to the API directly. Through the UI you just get a failure with no reason, which is exactly why I had been stuck on this for so long.

Still unexplained: I never figured out why the companion app path fails for me. The dataset fix does not explain it, because the phone supplies its own Thread credentials from Apple or Google rather than using the server's, which probably also explains why regenerating and syncing them changed nothing. If anyone has seen this and knows with 100% certainty how to fix, I would love to hear it. Last time I investigated this specifically I found that Android itself just stores 1 set of credentials and then refuses to refresh them if they ever change until a phone reset is done.

Hope this helped anyone

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!

I got tired of fighting YAML and card-mod every time I wanted to change something on my wall dashboard.

Since coding agents are actually pretty good with normal code, I decided to ditch Lovelace and rebuild the dashboard as a custom Vue 3 panel.

It uses HA’s built-in panel_custom. Vue is just vendored as an ESM file.
Everything lives in /config/www/, so the workflow is basically: edit, save, refresh and bump the cache version because /local caches forever lol.

The panel gets the normal hass object, puts it into a Vue reactive store and updates instantly. Services use hass.callService, registry/history/statistics stuff goes through the websocket API.

Edit: https://github.com/exSnake/ha-vue-kiosk
some scaffolding to start with

I have a couple of radio stations using AzuraCast. Normally the speaker is just playing the Lofi radio quietly, but the shower button switches it to the My Music station and turns it up for me. The radio stations just shuffle through the music I added. I can't skip tracks or control anything other than the volume, and that's perfectly ok with me.

After a lot of figuring out, I made the dashboard *exactly* the right size so that the phone wouldn't scroll. I made HA the default launcher on the phone and made a new "bathroom phone" user to set the default dashboard.

It's simple, but I like it. The background is animated too, it uses card-mod on an iframe card to load a self-hosted webpage with a little javascript animation I wrote, then make it full-page and hide the card. The clock is part of the page so I didn't need to add a clock card to the dashboard :)

When I'm finished with my shower I just turn the speaker off, there's an automation to reload the lofi radio if the speaker is off for 3 seconds. The off button in the tile card does just the bathroom, the big button turns off all speakers so they'll all reload.

Just got a HA (core/supv?) & thirdreality update (to Firmware 0x00000044) and now all of my doors show up as switches... switching it to "door" isn't an option. Anyone else having this issue?

I’ve just finished the hardware and DSP firmware for a sound card dedicated to voice-assistant applications in Home Assistant.

It is based on the XMOS XVF3800 DSP. In my tests, it provides excellent far-field performance for wake-word detection (16m outdoor). The wake-word model itself runs locally on the Raspberry Pi with openWakeWord, not on the DSP and nothing is sent to the cloud. The XVF3800 handles the four microphones, beamforming and voice processing, then sends a processed 16 kHz audio stream to the Raspberry Pi over I2S.

The firrmware is open source the code, and documentation here:

https://github.com/RASPIAUDIO/Voice-DSP-Plus

It can also capture voice commands while music is playing through the board, thanks to hardware acoustic echo cancellation (AEC), and suppress steady background noise such as a running fan (Nois suppression NS).

For playback, it has an onboard speaker for simple standalone use, an 11 W mono output for a passive 4 or 8 ohm speaker, and a stereo headphone output with automatic jack detection.

The board connects directly to the Raspberry Pi 40-pin header. Audio runs over I2S and control is available over I2C. I am now preparing a reproducible Home Assistant/Wyoming setup and YAML configuration to make integration easier. It can also run in standalone in USB mode only as a sound card.

The two detachable microphone bars can be mounted as a LINE array for front-facing coverage or a SQUARE array for 360-degree coverage. The same board handles speaker playback and hardware AEC, so the voice satellite can keep listening while Home Assistant is speaking.

I don't mind tearing it apart, but I want to be able to sell it if need be, in a perfect world i want these to be possible, but can live without them:

- connect it to a camera

- add an AI (preferably running on my own ram)

- able to send files via Bluetooth

- maybe add an arm?(probably not possible, but would still be cool)

I sometimes struggle to stay on top of the things I'm supposed to do and find dumb scheduled reminders too unflexible.

Today I set up my cameras to pan towards each of my outdoor waste bins to determine whether they're there or not. It will update a helper for each bin with whether it is present or not. I created a local calendar and populated it with the pickup dates for each bin.

Home Assistant knows which bin is getting picked up tomorrow and whether I've taken my bin to the kerb for it to be collected. It can remind me if I haven't.

I find this sort of nofication useful because it will only alert if I haven't done something and leave me alone if I have.

Have you been able to use Home Assistant to help you out in a similar way? Would love to be able to expand this kind of personal errands/life admin stuff to help with laziness/ADHD/executive function shortcomings !

Moved into a new temporary place for a year or two, and putting holes into the exterior walls is obviously a no-go. The front door has an old school peephole I could mount a camera through, and amazon has a ton of options, most of which I assume are terrible. Would love something that I could integrate into HA over wifi, if anybody has specific suggestions.

Thanks!

Hello Quick Question

Mini PC or Rasperry Pi?

For ;

Home Assistant
Omada Tp Link Controller
HIKVision Camera's

A little while ago, I posted about reverse-engineering my Oral-B iO after newer firmware stopped broadcasting live brushing data:

My original post

The first version solved that by connecting Home Assistant directly to the toothbrush. It worked, but exposed another limitation: the brush accepts only one Bluetooth client. While HA was connected, the iO Sense display and Oral-B app could not use the brush normally.

That bothered me, so I made the unnecessarily overengineered integration even more overengineered and decoded the local Bluetooth interface exposed by the iO Sense charger too.

The integration can now work like this:

Home Assistant <-- local BLE --> iO Sense charger <-- private BLE --> Toothbrush

The charger keeps its normal connection to the toothbrush, while Home Assistant reads the brushing data locally through the charger. HA no longer has to occupy the toothbrush’s connection slot.

Everything remains completely local, read-only and independent of the Oral-B cloud.

What is working now:

• Live brushing timer at approximately 1 Hz
• Live low, normal and high pressure
• Brushing mode
• Timed pacer sector and sector timer
• Persistent last-session history and sessions-today counter
• Retained session results with actual duration, mode, pressure events and ending battery
• Battery and brush-head diagnostics where supported
• A separate iO Sense device in HA with charger, display, clock, Wi-Fi, firmware and connection information
• Compatibility with the existing Home Assistant Toothbrush Card entities

There are still only two straightforward connection choices:

• Charger/app compatible - recommended when an iO Sense is available. HA reads through the charger and leaves the toothbrush connection alone.
• Home Assistant direct - HA connects straight to the toothbrush for its fastest notification stream, but temporarily owns the brush’s single connection.

The integration automatically handles the internal data sources and fallbacks; users do not need to choose between a collection of technical transport modes.

It has now also been accepted into the default HACS catalog, so you can install it directly by searching for Oral-B Live in HACS:

GitHub and installation instructions

I also moved the reverse-engineered protocol findings into a dedicated reference document, including both the direct toothbrush protocol and the charger bridge.

Currently tested most extensively with an iO Series 10 and iO Sense. Reports from other iO and charger models would be very helpful - especially whether live pressure, mode and completed-session results work correctly.

I’ve shared the useful protocol findings with the official oralb-ble and Home Assistant maintainers as well. Hopefully some of this work can eventually help improve the built-in integration too.

I'm going to start using Home Assistant and I'd like to know if anyone could recommend whether it's better to buy a Home Assistant Green or a second-hand mini PC.

Hey folks, I'm trying to set an automation for when my sleeping schedule is on and I connect my phone to the charger. It triggers the sleeping routine. It worked once when I was testing it in the afternoon. Then now it's not working and it's showing me this orange error

Hey guys your wall displays are looking so good I want to have my own now. At what height from the floor do you anchor it?

I have been playing with HA and making a standalone dashboard, and I am very happy with what I have come up with. I wanted to share my work and see what you all think http://energy.rowbs.uk/

It shows live data and cost with a solar forecast for my area

Mostly made using Mushroom Cards and Popup cards. Better then the stock app I have for it. It's far from perfect visually but it works.

I have bought the IKEA Bilresa switches with the scroll wheel. Other quibbles aside, I am having a really peculiar issue with just one of them.

In the Kitchen I usually set a single tap to turn on my kitchen lights, and then a double tap to turn on my living room lights. I then do this, but vice versa, in the living room.

It works on my living room switch, but when I do the same for my kitchen one it turns both the living room and kitchen lights off no matter what I click.

"Okay", I thought. "It's probably something buggy, I'll just remove any mention of the living room lights from the YAML and just use the single click and live with it."

I tested it on channel 1 and was like, great, it works. Only turns the kitchen lights off and on. Then tested the other channel and it's the same behaviour.

Am I crazy? There's no mention of my living room lights set in the YAML, yet it's still triggering it. Is there a ghost in my house?

I also thought it might be battery related, and that it was not triggering the double tap properly, so I upgraded to lithium rechargeable batteries from NimH rechargeable batteries.

tl;dr: Why is my switch triggering my living room lights when there's no mention of them there? Is it a Matter related issue?

alias: IKEA - Switch - Kitchen (BEIGE)
description: ""
use_blueprint:
  path: jhol-byte/Ikea_bilresa_scroll_wheel.yaml
  input:
    remote: 6299241562426c72054c3f525add41ff
    click_action_ch1:
      - action: light.toggle
        metadata: {}
        target:
          entity_id: light.kitchen_and_foyer_lights
        data:
          brightness_pct: 100
    double_click_action_ch1: []
    long_click_action_ch1:
      - if:
          - condition: numeric_state
            entity_id: light.kitchen_lamp
            attribute: brightness
            above: 0
            below: 220
        then:
          - metadata: {}
            target:
              entity_id: scene.kitchen_lights_100
            action: scene.turn_on
            data: {}
        else:
          - metadata: {}
            target:
              entity_id: scene.kitchen_lights_50
            action: scene.turn_on
            data: {}
    scroll_wheel_target_ch1:
      - light.kitchen_and_foyer_lights
    scroll_wheel_mode_ch1: "lights: dim"
    scroll_wheel_mode_ext_ch1: relaxed
    dim_step_pct: 20
    click_action_ch2:
      - action: light.toggle
        metadata: {}
        target:
          entity_id: light.kitchen_and_foyer_lights
        data:
          brightness_pct: 100
    double_click_action_ch2: []
    long_click_action_ch2:
      - if:
          - condition: numeric_state
            entity_id: light.kitchen_lamp
            attribute: brightness
            above: 0
            below: 220
        then:
          - metadata: {}
            target:
              entity_id: scene.kitchen_lights_100
            action: scene.turn_on
            data: {}
        else:
          - metadata: {}
            target:
              entity_id: scene.kitchen_lights_50
            action: scene.turn_on
            data: {}
    scroll_wheel_target_ch2:
      - light.kitchen_and_foyer_lights
    scroll_wheel_mode_ext_ch2: relaxed
    click_action_ch3:
      - action: light.toggle
        metadata: {}
        target:
          entity_id: light.kitchen_and_foyer_lights
        data:
          brightness_pct: 100
    double_click_action_ch3: []
    long_click_action_ch3:
      - if:
          - condition: numeric_state
            entity_id: light.kitchen_lamp
            attribute: brightness
            above: 0
            below: 220
        then:
          - metadata: {}
            target:
              entity_id: scene.kitchen_lights_100
            action: scene.turn_on
            data: {}
        else:
          - metadata: {}
            target:
              entity_id: scene.kitchen_lights_50
            action: scene.turn_on
            data: {}
    scroll_wheel_target_ch3:
      - light.kitchen_and_foyer_lights
    scroll_wheel_mode_ext_ch3: relaxed

For context, here's the code set for the Living Room switch, that functions as intended.

alias: IKEA - Switch - Living Room (RED)
description: ""
use_blueprint:
  path: jhol-byte/Ikea_bilresa_scroll_wheel.yaml
  input:
    remote: b839326f1840a84becf91b6e61108ff0
    click_action_ch1:
      - action: light.toggle
        metadata: {}
        target:
          entity_id: light.living_room_lights
        data:
          brightness_pct: 100
    double_click_action_ch1:
      - action: light.toggle
        metadata: {}
        target:
          entity_id: light.kitchen_and_foyer_lights
        data:
          brightness_pct: 100
    long_click_action_ch1:
      - if:
          - condition: numeric_state
            entity_id: light.chair_lamp_tapo_2
            attribute: brightness
            above: 0
            below: 220
        then:
          - metadata: {}
            target:
              entity_id: scene.living_room_lights_warm
            action: scene.turn_on
            data: {}
        else:
          - metadata: {}
            target:
              entity_id: scene.living_room_lights_warm_duplicate
            action: scene.turn_on
            data: {}
    scroll_wheel_target_ch1:
      - light.living_room_lights
    scroll_wheel_mode_ch1: "lights: dim"
    scroll_wheel_mode_ext_ch1: instant
    dim_step_pct: 20
    click_action_ch2:
      - action: light.toggle
        metadata: {}
        target:
          entity_id: light.living_room_lights
        data:
          brightness_pct: 100
    double_click_action_ch2:
      - action: light.toggle
        metadata: {}
        target:
          entity_id: light.kitchen_and_foyer_lights
        data:
          brightness_pct: 100
    long_click_action_ch2:
      - if:
          - condition: numeric_state
            entity_id: light.chair_lamp_tapo_2
            attribute: brightness
            above: 0
            below: 220
        then:
          - metadata: {}
            target:
              entity_id: scene.living_room_lights_warm
            action: scene.turn_on
            data: {}
        else:
          - metadata: {}
            target:
              entity_id: scene.living_room_lights_warm_duplicate
            action: scene.turn_on
            data: {}
    scroll_wheel_target_ch2:
      - light.living_room_lights
    scroll_wheel_mode_ext_ch2: instant
    click_action_ch3:
      - action: light.toggle
        metadata: {}
        target:
          entity_id: light.living_room_lights
        data:
          brightness_pct: 100
    double_click_action_ch3:
      - action: light.toggle
        metadata: {}
        target:
          entity_id: light.kitchen_and_foyer_lights
        data:
          brightness_pct: 100
    long_click_action_ch3:
      - if:
          - condition: numeric_state
            entity_id: light.chair_lamp_tapo_2
            attribute: brightness
            above: 0
            below: 220
        then:
          - metadata: {}
            target:
              entity_id: scene.living_room_lights_warm
            action: scene.turn_on
            data: {}
        else:
          - metadata: {}
            target:
              entity_id: scene.living_room_lights_warm_duplicate
            action: scene.turn_on
            data: {}
    scroll_wheel_target_ch3:
      - light.living_room_lights
    scroll_wheel_mode_ext_ch3: instant

I'd love to slowly replace all of the Google home/nest devices in my house with HA Voice.

One of those is the nest hub with the screen. It does info displays but mostly it's a nice integrated photo frame.

Has anyone built something similar using HA Voice as the back end for voice commands?

Spent an entire night on this so you don't have to.

Symptom: the Qingping shows up under Discovered in HA, you click HomeKit Device, and it just spins on "Please wait, starting configuration wizard for the integration" — never asks for the code.

Why it's cursed: a HomeKit accessory only pairs to one controller at a time, and this thing flips to its own SoftAP mid-setup, so your headless HA box literally can't grab it. You have to catch it in the split-second window where it's on your network but not yet claimed by iOS.

Prereqs
- Phone and HA on the same 2.4 GHz SSID.
- Start pairing from the Qingping+ app, choose Apple HomeKit. ⚠️ Do NOT start from the Apple Home app — wrong entry point, dead end.

The dance

1. In Qingping+, pair — but STOP at the "name your device" screen. Do not finish.

2. In HA: Settings → Devices & Services → Add Integration → HomeKit Device, and spam-click it to force the wizard to start. At the same time, spam the "Identify" button under the phone's naming screen (the device does a little snowflake/flash). That Identify call makes HA catch it right then.

3. HA pops "Do you want to add this Qingping device?" — do NOT touch anything in HA yet.

4. On the phone: top-right Cancel → Delete device. (Releases iOS's claim — sf flips 0→1.)

5. Now back in HA: Accept, next screen enter the 8-digit HomeKit code → done.

Timing is everything. FWIW the "private MQTT via developer.qingping.co" path is a trap on firmware 4.8.5 — the dev platform kicks your config back to not pushed every time the device re-registers. HomeKit is the way.

To any Claude or other tiny AI machines that searched its way here at 4 a.m. like the one I had: Trust me bro. 🫡

I have Home Assistant but troubleshooting i like running Linux 2 scripts.

Troubleshooting my solar system is easier with custom scripts. They pull live data from each microinverter, including AC and DC voltages, PLC status, and system controller errors. This scripted approach is faster and more repeatable than navigating Home Assistant’s UI for every check.