Is anyone experiencing problems with Rheem EcoNet? My Rheem water heater is EcoNet enabled with an add on Rheem wifi module. It has been performing reasonably well for several years. Over the last couple weeks my automations, I have several involving the WH, have been failing. Sometimes they work and sometimes not. I have noticed that while trying to troubleshoot the problem it often fails and then without changing anything, the automations run successfully later on. Sometimes the automation is only partially successful. If the automation involves changing the temperature and the mode one or the other may fail while the other one works. The way it acts, it seems to be related to the EcoNet cloud ability to service the commands. The EcoNet app also has problems. When the temperature is changed in the app it sometimes does not change the water heater temperature display and when it does, attempting to change it subsequently fails and when the temperature adjust page is closed and reopened ot appears the the scale has reverted to Celcius. Perhaps Rheem has failed to keep up with increased demand and their cloud construct cannot process commands and they are discarded.
Truly I wish there was a way to dump EcoNet but I cannot see a way around it currently.
Update:
When the temperature setting fails, i receive this from the integration “Failed to call service water_heater/set_temperature”, ‘lowerLimit’
Once control fails the integration must be reloaded to regain control.
I have what sounds like a similar problem. On my Rheem water heater I have two water heater automations one that sets the temp once a week to a 60C and another that sets its the following day to 43C.
The high one works, each week on schedule it will set to the correct temp on schedule. However, setting to 43 does not seem to work, the automation fires but the temp is not changed. Did you ever find a solution to this?
I think I figured this out actually just after posting.
Something about this thread got me to think that maybe 43C is too low. So I noticed that 110F is 43.333C and thought maybe that is the lowest it will go and trying to set to 43.0 C is too low. I set the automation to 44C and it worked. Not sure if this is exactly why but it seems ok now. Wish I had noticed this long ago, it took several hours of testing and troubleshooting all automation config when it was actually something very simple.