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

Misleading project name (should be mqtt2homekit) #170

Open
fredck opened this issue Jun 1, 2022 · 2 comments
Open

Misleading project name (should be mqtt2homekit) #170

fredck opened this issue Jun 1, 2022 · 2 comments

Comments

@fredck
Copy link

fredck commented Jun 1, 2022

The scope of this project is to expose MQTT devices into HomeKit. Therefore, I believe the correct name for it should be mqtt2homekit.

Please correct me if I'm wrong.


I reached this repository because I was searching for the opposite: to expose HomeKit devices into MQTT (hence the name confusion).

The problem I'm trying to solve is controlling some HomeKit devices which cannot be added to Home Assistant (e.g. Thread enabled devices like Nanoleak and Eve stuff) with Home Assistant through MQTT.

@ultrathew
Copy link

Hi @fredck I'm in the exact same situation. Let me know if you find a solution, and I'll do the same.

@noelhibbard
Copy link

noelhibbard commented Jan 20, 2023

Agreed on the poor naming. I am also looking for a way to programmatically control native HomeKit devices and thought this was the solution. The search continues.

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

No branches or pull requests

3 participants