# \[Request\] Web interface

**URL:** <https://community.homey.app/t/request-web-interface/117072>\
**Category:** Dashboards\
**Created:** [October 1, 2024, 11:04am UTC](https://community.homey.app/t/request-web-interface/117072 "2024-10-01T11:04:30Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![Farside](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/farside/32/124754_2.png) [@Farside](https://community.homey.app/u/Farside)\
**Post date:** [January 10, 2025, 11:00am UTC](https://community.homey.app/t/request-web-interface/117072/81 "2025-01-10T11:00:12Z")

</div>

> [@Emile](#):
>
> Web app usage is less than 20% of all users.

It’s a bit inconsistent strategy 🙂 While “advanced flow” functions are web only, but at the same time dashboards are mobile only. No place in Homey rules it all, you always have to be split between UI apps. I guess the 20% of users are folks who need the “advanced flow” or bigger “Insights” graphs constantly.  
Being a developer myself, I see a lot possibilities for re-usage of components alike the UIX from Insights into Dashboards, and vice-versa. In ideal case they should have the same look-n-feel, as a function. A good showcase is: a User can stack up several graphs at Insights in one graph, while I can’t do this at Dashboards, while the UIX of the graph looks the same. When you account for a HomeScreen - it comes even more obvious, that UIX between all three parts of the systems is the same: **Dashboards** , **Homescreen** , and **Insights**. This would “kill all the birds with one stone”, if one UIX-component would rule them all.

It’s what comes first here, a chicken or an egg. I’m guessing that when dashboards become available on the web, more users will adopt them. I enjoy a bigger screen when doing major configurations on my Homey Pro. I wish I could do most of it through the Web, while the final touches and daily usage itself is through a Tablet or Mobile device.

The dream scenario would be to have unique links for specific **Dashboards** and the possibility to save graphs from **Insights** - so they are easily accessible from any type of device through a web browser, computer, tablet, or mobile. This will give a new boost to Homey’s popularity and provoke the creation of new apps/dashboards/metrics/control panels.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [January 10, 2025, 11:16am UTC](https://community.homey.app/t/request-web-interface/117072/82 "2025-01-10T11:16:18Z")

</div>

> [@Farside](#):
>
> The dream scenario would be to have unique links for specific **Dashboards** and the possibility to save graphs from **Insights** - so they are easily accessible from any type of device through a web browser

Is is already the case.

---

<div class="post-metadata">

**Author:** ![Farside](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/farside/32/124754_2.png) [@Farside](https://community.homey.app/u/Farside)\
**Post date:** [January 10, 2025, 11:25am UTC](https://community.homey.app/t/request-web-interface/117072/83 "2025-01-10T11:25:48Z")

</div>

> [@Dijker](#):
>
> Is is already the case.

Hm, how can I access it? Isn’t the whole discussion here about **Dashboard** components are not being made for Web, and you can’t access it yet through the Web interface technically …  
at least this is what @Emile said:

> Web app … Unfortunately **the codebase is not very compatible** , even though we use React Native & React.

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [January 10, 2025, 11:34am UTC](https://community.homey.app/t/request-web-interface/117072/84 "2025-01-10T11:34:45Z")

</div>

> [@Farside](#):
>
> to save graphs from **Insights**

Like here

> [@\[Feature Request\] Shortcut button for favourite graphs in Insight](https://community.homey.app/t/feature-request-shortcut-button-for-favourite-graphs-in-insight/49929/15):
>
> After selecting and/or combining you can bookmark it in your browser:
> 
> will look something like this: https[:][//my.homey.app/homeys/deaf0001badx1337/insights?logs1=homey:manager:system:loadavg&logs2=homey:manager:system:memusage](https://my.homey.app/homeys/deaf0001badx1337/insights?logs1=homey:manager:system:loadavg&logs2=homey:manager:system:memusage)
> 
> and then return to it through using the bookmark

---

<div class="post-metadata">

**Author:** ![Farside](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/farside/32/124754_2.png) [@Farside](https://community.homey.app/u/Farside)\
**Post date:** [January 10, 2025, 12:44pm UTC](https://community.homey.app/t/request-web-interface/117072/85 "2025-01-10T12:44:00Z")

</div>

ah, yes, that I know, thank you!  
Yet we stepped out slightly from the original discussion line: the thread has a tag on **Dashboards** primarily, and this trick doesn’t work, unfortunately. We, as a Homey Users, have to bounce between Native App and Web, as the functions/possibilities differ.

**Dashboards** work only on Mobile (Native app), while **Insights** and **Advanced flows** are accessible from Web interface only. Ideally, we need a place that rules them all.

---

<div class="post-metadata">

**Author:** ![Theo\_de\_Koning](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/theo_de_koning/32/136062_2.png) [@Theo\_de\_Koning](https://community.homey.app/u/Theo_de_Koning)\
**Post date:** [January 14, 2025, 8:54am UTC](https://community.homey.app/t/request-web-interface/117072/86 "2025-01-14T08:54:58Z")

</div>

When I following the progress of this “mobile-phone” dashboard I see more and more tablet user posting there results.  
To see it for myself I get 4 x 3 switches in one row on my tablet.

My conclusion is:

- Mobile-phone is only for a quick look at it
- Homey dashboard is only good for tablets.
- An web dashboard is now more logical.

---

<div class="post-metadata">

**Author:** ![ricardovl](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ricardovl/32/16441_2.png) [@ricardovl](https://community.homey.app/u/ricardovl)\
**Post date:** [January 21, 2025, 9:49am UTC](https://community.homey.app/t/request-web-interface/117072/87 "2025-01-21T09:49:02Z")

</div>

@Emile What about raspberi pi with a cheap monitor like [Pora&Co - IPS Portable Game Monitor - Touchscreen - Beeldscherm 15.6 Inch - HDMI &... | bol](https://www.bol.com/nl/nl/p/pora-co-ips-portable-game-monitor-touchscreen-beeldscherm-15-6-inch-hdmi-usb-c-full-hd-computerscherm-draagbare-monitor/9300000172758451/?s2a=&bltgh=nST-hkTFbEOkw7I0JSFO7A.2_53_54.55.FeatureOptionButton#productTitle)

That way we can create insane dashboards with homey in our home.

Android tablets have batteries which die when constantly on power, are small and way more expensive.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 21, 2025, 10:02am UTC](https://community.homey.app/t/request-web-interface/117072/88 "2025-01-21T10:02:54Z")

</div>

You can install Android + Homey app on a Rpi, so your plan is already possible.  
I’m not sure if just any touchscreen can interact with Rpi / Android.

> [@ricardovl](#):
>
> Android tablets have batteries which die when constantly on power

Hmmm, not all of them: my 2011 samsung tablet was powered continuously until last year, only then I had to put in a €15 replacement battery.

---

<div class="post-metadata">

**Author:** ![Theo\_de\_Koning](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/theo_de_koning/32/136062_2.png) [@Theo\_de\_Koning](https://community.homey.app/u/Theo_de_Koning)\
**Post date:** [January 21, 2025, 10:44am UTC](https://community.homey.app/t/request-web-interface/117072/89 "2025-01-21T10:44:22Z")

</div>

So, now we have to bye extra stuff because the only thing where this dashboard is properly working on can handle 24/7 h battery on power.

---

<div class="post-metadata">

**Author:** ![homeslice](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homeslice/32/121525_2.png) [@homeslice](https://community.homey.app/u/homeslice)\
**Post date:** [January 22, 2025, 5:12pm UTC](https://community.homey.app/t/request-web-interface/117072/90 "2025-01-22T17:12:31Z")

</div>

I want web-based dashboards. Being on a browser would allow for more complex dashboard options and configurations as well. Because I want to build epic dashboards. I want status widgets to flash red when there’s an error condition. I want the whole dashboard to reconfigure itself under certain conditions.

For example, when my Nest Smoke Alarm go off, I want the dashboard to immediately show me all the smoke alarms so I can see the room with the emergency condition. Taking out my phone, unlocking it, loading up the app, waiting for it to refresh, clicking Nest Protect, takes forever when alarms are blaring. I’d rather glance at a home status dashboard on the wall real quick. That’s what I want to build with Homey.

---

<div class="post-metadata">

**Author:** ![homeslice](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homeslice/32/121525_2.png) [@homeslice](https://community.homey.app/u/homeslice)\
**Post date:** [January 23, 2025, 4:14pm UTC](https://community.homey.app/t/request-web-interface/117072/92 "2025-01-23T16:14:46Z")

</div>

It’s an example of an advanced dashboard. Replace emergency with whatever you want. Stay on target.

---

<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:** [January 23, 2025, 4:22pm UTC](https://community.homey.app/t/request-web-interface/117072/93 "2025-01-23T16:22:17Z")

</div>

The things you want don’t mix well with how Homey’s dashboards are structured, where each widget is basically a standalone webview showing some HTML. Running it in a browser doesn’t make that any different.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 23, 2025, 5:34pm UTC](https://community.homey.app/t/request-web-interface/117072/94 "2025-01-23T17:34:50Z")

</div>

> [@homeslice](#):
>
> Stay on target.

??  
A nice day to you too.

---

<div class="post-metadata">

**Author:** ![homeslice](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/homeslice/32/121525_2.png) [@homeslice](https://community.homey.app/u/homeslice)\
**Post date:** [January 23, 2025, 9:16pm UTC](https://community.homey.app/t/request-web-interface/117072/95 "2025-01-23T21:16:20Z")

</div>

Sorry, what I’m trying to say is that:

If Homey dashboards could be managed via the web app, then it would allow for more complex dashboard building and management. Like how Advanced Flows can only be managed via the web app because they’re too complex to try to force into a mobile app. Similarly, if Advanced Dashboards could be managed via the web app, then it would allow the developers to integrate more complex features.

Keeping dashboard management relegated to the mobile app pigeonholes the development team on what features are even possible to implement because anything complex is not practically feasible to implement on a mobile platform. It creates an artificial ceiling on what features are possible, similar to Flows vs Advanced Flows.

---

<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:** [January 24, 2025, 5:45am UTC](https://community.homey.app/t/request-web-interface/117072/96 "2025-01-24T05:45:04Z")

</div>

The features you want would basically require a complete rewrite of how dashboards are implemented (even more so than advanced flows, which are still “the same” flows under the hood).

And since dashboards are a recent add-on, I doubt that this will happen anytime soon. Athom has indeed created an artificial ceiling, but we have to assume they did so intentionally (😂).

---

<div class="post-metadata">

**Author:** ![Peter\_de\_Vos](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_de_vos/32/151925_2.png) [@Peter\_de\_Vos](https://community.homey.app/u/Peter_de_Vos)\
**Post date:** [January 24, 2025, 11:26am UTC](https://community.homey.app/t/request-web-interface/117072/97 "2025-01-24T11:26:13Z")

</div>

And there are other options for what he wants.

---

<div class="post-metadata">

**Author:** ![Greg\_Veres](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/greg_veres/32/113389_2.png) [@Greg\_Veres](https://community.homey.app/u/Greg_Veres)\
**Post date:** [January 27, 2025, 1:51pm UTC](https://community.homey.app/t/request-web-interface/117072/98 "2025-01-27T13:51:02Z")

</div>

Just adding my voice to the intense disappointment when I found out that dashboard configuration is not available in the webapp. I completely expected that it would be there and was shocked when it wasn’t. Setting up a dashboard on a small screen of a phone is completely insane.

---

<div class="post-metadata">

**Author:** ![larspalmqvistdk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/larspalmqvistdk/32/61333_2.png) [@larspalmqvistdk](https://community.homey.app/u/larspalmqvistdk)\
**Post date:** [February 3, 2025, 7:37am UTC](https://community.homey.app/t/request-web-interface/117072/99 "2025-02-03T07:37:02Z")

</div>

Why why why. Whats wrong with todays developer when they dont meet the need of the market. i was so happy in seeing that one could do mood in homey that could perhaps fix the missing grouping and controlling of several devices, all my work is being don on my mac laptop, where i cant get the ipad app to function, so unfurtunately i cannoth do moods, i know it is doable on the phone . But " come on " meet people where they work. The same goes for Dashboard , whoom in there wildest fantasy would sit on the phone and layout a dashboard, again Come into the game and do it right.  
Sorry for the complain have spend all weekend on my homey with all the lacking function. am i the only one being anoid over spending a furtune hoping to get a “Home assistent” replacement i gues not

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [February 3, 2025, 12:31pm UTC](https://community.homey.app/t/request-web-interface/117072/100 "2025-02-03T12:31:31Z")

</div>

Split this topic on February 3, 2025, 12:31pm UTC

A post was merged into an existing topic: [Missing functionality of Homey](https://community.homey.app/t/missing-functionality-of-homey/129616/4)

---

<div class="post-metadata">

**Author:** ![Barmoen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/barmoen/32/121492_2.png) [@Barmoen](https://community.homey.app/u/Barmoen)\
**Post date:** [February 3, 2025, 1:00pm UTC](https://community.homey.app/t/request-web-interface/117072/101 "2025-02-03T13:00:05Z")

</div>

Also gonna voice my opinion about web-based dashboards. It’s unfortunate that you’re not interested in this, I can see there’s a large demand for it and I’m hopeful you will come around and change your mind about this!

[Previous page](https://community.homey.app/t/request-web-interface/117072.md?page=4)

[Next page](https://community.homey.app/t/request-web-interface/117072.md?page=6)
