Problem statement
Work on the new Matter JS server has been ongoing for quite some time now, always aiming to become a drop-in replacement of the existing Python server version.
Also, work on introducing #40 is using these efforts already as it requires Matter 1.5.x.
Community signals
Beta has been running for quite some time as well yielding overall positive results leading to a common direction to aim for public release.
Scope & Boundaries
In scope
- Matter 1.5.1 compliance
- Finalize new Storage system and add as default
- Add Attestation verification to verify devices during commissioning
- Autogenerate Python classes based on matter-js model
- Proof reliability and stability for public release
Not in scope
Foreseen solution
- Being a drop-in replacement migration should not require any user interaction.
- Furthermore, work on optimizing the underlying WAL storage system should yield an efficient migration.
- Still, be aware that depending on the amount of devices the migration might take a couple of minutes.
Risks & open questions
- General reliability and stability while ongoing beta yielded positive results
- Deprecation of previous "island/undocumented" usage in the Python server (which we anyways don't aim to officially support)
Appetite
Small - 1 cycle as it's ongoing for quite some time now
Execution issues
No response
Decision log
Problem statement
Work on the new Matter JS server has been ongoing for quite some time now, always aiming to become a drop-in replacement of the existing Python server version.
Also, work on introducing #40 is using these efforts already as it requires Matter 1.5.x.
Community signals
Beta has been running for quite some time as well yielding overall positive results leading to a common direction to aim for public release.
Scope & Boundaries
In scope
Not in scope
Foreseen solution
Risks & open questions
Appetite
Small - 1 cycle as it's ongoing for quite some time now
Execution issues
No response
Decision log