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

Implement Home Assistant Autodiscovery for mqqt_room #154

Closed
bluesheep opened this issue Dec 22, 2021 · 8 comments
Closed

Implement Home Assistant Autodiscovery for mqqt_room #154

bluesheep opened this issue Dec 22, 2021 · 8 comments
Labels
enhancement New feature or request next Next in line to be worked on wontfix This will not be worked on

Comments

@bluesheep
Copy link

bluesheep commented Dec 22, 2021

Is your feature request related to a problem? Please describe.
I would like devices that I'm tracking to be automatically discovered and configured within home assistant.

Describe the solution you'd like
Newly discovered BLE devices should be able to publish their MQTT information in a format that allows home assistant to automatically discover them as new devices.

Describe alternatives you've considered
The existing process of manually editing sensors is functional but suboptimal.

Additional context
In high traffic areas this is likely to result in a lot of devices being discovered within home assistant. Consideration should be made for whether a whitelist/blacklist solution is required. c.f. #152

@bluesheep bluesheep added the enhancement New feature or request label Dec 22, 2021
@corgan2222
Copy link
Contributor

I will look into this.

@bluesheep
Copy link
Author

@corgan2222 let me know if I can do anything to help. I've got the code compiling and uploading locally. I'm OK at writing code but I have no experience with GitHub, and only hobby hacking with c++.

@corgan2222
Copy link
Contributor

Thanks. ATM im working on support for more input/output pins, like LED, switches, aso.
After that, I will look into this.

@stale stale bot added the wontfix This will not be worked on label Apr 3, 2022
@stale stale bot closed this as completed Apr 10, 2022
@ESPresense ESPresense deleted a comment from stale bot Aug 30, 2022
@DTTerastar
Copy link
Contributor

With v3 we now have the beginning of a ui (see /ui/) that I intend to use to make this happen. Stay tuned!

@bluesheep
Copy link
Author

Woohoo!

@DTTerastar DTTerastar reopened this Aug 30, 2022
@stale stale bot removed the wontfix This will not be worked on label Aug 30, 2022
@DTTerastar DTTerastar added the next Next in line to be worked on label Sep 1, 2022
@DTTerastar
Copy link
Contributor

next!

@stale stale bot added the wontfix This will not be worked on label Nov 1, 2022
@bluesheep
Copy link
Author

Still keen. Only replying to distract the stalebot

@stale stale bot removed the wontfix This will not be worked on label Nov 1, 2022
@ESPresense ESPresense deleted a comment from stale bot Dec 10, 2022
@stale
Copy link

stale bot commented Mar 10, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Mar 10, 2023
@stale stale bot closed this as completed Mar 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request next Next in line to be worked on wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants