Skip to content
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

[Feature]: Accessory mode #414

Open
3 tasks done
BrainDeLook opened this issue Jan 10, 2025 · 7 comments
Open
3 tasks done

[Feature]: Accessory mode #414

BrainDeLook opened this issue Jan 10, 2025 · 7 comments
Labels
feature Feature Request

Comments

@BrainDeLook
Copy link

BrainDeLook commented Jan 10, 2025

Requested feature

Some smart home systems are very picky about connecting bridge configurations and require individual accessories to be connected. I would like to see an accessory mode function

Documentation & Issues

@BrainDeLook BrainDeLook added the feature Feature Request label Jan 10, 2025
@kennylevinsen
Copy link
Contributor

Some smart home systems are very picky about connecting bridge configurations and require individual accessories to be connected.

It would be good to provide known examples of such smart home systems.

@BrainDeLook
Copy link
Author

BrainDeLook commented Jan 14, 2025

It would be good to provide known examples of such smart home systems.

Yandex smart home (Alice)

@hasmar04
Copy link

There's every chance that this could solve the issues I have been having in #431 too

@t0bst4r
Copy link
Owner

t0bst4r commented Jan 16, 2025

I don't think this is related to #431.

Having an "accessory mode" would expose EACH device with its own port and pairing QR code, right?

@BrainDeLook
Copy link
Author

BrainDeLook commented Jan 16, 2025

Having an "accessory mode" would expose EACH device with its own port and pairing QR code, right?

It would be more likely that the center to which you connect the device would see it not as a bridge, but as a separate accessory, for example: a light bulb, fan, switch.

In the Homekit plugin for HA such function is realized and it is very convenien

@kennylevinsen
Copy link
Contributor

I imagine that any Matter controller has to support bridges in order to function reasonably well with pretty much any border router. What do you mean when you say that it is "picky" about bridge configurations? Do some bridges work, do bridges work sometimes, do they never work, ...?

Having to pair each device manually definitely doesn't sound convenient. The HomeKit bridge has that functionality specifically because a few specific device types are supporter by HomeKit as accessories but not over an accessory bridge for some reason. You'd do it for such individual devices like media players while keeping everything else on the bridge, but that's all very Apple HomeKit specific.

@BrainDeLook
Copy link
Author

I imagine that any Matter controller has to support bridges in order to function reasonably well with pretty much any border router. What do you mean when you say that it is "picky" about bridge configurations? Do some bridges work, do bridges work sometimes, do they never work, ...?

Having to pair each device manually definitely doesn't sound convenient. The HomeKit bridge has that functionality specifically because a few specific device types are supporter by HomeKit as accessories but not over an accessory bridge for some reason. You'd do it for such individual devices like media players while keeping everything else on the bridge, but that's all very Apple HomeKit specific.

Once again, Yandex Alice does not support the matter breeches at the moment, at least that's how the support team answered me a month after my question. This system only supports connection of separate accessories - switch, lamp, smart sockets. If you try to connect matter bridge (any one, I tried the same on aqara m1s gen2) then the smart home center just goes into error without finding any of the accessories inside it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature Request
Projects
None yet
Development

No branches or pull requests

4 participants