Infuse 8.5.9: Firecore Transforms Media Automation with New Local API

The media consumption landscape is constantly evolving, and for power users who rely on Apple’s ecosystem for their home theater setups, the name "Infuse" has long been synonymous with quality, versatility, and elegance. Firecore, the development house behind the award-winning media player, has just released version 8.5.9, a significant update that bridges the gap between passive media consumption and active smart home automation. By introducing a "Now Playing" API, Firecore is effectively turning Infuse from a simple playback client into an integrated hub for home automation enthusiasts.

Main Facts: What’s New in Version 8.5.9

The headline feature of the latest Infuse update is undoubtedly the Local Now Playing API. This feature, while niche in its initial appeal, represents a massive leap forward for users who integrate their media setups with broader smart home ecosystems like Home Assistant, Homebridge, or custom automation scripts.

In addition to this flagship functionality, version 8.5.9 introduces:

• Expanded Device Support: Full compatibility with the latest iPhone models (including the iPhone Duo, marking an expansion in hardware optimization).
• Subtitle and SMB Enhancements: Advanced control over formatted subtitles and the ability to toggle IAKERB for SMB connections to troubleshoot network stability.
• UI/UX Polish: Refined behavior for playback and pausing when toggling fullscreen modes on macOS.
• Critical Bug Fixes: Comprehensive resolutions for Jellyfin 12 folder-handling issues, Google Cast subtitle rendering, and intermittent start-screen loading errors.

Chronology: The Evolution of Infuse

To understand why this update is significant, one must look at the trajectory of Infuse. Originally launched as a streamlined way to play various media formats on Apple devices without needing to transcode files via Plex or other servers, Infuse has gradually become the "gold standard" for local playback.

1. Early Years (2012–2016): Infuse focused on codec support and a beautiful, Apple-native interface that felt more at home on an Apple TV than the official apps of the time.
2. Middle Period (2017–2021): The shift toward cloud and network-attached storage (NAS) support. Infuse began supporting protocols like SMB, WebDAV, and eventually deep integration with metadata providers like Plex, Jellyfin, and Emby.
3. Modern Era (2022–Present): With version 8.x, Firecore shifted toward professional-grade customization. Features like Dolby Vision support, spatial audio, and now, developer-friendly APIs, signal a shift toward capturing the "enthusiast" market that demands total control over their data and playback environments.

Supporting Data: Why the Now Playing API Matters

For the uninitiated, a "Now Playing" API allows a device to broadcast its current status—what is playing, the duration, the progress, and the metadata (title, artist, album art)—to other devices on the same local network.

Previously, if a user wanted to dim the lights automatically when a movie started or pause their media when a doorbell rang, they had to rely on cumbersome workarounds or specific, closed-ecosystem hardware. By opening this API, Firecore is allowing users to create "triggers."

• Scenario A: When Infuse begins playing a movie, a smart home controller detects the "Playing" state and automatically triggers a "Cinema Scene," lowering the living room lights to 10% and closing the smart blinds.
• Scenario B: If a user is listening to a concert film and pauses, the system can automatically unmute a smart speaker in another room, ensuring the user doesn’t miss an announcement or a phone call.
• Universal Compatibility: Unlike proprietary solutions, this API works regardless of the source. Whether the file is stored locally on a NAS, streamed via Plex, or pulled from a Jellyfin instance, Infuse provides a unified data stream to the local network.

Official Responses and Implementation

Firecore has opted for a privacy-first approach regarding this API. Recognizing that broadcasting what a user is watching across a network could be seen as a privacy concern, the feature is disabled by default.

In the official documentation provided by Firecore, the company emphasizes that this is a "read-only" service. It does not allow external apps to control the playback—only to observe it. This ensures that the user remains in complete control of their privacy.

To enable this feature, users must navigate to:
Settings > Playback > Now Playing API.

Firecore’s support page for the API provides clear, technical documentation for developers, including JSON schema examples and port requirements, ensuring that even users with modest scripting knowledge can implement their own automations.

Implications for the Smart Home Industry

The decision to add a local API is a strong indicator of the "pro-sumer" direction of the home media market. As platforms like Plex move toward more closed, server-side management, Infuse is doubling down on the "Local-First" philosophy.

1. Privacy and Security

By relying on a local API rather than cloud-based tracking, Infuse is appealing to the privacy-conscious demographic. In an era where media providers often track user viewing habits for data mining, keeping "Now Playing" status within the four walls of a home is a significant selling point.

2. Integration over Aggregation

While other media players strive to be "all-in-one" apps that aggregate content from various streaming services (like Netflix, Hulu, etc.), Infuse remains focused on the player experience. By providing an API, they aren’t trying to be the "everything" app; they are trying to be the best component in a user’s bespoke home automation system.

3. Stability and Performance

The inclusion of SMB-specific fixes and Jellyfin-specific patch notes shows that Firecore is listening to the feedback of users running complex home-lab setups. As users move away from commercial streaming services toward self-hosted media, the reliability of these connections becomes paramount. The ability to toggle IAKERB, a protocol-level authentication setting, demonstrates that the developers are aware of the specific network configurations found in professional or advanced home environments.

Conclusion: A New Standard for Playback

Infuse 8.5.9 is more than just a maintenance update. It is a strategic move that acknowledges the increasing complexity of home media setups. By offering an open, local, and privacy-conscious API, Firecore has empowered its user base to move beyond simple playback.

Whether you are a casual viewer who just wants a smoother subtitle experience or a dedicated smart home architect looking to bridge your Apple TV with your lighting and sound systems, this update provides the tools necessary to elevate your home cinema experience.

As we move toward a future where our devices are expected to "talk" to one another, Firecore has ensured that Infuse remains the most versatile player on the market. The technical depth of this update—from network protocol adjustments to the new API—confirms that while the interface remains simple and elegant, the engine under the hood is becoming increasingly powerful.

For those looking to get started, the comprehensive documentation on the Firecore support site is a goldmine for anyone interested in exploring the world of local media automation. The era of the "smart" home cinema has arrived, and with Infuse 8.5.9, it has never been more accessible to the home user.

Disclaimer: This article contains affiliate links. Purchases made through these links support the continued production of high-quality, independent content at no extra cost to the consumer. Our editorial integrity remains our highest priority, and these links do not influence our assessment of the software or services discussed.