core: EcoNet Integration Not Working

The problem

Important

It is probable that the problem described below is the result of changes on the EcoNet API end.
The integration broke without any changes to my system as far as I know.
- first time noticed the problem while the system was on core-2023.8.1
- still having the problem with core-2023.10.5

Description of the problem

I have a Rheem Hybrid (Heat Pump and Electric) water heater. It has worked well with the EcoNet integration for the past 2y or so. Since last night it has been showing “Unavailable” on all related entities.

The integration shows: Initializing...Failed setup, will retry

Logs show:

Logger: homeassistant.config_entries
Source: config_entries.py:441
First occurred: 11:33:14 (1 occurrences)
Last logged: 11:33:14

Config entry '------@-----.com' for econet integration not ready yet; Retrying in background

After enabling detailed logs I see:

2023-10-25 11:44:18.185 DEBUG (MainThread) [pyeconet.api] {'options': {'@CONNECTIVITY': {'last_connected': 1698247882045, 'last_disconnected': 1698248306562}, '_id': 'ObjectID("****")', 'account_id': '****', 'address': '', 'allow_email_notifications': False, 'allow_product_alert_emails': False, 'allow_product_alert_text_msg': False, 'allow_push_notifications': True, 'allow_special_offers_emails': False, 'allow_special_offers_text_msg': False, 'allow_text_notifications': False, 'app_brand': 'econet', 'app_version': '4.0.8', 'cb_service_account': False, 'cb_ttl_override': 0, 'city': '', 'connected': False, 'country': 'US', 'email': '***', 'email_validated': False, 'first_name': 'Rr', 'is_phone_verified': True, 'last_name': 'Tt', 'os_version': 'android', 'phone': '', 'phone_number': '****', 'phone_validated': False, 'postal_code': '', 'receive_marketing_messages': False, 'report_state': True, 'role': 0, 'state': '', 'success': True, 'temperature_display_unit': 'Celsius', 'two_factor_enabled': False, 'two_factor_method': 'email', 'user_id': '***'}, 'user_id': '***', 'user_token': '***'}
2023-10-25 11:44:19.750 DEBUG (MainThread) [pyeconet.api] {'results': {}, 'success': False, 'logs': 'The error has occurred in getLocation'}

Error

It seems the error is in getLocation but not quite sure what to make of that.

What version of Home Assistant Core has the issue?

core-2023.10.5

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

econet

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

Original URL
State: closed
Created 8 months ago
Comments: 54 (14 by maintainers)

Most upvoted comments

Sweet! I have the PR open to make the change official. No idea what the Home Assistant release stuff is like now, I’m out of touch with that. So I wouldn’t expect this until the next major release.

w1ll1am23 on Oct 25, 2023

I just switched to the ESP integration today. Very nice

51av0sh on Nov 9, 2023

Everyone this library bump was included in today’s HA release. If you manually upgrade by using the custom component please be sure to delete that after upgrading so you get future updates.

Also, side note switch to the esphome integration if you can. I’ll continue to try helping with bug fixes related to the cloud integration but I’m not longer using it as of yesterday.

w1ll1am23 on Nov 1, 2023

I know this is closed but leaving this here in case it’s useful. I didn’t implement this change and everything has started working for me again today out of nowhere including the native EcoNet app which was not working for me for about a week

51av0sh on Oct 27, 2023

Just a quick, shameless plug to say we’ve built out a superior, entirely local Rheem integration: https://github.com/esphome-econet/esphome-econet

With ~$30 in hardware (an no soldering required) you get local control of a Rheem Heat-Pump Water Heater, Electric Water Heater, Tankless Water Heater, or HVAC system with a lot more granular data and responsive controls than the official app provides:

barndawgie on Oct 25, 2023

Looking at the API quickly it looks like the response is the same shape so maybe we can just swap to the new endpoint? I’ll try to test that out.

Well that seems to fix it… from my quick test. I’ll see about getting a new lib published. One issue I foresee is the request is a POST with a body the old one had no body. I wonder if the app version in that request being something old in the future will break things.

Example.

{
  "location_only": false,
  "type": "com.econet.econetconsumerandroid", 
  "version_number": "6.0.0-375-01b4870e"
}

w1ll1am23 on Oct 25, 2023

