I just updated and wanted to watch a movie, and the pypjlink is gone from the ha??? I didn’t read anything about that in the release notes, and the pjlink integration is still on the site.
Apart from the pypjlink is broken (but works with a simple patch), and needs to be replaced with aiopypjlink which is still alive, this integration controls my projector, it is one of the few proper standard integrations to projectors.
This is really bad. Please correct me if I’m wrong, I did a ‘find -name pypjlink’ from root, but didn’t find it anywhere, it was previously placed under /usr/local/lib/python3.13/site-packages/pypjlink/
I just tried rolling back to 2026.1.3, which I only had for a week or so, and I can’t seem to find it there either, unfortunately I don’t have older backups than 1.3.
seems still legit, but code is not toucher very much.
Yeah, but where is the library for it, it’s not in that folder?
Not sure where you did your find from, nor what installation method you use, but the library is definitely in the HA docker images
triton:/config# ls /usr/local/lib/python3.13/site-packages/pypjlink*
/usr/local/lib/python3.13/site-packages/pypjlink:
__init__.py cli.py cliutils.py projector.py protocol.py
/usr/local/lib/python3.13/site-packages/pypjlink2-1.2.1.dist-info:
INSTALLER LICENSE METADATA RECORD REQUESTED WHEEL entry_points.txt top_level.txt
1 Like
This is an HAOS install, not Core (which is pure python).
Be it be SSH’ing to the Terminal addon or to HAOS itself, you won’t find the python libraries there, only inside the HA docker container itself.
Yes, I miswrote.
Interesting argument, which is not supported by the facts, they were there for years, and patching them made the pjlink work, so that is not true. Not sure why it was made that way, but it was.
Oh, and shooting me down, doesn’t solve the problem, please focus on that.
Because you used a “Core” installation, pure python, through pip. That’s the only way you could have seen them on the host.
All the other installation methods use docker containers for HA.
Pal, if you call my tone “shooting you down”, you have never been “shot down” on internet, lucky you.
Oh, and insulting people trying to help you doesn’t solve YOUR problem, reflect on that.
I’m in no way offended, but I can see on your response that you might feel that way.
This is an installation done through the usual proxmox script. My point was to focus on the issue, and not that I used the wrong word, despite what it showed in the image.
So, no I haven’t done any unusual installation, it’s a simple VM in proxmox with HAOS.
Then pypjlink is there, as stated earlier.
Not sure what you did before to patch it, but you’ll have to remember for further help.
Note however that if you patch it directly in the docker image, those changes disappear at every upgrade, that is just how docker works.
I don’t actually see how you would have done it otherwise in HAOS, but that requires root access to HAOS itself, and docker knowledge, which is probably something you would remember.
I update the HA and OS in a regular way through the HA interface, then after a HA update, I go and patch that single file, so it works, and then reboots it, quite simple.
I tried rolling back to 2026.1.3, but that didn’t help, I think I’ll build a new VM and restore the backup to, and hope its there.
But how, precisely?
Well, I can’t take credit for the patch, m-filippi made it, he even did an automation and a shell script for it, as described here:
Oh, @koying , you are right, I forgot the docker exec -it command to go inside the docker container, and there it is, the pypjlink, now I just have to find out why the patch script doesn’t work.
1 Like