How-to integrate HomePod Mini Sensors into Home Assistant When Direct Integration Isn't Possible

Community Guides
, ,
127

In my configuration.yaml, I finally added sensor template…

template:
  - sensor:
      # ✅ Humidité HomePod Mini CHM
      - name: "HomePod Mini CHM Humidity"
        state: "{{ states('sensor.homepod_mini_chm_humidity') }}"
        unique_id: "homepod_mini_chm_humidity_sensor"
        unit_of_measurement: "%"
        device_class: humidity
        icon: "mdi:water-percent"
      # ✅ Température HomePod Mini CHM
      - name: "HomePod Mini CHM Temperature"
        state: "{{ states('sensor.homepod_mini_chm_temperature') }}"
        unique_id: "homepod_mini_chm_temperature_sensor"
        unit_of_measurement: "°C"
        device_class: temperature
        icon: "mdi:thermometer"

Thank,

129

For those having trouble configuring the automation shortcut, as best as I can tell, macOS 26.5 cannot insert variables; the shortcut has to be modified or created on iOS or iPadOS, where placing the cursor into the value field causes a popup in the predictive keyboard to insert one of the values.

130

This was working great for me until I upgraded to xOS27. I’ve deleted and recreated and when I select “Test This Automation” it still works but not via the input_boolean switch trigger.

5 Likes
131

Same behaviour. I have also tried to trigger it with a physical switch with no success. Test This Automation continues to works perfectly

2 Likes
132

Same issue here, adding another data point since this seems to be a growing pattern with xOS27.

Setup: Home Assistant OS on a Raspberry Pi, Method B (via /api/states/ with Bearer token, no webhook/python_script). Tried both an Apple TV (tvOS 26) and a HomePod mini (audioOS 27) as the home hub — identical behavior on both.

Symptom: “Test This Automation” runs perfectly every time. The automatic trigger (input_boolean toggled every 2 min from HA) does nothing — not even a failed attempt.

What I’ve confirmed:

  • Enabled debug logging on the HA side (homeassistant.components.http + aiohttp.access) and watched the log live across multiple trigger cycles. On automatic triggers: absolutely no incoming request, ever. On manual test runs: request arrives immediately, correct source IP, correct response.
  • The HomeKit trigger itself is definitely being received — I temporarily added a native “Play Music” action as the first step in the same automation, and it fires reliably on every automatic trigger. So the trigger detection and the hub’s native action execution both work fine.
  • It’s specifically the “Run Shortcut” action that never starts when triggered automatically — no error, no log entry, nothing. Silent no-op.
  • Started roughly two days ago, coinciding with the xOS27 update and some local network changes (which I initially suspected, but have since ruled out via the logging above).

Given how cleanly this isolates to the Shortcut-execution step specifically failing on background/automatic triggers (while manual and native actions are unaffected), this looks like the same underlying regression as the 18.2/18.3 issue from late 2024/early 2025 that got fixed in 18.4 — just resurfaced in the xOS27 cycle.

2 Likes
133

Yes I can confirm the same in xOS27 too - exactly the same as described here.

So we’ve all hit the same brick wall that probably can’t be fixed and it’s on Apple’s side again. Annoying!

2 Likes
134

Confirming hitting the same issue after upgrading to xOS27

1 Like
135

Same issue. As far as I can tell, it’s the”Get Contents of URL” action that causes the issue.

I suspected this as I’m having exactly the same issue with a Pushover api call in my HomeKit automations.

As far as I can tell, “test this automation” runs the automation on the device in your hand. And these “Get contents of URL” actions work fine then.

However, they fail when the automation is triggered to run on the Home Hub.

I’ve proved this for myself by setting up various time-triggered automations. Some with just the Get URL, some with other standard actions before or after.

It seems that any shortcut runs up to the Get URL action then fails. It will turn a light on if that’s the first action, but won’t execute any actions after the Get URL action.

Unless I “test this automation” or run the shortcut with the play button. Then it all works fine. Because, I think, it runs on my phone instead of the HomePod.

Very glad I found this thread as I was about to start tearing my network apart to find what was blocking the HomePods from accessing these URLs.

Suggest we all report the bug to Apple and hope they fix it soon…

In the meantime I’m not sure what we can do except maybe have a switch and HomeKit loops the number of degrees, toggling it each time so HA can count the number of times it switches…? :rofl:

136

From Apple Discussions:

Home automation with “Get Contents of URL” fails after OS 27 update, but manual testing works

Allegedly the beta of 27.2 fixes it. I’ll try it tomorrow…