# \[APP\]\[Pro\] Dashboards

**URL:** <https://community.homey.app/t/app-pro-dashboards/84837>\
**Category:** Apps\
**Tags:** app, dashboard, homey-pro\
**Created:** [July 18, 2023, 7:45pm UTC](https://community.homey.app/t/app-pro-dashboards/84837 "2023-07-18T19:45:18Z")\
**Posts on this page:** 20\
**Page:** 44

<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 3, 2024, 1:42pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/870 "2024-01-03T13:42:55Z")

</div>

Sometime you find finally what you was looking for.  
Now I want to share it.

![](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/b/cbbc0fe6af699553bdf786f63c146a0783a90b84.jpeg)

Maart-Oktober is a variable.  
In this period it’s too long too dark in the kitchen to use the Small lamp.  
Then the main light is used.

Only the indication for one light was bordered me.  
It was not showing what like.

Then I found out that you kan change the name of the variable. (OK I’m late here 😉 )  
By reversing the colours and the icon’s I get the right one for the other period.

That Omschakelpunt Keuken (Kitchen switching point) is in Lux what the next level of switching is.  
In this case when it’s go’s on.  
But then it’s also changed to 35 Lux for going off again.  
So you have a 10 Lux buffer.

---

<div class="post-metadata">

**Author:** ![Bebopper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bebopper/32/2508_2.png) [@Bebopper](https://community.homey.app/u/Bebopper)\
**Post date:** [January 3, 2024, 2:00pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/871 "2024-01-03T14:00:27Z")

</div>

My preference would definitely be to have local access - but unfortunately this does not work (yet) for me.

And I only need Homey stored dashboards of which I have now created 2, both of them renamed.

Unfortunately I do not see either of these two Homey stored dashboards when I access the Dashboards via the Remote URL (since the Local URL does not work).

I can create browser stored dashboards, but for these I do not get any results in the ‘search box’.

My hunch is therefore a connection/rights issue since I do not see the Homey stored dashboards nor do I get any devices/capabilites back in the ‘search box’.

I double checked:

- API key has full access
- both Homey and the laptop I am using are connected to the same WiFi network

---

<div class="post-metadata">

**Author:** ![Teddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/teddy/32/13818_2.png) [@Teddy](https://community.homey.app/u/Teddy)\
**Post date:** [January 3, 2024, 2:24pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/872 "2024-01-03T14:24:58Z")

</div>

Does the local link work when you use the link on your mobile phone on local wifi? I mean opening it from the settings page on the mobile? If it does copy it to your PC.

---

<div class="post-metadata">

**Author:** ![Bebopper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bebopper/32/2508_2.png) [@Bebopper](https://community.homey.app/u/Bebopper)\
**Post date:** [January 3, 2024, 2:40pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/873 "2024-01-03T14:40:41Z")

</div>

On my phone I get exactly the same results as on my laptop ☹ .

Tried some more things;

On both the http:// and https:// versions of [[http://192-168-1-235.homey.homeylocal.com/app/skogsaas.dashboards/assets/dashboard](http://192-168-1-235.homey.homeylocal.com/app/skogsaas.dashboards/assets/dashboard)] I get a DNS error → this site cannot be reached (IP address is correct, this is Homey in my local network) - before I only tried the https:// version, now also the http://

In this topic I found the tip to try [[http://homey-MY-HOMEY-ID.local/app/skogsaas.dashboards/assets/dashboard/](http://homey-MY-HOMEY-ID.local/app/skogsaas.dashboards/assets/dashboard/) → this one does load but with an error in the console:  
`POST https:// ****************.ingest.sentry.io/api/**************** /envelope/?sentry_key= ******************** &sentry_version=7&sentry_client=sentry.javascript.svelte%2F7.69.0 net::ERR_BLOCKED_BY_CLIENT`  
The page does load but when I try to connect using the ‘Direct’ method with the API key the “Verify” does not work after I enter a (newly created) API key.

Lastly I now also tried the option using [https://homeyboard.github.io/](https://homeyboard.github.io/) and gave it full access to my Homey. Again however I do not see the dashboard locally stored on my Homey. I can create a new local dashboard (stored in the browser) but with the same issues as before - the ‘search bar’ gives no results.

---

<div class="post-metadata">

**Author:** ![Teddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/teddy/32/13818_2.png) [@Teddy](https://community.homey.app/u/Teddy)\
**Post date:** [January 3, 2024, 5:36pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/874 "2024-01-03T17:36:17Z")

</div>

That is same buildup like mine but that dns entry error is that it cant resolv the name to a ip.

What happens when you do a nslookup on the dns name you should get the internal ip. Problem is i think there is a Lets encrypt cert in the mix that only works if you have a proper dns entry resolution

You could try add the ip to the dns name in your hosts file on your computer to fool the computer todo a proper dns lookup and be able to use the cert when it connects and so on. If you try to use the ip directly it will sort of just give you the finger. If im going to be a litle colorful in my language 😉

---

<div class="post-metadata">

**Author:** ![Teddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/teddy/32/13818_2.png) [@Teddy](https://community.homey.app/u/Teddy)\
**Post date:** [January 3, 2024, 5:48pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/875 "2024-01-03T17:48:53Z")

</div>

Additional question to the above. Do you use your own dns server in your router or do you possibly use a external dns server that is controlled by your internet provider or some orther reason why the dns entry aint beeing registered for your homey. As i said you got a dns resolution problem for the address. But try that workaround i gave it should work.

---

<div class="post-metadata">

**Author:** ![skogsaas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/skogsaas/32/87995_2.png) [@skogsaas](https://community.homey.app/u/skogsaas)\
**Post date:** [January 3, 2024, 7:56pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/876 "2024-01-03T19:56:41Z")

</div>

You are not the first to report an issue similar to this. But sadly I have no clue what the issue is, as the only exception in the console is not relevant. Can you see any failed network calls? Please filter on `XHR/Fetch` and `WS`.

> [@Bebopper](#):
>
> The page does load but when I try to connect using the ‘Direct’ method with the API key the “Verify” does not work after I enter a (newly created) API key.

Yeah, this is a simple issue, but might not be fixed. My bad 😅

> [@Bebopper](#):
>
> Lastly I now also tried the option using [https://homeyboard.github.io/](https://homeyboard.github.io/) and gave it full access to my Homey. Again however I do not see the dashboard locally stored on my Homey. I can create a new local dashboard (stored in the browser) but with the same issues as before - the ‘search bar’ gives no results.

The different search dialogs should present a result immediately, without entering a search phrase.

> [@Bebopper](#):
>
> - several restarts of the app
> - restart of Homey

None of these should have any effect, btw 😅

---

<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 3, 2024, 8:38pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/877 "2024-01-03T20:38:33Z")

</div>

> [@Teddy](#):
>
> [Github.io](http://Github.io) (this is a online url solution that talks to athom homey.) Personaly i do ot realy like this one

While I have a Pro 2019, I have no choice but to like [https://homeyboard.github.io](https://homeyboard.github.io) very much 🍻

> [@Teddy](#):
>
> I had to remove my lan adapter or else

Just switch Homey’s wifi off?

---

<div class="post-metadata">

**Author:** ![Teddy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/teddy/32/13818_2.png) [@Teddy](https://community.homey.app/u/Teddy)\
**Post date:** [January 4, 2024, 9:39am UTC](https://community.homey.app/t/app-pro-dashboards/84837/878 "2024-01-04T09:39:34Z")

</div>

Hehe yea i have 2 older and a 2023. But i only use the dashboard for the 2023 homey. Yea know problem is i have to redo the entire dashboard due to the way the app links the dns for the dash devices. Am going todo that just havent gotten around to it yet 😉

---

<div class="post-metadata">

**Author:** ![Bebopper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bebopper/32/2508_2.png) [@Bebopper](https://community.homey.app/u/Bebopper)\
**Post date:** [January 4, 2024, 12:59pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/879 "2024-01-04T12:59:05Z")

</div>

@Teddy thanks again for all the help!

Did a nslookup on [http://192-168-1-235.homey.homeylocal.com](http://192-168-1-235.homey.homeylocal.com) and got a timeout (tried on my home internet connection and also via a mobile internet connection).

I added 192.168.1.235 [192-168-1-235.homey.homeylocal.com](http://192-168-1-235.homey.homeylocal.com) in my hosts file and did a DNS flush; strangely enough I still get an unresolved DNS if I do a nslookup after this. Did all this on a Mac (not my normal OS, usually use windows), no windows laptop available at the moment. Hope to try this on a windows machine later.

I have no DNS server running myself nor does my provider.

If I go to the Local URL option in the Dashboards app I get to the page where to enter my API key. After doing so (new API key) I get the same as yesterday, the local Homey stored dashboard (created as a device on Homey) is not available and I can only create new dashboards stored in the browser where the search box stays empty ☹ .

@skogsaas thank you as well for the support!

I get the following in the console tab when using the local URL option:

```auto
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
/api/manager/sessions/session/me:1 
 
       Failed to load resource: the server responded with a status of 401 (Unauthorized)

AthomCloudAPI.edc7b9cb.js:13364 Uncaught (in promise) Error: Cannot Sign In: Missing AthomCloudAPI
    at AthomCloudAPI.edc7b9cb.js:13364:17

```

In the network tab the following (Fetch):

```auto
https://o4505591422648320.ingest.sentry.io/api/4505591444602880/envelope/?sentry_key=bfc7c7515f17454189e180ba8b9d187c&sentry_version=7&sentry_client=sentry.javascript.svelte%2F7.69.0

Referrer Policy:

origin

Response Headers

Request Headers

Console

top

Default levels

No Issues

o4505591422648320.in…t.svelte%2F7.69.0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

/api/manager/sessions/session/me:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)

AthomCloudAPI.edc7b9cb.js:13364 Uncaught (in promise) Error: Cannot Sign In: Missing AthomCloudAPI at AthomCloudAPI.edc7b9cb.js:13364:17

o4505591422648320.in…t.svelte%2F7.69.0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

o4505591422648320.in…t.svelte%2F7.69.0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

o4505591422648320.in…t.svelte%2F7.69.0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

o4505591422648320.in…t.svelte%2F7.69.0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

o4505591422648320.in…t.svelte%2F7.69.0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

o4505591422648320.in…t.svelte%2F7.69.0:1 POST https://o4505591422648320.ingest.sentry.io/api/4505591444602880/envelope/?s…a8b9d187c&sentry_version=7&sentry_client=sentry.javascript.svelte%2F7.69.0 net::ERR_BLOCKED_BY_CLIENT

o4505591422648320.in…t.svelte%2F7.69.0:1 POST https://o4505591422648320.ingest.sentry.io/api/4505591444602880/envelope/?s…a8b9d187c&sentry_version=7&sentry_client=sentry.javascript.svelte%2F7.69.0 net::ERR_BLOCKED_BY_CLIENT

o4505591422648320.in…t.svelte%2F7.69.0:1 POST https://o4505591422648320.ingest.sentry.io/api/4505591444602880/envelope/?s…a8b9d187c&sentry_version=7&sentry_client=sentry.javascript.svelte%2F7.69.0 net::ERR_BLOCKED_BY_CLIENT

o4505591422648320.in…t.svelte%2F7.69.0:1 POST https://o4505591422648320.ingest.sentry.io/api/4505591444602880/envelope/?s…a8b9d187c&sentry_version=7&sentry_client=sentry.javascript.svelte%2F7.69.0 net::ERR_BLOCKED_BY_CLIENT

Network Log Row Name: envelope/?sentry_key=bfc7c7515f17454189e180ba8b9d1…7&sentry_client=sentry.javascript.svelte%2F7.69.0o4505591422648320.ingest.sentry.io/api/4505591444602880/envelope, Status: (blocked:other), Type: fetch, Initiator: Other, Size: 0 B0 B, Time: 9 ms-

```

Not an expert (at all) in this; but seems like the API does not work /authenticate and requests get blocked because of that?

---

<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 5, 2024, 12:01am UTC](https://community.homey.app/t/app-pro-dashboards/84837/880 "2024-01-05T00:01:16Z")

</div>

First thought: log out from homey _everywhere_, log in again and try again

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [January 6, 2024, 7:48am UTC](https://community.homey.app/t/app-pro-dashboards/84837/881 "2024-01-06T07:48:53Z")

</div>

> [@Bebopper](#):
>
> Did a nslookup on [http://192-168-1-235.homey.homeylocal.com](http://192-168-1-235.homey.homeylocal.com) and got a timeout

This must work, check out your DNS / DHCP server settings on the router - I know there is one settings which influence this (Disregard upstream queries or something like that). Do not add it to ant hosts file, that’s not a solution.  
Which router do you have?

---

<div class="post-metadata">

**Author:** ![LRvdLinden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lrvdlinden/32/80786_2.png) [@LRvdLinden](https://community.homey.app/u/LRvdLinden)\
**Post date:** [January 10, 2024, 8:38am UTC](https://community.homey.app/t/app-pro-dashboards/84837/882 "2024-01-10T08:38:09Z")

</div>

Or just images from KNMI 2.0

> **[KNMI](https://homey.app/nl-nl/app/nl.lrvdlinden.knmi-weerwaarschuwing/KNMI/)**
>
> Ontvang alle Nederlandse KNMI weersomstandigheden en voorspellingen.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/3/a35d2054ee0e918450d0d95d07469859b426a3db.png)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/d/8dd7483d8fda2f3856a5f84342d17cd43c9caaa0.png)

---

<div class="post-metadata">

**Author:** ![Philippe\_Mucher](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/philippe_mucher/32/73654_2.png) [@Philippe\_Mucher](https://community.homey.app/u/Philippe_Mucher)\
**Post date:** [January 13, 2024, 5:59pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/883 "2024-01-13T17:59:12Z")

</div>

Hi @skogsaas Marcus,

I love where this is headed 🙂

I have a Homey Pro 23. I installed the app from the homey website and created a device called “Dashboard”. After reading through the thread, trying to find everything related to local access, I came to the point where I made a local dashboard in the github io, but I cannot get it to load locally.

The local link from the dashboard app settings page doesn’t connect:  
neither [https://192-168-2-173.homey.homeylocal.com/app/skogsaas.dashboards/assets/dashboard](https://192-168-2-173.homey.homeylocal.com/app/skogsaas.dashboards/assets/dashboard) nor [http://192-168-2-173.homey.homeylocal.com/app/skogsaas.dashboards/assets/dashboard](http://192-168-2-173.homey.homeylocal.com/app/skogsaas.dashboards/assets/dashboard)

The alternative that was offered:  
[http://192.168.2.173/app/skogsaas.dashboards/assets/dashboard/](http://192.168.2.173/app/skogsaas.dashboards/assets/dashboard/)  
works and gets me to the page where I can supply the ID and the API key, but then this happens:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/2/02c450bb9fd034dda1b3cbe5539dfe2090dc6aa1.png)

Any ideas to help me out?

---

<div class="post-metadata">

**Author:** ![skogsaas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/skogsaas/32/87995_2.png) [@skogsaas](https://community.homey.app/u/skogsaas)\
**Post date:** [January 13, 2024, 6:37pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/884 "2024-01-13T18:37:16Z")

</div>

Good evening

I understand that some people have issues with the secure local url. No clue why some experience this 🤷‍♂️  
The last url you list is a non-secure url, and I have not added support for all the different urls people might use. I know about this and plan to improve this. The issue is basically that the app expects a set of know url formats to determine if this is local, remote or cloud login.

A workaround is to add the `apikey` manually. Open the developer tools (F12 on your keyboard), go to `Application` → `Local storage` → right click and select `Add new` → key should be `apikey`, and value should the api-key you generated in HP23. Press enter to save the row, and just refresh the page.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/4/a492b6240640218af3fbaa5c5bba9d8d5fac1590.png)

I’m unsure what you mean by this:

> [@Philippe\_Mucher](#):
>
> I came to the point where I made a local dashboard in the github io, but I cannot get it to load locally.

As the concept of local dashboards is just data stored in your browser for that exact page. This means that if you create a local dashboard in [homeyboard.github.io](http://homeyboard.github.io), it won’t be available when you browse dashboards at the local url.

I’ve questioned if I should remove this feature to add local dashboards, as it only seem confusing for users 🤔

---

<div class="post-metadata">

**Author:** ![Philippe\_Mucher](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/philippe_mucher/32/73654_2.png) [@Philippe\_Mucher](https://community.homey.app/u/Philippe_Mucher)\
**Post date:** [January 13, 2024, 7:47pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/885 "2024-01-13T19:47:59Z")

</div>

> [@skogsaas](#):
>
> As the concept of local dashboards is just data stored in your browser for that exact page. This means that if you create a local dashboard in [homeyboard.github.io](http://homeyboard.github.io), it won’t be available when you browse dashboards at the local url.

Aaaah I thought it meant it would store that local page on the Homey for local use - why else would you have a local option in an online design tool? well, part of my confusion resolved. You may have a reason to have that option, I can’t know that, but I think it can be removed.

> [@skogsaas](#):
>
> I’ve questioned if I should remove this feature to add local dashboards, as it only seem confusing for users 🤔

As long as you don’t consider to remove the feature of having a local option completely 😱 (completely meaning not only from [homeyboard.github.io](http://homeyboard.github.io), but also from the app). To me it is fairly important to reduce internet dependency of my Homey as much as I can. I’m guessing a lot of users feel that way.

> [@skogsaas](#):
>
> A workaround is to add the `apikey` manually. Open the developer tools (F12 on your keyboard), go to `Application` → `Local storage` → right click and select `Add new` → key should be `apikey` , and value should the api-key you generated in HP23. Press enter to save the row, and just refresh the page.

This helps me reach a dashboard, and ow, it is the same one as I was editing in [homeyboard.github.io](http://homeyboard.github.io). Now I get it - THAT is the one that is stored on Homey. OK, despite workaround, some progress.  
What I do not understand is this. Adding the api key in that F12 devveloper tools thing - where does that actually store the key? Some kind of cookie? It only helps me to reach the board with this browser, correct? I suppose it will not help me cast a local URL of the board to my Nest, correct? That is the goal. Casting this local boards URL doesn’t work. (I can’t make the online [homeyboard.github.io](http://homeyboard.github.io) version work either, but - one thing at a time).

Thanks for your answer and for taking the time to educate a guy.

---

<div class="post-metadata">

**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\
**Post date:** [January 14, 2024, 10:43am UTC](https://community.homey.app/t/app-pro-dashboards/84837/886 "2024-01-14T10:43:03Z")

</div>

> [@Henk\_Renting](#):
>
> I get an error on Dashboards when I run a check for updates in the App Version Checker app (downloaded from the old Homey Community Store):
> 
> ![Screenshot_20231120_180703_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/3/834b4a426d3356c2a1790ed0a3c34fbb9330dde6.jpeg)
> 
> Checking for updates halts whe it reaches the Dashboards app and is not continued.  
> When I uninstall Dashboards there is no problem

Still having this problem (you too, @Walter_vande_kerkhof?), which keeps me from installing the app…  
Any plans to list it publically @skogsaas?  
Or anyone having other thoughts about this (small) problem? 😃

---

<div class="post-metadata">

**Author:** ![skogsaas](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/skogsaas/32/87995_2.png) [@skogsaas](https://community.homey.app/u/skogsaas)\
**Post date:** [January 14, 2024, 11:46am UTC](https://community.homey.app/t/app-pro-dashboards/84837/887 "2024-01-14T11:46:47Z")

</div>

Have you tried mentioning this issue to the developer of the version checker app?  
I’ve thought about having it publicly listed after the next release. With over 1000 installs, it’s basically public already 😅

Though, it will still be a while before the next release. As always, I’m doing major changes that very likely might break stuff for the 1000 people already using the app. Much of the features I want to implement is in place now, but I’m missing some key functionality to make it more user friendly. Otherwise I’ll get a lot of complaints 😂

---

<div class="post-metadata">

**Author:** ![Guido\_Groeneweg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/guido_groeneweg/32/81606_2.png) [@Guido\_Groeneweg](https://community.homey.app/u/Guido_Groeneweg)\
**Post date:** [January 14, 2024, 1:25pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/888 "2024-01-14T13:25:32Z")

</div>

@ [skogsaas](https://community.homey.app/u/skogsaas) I have the capabilities visible, but the numbers or switches are in the corner instead on the tile. How can I change this?

 ![1000008754](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/5/95c29a6dfbd6d9e3ef8c43219564f05392b2ff24.jpeg)

---

<div class="post-metadata">

**Author:** ![Walter\_vande\_kerkhof](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/walter_vande_kerkhof/32/28963_2.png) [@Walter\_vande\_kerkhof](https://community.homey.app/u/Walter_vande_kerkhof)\
**Post date:** [January 14, 2024, 7:07pm UTC](https://community.homey.app/t/app-pro-dashboards/84837/890 "2024-01-14T19:07:55Z")

</div>

@Henk_Renting @skogsaas yep I’m still having this issue as well.

[Previous page](https://community.homey.app/t/app-pro-dashboards/84837.md?page=43)

[Next page](https://community.homey.app/t/app-pro-dashboards/84837.md?page=45)