Feature Request Guidelines 📔

Feature Requests work best if you pick an integration or core function, clearly state why it is not to your liking, then what you think it should do or what features you think are missing.
A good title goes a long way to attract attention to your problem/solution.

Remember to search the entire Feature Requests Catalog first before you add a duplicate. If you find one that is close to what you would like to see, consider voting for that one instead. The forum tool is pretty good at guessing about things that are similar, and search is also a good idea.

If your Feature Request is determined by us to be a duplicate, it will be immediately closed.

If you have a specific idea how to fix the issue, that should be added next. Examples and details that would convince others that this is a good idea are helpful here either on your Feature Request or the one you found to vote for.

Remember your audience. You are trying to recruit (usually) another community member to help you make your idea happen. While the Nabu Casa Devs are known to frequent this category, there are more Community Members and they are more often the resource that takes on projects not in the main stream of the Home Assistant.

Always remember to vote for your own Feature Request
If you won’t even vote for it, noone will.
The more votes, the more likely it will be seen which makes it more likely that it will be worked on.

If you have a feature request for the frontend (HA Dashboards & User Screen actions) you can open one in Github instead. It will not be watched for here in a forum post,

Feature Requests are NOT for:

  • Asking for help to fix your specific configuration problem / question.
  • Asking for new ZHA, ESPHome, Zigbee2MQTT, ZWaveJS, etc. hardware to be added. These links will take you to those places.
  • Anything related to non-core Custom Integrations or Add-Ons.

If there are non-core custom integrations that you want to see implemented into core, that is done by the Individual custom integration developer, so encourage them to develop the integration for core.

If you are looking for a new custom integration (Most integrations for new things start out as custom integrations) or add-on, we encourage you to develop them and contribute to the opensource project. Add-ons with a few exceptions are NOT written by the Nabu-Casa team, and are created by interested Community Contributors like You. Therefore Feature Requests for these things are pleas to the community for help, not requests to Nabu-Casa. Be sure to promote your idea to interested parties and offer to help to get the ball rolling.