-
Notifications
You must be signed in to change notification settings - Fork 1
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
Provide sensible, default-enabled channel configurations #235
Comments
It's unclear to me what sensible defaults would be for the bias DAC setting. Some options:
|
I don't see a way either to do it without valid settings. The best we can do is the following: If there are valid settings (hence a calibrated bias voltage), and if the settings do not indicate that the channel should remain off, use that voltage and turn on the channel. With that it will work without broker once the user has set up the bias voltage on a channel once and saved the settings. |
This is already the current behavior. If the channel is saved in an "Active" state, it will power-on by default at power-up, but this still necessitates using a broker once for initial setup |
Closing as resolved. It's not clear that we should have different default settings than what already exist. |
Reopening this. We discussed that there's interest from Creotech in either:
This would allow shipment of boosters in a default usable state without the owner having to set up any MQTT broker. |
Currently, Booster keeps everything disabled by default until a channel is configured via the MQTT broker. While this safe, it can result in an unsatisfying user experience where Booster does not do anything out-of-the-box until it is connected to the MQTT broker and configured.
I twould be useful to provide sensible default configurations for Booster channels such that they are enabled by default.
The text was updated successfully, but these errors were encountered: