Are you seeing any other connection issues? The api access has never been perfect since we are tying to imitate being the app, but this isn’t something i’ve seen on my end (neither the api going down or the crash). This component uses the standard aiohttp library and it’s typical timeout method, not something that should be causing an issue, especially considering it’s a polling component and isn’t trying to keep a constant connection open. If it’s repeatable you should open an issue with logs.
It’s happened only over the past 3 days, everyday at about the same time. I am suspecting the eight sleep component because after HA restarts, only the eight sleep component is failing to connect. It lasts for 30min-1h and then I have to restart HA again and all is well. I will keep an eye on it.
Is this still a concern? I’m looking at getting one of these, and this sounds bad, lol.
It was a convoluted problem with the way HA is handling a number of other integration asynchronously. Under normal condition it isn’t a problem. I have been able to mitigate it as of late as I am using a large number of integrations. Some of them are rather unusual.
I like the sound of what you proposed. Any progress?
1 Like
Did anyone have trouble with the basic setup? I put my email and password in the configuration.yaml as per the setup and I get these errors:
2021-12-08 15:02:22 ERROR (MainThread) [pyeight.eight] Error posting Eight data: 400
2021-12-08 15:02:22 ERROR (MainThread) [pyeight.eight] Unable to authenticate and fetch eight token.
2021-12-08 15:02:22 ERROR (MainThread) [homeassistant.setup] Setup failed for eight_sleep: Integration failed to initialize.
I’m still poking around just in case.
If you look at the pull request, it was closed and not integrated. I’m assuming it’s not going to get added. @robbiet480 Seems to not be a user here anymore either, which is very odd.
2 Likes
I know it’s been a few months, but for what it’s worth: I was having a similar issue with “Unable to authenticate and fetch eight token”; it turned out to be because my password contained a special character (as defined by YAML, according to this) and I needed to enclose it in double quotes, ala:
eight_sleep:
username: foo
password: "abcd1234!!"
It’s a shame this never came to fruition. These improvements would be incredible 
It’d be great to see this integration get some life back in it. I’m hoping to leverage my Pod 2 Pro for presence detection to trigger some lights under the bed.
1 Like
I would love if ha can set away mode for this eight sleep integration.
Now I have to manually set it every time in the app.
This is unfortunate. I was researching Eight Sleep but after seeing that the existing integration is Cloud-based, undocumented, and now potentially abandoned, I am not inclined to purchase.
I was going to reach out to them about local control options, but based on this post I found, they appear to be pushing a mandatory subscription model now. Can never trust cloud-only products.
https://www.reddit.com/r/EightSleep/comments/11h3bzf/8_pro_subscription_required_for_purchase/
Is it possible to use this integration without a subscription active?
1 Like
I’m considering getting a pod 3 cover and would very much like to know this too. Does anyone know if the integration is usable without an active subscription?