-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
add python matter server #6481
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
base: master
Are you sure you want to change the base?
add python matter server #6481
Conversation
- initial version with custom chip library for home-assistant-chip-core
@24mu13 I found a workaround to avoid The custom libraries are taken from https://github.com/hgy59/chip-wheels If I will get confirmations that this matter-server package works, I probably will create a PR in https://github.com/home-assistant-libs/chip-wheels to officially support custom config data path. Since I do not have matter compatible devices for functional tests, every feedback to this packag is welcome. |
…hip_core - avoid need of chip library replacement of original home_assistant_chip_core wheel - build pure python-matter-server wheel depending on custom home_assistant_chip_core wheel - patch python-matter-server source to custom wheel and to force original version in check - install custom python-matter-server and home_assistant_chip_core version 2025.3.dev1801 - add matter-server admin page
- avoid need to create patched python-matter-server wheel to use custom wheel
@24mu13 I found a better solution than replacing the lib file at installation. I now built the custon wheel with original version number (and additionally stripped the library file) so it perfectly works together with oribinal python-matter-server wheel. I also added a link to the admin page. |
@24mu13 are you still looking for a package of python-matter-server? |
@24mu13 this is now ready for testing. I had some issues that required to run the package as root. But finally is runs fine with limited privileges. |
@24mu13 are you still looking for matter server package? I am waiting for confirmation that it works. |
Thank you @hgy59 for the good work and sorry for the late. To test the new package, I will
|
Thanks for the feedback. I guess you have seen that Supervised HA and HA Core will not be supported anymore with HA 2025.12? |
Thank you for the info: this will not affect me (I have DS224+ product with 64bit architecture) but you're right - all 32bit architectures instead are affected by this deprecation. |
I have created pre-release versions of matter-server 7.0.1 and 8.0.0 |
That is by intention We have a lot of packages that define ADMIN_PORT = $(SERVICE_PORT), but IMHO this is not good practice. We should use ADMIN_PORT only if it is different to SERVICE_PORT i.e. the regular UI of a package is under SERVICE_PORT and (a different) admin UI is on a different port. IMHO we shouldn't fix this in existing packages, because users might be used to use the admin link in package center, |
So you’re suggesting installing a package without an easy-to-access admin interface? Is that because it lacks authentication and you’re concerned about inexperienced users making changes? Could you share another package where you’d recommend a similar approach? I’m trying to put this in context and better understand the intent. |
But it will affect your Supervised installation, as supervised will get deprecated. On Synology Devices, only Docker installations (or may be Home Assistant OS as virtual machine) will be supported. |
I thought that everyone used the url to open the packages, because of the definition of ADMIN_PORT. I want to point out, that there is a difference between package interface and admin interface.. If both are the same, it does not make sense to have the URL in package center. For me the matter server package web ui is not a common web ui (like in owncloud) it is only to administrate matter devices. |
- add chip_core wheels 2025.7.0 - update requirements - install package with integration into DSM UI
@mreid-tt I have now switched to SERVICE_PORT (and DSM UI integration). |
@hgy59 this is a very different understanding than what I had for its use. Looking into our documentation we have:
This is in alignment with what you have stated and in the DSM Developer Guide we have definitions of the admin port as follows: Field Name: adminport
This as noted, is separate from the UI files which define the icon and button behaviour for the app. The issue, as I see it, is that we’ve blended the two for so long that this may now be the expected behavior for our users. A quick check of the Makefiles in spksrc shows 58 files with an Since I haven’t contributed code to these particular apps, I’ve never encountered a case where the Open button and the admin URL pointed to different places. |
@mreid-tt the icecast package has such an approach. A real use case would be, when the Open Button opens a Dialog integrated into DSM and the admin url opens a web UI of the package. I propose to avoid ADMIN_PORT, ADMIN_URL, SERVICE_URL, etc. at least when the package does not provide two different web interfaces. |
Agreed. I'll keep this in mind for any future code I work on. |
Description
Closes #6321
Restrictions
findings so far
Checklist
all-supported
completed successfullyType of change