Enhancement QR Code generated from secrets.yaml

[open-forest]

Enhancement Summary

I would like to have a central place to store my Guest Wifi password

Detailed Description

Could we reference secrets.yaml in the QR code field (e.g. !wifi_password instead of actual password)?

The idea being that if we can store the Wifi password in secrets.yaml, we do not have to manually update each and every NSPanel blueprint when we update/change the Wifi password. I have one panel per room, lots of rooms, so that is a lot of manual work. Use case could be an AirBNB where it might be useful to change the WiFi password between guests.

Additional Context

https://community.home-assistant.io/t/how-to-use-secrets-yaml-in-addons/358504

[tbretz65]

If the entry is contained in the secrets, then you always have to rebuild nspanel.
In the HA there is an action to execute.
With this it is possible to recreate the qr code

[edwardtfn]

Implement this from a secret is feasible, but it would be as a overlap to whatever is set on the blueprint, however, as @tbretz65 mentioned, you will have to flash your panel every time the QR code changes.
One option is to use a sensor (or an input text helper) to dynamically populate the QR code, which looks more logical for your use case.
There was #504 about this when I've started playing with this project. That was never merged, but would be an easy implementation.
In this case, you can use a template sensor getting the value from your secret. 😉
Please let me know your thoughts.

[open-forest]

Hey Edward, That sounds like a great solution! Your support is second to none. Thanks!

…

On Thu, Sep 19, 2024 at 12:09 AM Edward Firmo ***@***.***> wrote: Implement this from a secret is feasible, but it would be as a overlap to whatever is set on the blueprint, however, as @tbretz65 <https://github.com/tbretz65> mentioned, you will have to flash your panel every time the QR code changes. One option is to use a sensor (or an input text helper) to dynamically populate the QR code, which looks more logical for your use case. There was #504 <#504> about this when I've started playing with this project. That was never merged, but would be an easy implementation. In this case, you can use a template sensor getting the value from your secret. 😉 Please let me know your thoughts. — Reply to this email directly, view it on GitHub <#2283 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASKOCF42I2SO37K5HB5DFHDZXJTAVAVCNFSM6AAAAABOMUSALCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRQGA2TQNBYGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>