Home Assistant users hand-build missing service integrations
Home Assistant users with niche services, devices, and self-hosted tools often cannot see their data in Home Assistant because a suitable integration is missing or incomplete. They resort to REST calls, Docker-to-MQTT setups, manual API authentication, or separate vendor apps; these workarounds take effort and can still leave important entities unavailable. A maintained set of focused community integrations could address most of these requests, though the alerts, release-note, and web-grounding signals are separate problems.
For home Assistant self-hosters and smart-home power users. Mentioned from Mar 2025 to Feb 2026 on product forums.
9 different people described this problem in 7 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.1/10
- Frequency
- 8.3/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Consumers
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
At current, considering some rest calls and probably just some docker to mqtt lightweight containers, but it feels like too much recreation of native Komodo features
They only support the external provider flow. Login to https://api.petivity.com/ and obtain the refresh_token cookie value
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 7 more quotes from people who have this problem
- Current workarounds, existing solutions and risks