Interestingly, it updated it's presence correctly this morning.
Edit: Logs deleted
This is the registered url test response post reauthentication;
Logs look good to me (although they should be redacted for personal info) despite the test saying unreachable. Must be a relic of your old hub. These emails have resolved spontaneously for me in the past. As long as your new hub is updating, ai think you can ignore the emails and chalk them up to your old hub being unreachable.
Awesome, thanks. Is the access token personal info?
Yes IMO. With those sorts of detailed logs a private message is more appropriate
Ah, apologies, just deleted them all. Thanks for the clarification, and for looking into it for me 
1 Like
I’ve been noticing intermittent outages with my sleep sensors. When I tried to check the device events I got an error. So, I tried reauthorizing my account and I just get “no response from hub.” Any suggestions?
EDIT: Solved with a hub reboot.
Is there a guide for getting this working with the sleep state chart tile?
My FileManagerDevice01 shows the last file written as WithingsSleepDataForDevice83.txt, but my Withings Chart Device isn't showing any Current States.
Can anyone show an example of their dashboard using the withings integration?
Also what type of automations are you using with the health data?
Justin how do you have the tiles in the circle displaying yout information?
Getting this in my logs. I'm definitely connected to Withings, but none of my rules work for it.
The device shows current stats though
bump
I'm afraid I didn't write any of this code for refreshing the token and can't really tell what could be going on - the error looks like it is comnig from the Withings side. Have you tried reconnecting the withings account to HE and re-authorizing the app?
Yeah I've done that a few times. Eventually gets the same error... Too bad @dman2306 isn't around anymore.
are you using the latest version of this integration?
Try this test to see if this fixes the error as a debugging step:
In the Withings User app, change "resp.data.body.expires_in" to "10800". I think resp.data.body.expires_in is somehow returning null for you. This will confirm if that's the case.
