Skip to content
Home Assistant TestFlight
Computers & network

PrusaLink

prusalink

Built inLocal polling

The PrusaLink integration allows you to monitor your Prusa 3D printer and its progress with your Home Assistant installation. This integration works with Prusa MINI/MINI+, Prusa MK3.9/MK4, Prusa XL, Prusa CORE One, and with the older Raspberry Pi-based Prusa MK2.5/MK3.

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
cameraCameraNeeds its own HomeKit Bridge in accessory mode
binary_sensorSensor (motion, contact, leak, smoke…)
sensorSensor (temperature)
buttonButton (as a switch)

What people report

PrusaLink works locally with Prusa printers on supported API versions; PrusaLink 0.7.0 with legacy API failed for MK3S and MK4 users in 2023.

  • Works1
  • Not working2
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
Prusa XLWorks LocalWorks fine as delivered
Saved copy
The problem Have intalled PrusaLink 0.7.0 on my Raspberry Pi3 on PrusaMKS3+, unfortunately the integration fails with the error "Only PrusaLink API v2 is supported". PrusaLink does display: API 0.9.0-legacy Hostname prusalink Firmware 3.12.2-5713 Server 0.7.0 Text PrusaLink 0.7.0 SDK 0.7.0 Frontend 3.12.0 ### What version of Home Assistant Core has the issue? ## System Information version | core-2023.6.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.11.4 os_name | Linux os_version | 6.1.21-v8 arch | …

Excerpt saved from GitHub on 2026-10-23.

Issue #95529 · 2023-06
Prusa MK3S via PrusaLink 0.7.0Not working LocalFails with 'Only PrusaLink API v2 is supported' on legacy API 0.9.0
Saved copy
The problem Have intalled PrusaLink 0.7.0 on my Raspberry Pi3 on PrusaMKS3+, unfortunately the integration fails with the error "Only PrusaLink API v2 is supported". PrusaLink does display: API 0.9.0-legacy Hostname prusalink Firmware 3.12.2-5713 Server 0.7.0 Text PrusaLink 0.7.0 SDK 0.7.0 Frontend 3.12.0 ### What version of Home Assistant Core has the issue? ## System Information version | core-2023.6.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.11.4 os_name | Linux os_version | 6.1.21-v8 arch | …

Excerpt saved from GitHub on 2026-10-23.

Issue #95529 · 2023-06
Prusa MK4Not working LocalFails on PrusaLink 0.7.0 legacy API
Saved copy
The problem Have intalled PrusaLink 0.7.0 on my Raspberry Pi3 on PrusaMKS3+, unfortunately the integration fails with the error "Only PrusaLink API v2 is supported". PrusaLink does display: API 0.9.0-legacy Hostname prusalink Firmware 3.12.2-5713 Server 0.7.0 Text PrusaLink 0.7.0 SDK 0.7.0 Frontend 3.12.0 ### What version of Home Assistant Core has the issue? ## System Information version | core-2023.6.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.11.4 os_name | Linux os_version | 6.1.21-v8 arch | …

Excerpt saved from GitHub on 2026-10-23.

Issue #95529 · 2023-06

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local polling

Talks to the device on your network, asking it for updates every so often.

Found automatically over

  • DHCP

Details

Installs (analytics)2,902 (0.41%)
Added inHome Assistant 2022.9
Set up in the UIYes

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.