[No longer maintained] Rheem EcoNet Integration

Sorry, I'll give a little more of a step by step. Open up the Logs page. While that page is open, go to Apps -> Rheem EcoNet Integration and page through to step 2 where you will see a screen like this:

At that point you'll see a log entry like this:

That's what I need. Basically I need to see how to detect the particular capabilities of your device.

Hopefully that clears it up!

Ok, I think I have this working but I can't test because I don't have a device that works this way so I need some help testing.

What I would need you to do is to uninstall the app and reload the code from
App - https://raw.githubusercontent.com/dcmeglio/hubitat-rheem/enable-disable/apps/Rheem_EcoNet_Integration.groovy
Driver - https://raw.githubusercontent.com/dcmeglio/hubitat-rheem/enable-disable/drivers/Rheem_EcoNet_Water_Heater.groovy

At that point, go through the app and let it create your device. At that point, go to the device for your water heater and scroll all the way to the bottom and you will see:


By that tempOnly you should see another entry that says enabledDisabled true (I hope). If it doesn't, let me know because I screwed something up. If it does show up, then give the modes a try. Basically the way I designed it is you have two modes, off and heat (basically disabled and enabled).

Let me know how it goes!

1 Like

Hey @dman2306 it works! thank you very much for taking the time to add the function to your app. Sorry you had to hand hold me a few times. I sent some beer/coffee money as appreciation!

Glad we got it working and happy to help!

I'll merge it into the main code later this week I just want to do some more testing to make sure I didn't break existing devices!

And thanks, beer will be bought :wink:

1 Like

For some reason I suddenly got these errors after working great for months now. I was able to log back in and it stopped the error. Not sure what is up with those all the sudden? Maybe Rheem "cleaning house" or something?

Also, PM sent.

I think they had a brief outage. Had the same logs at the same time but mine reconnected on its own around 9:30

1 Like

Once in a "blue moon" you have to hit the "Initialize" button on the device page. That resyncs the MQTT and things move right along again.

Hmm. I'll take a look, I haven't noticed this but I reboot my hub nightly and a reboot auto calls Initialize so that might be why.

FYI, just merged in the changes for enable/disable devices. @aoe2exp first thanks for the help getting this working. Secondly, found a couple bugs after we talked so I'd recommend upgrading. When you do, click the Initialize button on the device page. The version you had probably didn't work properly if you put the water heater on a dashboard since I wasn't properly setting the list of supported modes.

1 Like

Thanks for the heads up.

@dman2306 Hi, thanks for working on this. I just installed and was able to get authenticated without issue. I see the mode change then I do it via the app, however I cannot change the mode in Habitat. Any ideas?

Is there anything in the logs for either the integration or the device? Also, try doing it WITHOUT the mobile app running on your phone. Their server didn't seem to like multiple simultaneous connections so the mobile app might be overriding hubitat.

The integration works great for me except that when I use Rule Machine to set the thermostat on my heat pump to "heat" I find that in the Econet app it reports as being in Electric mode. How can I set it to heat pump mode?

Hmm that's odd. The only way I see that possible is if the integration thinks your device doesn't support heat pump mode. Could you do this, go to the app, click on the gear icon next to it . Under Application State you'll see a line like this:

deviceModes {YOUR DEVICEID HERE=[OFF, ENERGY SAVING, HEAT PUMP ONLY , HIGH DEMAND, ELECTRIC MODE]}

Could you paste that here? Notice mine is actually "HEAT PUMP ONLY " (a space at the end... a typo in their api). I'm wondering if maybe in later models they fixed that typo or something like that.

This is what I have:
=[Off , Energy Saver , Heat Pump , High Demand , Electric , Vacation ]}

Looks like they added a space after all of the modes now and removed the ONLY. Also, I would love to be able to enable Vacation mode since the heat pump only mode still has a minimum heating level of 110 and my impression is that Vacation mode is lower than that.

P.S. I just received my unit last week so it may be a newer version. My wifi software version is RH-WIFI-04-01-55

Ah the real issue here is that it's no longer upper case. Fun fun!

Vacation mode is a bigger change, I'll look into it, but not going to be able to bang that out tonight. Can you try this, open up the App Code and go to line 159

It should look like:
if (deviceMode == mode)

Change it to:
if (deviceMode.toUpperCase() == mode.toUpperCase())

Then try setting it to heat again, it should use heat pump. If that works I'll put out an update.

Just as another data point, mine is still like yours, OFF, ENERGY SAVING, HEAT PUMP ONLY , HIGH DEMAND, ELECTRIC MODE.

1 Like

Tried it. It still switched to electric.

Oops, you also need to go to the driver code and go to line 245 which looks like:

if (parent.hasMode(device, "HEAT PUMP") || parent.hasMode(device, "HEAT PUMP ONLY") || parent.hasMode(device, "HEAT PUMP ONLY "))

Change it to:

if (parent.hasMode(device, "HEAT PUMP") || parent.hasMode(device, "HEAT PUMP ONLY") || parent.hasMode(device, "HEAT PUMP ONLY ") || parent.hasMode(device, "HEAT PUMP ")

FOrgot about the stupid space!

You're missing a ) .
It didn't work and still just switched to electric. Auto, and emergency heat work as intended.
I should mention that when I use setWaterHeaterMode it doesn't do anything for any mode.

hmm. I'll have to take a closer look. setWaterHeaterMode won't work because of the same casing issue. I'd recommend turning on debug logging and lets capture some log data. Your device seems a little different so we'll need to figure it out. But I suspect it's small tweaks.