Feature request: Password protection of adding lights to app

[fribse]

Hi Aircookie

The 0.9.0-b1 is performing very well here. Very smooth. I had an idea, because I've now added some LED's to my youngest desk, and as some features are not controllable through the IKEA remote I've given him, he has to have the WLED app installed. This in itself is not a problem, everybody can just download it, but it is a problem that he (and others) can add our lights to their app, and create chaos for us (if they have access to our Wifi of course).

Thus I would very much like to have a password protection or the like, built in to the code, so that you have to give the password in the app to be allowed to add it.

This will eliminate the problem of him (and others) making funny effects with the other wled's in the house.

My thought was that you could set the password during the initial setup, and then to be able to add it to the app, you would have to enter the password as well.

[Aircoookie]

Hi! I am glad that you like WLED!

It would probably be a good idea for me to implement one of the following at some point:

• Password protection for UI
• API key system so that you need to approve any new client device before it may control the light
• Limited accessibilty, e.g. only from certain white-listed IPs

What you could do for now though, is after adding the light to every app you want to control it from, clear the mDNS field in WiFi settings. This will make it impossible for the app to discover the light (you can still add it manually by IP though)

[fribse]

An API key system would be perfect, but might also be overkill :-) I guess White-listing and PW protection would be the low-hanging fruits. Ok, good to know. I'll do that to start with, as the other lights are already present, and connected to HA.

[blazoncek]

#2610 has a PIN code as a protection mechanism for changing Settings.