That’s what I did. It’s working great on my PC, but not my pad - so I’m guessing it’s something on the pad.
You can save the guest’s PC URL, and copy it to, and open it on the pad!
The URL I open on my pc was copied from the tab. It’s the exact same link, the tab just opens my main user for some reason. I’ve even created a new user with a new link - and still same result on the pad. That’s what’s puzzling… And even more puzzling as it happens in two different browsers and it’s not affected by which user’s logged into the app, homey.ink or forum 
Maybe clearing the cache, or uninstall / reboot pad / install browser does the trick.
2 Likes
Thanks. Did all that (except reinstalling, as I couldn’t uninstall samsung’s browser anyway). What fixed it (clearing data strangely didn’t) was using Kiwi’s built-in “delete data” function and getting rid of all cookies (which should have been removed when clearing the data…).
Thanks! Now it seems to work 
2 Likes
@ all, did somebody got this working for a Kobo reader type N613 GLO? Tried the normal procedure > verified token in Chrome and Firefox but no succes on the Kobo. Hope someone can help :).
Thanks in advance
Hi All,
I bought a second hand Kobop H2O 2nd generation to use with homey.ink but i cannot get it to work.
I managed to downgraade the firmware to get the fullscreen back, but the screen still wont turn and keeps displaying n/a for weather and not showing any favorite flows or devices (similar to the screenshot of @Stevos , but without the Good morning part since the screen its not turned… The link in the config file does work in my own browser, but it seems to do the rotation and loading of the devices after some sort of refresh. This does not seem to happen on my kobo. Does anyone know how to fix this?
Long time, no activity.
I found this today (yeah, slow…) and tried getting a token by logging into homey.ink. Clicking “Log in” fires a popup where I can select my (newly created and verified residental or guest, tried both) user.
I get to the “Homey.ink would like to” part and hit Accept.
Then the popup goes blank. Not much in the HTML response at all. Redirected to https://homey.ink/login.html?code=da… and reloading the main page just mentions “Log in”.
Is this a known problem now?
I think it’s about Reading The Fine Manual 
Open this post to view the ‘how to get the token’ part:
https://community.homey.app/t/homeydash-com-a-homey-dashboard/13509
There is nothing happening after I accept. No green hook, nothing. Which mean the browser never goes from step 1 to step 2. The login popup do not disappear and nothing happens on the main page.
Followed the network traffic and all, nothing.
Firefox, Vivaldi and Chromium, all on Linux. No go.
Edge on Windows 11, no go.
OK. You don’t mention opening the console. Is that part of the manual I linked to unclear?
Of course I’ve opened up the console. I have also looked at the network traffic in the console.
The problem is that there is nothing at all happening after point 2, login. I would presume the popup would close and main page reload to give me the box with the green hook as pictured in step 3. Instead the login box receives a redirect to basically itself, as I’ve mentioned in my first post.
There is a token in one of the login URLs, “user_token” and I’ve tried that to no avail.
I would have guessed third party cookies issue, but with four different broswers and two OSes? Don’t think so. And if it is, the way to log in should be changed to make sure it works on more browsers.
Again:
1 . Click “Log in”
2. Popup to “accounts.athom.com/login?origin=https%3A%2F%2Faccounts.athom.com%2Foauth2%2Fauthorise%3Fclient_id%3D52e46%26redirect_uri%3Dhttps%253A%252F%252Fhomey.ink%252Flogin.html%26response_type%3Dcode” opens up with “Select your account” and I can choose my athom account.
3. New page in the same popup: “Homey.ink would like to:” and the url is `https://accounts.athom.com/authorise?client_id=5cbbXXXXXX46&redirect_uri=https%3A%2F%2Fhomey.ink%2Flogin.html&response_type=code&user_token=eyJhbGciO…’
4. The form url for the POST is the same as the URL in the popup. I’ve tried this user_token, but seems like it is not the one.
5. My Homey is metioned in this popup as the only one and the radio button is checked.
6. Hitting the “Allow” button.
7. I receive a 302 Found with a Location: ‘https://homey.ink/login.html?code=32bd..987hj’
8 Content of the response from that URL is basically nothing. A javascript with:
const code = getQueryVariable(‘code’);
window.opener.postMessage({ code }, ‘*’);
And some tags around it.
My theory is that the API call behind all this fails, or my user is not authorized either by my Homey or accounts.homey.app. I have tried with both a guest and a resident. Both mentioned in this or the other post as being used. The user is also email verified. I cxan log into my Homey without any problem.
But I have no idea because there is no hints about what’s being wrong in the responses I get from accounts.homey popup.
My guess is that there is a step somewhere I have not done or an app not installed?
The Homey is a 2023 Pro. (Failed to mention that until now, sorry!)
Hi,
I have the same problem. If I login at homey.ink, the page that opens is just blank. opening the console does not show the link/token but only errors.
Can someone fix this? I assume that for everyone already having a token it keeps working.
I really want to create a nice dashboard… and this seemed the best option so far.
Hope anyone can resolve this.
Did someone solved this issue? I have a Kobo Auro H2O with the exact same error. The same url works on my laptop.
homey.ink login works fine for me; everything actually works fine, until I try it; no matter if I try it with computer or Kobo Aura HD, it’s just empty page; Good afternoon, 13c and light rain, etc basic stuff.. But favourite flows and favourite devices is empty. Even though I set my temperature sensor as a favourite device. If I change domain name part to homeydash.com and theme to web, it works. It’s like app.homey.ink wouldn’t be connected to my homey at all… And like I said, I also tested on computer, both Safari and Chrome result the same.
