[FEATURE REQUEST] Allow configuring a custom Home Assistant MQTT Discovery prefix #215
Labels
feature request
New feature or request
Comments
CWSpear
changed the title
CWSpear
changed the title
|
You're indeed the first one with this request, because it's the standard prefix |
Merged
Blueforcer
added a commit
that referenced
this issue
Jul 25, 2023
### 📈 New Features - Allows to loop the sound in notifications sou youre able to build your own timer or Alarm Clock for example. closes #232 - Youre able to save Customapps wich are reloaded automatically after boot - Adds effects wich can be used in Notifications, CustomApps and as a general background layer. - Allows to set the Home Assistant MQTT Discovery prefix. Closes #215 ### 🐞 Bug Fixes and Optimizations - Sets comma one pixel down. closes #208 - Removes Eyes native app and add it as an effect - Removes Timer and Alarm, not in code for now, but in documentation. This gives you time to write your own timer and alarm clock via smarthome (whats the base idea of awtrix) until it will be removed also from code in the next version. - Fixes a bug with textOffset & pushIcon in customapps. closes #231 - Fixes a bug in colorconvertion when sending RGB array. closes #230 - Fixes a bug in customapp duration calculation. closes #204 - Fixes a bug where the menu text gets Textcolors from Customapps - Ignores repeat if noScroll is set to true. closes #216
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Is your feature request related to a problem?
The Home Assistant MQTT Discovery is configurable in Home Assistant. awtrix hardcodes it to
homeassistantDescribe the solution / feature you'd like
Please allow the Home Assistant MQTT Discovery to be configurable if HA MQTT Discovery is enabled.
Describe alternatives you've considered
I've considered changing my discovery prefix, but that would require changing a lot of other things, I don't even know all what I've got set up using it, but more than a few. I also can't be the only one use has this issue.
The text was updated successfully, but these errors were encountered: