# Homeycompose and Custom View

**URL:** <https://community.homey.app/t/homeycompose-and-custom-view/134009>\
**Category:** Developers\
**Created:** [April 3, 2025, 7:48pm UTC](https://community.homey.app/t/homeycompose-and-custom-view/134009 "2025-04-03T19:48:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![s\_dimaio](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/s_dimaio/32/78995_2.png) [@s\_dimaio](https://community.homey.app/u/s_dimaio)\
**Post date:** [April 3, 2025, 7:48pm UTC](https://community.homey.app/t/homeycompose-and-custom-view/134009/1 "2025-04-03T19:48:38Z")

</div>

Hi, I’m using templates in homeycompose to use the common driver.json code on multiple drivers, in particular the part relating to pairing. To do the paring I use a custom view that is the same for all drivers.  
Unless I’m mistaken, despite using homeycompose the custom view must be inserted inside the “pair” folder of each driver with the result that I have several custom\_view.html (one for each driver) all the same and I have to repeat each change on each file. Is it possible to simplify this part by providing a single custom\_view.html for all my drivers?

Thanks in advance,

Simone

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [April 4, 2025, 4:47am UTC](https://community.homey.app/t/homeycompose-and-custom-view/134009/2 "2025-04-04T04:47:39Z")

</div>

> [@s\_dimaio](#):
>
> Is it possible to simplify this part by providing a single custom\_view.html for all my drivers?

AFAIK it’s not possible. I remember asking for this feature _years_ ago, but making developer life easier doesn’t get a lot of priority.

I also don’t think `homey` allows for additional build steps to be added that would allow you to run a script to copy the file to all driver directories, so the only option I see for that is to create a script entry in `package.json` that does that. However, that would require a manual `npm run SCRIPT` before each `homey run`.

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [April 5, 2025, 8:20pm UTC](https://community.homey.app/t/homeycompose-and-custom-view/134009/3 "2025-04-05T20:20:39Z")

</div>

Just to be clear… you want to use one view (html) for all devices?  
Yes, that’s possible. It’s the same for pair and repair.  
You have to use a folder with custom view id as folder name and a index.html in every view folder.  
Example:

> **[io.home-assistant.community/.homeycompose/drivers at main ·...](https://github.com/RonnyWinkler/io.home-assistant.community/tree/main/.homeycompose/drivers)**
>
> Home-assistant integration for Homey (Community version) - RonnyWinkler/io.home-assistant.community

PS: The content (html) from homeycompose is copied into your driver par/repair folder on run/install/publish. So don’t edit these driver filey when using homeycompose.

---

<div class="post-metadata">

**Author:** ![s\_dimaio](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/s_dimaio/32/78995_2.png) [@s\_dimaio](https://community.homey.app/u/s_dimaio)\
**Post date:** [April 6, 2025, 12:46pm UTC](https://community.homey.app/t/homeycompose-and-custom-view/134009/4 "2025-04-06T12:46:56Z")

</div>

Thanks Ronny! It works perfectly! Just a curiosity…how did you find out? Except for my errors, in the documentation nothing is reported

---

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [April 6, 2025, 8:35pm UTC](https://community.homey.app/t/homeycompose-and-custom-view/134009/5 "2025-04-06T20:35:30Z")

</div>

I think I found an example in app code on Github.  
At that time, it was only possible for pair flows. So I added the repair version as Github PR becaus that was what I needed 😁  
But yes, it’s not documented - same for other details about driver settings compose or capability filter for flows 🤷‍♂️
