-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why remove old compability in prusalink #31582
Comments
Hey there @balloob, @Skaronator, mind taking a look at this feedback as it has been labeled with an integration ( Code owner commandsCode owners of
|
Why can't you update the firmware on your printer? |
As there was no response to the above, I'll go ahead and close up this PR. ../Frenck |
Then I need to replace the motherboard of the printer, this only works on prusa 3.5 , 39, and 4.0
All prusa before tah is unsupported, read the case
Fra: Paulus Schoutsen ***@***.***>
Sendt: fredag 23. februar 2024 19:32
Til: home-assistant/home-assistant.io ***@***.***>
Kopi: Morten ***@***.***>; Author ***@***.***>
Emne: Re: [home-assistant/home-assistant.io] why remove old compability in prusalink (Issue #31582)
Why can't you update the firmware on your printer?
—
Reply to this email directly, view it on GitHub <#31582 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG5EN4AKUV63IY756EUT7DDYVDOBNAVCNFSM6AAAAABDW7HLGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRHAYDIOBUGA> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AG5EN4C3CTSQNG5CZ7XUHO3YVDOBNA5CNFSM6AAAAABDW7HLGCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTU53CCQ.gif> Message ID: ***@***.*** ***@***.***> >
|
As far as I am aware, they where never supported? Our documentation has always been clear on which printers and firmware versions where supported by the integration. This has not changed, only extended. ../Frenck |
It was working until the update of the integration, it even said in release
notes the support for older printers was removed, and I had it working, but
since I can't get back the old integration since its internal in main
release of homeassistant without downgrade everything.
Alternative is to pay 450 euro for the new upgraded printer, and this is a
little excessive
man. 11. mars 2024, 18:39 skrev Franck Nijhof ***@***.***>:
… As far as I am aware, they where never supported? Our documentation has
always been clear on which printers and firmware versions where supported
by the integration. This has not changed, only extended.
../Frenck
—
Reply to this email directly, view it on GitHub
<#31582 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG5EN4CH7W4YI56JFYI6ZDTYXXT4NAVCNFSM6AAAAABDW7HLGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBZGA2DSOBVGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Home-Assistant only officially supports PrusaLink that runs directly on the printer and not the old Prusa Connect Local, which has been renamed to Prusa-Link, as @frenck mentioned previously. However, it looks like the latest alpha builds added support for the newer APIs, but they are still alpha. Prusa Connect Local, the Raspberry Pi PrusaLink, handles Digest Auth differently than the PrusaLink for Mini/MK4/XL, which is the reason these new alpha builds don't work yet. @the-ress did some work on fixing that in home-assistant-libs/pyprusalink#78, but It's not yet in home-assistant. I don't have a MK3, but you're welcome to contribute so we can officially support the older Prusa i3 printer as well. |
Feedback
why did you take away the complability for the printers utilizing the old prusalink, which was working great until you f*****ed it up., and since I cant get it to work unless i downgrade everything to old enough homeassistant or spend 400 euro to upgrade my prusa.
what i (and other) think of this smart move isn't suitable for print
URL
https://www.home-assistant.io/integrations/prusalink/
Version
2024.2.3
Additional information
No response
The text was updated successfully, but these errors were encountered: