Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Request: Can't relink account #817

Closed
tbaur opened this issue Feb 5, 2024 · 34 comments
Closed

Support Request: Can't relink account #817

tbaur opened this issue Feb 5, 2024 · 34 comments
Assignees
Labels
pinned Pinned to not be closed by stale question Further information is requested

Comments

@tbaur
Copy link

tbaur commented Feb 5, 2024

Describe Your Problem

Can't relink account

Relevant log output

Unclear what is going on, but after version 2.0.0 update, refresh or access token became invalid and I had to relink:

[2/5/2024, 10:46:14 AM] [Resideo] Bad Request, statusCode: 400, Action: getAccessToken
[2/5/2024, 10:46:14 AM] [Resideo] Failed to refresh token in config
[2/5/2024, 10:46:14 AM] [Resideo] Missing Access Token. Re-Link Your Resideo Account.

However, relinking fails constantly. The callback on port 8585 is running, can be loaded, but fails every single time during relink process with err_time_out -- upstream timeout?

There are misc js errors in the logs, as soon as plugin config is opened

[2/5/2024, 10:47:44 AM] [Homebridge UI] [homebridge-resideo] Incoming Request: Start Resideo Login Server
[2/5/2024, 10:47:44 AM] [Homebridge UI] [homebridge-resideo] Server is running
[2/5/2024, 10:48:10 AM] [Homebridge UI] [homebridge-resideo] (Authroize) [object Object]: {"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null}}, statusCode: 302
[2/5/2024, 10:48:10 AM] [Homebridge UI] [homebridge-resideo] SyntaxError: Unexpected end of JSON input

Config for homebridge-resideo

None, default unconfigured, ended up trying to start over. Also tried manually inserting last known good config, no joy.

Screenshots

No response

Device & Model

macOS

Node.js Version

current

NPM Version

current

Homebridge Version

current

Homebridge Resideo Plugin Version

current

Homebridge Config UI X Plugin Version

current

Operating System

macOS

@tbaur tbaur added the question Further information is requested label Feb 5, 2024
@eoddc5
Copy link

eoddc5 commented Feb 6, 2024

try downgrading your version to 1.4.6

this happened to me today, as well, and i moved back to that version and i was able to get everything up and running again

i updated to 2.0.0 and 2.0.1 beta and both lost my devices again, they were all showing offline.

reinstaled 1.4.6 again, everything works again.

im not moving off the version number until its sorted

@donavanbecker
Copy link
Collaborator

Can you try the latest beta:

npm version

Click here to find out how to install Beta

@eoddc5
Copy link

eoddc5 commented Feb 6, 2024

just tried with beta.33 - looks ok so far, ill update if they disappear again

@tbaur
Copy link
Author

tbaur commented Feb 6, 2024

Updated to beta 33 -- Callback URL is auto populated correctly on the first screen (re "Give your application a name, and enter the 'Callback URL' exactly as it is displayed below.") -- on the next screen where you enter key/secret, a new field for Callback URL exists, value is required, but the field is empty and is also not editable. Can not proceed....

@eoddc5
Copy link

eoddc5 commented Feb 6, 2024

also just updating to my last. with beta.33 - after about 30 minutes, the leak detectors that im linking from my resideo account fell back offline in the home app

downgrading back to 1.4.6 restored them

@tbaur
Copy link
Author

tbaur commented Feb 6, 2024

I decided to go back to 1.4.6 as well, was able to relink and had to re-add everything, update/fix automations etc. -- will hold off on updates till things settle :)

@donavanbecker
Copy link
Collaborator

I decided to go back to 1.4.6 as well, was able to relink and had to re-add everything, update/fix automations etc. -- will hold off on updates till things settle :)

you shouldn't have to remove it completely.

@eoddc5
Copy link

eoddc5 commented Feb 7, 2024

if he had to set everything up from scratch, then downgrading to 1.4.6 was needed

i had to blast the plugin away the other day, and then reinstall, while on any of the 2.0.x - the pop up that comes with "link account" where it offers the resideo login page just showed up blank each time, i tried to manually do it, and it wouldnt connect

going back down to 1.4.6 - the pop up portal launched properly

@ndradar
Copy link

ndradar commented Feb 15, 2024

I also am having an issue with 2.0.0 and not being able to link my account. I get an error on the verification screen that is cannot access the server.

@JerGitHub
Copy link

Same issue as others here on v2.x. No way to re-link account - Honeywell login never appears. Downgrading to 1.4.6 restores everything.

@eoddc5
Copy link

eoddc5 commented Feb 19, 2024

@donavanbecker just wanted to call your attention here. i am sure its not a major issue staying on 1.4.6 - but you might want to pull 2.0.0+ for now?

@sslupsky
Copy link

sslupsky commented Mar 2, 2024

Attempted to install the plugin today and ran into this problem when attempting the link step. Browser page opens with the callback URL but the page is blank / does not load.

@tbaur
Copy link
Author

tbaur commented Mar 2, 2024 via email

@sslupsky
Copy link

sslupsky commented Mar 2, 2024

@tbaur Thanks. I downgraded to 1.4.6 and the link page opened correctly with using the Honeywell API URL instead of the callback URL that 2.0.x was doing.

Copy link

github-actions bot commented Apr 2, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Apr 2, 2024
@tbaur
Copy link
Author

tbaur commented Apr 2, 2024 via email

@donavanbecker donavanbecker added pinned Pinned to not be closed by stale and removed stale labels Apr 2, 2024
@tbaur
Copy link
Author

tbaur commented Apr 20, 2024 via email

@bwp91
Copy link
Contributor

bwp91 commented Apr 20, 2024

And due to homebridge UI, the bad release is blocking other options — ex. you can’t move the plugin to a child bridge if there is an upgrade pending, the upgrade UI blocks / replaces that action — separate issue

Looking at this for the UI 👀

@bwp91
Copy link
Contributor

bwp91 commented Apr 20, 2024

Screenshot 2024-04-20 at 05 18 37

@tbaur UI issue is fixed in the UI beta version, and will be part of the next release.

Now I shall leave this thread, not that I was really invited in the first place 😆

@tbaur
Copy link
Author

tbaur commented Apr 20, 2024 via email

@donavanbecker
Copy link
Collaborator

Can you try v2.0.1?

@tbaur
Copy link
Author

tbaur commented Apr 28, 2024 via email

@tbaur
Copy link
Author

tbaur commented Apr 28, 2024 via email

@cjvogl
Copy link

cjvogl commented May 2, 2024

+1 I also have the same problems as discussed above: cannot relink account after upgrading v2.0.0 or v.2.0.1. Second time rolling back to v.1.4.6 and having to reset all related automations.

@tbaur
Copy link
Author

tbaur commented May 7, 2024 via email

@donavanbecker
Copy link
Collaborator

donavanbecker commented May 7, 2024

I can't pull those version but I just set v1.4.6 as latest for now. Also set 2.0.1 to beta tag, which then makes Homebridge not ask you to upgrade.

@tbaur
Copy link
Author

tbaur commented May 7, 2024 via email

donavanbecker added a commit that referenced this issue May 29, 2024
@donavanbecker
Copy link
Collaborator

Try beta: v2.1.1

Also @tbaur, this isn't my full-time job, I do this as a hobby and when I have free time. If you choose to leave then that is that... I am trying the best I can. I have self thought myself to program with the help of some other great Homebridge plugin developers. If someone else has a fix for this I will never turn down a PR.

@sslupsky
Copy link

@donavanbecker
Copy link
Collaborator

no because typescript gets compiled to javascript.

@sslupsky, have you tired the latest beta?

@tbaur
Copy link
Author

tbaur commented May 30, 2024

2.x including 2.1.1 -- they are all broken, do not work.

Can not even try to relink, callback url is blank and uneditable.

This is very trivial to test, are you testing the code before you are pushing out? Or just asking others?

Once more, please set 1.4.6 back to latest.
Please keep these beta until it actually works and confirmed, 2.0.1 should not be marked latest.

@donavanbecker
Copy link
Collaborator

@tbaur so you aren't even testing the beta?

@tbaur
Copy link
Author

tbaur commented May 30, 2024

I just replied, 2.1.1 is broken, like all of the 2.x releases.

1.4.6 should remain set to latest.

@donavanbecker
Copy link
Collaborator

Your comments are really helpful. I am not having any issues with the beta. So I am releasing and closing this issue. If you can provide more helpful info then just saying it doesn't work or providing a PR, then I will merge the fix that you provide. Thanks.

@homebridge-plugins homebridge-plugins locked and limited conversation to collaborators May 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pinned Pinned to not be closed by stale question Further information is requested
Projects
None yet
Development

No branches or pull requests

8 participants