Sometime you find finally what you was looking for.
Now I want to share it.
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.
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
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.
In this topic I found the tip to try [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/ 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.
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
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.
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.
Yeah, this is a simple issue, but might not be fixed. My bad
The different search dialogs should present a result immediately, without entering a search phrase.
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
I added 192.168.1.235 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 .
I get the following in the console tab when using the local URL option:
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):
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?
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?
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.
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.
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, 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
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.
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, 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.
This helps me reach a dashboard, and ow, it is the same one as I was editing in 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 version work either, but - one thing at a time).
Thanks for your answer and for taking the time to educate a guy.
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?
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
)
.
(completely meaning not only from 
