Warning Matter 1.2 support is needed to use this. Currently no major Smarthome platform supports this. This will lead to a error similar to this: "This device is currently not supported in the Home App"
![State Machine](https://private-user-images.githubusercontent.com/34026653/331886761-1d1d448c-9261-4d6e-9f06-82ced4252290.jpeg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM4NzY0MTksIm5iZiI6MTcyMzg3NjExOSwicGF0aCI6Ii8zNDAyNjY1My8zMzE4ODY3NjEtMWQxZDQ0OGMtOTI2MS00ZDZlLTlmMDYtODJjZWQ0MjUyMjkwLmpwZWc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgxN1QwNjI4MzlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mZDMyZWY2M2FkYmFkMTdiN2Y3YmNhMDc0MWVkYjBjNjU5NjhjMjNiOTIzOTZiODc1MTI0NmMwMzM2MTQ5ODk2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.bA521vVUehohM7_aHh0udAgLC6Zdjsr5Qawk91xfDNI)
Replace the Wifi Chip within a Tesvor x500 with a ESP32 H2 to support Matter over Thread.
Not all States and state switches that are used within the matter protocol for Vaccumes are supported. Oiginal can be found here: https://github.com/project-chip/connectedhomeip/tree/e079364d2f18aae6c4718cd7074ea62fae3f0360/examples/rvc-app I could find the following information being communicated to the wifi chip:
- Wake up
- Vacuum start
- Vacuum stop
- Charge start
- Stops Charging
- Power Mode
- Quite Mode
- Battery Percentage No information about the docking status could be found.
This would allow for follwong state State Machine within Matter:
- Tasmoto for Tesvor x500: arendst/Tasmota#19554
This section defines conformance for the Robotic Vacuum Cleaner device type.
This is the revision history for this document.
Revision | Description |
---|---|
1 | Initial release of this document |
ID | Device Name | Superset | Class | Scope |
---|---|---|---|---|
0x0074 | Robotic Vacuum Cleaner | Simple | Endpoint |
Please see the Base Device Type definition for conformance tags.
Each endpoint supporting this device type SHALL include these clusters based on the conformance defined below.
ID | Cluster | Client/Server | Quality | Conformance |
---|---|---|---|---|
0x0003 | Identify | Server | M | |
0x0054 | RVC Run Mode | Server | M | |
0x0055 | RVC Clean Mode | Server | O | |
0x0061 | RVC Operational State | Server | M |
The table below lists qualities and conformance that override the cluster specification requirements. A blank table cell means there is no change to that item and the value from the cluster specification applies.
ID | Cluster | Element | Name | Constraint | Access | Conformance |
---|---|---|---|---|---|---|
0x0054 | RVC Run Mode | Feature | OnOff | X | ||
0x0055 | RVC Clean Mode | Feature | OnOff | X | ||
0x0061 | RVC Operational State | Command | Start | X | ||
0x0061 | RVC Operational State | Command | Stop | X |