core: EphEmber Integration not working

The problem

Hello,

The EPH Ember integration is no longer working. I am receiving the error “Cannot connect to EphEmber” in the logs.

The connection to the endpoint “eu-https.topband-cloud.com” seems to be OK on my machine and other machines.

Also the API seems to work OK, as I have tested that with POSTMAN:

POST https://eu-https.topband-cloud.com/ember-back/appLogin/login 200 85 ms POST /ember-back/appLogin/login HTTP/1.1 Accept: application/json Content-Type: application/json;charset=utf-8 User-Agent: PostmanRuntime/7.26.10 Postman-Token: cb1bfed9-bf8b-4fc0-8216-d69912078761 Host: eu-https.topband-cloud.com Accept-Encoding: gzip, deflate, br Connection: keep-alive Content-Length: 117 { “password”: “EPHPASSWORD”, “model”: “iPhone 7”, “os”: “13.1.3”, “userName”: “email@gmail.com” } HTTP/1.1 200 OK Date: Mon, 08 Feb 2021 14:10:40 GMT Content-Type: application/json;charset=UTF-8 Content-Length: 173 Connection: keep-alive { “data”:{ “refresh_token”:“refresh_token”, “token”:“access_token” }, “message”:null, “status”:0, “timestamp”:1612793440983 }

What is version of Home Assistant Core has the issue?

core-2021.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

EPH Controls

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ephember/

Example YAML snippet

# Put your YAML below this line
climate:
  - platform: ephember
    username: !secret ember_username
    password: !secret ember_password

Anything in the logs that might be useful for us?

# Put your logs below this line
2021-02-08 14:18:37 INFO (SyncWorker_1) [homeassistant.loader] Loaded ephember from homeassistant.components.ephember
2021-02-08 14:18:38 INFO (MainThread) [homeassistant.components.climate] Setting up climate.ephember
2021-02-08 14:18:40 ERROR (SyncWorker_2) [homeassistant.components.ephember.climate] Cannot connect to EphEmber

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 20 (6 by maintainers)

Most upvoted comments

I got some testing done over the weekend with the new API (thanks @walshtj ) and it looks like they have split their new API into 2 parts.

A JSON / HTTPs API for authentication and returning some information about the home / zones. Some of the JSON naming isn’t as clear as the old API but it’s understandable enough to read the basic zone information, set times, current temp, target temp.
When changing data (e.g. setting boost), I don’t see anything over the HTTP API. Doing a packet capture I can see that the app is also sending encrypted TLS data to a server like eu-mqtt.topband-cloud.com on port 18883. Which seems to me to imply that they have split some of their control data out to an MQTT interface.

To proceed with keeping the same functionality we currently have I would need to capture and decrypt the MQTT traffic to see the data they are sending there. I’m not very familiar with MQTT so will need to do some investigation on how to do that.

ttroy50 on Feb 15, 2021

/login. ( think this also works on HA still) POST {"password":"xxxxxx","model":"iPhone","os":"14.3","type":2,"appVersion":"2.0.4","userName":"xxxxxxx"}

RESPONSE

{
	"data": {
		"refresh_token": "long_refresh_token",
		"token": "long_token"
	},
	"message": null,
	"status": 0,
	"timestamp": 1613237316835
}

Actually before I start pasting in piles of json… a few thoughts: I noticed that the sequence of calls when I login to the app(see attached image) is login, reportToken, selectUser, list (x2), details…etc. I think some of those are new endpoints that are not referenced in your list of endpoints. While your example.py code does the /login first, and then /zonePolling (in the getHome() method). Its the 2nd call where we get the "WiFi device is not online, please check and try again." message.

Anyway earlier today, since there is no chat in github, I sent you a linkedin request and I offered to add you to my EPH ember. As much as I enjoy learning about this stuff the reality is that its still all new to me. By adding you (@ttroy50) then you have a system which works (yours) and a system which doesn’t (mine) and you’ll probably be able to spot the problem quicker. If this works for you can you accept my linkedin request and we can swap emails.

walshtj on Feb 13, 2021