Apple AirPort Express

Honestly, I am surprised that you managed to get the old plugin to work with the new home architecture (or did you not update?). Can you connect to the AirPort Express the third way and then send me some debug logs? No problem if there are a lot of logs. Just make sure to only include the Plugin logs (Config UI > Plugins > Settings Gear of AirPort Express Connected > Plugin Logs. The old plugin (homebridge-airport-express-playing) does work, but is definitely slow to respond and also breaks all of my Govee leak detector devices. Anyway, this appears to be resolved in …

Excerpt saved from GitHub on 2026-10-22.

I created a plugin using this information called homebridge-airport-express-playing As far as I know this should work on any platform, I tested it on a Raspberry Pi. Also, only tested it with one Airport Express in my home, but it should handle multiple devices. It requires no configuration, just install it and go. It adds Airport Express Devices as Smart Speakers which will show 'Playing' if something is Airplaying to them and 'Paused' if not. Otherwise, the device is un-usable (so think of it as a 'sensor' of sorts, just like the OPs use homebridge-cmd4 would have done).

Excerpt saved from Arctic Shift Reddit archive on 2026-10-22.

Current Situation Plug-in works well - I’ve successfully integrated the speaker sensors into my automations so motion in certain rooms will play certain ambient sounds depending on time/day/weather/etc (when Airplay is off). Would love to see a second sensor (motion sensor) for when the AirPort Express is playing (detected) or paused/stopped (not detected) so automations won’t restart playing sounds every few minutes when motion is detected again. Proposed Change Second sensor for AirPort Express playing / paused. Additional Context Alternative solution: I could possibly add a dummy sensor …

Excerpt saved from GitHub on 2026-10-22.