Product Library / Blinds, Shades & Curtains
Research profile · last verified 2026-10-03Compatibility at a glance
Choose your platform to see its setup and functions. Your choice carries across product pages.
A connection can work while individual controls or automations remain unconfirmed. Read the connection details ↓
Protocols: MATTER · THREAD[1][4][5][6][14][15]
Before you buy
Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
Yes, in the way every Matter-over-Thread device needs one, and Zemismart says so without saying what it means: 'Support Matter-cetified ecosystem via smart home hub' (the spelling is the vendor's). A Thread device is not reachable on its own - it needs a Thread border router to join the mesh and a Matter controller to commission and command it, and in most households one box does both. Zemismart does not name a single qualifying hub for this product, does not state a Thread version, and does not say whether its own M1 hub is required or merely one option. The 'Sub-device Work with M1 Hub' line that appears near this product is part of the site-wide Matter Solution navigation rather than the product's own copy, so it is not treated as an answer. The practical reading: if the household already runs the 2021 Apple TV 4K, the Wi-Fi + Ethernet 2022 model or a HomePod, a Google Nest hub, a SmartThings hub or an equivalent Thread border router, that is the hub Zemismart means. If it does not, one has to be bought, and Zemismart does not tell you which.[1][4][14]
Follow the documented setup. Read the equipment details and connection limits below.
Zemismart MTP1 Matter over Thread Blind Driver
What you gainUse the platform’s Matter support for local communication.
Keep in mindNeeds a Thread border router and a Matter controller for this platform. Zemismart names no specific hardware; check which device supplies each role.
Check the function table and setup notes for this route. An alternative connection does not inherit every capability of the recorded primary connection. A Thread border router, a Matter controller and a platform home hub are different roles; suitable hardware may provide more than one.
These paths summarize documented setup options. Check the function table for the connection covered by each recorded capability.
Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
Named in both of Zemismart's own product enumerations - the description's 'works with HomeKit, Google Home, SmartThings, Home Assistant, and Homey' and the feature block's 'Supports HomeKit, Google Home, Alexa, SmartThings for easy remote & voice control' - and the mechanism is the one thing about this product that is not in doubt, because Matter over Thread is what the product is. Transport is recorded as local for the same reason: a Matter device commissioned to an Apple Home border router is controlled over Thread on the local network, not through a Zemismart cloud. One caveat belongs on this cell: Zemismart names Siri voice control, but Apple's own accessory list does not name this product. The Matter certification itself checks out, because the Matter certification ledger lists the MTP1 as certified.[1][14]
Follow the documented setup. Read the equipment details and connection limits below.
Zemismart MTP1 Matter over Thread Blind Driver
What you gainUse the platform’s Matter support for local communication.
Keep in mindNeeds a Thread border router and a Matter controller for this platform. Zemismart names no specific hardware; check which device supplies each role.
Check the function table and setup notes for this route. An alternative connection does not inherit every capability of the recorded primary connection. A Thread border router, a Matter controller and a platform home hub are different roles; suitable hardware may provide more than one.
These paths summarize documented setup options. Check the function table for the connection covered by each recorded capability.
Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
The one platform named in both of Zemismart's enumerations and in the product title. Same mechanism as the other Matter cells, and the same unnamed requirement: a Google hub that acts as a Thread border router. Zemismart writes 'Google Home', which is the app rather than the voice service.[1][14]
Follow the documented setup. Read the equipment details and connection limits below.
Zemismart MTP1 Matter over Thread Blind Driver
What you gainUse the platform’s Matter support for local communication.
Keep in mindNeeds a Thread border router and a Matter controller for this platform. Zemismart names no specific hardware; check which device supplies each role.
Check the function table and setup notes for this route. An alternative connection does not inherit every capability of the recorded primary connection. A Thread border router, a Matter controller and a platform home hub are different roles; suitable hardware may provide more than one.
These paths summarize documented setup options. Check the function table for the connection covered by each recorded capability.
Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
Named in the feature block's 'Supports HomeKit, Google Home, Alexa, SmartThings for easy remote & voice control' and absent from the description's enumeration, which lists HomeKit, Google Home, SmartThings, Home Assistant and Homey. The two lists on this page do not match, and the union is taken rather than the intersection because neither list denies what the other names - each is an incomplete enumeration rather than a contradiction. Reaching Alexa requires an Echo device that is both a Thread border router and a Matter controller; Zemismart names no such requirement and no specific device.[2][14]
Follow the documented setup. Read the equipment details and connection limits below.
Zemismart MTP1 Matter over Thread Blind Driver
What you gainUse the platform’s Matter support for local communication.
Keep in mindNeeds a Thread border router and a Matter controller for this platform. Zemismart names no specific hardware; check which device supplies each role.
Check the function table and setup notes for this route. An alternative connection does not inherit every capability of the recorded primary connection. A Thread border router, a Matter controller and a platform home hub are different roles; suitable hardware may provide more than one.
These paths summarize documented setup options. Check the function table for the connection covered by each recorded capability.
Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
Named in both Zemismart enumerations and in the product title. Same Matter-over-Thread mechanism, and the same unstated requirement for a SmartThings hub with a Thread radio - not every SmartThings hub has one, and Zemismart does not raise the distinction.[1][14]
Follow the documented setup. Read the equipment details and connection limits below.
Zemismart MTP1 Matter over Thread Blind Driver
What you gainUse the platform’s Matter support for local communication.
Keep in mindNeeds a Thread border router and a Matter controller for this platform. Zemismart names no specific hardware; check which device supplies each role.
Check the function table and setup notes for this route. An alternative connection does not inherit every capability of the recorded primary connection. A Thread border router, a Matter controller and a platform home hub are different roles; suitable hardware may provide more than one.
These paths summarize documented setup options. Check the function table for the connection covered by each recorded capability.
Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
Named in the description's enumeration - 'works with HomeKit, Google Home, SmartThings, Home Assistant, and Homey' - and in the page title, which reads 'Works with HomeKit Homey Home Assistance Google Home SmartThings'. That title is worth a note, because the shorter product title above it reads 'HomeKit Google Home Assistant Smartthings' and can be parsed two ways: as Google Home plus Home Assistant, or as Google plus Home Assistant. The longer title, which separates 'Homey', 'Home Assistance' and 'Google Home' into distinct items, is what settles it - Home Assistant is being named as a platform in its own right. Absent from the feature block's shorter list. Home Assistant reaches Matter devices through its own Matter integration and a Thread border router, which is a route Home Assistant documents generally rather than something Zemismart built.[2][14]
Home Assistant: If this device joins over Thread and your Thread border router is Apple's (a HomePod or Thread-capable Apple TV), Home Assistant can't deliver its firmware updates today. Home Assistant documentation · checked 2026-09-25
One device can provide more than one role. These are setup requirements, not a shopping list of separate purchases.
What could you do with this?
Start with a documented control or event. The selected connection shows what is confirmed for that platform.
Apple Home · Works
This device supports open/close.
Setup: Matter controller
Matter controller. Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
Named in both of Zemismart's own product enumerations - the description's 'works with HomeKit, Google Home, SmartThings, Home Assistant, and Homey' and the feature block's 'Supports HomeKit, Google Home, Alexa, SmartThings for easy remote & voice control' - and the mechanism is the one thing about this product that is not in doubt, because Matter over Thread is what the product is. Transport is recorded as local for the same reason: a Matter device commissioned to an Apple Home border router is controlled over Thread on the local network, not through a Zemismart cloud. One caveat belongs on this cell: Zemismart names Siri voice control, but Apple's own accessory list does not name this product. The Matter certification itself checks out, because the Matter certification ledger lists the MTP1 as certified.
Connection documentation: [1] [14]
Device documentation: [1] [14]
zemismart.com · checked 2026-10-03
Apple Home — Matter path · checked 2026-09-04
Apple Home — Matter path · checked 2026-10-03
Google Home · Works
This device supports open/close.
Setup: Matter controller
Matter controller. Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
The one platform named in both of Zemismart's enumerations and in the product title. Same mechanism as the other Matter cells, and the same unnamed requirement: a Google hub that acts as a Thread border router. Zemismart writes 'Google Home', which is the app rather than the voice service.
Connection documentation: [1] [14]
Device documentation: [1] [14]
zemismart.com · checked 2026-10-03
Google Home — Matter path · checked 2026-10-03
Alexa · Works
This device supports open/close.
Setup: Matter controller
Matter controller. Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
Named in the feature block's 'Supports HomeKit, Google Home, Alexa, SmartThings for easy remote & voice control' and absent from the description's enumeration, which lists HomeKit, Google Home, SmartThings, Home Assistant and Homey. The two lists on this page do not match, and the union is taken rather than the intersection because neither list denies what the other names - each is an incomplete enumeration rather than a contradiction. Reaching Alexa requires an Echo device that is both a Thread border router and a Matter controller; Zemismart names no such requirement and no specific device.
Connection documentation: [2] [14]
Device documentation: [1] [14]
zemismart.com · checked 2026-10-03
Alexa — Matter path · checked 2026-09-04
SmartThings · Works
This device supports open/close.
Setup: Matter controller
Matter controller. Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
Named in both Zemismart enumerations and in the product title. Same Matter-over-Thread mechanism, and the same unstated requirement for a SmartThings hub with a Thread radio - not every SmartThings hub has one, and Zemismart does not raise the distinction.
Connection documentation: [1] [14]
Device documentation: [1] [14]
zemismart.com · checked 2026-10-03
SmartThings — Matter path · checked 2026-10-07
SmartThings — Matter path · checked 2026-10-14
SmartThings — Matter path · checked 2026-10-14
SmartThings — Matter path · checked 2026-10-14
SmartThings — Matter path · checked 2026-10-14
Home Assistant · Works
This device supports open/close.
Setup: Matter controller
Matter controller. Zemismart states the dependency generically as 'via smart home hub' and names no model, no brand and no Thread version. Recorded as the Matter controller the protocol requires rather than as a Zemismart product, because Zemismart itself never restricts it to one.
Named in the description's enumeration - 'works with HomeKit, Google Home, SmartThings, Home Assistant, and Homey' - and in the page title, which reads 'Works with HomeKit Homey Home Assistance Google Home SmartThings'. That title is worth a note, because the shorter product title above it reads 'HomeKit Google Home Assistant Smartthings' and can be parsed two ways: as Google Home plus Home Assistant, or as Google plus Home Assistant. The longer title, which separates 'Homey', 'Home Assistance' and 'Google Home' into distinct items, is what settles it - Home Assistant is being named as a platform in its own right. Absent from the feature block's shorter list. Home Assistant reaches Matter devices through its own Matter integration and a Thread border router, which is a route Home Assistant documents generally rather than something Zemismart built.
Connection documentation: [2] [14]
Device documentation: [1] [14]
zemismart.com · checked 2026-10-03
Home Assistant — Matter path · checked 2026-10-04
A documented control or event is one part of a setup. It does not by itself establish a complete automation.
A platform connection does not confirm every function. Controls and reported events are shown separately from what an automation can use.
Compare all five platforms. On a narrow screen, scroll the table sideways.
| Device function | Apple HomeWorks[1][14] | Google HomeWorks[1][14] | AlexaWorks[2][14] | SmartThingsWorks[1][14] | Home AssistantWorks[2][14] |
|---|---|---|---|---|---|
| Open/closeDevice control | Control Supported for this Matter device type Automation ✓ routines can use it | Control Supported for this Matter device type Automation ✓ routines can use it | Control Supported for this Matter device type Automation ✓ routines can use it | Control Supported for this Matter device type Automation ✓ routines can use it | Control Supported for this Matter device type Automation — |
✓ Documented for this connection. × A stated limit. ◐ A partial function. ? Not established. A listed device function does not establish a complete routine, its other equipment or any plan requirements.
Matter device-type support is based on the platform’s list for this kind of device; this exact model is not named.
Named in both of Zemismart's own product enumerations - the description's 'works with HomeKit, Google Home, SmartThings, Home Assistant, and Homey' and the feature block's 'Supports HomeKit, Google Home, Alexa, SmartThings for easy remote & voice control' - and the mechanism is the one thing about this product that is not in doubt, because Matter over Thread is what the product is. Transport is recorded as local for the same reason: a Matter device commissioned to an Apple Home border router is controlled over Thread on the local network, not through a Zemismart cloud. One caveat belongs on this cell: Zemismart names Siri voice control, but Apple's own accessory list does not name this product. The Matter certification itself checks out, because the Matter certification ledger lists the MTP1 as certified.[1][14]
The one platform named in both of Zemismart's enumerations and in the product title. Same mechanism as the other Matter cells, and the same unnamed requirement: a Google hub that acts as a Thread border router. Zemismart writes 'Google Home', which is the app rather than the voice service.[1][14]
Named in the feature block's 'Supports HomeKit, Google Home, Alexa, SmartThings for easy remote & voice control' and absent from the description's enumeration, which lists HomeKit, Google Home, SmartThings, Home Assistant and Homey. The two lists on this page do not match, and the union is taken rather than the intersection because neither list denies what the other names - each is an incomplete enumeration rather than a contradiction. Reaching Alexa requires an Echo device that is both a Thread border router and a Matter controller; Zemismart names no such requirement and no specific device.[2][14]
Named in both Zemismart enumerations and in the product title. Same Matter-over-Thread mechanism, and the same unstated requirement for a SmartThings hub with a Thread radio - not every SmartThings hub has one, and Zemismart does not raise the distinction.[1][14]
Named in the description's enumeration - 'works with HomeKit, Google Home, SmartThings, Home Assistant, and Homey' - and in the page title, which reads 'Works with HomeKit Homey Home Assistance Google Home SmartThings'. That title is worth a note, because the shorter product title above it reads 'HomeKit Google Home Assistant Smartthings' and can be parsed two ways: as Google Home plus Home Assistant, or as Google plus Home Assistant. The longer title, which separates 'Homey', 'Home Assistance' and 'Google Home' into distinct items, is what settles it - Home Assistant is being named as a platform in its own right. Absent from the feature block's shorter list. Home Assistant reaches Matter devices through its own Matter integration and a Thread border router, which is a route Home Assistant documents generally rather than something Zemismart built.[2][14]
Open/close: Home Assistant setup limit
Platform documentation:
zemismart.com · checked 2026-10-03
Apple Home — Matter path · checked 2026-09-04
Apple Home — Matter path · checked 2026-10-03
Google Home — Matter path · checked 2026-10-03
Alexa — Matter path · checked 2026-09-04
SmartThings — Matter path · checked 2026-10-07
SmartThings — Matter path · checked 2026-10-14
SmartThings — Matter path · checked 2026-10-14
SmartThings — Matter path · checked 2026-10-14
SmartThings — Matter path · checked 2026-10-14
Home Assistant — Matter path · checked 2026-10-04
Listed device functions are established from vendor documentation. An ability missing here is unestablished, not necessarily absent.
| Ecosystem | Support | The catch |
|---|---|---|
| Apple Home | WorksWorks with this ecosystem[1][14] | Named in both of Zemismart's own product enumerations - the description's 'works with HomeKit, Google Home, SmartThings, Home Assistant, and Homey' and the feature block's 'Supports HomeKit, Google Home, Alexa, SmartThings for easy remote & voice control' - and the mechanism is the one thing about this product that is not in doubt, because Matter over Thread is what the product is. Transport is recorded as local for the same reason: a Matter device commissioned to an Apple Home border router is controlled over Thread on the local network, not through a Zemismart cloud. One caveat belongs on this cell: Zemismart names Siri voice control, but Apple's own accessory list does not name this product. The Matter certification itself checks out, because the Matter certification ledger lists the MTP1 as certified.In Apple Home you also need: a Matter controller |
| Amazon Alexa | WorksWorks with this ecosystem[2][14] | Named in the feature block's 'Supports HomeKit, Google Home, Alexa, SmartThings for easy remote & voice control' and absent from the description's enumeration, which lists HomeKit, Google Home, SmartThings, Home Assistant and Homey. The two lists on this page do not match, and the union is taken rather than the intersection because neither list denies what the other names - each is an incomplete enumeration rather than a contradiction. Reaching Alexa requires an Echo device that is both a Thread border router and a Matter controller; Zemismart names no such requirement and no specific device.In Amazon Alexa you also need: a Matter controller |
| Google Home | WorksWorks with this ecosystem[1][14] | The one platform named in both of Zemismart's enumerations and in the product title. Same mechanism as the other Matter cells, and the same unnamed requirement: a Google hub that acts as a Thread border router. Zemismart writes 'Google Home', which is the app rather than the voice service.In Google Home you also need: a Matter controller |
| SmartThings | WorksWorks with this ecosystem[1][14] | Named in both Zemismart enumerations and in the product title. Same Matter-over-Thread mechanism, and the same unstated requirement for a SmartThings hub with a Thread radio - not every SmartThings hub has one, and Zemismart does not raise the distinction.In SmartThings you also need: a Matter controller |
| Home Assistant | WorksWorks with this ecosystem[2][14] | Named in the description's enumeration - 'works with HomeKit, Google Home, SmartThings, Home Assistant, and Homey' - and in the page title, which reads 'Works with HomeKit Homey Home Assistance Google Home SmartThings'. That title is worth a note, because the shorter product title above it reads 'HomeKit Google Home Assistant Smartthings' and can be parsed two ways: as Google Home plus Home Assistant, or as Google plus Home Assistant. The longer title, which separates 'Homey', 'Home Assistance' and 'Google Home' into distinct items, is what settles it - Home Assistant is being named as a platform in its own right. Absent from the feature block's shorter list. Home Assistant reaches Matter devices through its own Matter integration and a Thread border router, which is a route Home Assistant documents generally rather than something Zemismart built.In Home Assistant you also need: a Matter controller |
✓ Works without a subscription: Yes.
Vendor account required: Not established — we have not sourced this yet.
No subscription is referenced anywhere on Zemismart's listing for this product. Recorded on absence: there is no Zemismart pledge that anything stays free, and no Zemismart account or app tier is described on the page at all. A Matter device commissioned into a third-party ecosystem is in any case operated by that ecosystem's app rather than by the vendor's, which limits what a vendor subscription could plausibly gate.
Zemismart publishes almost no specifications for this motor, and for a retrofit blind driver that is the catch rather than a footnote. There is no battery capacity, no charging method, no rated load or maximum shade weight, no dimensions, no working temperature and no warranty term anywhere on the listing - which means the single question a buyer needs answered, will it lift my shade, has no first-party answer. Second, the hub requirement is real and unnamed: this is a Thread device, so it needs a Thread border router and a Matter controller before it does anything at all, and Zemismart's entire statement on the subject is 'Support Matter-cetified ecosystem via smart home hub'. A household without an Apple TV, HomePod, Nest hub, Thread-capable SmartThings hub or equivalent is buying a second product it has not been told about. Third, the two platform lists on the page disagree about which ecosystems are supported - one names Home Assistant and Homey, the other names Alexa - and this record takes the union of the two rather than either one. Finally, the price is a flash-sale figure against a struck-through list price, and the shipping origin is a dropdown spanning five countries, so what arrives and how long it takes depends on a choice made at checkout.
Someone who already has a Thread border router in the house - an Apple TV or HomePod, a Nest hub, a Thread-capable SmartThings hub, or Home Assistant with a Thread stick - and wants a cheap way to motorise an existing roller, zebra, venetian or honeycomb blind without a vendor bridge or a vendor account in the middle. The appeal is genuine and specific: a Matter device joins the ecosystem the household already runs, is controlled locally, and does not add another app. It suits someone comfortable buying hardware whose specifications are not published, and confident their shade is well within whatever the motor can pull. It is the wrong pick for a household with no Thread border router, since that cost is not on the listing; or for anyone who needs to know the load rating before ordering, because Zemismart does not publish one.
This opens Zemismart's own website. We earn nothing from this link.
Numbered sources below back the facts marked with the matching number above. This is a research profile: compiled from manufacturer documentation, certification registries, and published testing — we state facts, not verdicts, and we have not physically tested this unit. How we work →
Compatibility and lifecycle information reflects the last-verified date above and can change without notice (firmware updates, cloud-service changes, discontinuations). It is provided as-is, for information — verify with the manufacturer before purchasing. Spot an error? Tell us and we'll fix it. Full terms: Terms of Service.
Your platform, exact hub and the functions you need determine the answer. A Setup Check researches how they fit together.