I was using the EcoNET integration, but switched to ESP last night and posted a YouTube video about it. Works great.

Ylianst on Nov 12, 2023

Yes I already did all that and it shows correctly for me. Tried multiple times and hours in between. I think we have different models though since most of my entities are “unknown” state so I only a few useful ones. Mine is a Gen 4. The diagnostic sensor I’m referring to is the wifi signal

Thanks for clarifying!

remygithub on Oct 30, 2023

@barndawgie thanks for sharing. I keep meaning to look in to this. Everyone really should consider moving to this, this integration is only going to continue to break over time, we aren’t using an open API and we all know how cloud products are… this is one of the two devices I have that still use a cloud connection.

Also, last I heard electric water heaters weren’t working? Assume there has been movement there based on your comment?

Yes! That is a recently added feature, compliments of @tronikos.

EDIT: I should add that I only added this to my setup in the last 3-6 months. It is probably one of the easiest ESPHome projects to get into because you’re basically buying spec hardware and just attaching it to an existing jack.

has anyone created a youtube video of the process to create the device and program for simplicity?

No but it’s a great idea! Just opened

https://github.com/esphome-econet/esphome-econet/issues/121

barndawgie on Oct 28, 2023

@barndawgie thanks for sharing. I keep meaning to look in to this. Everyone really should consider moving to this, this integration is only going to continue to break over time, we aren’t using an open API and we all know how cloud products are… this is one of the two devices I have that still use a cloud connection. Also, last I heard electric water heaters weren’t working? Assume there has been movement there based on your comment?

Yes! That is a recently added feature, compliments of @tronikos.

EDIT: I should add that I only added this to my setup in the last 3-6 months. It is probably one of the easiest ESPHome projects to get into because you’re basically buying spec hardware and just attaching it to an existing jack.

has anyone created a youtube video of the process to create the device and program for simplicity?

fireheadman on Oct 28, 2023

Wow, I don’t know how I missed this before. Just ordered a couple of the K045’s (so I can blow one up if If miss something). This looks great, I had my HPHW replaced under warranty and the new one displays a LOT less information, e.g. internal sensors. Plus I can do away with their idiotic cloud service. One more down!

Linwood-F on Oct 26, 2023

Just ordered the stuff!

w1ll1am23 on Oct 26, 2023

@barndawgie thanks for sharing. I keep meaning to look in to this. Everyone really should consider moving to this, this integration is only going to continue to break over time, we aren’t using an open API and we all know how cloud products are… this is one of the two devices I have that still use a cloud connection.

Also, last I heard electric water heaters weren’t working? Assume there has been movement there based on your comment?

Yes! That is a recently added feature, compliments of @tronikos.

EDIT: I should add that I only added this to my setup in the last 3-6 months. It is probably one of the easiest ESPHome projects to get into because you’re basically buying spec hardware and just attaching it to an existing jack.

barndawgie on Oct 26, 2023

@barndawgie thanks for sharing. I keep meaning to look in to this. Everyone really should consider moving to this, this integration is only going to continue to break over time, we aren’t using an open API and we all know how cloud products are… this is one of the two devices I have that still use a cloud connection.

Also, last I heard electric water heaters weren’t working? Assume there has been movement there based on your comment?

w1ll1am23 on Oct 26, 2023

Worked for me as well. Thank you

vladtyu on Oct 25, 2023

yup, It’s working for me.

evilalmus on Oct 25, 2023

feeling silly, trying again.

evilalmus on Oct 25, 2023

Woot okay I had a typo

Can someone here confirm if the most recent change is working for them?

Basically need to copy the existing econet directory located here https://github.com/home-assistant/core/tree/dev/homeassistant/components/econet in to your config directory in a folder called custom_components

Then edit the manifest file to look like the below. Adding version and updating the pyeconet version to 0.1.22

Then reboot.

{
  "domain": "econet",
  "name": "Rheem EcoNet Products",
  "config_flow": true,
  "documentation": "https://www.home-assistant.io/integrations/econet",
  "requirements": ["pyeconet==0.1.22"],
  "codeowners": ["@vangorra", "@w1ll1am23"],
  "iot_class": "cloud_push",
  "loggers": ["paho_mqtt", "pyeconet"],
  "version": "1.0.0"
}

w1ll1am23 on Oct 25, 2023