Exception while attempting to get latest data

[s28400]

Noticed my integration stopped working on 3/16. HA logs show the following:

Logger: custom_components.uhoo
Source: custom_components/uhoo/__init__.py:85 
Integration: uHoo ([documentation](https://github.com/csacca/uhoo-homeassistant), [issues](https://github.com/csacca/uhoo-homeassistant/issues)) 
First occurred: 9:42:19 AM (382 occurrences) 
Last logged: 4:11:48 PM

Error: an exception occurred while attempting to get latest data: Error requesting data from https://auth.uhooinc.com/renewusertoken: 410, message='Gone', url=URL('https://auth.uhooinc.com/renewusertoken')

I tried deleting integration and re-authenticating. Looks like it got one data point but none after.

Running HASS: 2022.3.5 and latest integration version from HACS.

[startledhighlandhippo]

Seeing the same thing with mine - started on the same day (3/16). Any time the integration is restarted, it seems to grab one data point and then all sensors read "unavailable".

Confirmed that data is still being received in the phone app, so this seems to be something with how HomeAssistant is interfacing with the sensor.

[s28400]

I am thinking uhooair changed their link. I tried that URL manually and it is a blank page.

[s28400]

Did some debugging this weekend, the issue is within pyuhooair package. I wrote a comparable python package that can be used for this home assistant integration here: https://pypi.org/project/pyuhooairq/0.0.1 I am happy to help integrate to get this integration up and running again. If not, I can create a comparable home assistant integration to maintain. Thanks!

[csacca]

@s28400 Sorry for not responding earlier. This is a real issue, mostly due to using a reverse engineered API. I just wrote uHoo again and I'm hoping they'll give me access to their API now that they're supporting more third party integrations that just IFTTT. This integration uses the pyuhoo package, not pyuhooair. I'm a little busy right now with life, but if you submit a pull request to pyuhoo air that fixes the problem I'll take a look and if it works I'll push it and update both pyuhoo and this package. Thank you!

[howlermonkeys]

Did some debugging this weekend, the issue is within pyuhooair package. I wrote a comparable python package that can be used for this home assistant integration here: https://pypi.org/project/pyuhooairq/0.0.1 I am happy to help integrate to get this integration up and running again. If not, I can create a comparable home assistant integration to maintain. Thanks!

Any chance you'd be willing to teach others how to use your package to fix our uHoo intergrations?

[yingyann]

Hello, I’m interrested to know how to solve this issue also please:-) thank you

[startledhighlandhippo]

I have been trying to look into this. Unfortunately, I haven't found a fix yet. I did want to share what I've done though, in case it helped anyone out. I am far from an expert, so definitely take all this with a grain of salt. Sorry for the novel!

First, I have tried both @s28400's package and the PR created by @adig. Neither has been able to run successfully for me. I still see that after a short amount of time, the script fails to refresh the user token. The error is:
pyuhoo.errors.RequestError: Error requesting data from https://auth.uhooinc.com/renewusertoken: 410, message='Gone', url=URL('https://auth.uhooinc.com/renewusertoken')

I did learn how to set up an Android emulator and intercept HTTP traffic from the app. I suspect @adig did too as some updates from their PR seem related to what I was seeing (e.g. using the allconsumerdata endpoint). However, I saw something else not covered by that PR:

It seems the POST to refresh the user token now goes to a URL like:
https://auth.uhooinc.com/renewusertoken?millis=#############
Where ############# is a Unix epoch timestamp expressed in milliseconds.
However, trying this with the current UTC time has not worked. I also noticed there was an offset between the origination time of the request and the value used for millis (varying by the session, sometimes hours, sometimes just seconds). Trying to replicate that hasn't worked for me either.

Posting to plain-old https://auth.uhooinc.com/renewusertoken does work, but only for about a minute after the last renewal, after that it somehow expires/disappears.

A really brute-force fix here might just be to refresh the token every 30s or something. The uHoo app refreshes its token every 10 minutes, though, so it must be possible to go longer.

My uneducated suspicion is that the way the millis parameter is determined needs to be reverse engineered and then pyuhoo updated to include it.

I'll keep plugging at it in my free time, but maybe this write-up will give someone an idea.

[s28400]

@startledhighlandhippo startledhighlandhippo do you have the latest pypi package installed? Version 1.1.0 of pyhuooairq had some bug fixes around this issue and support for python 3.10. I simply re-authenticated by logging in once the token was determined to be expired. I have been trying to make an integration in my free time with little progress but hopefully this is helpful to get this one fixed.

[startledhighlandhippo]

@s28400 - yep, good call, turns out I was still on v1.0.0. Updating to v1.1.0 did get data to stream continuously.

In the interest of the shortest path to getting something working, I did go ahead and open up a PR that implements the same fix, but on the pyuhoo package used by @csacca's existing integration to hopefully get it up and running again. Ran it on my computer for a few hours and it seemed to work.

@csacca - if you could take at look at that PR it would be much appreciated. Should be quick - only touches 5 lines of code.

[howlermonkeys]

Any update on this, Does it still work via the updated pyuhoo library?
I'd much prefer to access Uhoo through a free method vs their 120 dollar a year "premium" serivce.
or anything I can do to help?

[frankvandenhurk]

+1