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

Failed Setup, will retry: none #4

Open
rbhun opened this issue Aug 5, 2024 · 21 comments
Open

Failed Setup, will retry: none #4

rbhun opened this issue Aug 5, 2024 · 21 comments

Comments

@rbhun
Copy link

rbhun commented Aug 5, 2024

-New HA green hardware, plus a Z-wave stick
-core: 2024.7.4, OS 12.4
-uhoo from HACS, version is stated as 0.0.4 from @andrewleech in the HACS page, 0.0.5 in the Integration page

Uhoo is installed and then configured, accepts user and password. Then says: Failed Setup, will retry:none

I have these in the log:
Error: an exception occurred while attempting to get latest data: Error requesting data from https://api.uhooinc.com/v1/getalllatestdata: 400, message='Bad Request', url=URL('https://api.uhooinc.com/v1/getalllatestdata')

also have this:
This error originated from a custom integration.

Logger: custom_components.uhoo
Source: helpers/update_coordinator.py:344
integration: uHoo (documentation, issues)
First occurred: 03:25:18 (12 occurrences)
Last logged: 03:32:55

Error fetching uhoo data:

just for fun I tried the webpage linked and it indeed says invalid.

@andrewleech
Copy link
Owner

Hmm, my install seems to be working. The version numbers reported are confusing, which made me realise I never tagged my "current" version as a release.

I've just done so, as v0.0.5

Maybe check if hacs offers this as an update now?

@rbhun
Copy link
Author

rbhun commented Aug 5, 2024 via email

@andrewleech
Copy link
Owner

I'm not getting the pictures sorry, but yeah 0.0.4 is a release from the original csacca repo, not mine, so it looks like maybe that's what's installed instead?

@andrewleech
Copy link
Owner

Oh...
I originally made my changes here as a pull request into csacca repo, not expecting people to ever need to install directly from here.
However csacca repo hasn't been updated since / my changes never got merged.

I never updated the instructions in the readme on this fork to show how to install directly from this repo, so the instructions still give the url for the original csacca one.

@andrewleech
Copy link
Owner

Ok, I've just updated the readme to hopefully make this easier!
You're probably best to remove your current copy from hacs and try again from the updated instructions on the front page of this repo.

@rbhun
Copy link
Author

rbhun commented Aug 5, 2024 via email

@rbhun
Copy link
Author

rbhun commented Aug 5, 2024

image

@rbhun
Copy link
Author

rbhun commented Aug 5, 2024

image

@rbhun
Copy link
Author

rbhun commented Aug 5, 2024

here you can see me using your new readme, selecting 0.0.5. On the top left, you can still see the tag 0.0.4

Unfortunately, I get the same error.

@andrewleech
Copy link
Owner

Did you restart home assistant in between? It does look like it's still using the old one.

@rbhun
Copy link
Author

rbhun commented Aug 5, 2024 via email

@andrewleech
Copy link
Owner

andrewleech commented Aug 5, 2024

On the hacs page, bring up custom repositories again and just double check the url for the repo, eg.

Screenshot_20240805-210841.png


Screenshot_20240805-210854.png

and then back on the hacs main page see if it's listed as "pending update" like mine, if so hit the update button.

Screenshot_20240805-211119.png

@rbhun
Copy link
Author

rbhun commented Aug 5, 2024

yes, it looks like this:
image
and if I open it from the list, and click on the repository under the 3 dots here, it takes me to you github.
image

after I download it, I get a Pending Restart:
image

@andrewleech
Copy link
Owner

I've made another new release tag v0.0.6 just to include the readme changes.
If you update to that then the rest of the display for uhoo integration should show the correct version too.

Hopefully after that and the home assistant restart it works for you.

I haven't tested logging in from scratch with a new install for a while so there's still a chance something has gone wrong there, but hopefully not!

@rbhun
Copy link
Author

rbhun commented Aug 5, 2024

I deleted all traces (hopefully), even the custom repo from the HACS window. I have rebooted (not just restarted after delete.
I have then installed the new repo, using the link from the new readme. It does show 0.0.6, along with 0.0.5. However, in the corner, it still says 0.0.04, and that tag links to the old github page.
image
After I downloaded this, I got a prompt to restart. I rebooted again, and installed the integration.
Unfortunately, it is still the same result. I dont get it..

PS: I am not sure it matters, but the Configure window looks like this:
image

@rbhun
Copy link
Author

rbhun commented Aug 15, 2024

Sorry I still cannot get this working.
-do I need an uHoo premium subscription?
-what is the correct URL? I assume https://api.uhooinc.com/v1/getalllatestdata is not it.

@andrewleech
Copy link
Owner

I haven't paid for premium, I don't think it's that.

Oh, I see now in your previous pictures about the versions, I think mine does show all the same as you now. That 0.0.4 is the GitHub badge picture, that link in the readme must still be wrong sorry.

Perhaps yours is correctly installed now, which doesn't explain why the setup fails.

There's a chance the setup process in the integration is actually broken, maybe it's been broken by a recent home assistant update or something. My copy has been installed and untouched for a long time now.

I'll have to try resetting my installation and go through the setup process myself to see what's going on, which will have to wait until I'll have a little bit of time free to fix anything needed when I do so to keep my uhoo working.

@rjkrom
Copy link

rjkrom commented Sep 7, 2024

Is there any news on this repo? I have the same issue as rbhun. Are we one of the few experiencing this issue? Curious if @andrewleech did have the time to look into the issue?

@andrewleech
Copy link
Owner

No I haven't had time to look closer, though considering there's a few reports now it certainly sounds like there's a common issue with initial log in.

My existing installation is still working correctly so most of the server configuration is presumably still correct and valid, just something has changed with the login.

Between having a very young family and busy work I don't have much time for personal projects like this lately, but this issue is on my list to look at eventually - just really can't give much indication when that might be sorry.

@rjkrom
Copy link

rjkrom commented Sep 7, 2024

I can fully understand that this is not your first priority in your situation. Of course I hope you will find some time for this issue. Thank you and cheers!

@frankvandenhurk
Copy link

same problem here, please let me know if I can help (e.g. testing)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants