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

configuration via web interface #158

Open
dakhnod opened this issue Jun 7, 2022 · 3 comments
Open

configuration via web interface #158

dakhnod opened this issue Jun 7, 2022 · 3 comments

Comments

@dakhnod
Copy link
Contributor

dakhnod commented Jun 7, 2022

It would be great if the gateway was configurable over a web interface, without any configuration files.
Here's what I have in mind:
If no wifi is configured, the ESP starts in AP mode and presents a website to any connected device prompting for the wifi credentials.
After that, the website allows to scan BLE devices and connected to them.
After a successful connection and service discovery, the website allows to select which characteristics to subscribe to or unsubscribe from.
The website could even be used to whitelist/blacklist devices.

Obviously, all changes should somehow be persisted.

@dakhnod
Copy link
Contributor Author

dakhnod commented Jun 7, 2022

ups, me stupid. sorry.

@dakhnod dakhnod closed this as completed Jun 7, 2022
@dakhnod
Copy link
Contributor Author

dakhnod commented Jun 7, 2022

After playing with the web interface for a bit, I would still say that it would be nice to have a little whitelist button next to each discovered device.
Also, I was a bit suprised to see that the esp tries to connect to every discovered device. Maybe the the default behaviour should be an empty whitelist instead of an empty blacklist?

@dakhnod dakhnod reopened this Jun 7, 2022
@shmuelzon
Copy link
Owner

Hey,

As you've probably already seen, we have an AP started when WI-Fi isn't configured and a basic web interface.
The web interface has access to the configuration file to load and modify it so implementing a whitelist/backlist from the UI should be possible with modifications to the frontend only. One would need to take into consideration what would happen if you have a whitelist configured, and someone would like to blacklist a device as the whitelist and blacklist can't work together.
A pull request for that would be most welcome.
I guess the same can be done for services and characteristics but those would need to be exposed by the backend as well.

As for the default, if it were to be an empty whitelist, it would mean that on first installation nothing would happen. I'm less fond of that option. Only after the users have installed the application and saw that everything works, then they can start tweaking it to their needs.

Good day!

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

No branches or pull requests

2 participants