homebridge-mrcool.MrCool starts, and crashes.

[lvnilesh]

Thanks for the update. I installed and restarted homebridge.

I notice that homebridge-mrcool.MrCool starts, and crashes.
And then repeats.

[2/12/2023, 9:43:55 PM] Registering platform 'homebridge-mrcool.MrCool'
[2/12/2023, 9:43:55 PM] [homebridge-mrcool] Loaded homebridge-mrcool v1.0.0 child bridge successfully
[2/12/2023, 9:43:55 PM] Homebridge v1.6.0 (HAP v0.11.0) (homebridge-mrcool) is running on port 34070.

/homebridge/node_modules/homebridge-mrcool/node_modules/node-mrcool/MrCool.js:413
        return cookieArray.map((element) => element.split(';')[0]).join(';');
                           ^
TypeError: Cannot read properties of undefined (reading 'map')
    at MrCoolAPIConnection.#getCookiesFromResponse (/homebridge/node_modules/homebridge-mrcool/node_modules/node-mrcool/MrCool.js:413:28)
    at MrCoolAPIConnection.#getApplicationCookies (/homebridge/node_modules/homebridge-mrcool/node_modules/node-mrcool/MrCool.js:237:44)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at MrCoolAPIConnection.establishConnection (/homebridge/node_modules/homebridge-mrcool/node_modules/node-mrcool/MrCool.js:117:36)
    at HomebridgeAPI.<anonymous> (/homebridge/node_modules/homebridge-mrcool/src/platform.ts:57:7)
[2/12/2023, 9:43:55 PM] [homebridge-mrcool] Child bridge process ended
[2/12/2023, 9:43:55 PM] [homebridge-mrcool] Process Ended. Code: 1, Signal: null
[2/12/2023, 9:44:02 PM] [homebridge-mrcool] Restarting Process...

[jfarlow12]

I have the same issue. Were you able to find a resolution?

[lvnilesh]

no :(

[ryanfroese]

I have the same problem. I've tried to do some digging, but I'm having trouble accessing the API the code is using. Has anyone tried with postman to see if you are able to get a response?

[isaac-webb]

Sorry for the radio silence everyone! My installation also broke around the same time, and, after some quick checks on their website, it looks like they changed the way their API works, breaking my plugin/API. I (or anyone really) need to use browser debuggers to do some reverse engineering to figure out how their new API works and change the code to work with it. Some of the changes look good (more RESTful and easier to work with), but I haven't had the time to really dig in yet. If anyone has started, I'd be more than willing to help.

[ryanfroese]

I am getting 405 Method Not Allowed when using Method: POST, however GET is working.

I'm definitely willing to help, but lack experience in this area (usually write self-contained react apps with my own backend). Not used to digging into an API with no documentation. Any suggestions where I should get started?

[ryanfroese]

I have made some progress:

The new API is at https://api.smartcielo.com/web/login as opposed to https://home.cielowigle.com/auth/login.

I've found a POST for login, which I have working. It's fairly simple.

There is a GET for Devices and GET for Appliance List. All of these are working for me right now on Postman.

Major problem I'm having, when I change temperatures from the web app I'm not seeing any in the "Network" activity in my Chrome dev tools. I honestly don't even know how that's possible, so I'm probably missing something.

[ryanfroese]

OK, more progress. I have determined that there is an API for login and getting appliance/device lists, however it appears to be using a web socket for all controls.

The web socket looks like this for a change temperature command:

Websocket response (status update, which also is periodically/randomly sent):

[jfarlow12]

Nice work! What else is needed then? Also, do I see an option here to turn off the LED using this API? That would be amazing!

[ryanfroese]

The code needs to be altered, which I've begun digging into. Unfortunately I'm not sure how the npm ws package functions (I've never messed with web sockets).

@isaac-webb , are you familiar with this part of things?

The new web socket is at: wss://apiwss.smartcielo.com/websocket/?sessionId=<yourSessionId>&token=<yourToken>

Both <yourSessionId> and <yourToken> come from response to a simple POST https request like this:
const loginUrl = new URL("https://api.smarcielo.com/web/login"); const loginPayload = { agent: this.#agent, headers: { authority: "api.smartcielo.com", accept: "application/json, text/plain, */*", "accept-language": "en-US,en;q=0.9", "cache-control": "no-cache", "content-type": "application/json; charset=UTF-8", origin: "https://home.cielowigle.com", pragma: "no-cache", referer: "https://home.cielowigle.com/", "x-api-key": <notPostingHere>, }, body: { user: { userId: username, password: password, mobileDeviceId: "WEB", deviceTokenId: "WEB", appType: "WEB", appVersion: "1.0", timeZone: "America/Los_Angeles", mobileDeviceName: "chrome", deviceType: "WEB", ipAddress: ip, isSmartHVAC: 0, locale: "en", }, }, method: "POST", }; const response = await fetch(loginUrl, loginPayload);

That's where I am so far. I have also found some cookie stuff, but I'm still not entirely sure how that aspect works...

[ryanfroese]

I have it working with the exception of the #pingSocket() function! It appears all the cookie stuff is unnecessary with the new code, so I removed all of it. I'm trying to discover if the ping function is really just a refresh token function.

[ryanfroese]

Still having some issues with #pingSocket, it disconnects and reconnects but other than that it works! I would be willing to submit a PR from my fork if @isaac-webb would like, but it would be nice to get some help figuring out the ping/disconnect issue first. Give it a shot! I named it homebridge-cielo, so it should come up in a homebridge search.

My repo is https://github.com/ryanfroese/homebridge-smartcielo