Unable to sign in after re-creating my nework

[NPSconsultingLLC]

Describe The Bug: I recently rebuilt my home network and I am not able to log into my 8 sleep account. HomeBridge is reporting this as the error:

To Reproduce: Install the Eight8Sleep Homebridge plugin: this is the config for my 8Sleep:

Expected behavior: Login and expose my bed as thermostats

Logs:

Something went wrong... Error: Unexpected failure occured during plugin load. at EightSleepThermostatPlatform.discoverDevices (/var/lib/homebridge/node_modules/homebridge-eightsleepthermostat/src/platform.ts:70:13) at processTicksAndRejections (node:internal/process/task_queues:95:5)

Plugin Config:

   ` {
        "name": "Eight Sleep Thermostat",
        "email": "MY-Email Address",
        "password": "My Password",
        "left-bed-name": "Partner Bed",
        "right-bed-name": "My Bed",
        "platform": "EightSleepThermostat",
        "_bridge": {
            "username": "Running on Bridge",
            "port": PORT
        }
    }`

Screenshots:

Environment:

• Plugin Version: homebridge-eightsleepthermostat v0.2.2-beta.0
• Homebridge Version: 1.6.1
• Node.js Version: v18.16.0
• Operating System: Raspbian

[carmanj]

@NPSconsultingLLC - I'm almost positive this has nothing to do with your network, other than merely coincidental timing. Eight Sleep, in their infinite wisdom, has killed the IFTTT integration (even though it is still up on IFTTT) that was available through the app, which I believe is the API that this project was using as well.

I set this up today hoping I'd be able to use it, but between what you've noticed, what they've said regarding IFTTT support ending, and after opening this up in a local dev environment where I can see additional logging. I think this project is unfortunately dead, at the behest of Eight Sleep.

This is what I'm getting from their API, the error probably sheds light on why things are failing to run.

data: {
    status: 401,
    code: 'Unauthorized',
    error: 'session token not supported'
}  

I'll go ahead and investigate more during the week, but I suspect we're SOL until they either release a new API, or drag us along forever with vague claims that they might.

Eight Sleep is absolutely awful and sucks as a company - particularly with their predatory "buy this insanely expensive mattress pad and pray we don't brick it while also charging you hundreds in "support" each year!" business model, this is just further evidence of it.

Thanks! Justin

[carmanj]

Oh, and I just reached out to Eight Sleep regarding API information. If they come back with anything useable documentation wise, I'll be happy to help contribute to get this up running.

Thanks! Justin

[carmanj]

@NPSconsultingLLC & @dillonp23 - I should have a PR to resolve the API changes sometime next week. Could either of you let me know what Pod models you have? I have a Pod 3 w/ Perfect Fit. If you happen to have different Pod versions, it'd be super helpful to have account credentials that I could play around with. I've got no API schema documentation, can only make changes based on the device on my account, and it's hard to tell what they deprecated/changed and what might be different because of a different device.

@dillonp23 - I'm not sure if you are active (or wish to be) in this project anymore or not, since it looks like it's been a bit over a year since any commits. If you'd prefer I'd just create a fork of this project and if you want to deactivate this one, I'm fine with that too, just let me know. Happy to help out either way. :)

Thanks! Justin

[NPSconsultingLLC]

Hey @carmanj My appologies, I didnt get the update that you had responded (thank you for the investigation! and potential fix)

I have a Pod 2 Pro If you want to shoot me an email I'm happy to give you my credentials to mess around with, Or if you prefer I can use Charles Proxy and just capture some logs for you.

I'll be more diligent checking this (there were a few plugins that have died this past month MyQ and 8Sleep .. //Frustrating ;)

[carmanj]

Shoot me an email at dev[dot]justin[dot]carman[at]gmail[dot]com - I shouldn’t need credentials for more than a day to get the network requests. If you can sort out capturing the https traffic it in Charles and getting it decrypted, that’s fine too. Just do a log out -> log in -> select pod device -> turn pod on -> change temp -> turn pod off. That should be all the traffic I need to see.

Thanks! Justin

On Nov 13, 2023, at 10:07 PM, Nathan Stryker @.***> wrote:

Hey @carmanj https://github.com/carmanj My appologies, I didnt get the update that you had responded (thank you for the investigation! and potential fix)

I have a Pod 2 Pro If you want to shoot me an email I'm happy to give you my credentials to mess around with, Or if you prefer I can use Charles Proxy and just capture some logs for you.

I'll be more diligent checking this (there were a few plugins that have died this past month MyQ and 8Sleep .. //Frustrating ;)

— Reply to this email directly, view it on GitHub https://github.com/dillonp23/homebridge-eight8sleep/issues/7#issuecomment-1809473756, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHJA7PUKDITOAUMETSE4W2DYELOATAVCNFSM6AAAAAA6K7G5OKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZGQ3TGNZVGY. You are receiving this because you were mentioned.

[abonstu]

app-api.8slp.net.chlsj.zip

here's the charles session log for the sequence above.

is there a further step required to decrypt or is this sufficient?

[abonstu]

@carmanj 🤔

[carmanj]

Sorry everyone! I've been slammed with work and holiday related busyness. I have the back half of the month off, so I anticipate creating a new project from scratch, because even if I make a PR, I don't think it'll get picked up. It seems like this is probably a dead/defunct project. I'm happy to find out I'm wrong in the interim though.

Thanks, Justin