OK so i got it connected again yesterday morning and it updated correctly twice. I left it alone but at some point, the update message that includes the @Running stopped coming from Rheem. Due to the limitations of logging on Hubitat, I was unable to capture the last message but I know the last time it properly set the Heating status was around 10:30 AM.
I have attached the logs I was able to see this morning and they seem to demonstrate your app is still receiving @Connected messages from Rheem, but no others. I also attached the Rheem app screenshot which showed that the Water heater was actually heating during the window reflected in the logs. No messages were received from Rheem other than the @Connected message. It may not be your directly, but for some reason Rheem seems to not be able to stay connected to it.
Another observation. It appears to work fairly consistantly if I force a run by changing the set point in the rheem app. But it seems to miss it if the water heater just kicks in on its own. I will try to capture that, though that will be hit or miss. I will let you know.
So this example shows that I changed the set point to 133 to kick off the @Running. That worked and your app updated properly. I then changed the setpoint to 130 and was waiting for the Heating cycle to stop. I came back and looked at the Rheem App at 12:50 and it showed it was no longer Running. The log below shows that nothing was received by your app. That might indicate that Rheem isn't sending it, but why?
It appears to me that Rheem is not reliably sending the @RUNNING, "" message when the Running state changes to idle. So I ran my manual test two more time by changing the setpoint through the Rheem App. Each time the Running message was sent. After the first test I put the Rheem app in the background on the iPhone and went on with business, but watched the Hubitat Logs. I say the @AWAY message and nothing else. I went to check the Rheem App 30 minutes later it it reflected that the running state had ended the heater was idle. No message was received by your app to that effect.
The second test I did the same, except that I kept the Rheem App alive on the iPhone screen and kept the phone from going to sleep to more precisely catch the change from Running to Idle. When It change this time Your app immediately logged the @RUNNING, "" message.
Again it appears that Rheem is not reliably sending the @RUNNING, "" message. Do you understand what the @AWAY message means? Can you explain it to me? I got that message both times in these tests but could it be that if RHEEM thinks the app is not listening it doesn't send the message when the running state stops?The reason I ask is in the second test I got the @RUNNING, "RUNNING" message, then an AWAY message, then I set the temp back to 130 from the rheem app and didn't receive another AWAY message. Then when the Running state changed to idle I got that. There was no AWAY message between them. This might be a problem.
It's related to the home/away feature but I don't know too much. The fact that it is false means you're home which would be correct I assume.
That wouldn't make sense the way MQTT works. MQTT is a pub/sub interface. Devices publish messages to a topic and other things read from the topic. Even if no one is connected, it would still be publishing. Could there be a bug in the MQTT server the use? Sure, but I'd be doubtful of this.
I really don't know that this is a problem as I don't really know when Rheem sends this message. In my logs, it seems inconsistent.
While I would like to help, I really don't know what I can offer here. All of this is undocumented by Rheem and is the result of looking at the work of others (Home Assistant and Homebridge) and looking at traffic on my own network. I can say what I'm doing matches what those other integrations are doing. I'm not saying there isn't a bug, it just seems to point to your device being the problem when, so far, everyone else is saying it works for them.
Out of curiosity, what is the Wifi software version of your device? Mine is RH-WIFI-02-01-25.
Thanks for the responses. and Please don't get me wrong. I a very appreciative of your support and efforts in this app. I am not trying to imply that you have done something wrong here. This is a lot of work and I am grateful to you and all the developers out there who make this Hubitat product what it is.
That said, I am so frustrated and disappointed with RHEEM. I bought this Hybrid Water heater for two reasons, Efficiency, and Econet. It is living up to the efficiency promises, but I am so disappointed in the approach that Rheem is taking on econet. They just don't seem to see the positive impact to their bottom line that Econet could offer them. The home automation market is not Huge but it is significant and this could be a competitive advantage for them. They are squandering that. They treat it like simply a control panel and proprietary phone app and ignore so many things in the Internet of Things market. Their software is inconsistent and flaky.
Such a disappointment. I wanted another Home Automation toy.
I agree. And I would say the same for Honeywell and probably a few others too. They are so short sighted and try to lock people into their proprietary but very limited ecosystems.
The enhanced and open ecosystem would probably boost sales more than it would scare people away.
I completely understand. It's a sad state of affairs how companies want to lock us into their apps. Whenever possible I choose someone with an open api but there are so many device categories where there are no such options.
Anyway, I'm happy to keep trying to troubleshoot I'm just at a bit of a loss. I'm at the standard "have you tried rebooting it?" kind of debugging. I would be interested to see your wifi software version though. I'm curious if perhaps you're on a different version than everyone who is working. I'll keep digging and see what I can find I just don't know what else to try right now.
Unfortunately I have the same wifi version as you.
That does bring up an interesting question though. Does anyone know what the RJ45 plug is for on the right side of the EcoNet panel? Is it just for servicing or can it connect to the internet instead of wifi?
I'm late to the party here, but also appreciate the hard work that's been put into this. I have a quick question. I have an electric water heater w/ econet. I've successfully installed this app and created a water heater device with it (yea!). However, when I look at the variables, I don't see anything about the water sensor cable or leak detection. Is that a no-go?
TIA.
I am afraid that Rheem has really killed the integration capabilities of their EcoNet for all others to connect to it when they migrated their protocol to MQTT last year. Alarms don't appear to be available as well as access to all the various temperature sensors in the Water Heater. We are all disappointed in them. We are hoping they will wise up about the business advantage of going fully open API in the future.
Theoretically, the API supports the leak sensors for some models. However, the list is limited (and unknown). For example, my water heater has a leak sensor and the API does not make it available. From what I've seen it may only be 2020 models and newer? Not totally sure. That said, the idea of using a cloud based leak sensor, in my mind, is ill advised. The notion that if the internet is down, no leak detection is just a bad idea. As a result, it's not high on my list to add this support to begin with. My recommendation would be to do what I did, throw a locally controlled zigbee or zwave leak sensor by the water heater and use that, much more reliable.
That said, @ljp-hubitat is generally right, they removed all of the temperature sensors from the integration. While some may hope they create an open API, this, unfortunately, is not the trend in the "big guys" smart home playbook. I don't expect to see an open API soon, or really ever, from Rheem. All the big companies want you using their apps so they can advertise to you and sell your data. If you do everything from a smart home hub they lose that capability... so what's the incentive to add an API? Nothing that I can see.
The only one I can think of is to give them a competitive advantage in being a more attractive choice to the buyers in the $63 billion home automation market. There are other good Hybrid water heaters out there. Rheem won me because of EcoNet possibility to integrate to my Smart Home.
I'm going to be replacing my water heater soon and one of the ones I'm looking at has the Econet module built in. Can someone summarize what functions are available through the Hubitat integration?
I've had the app installed for over a year. First solo, then once it became available on the HPM I moved it to there. But I assume it was already broken since then. I've tried removing it and adding it again. Manual removal and then install via the HPM. Other than that no other debugging.
I only started looking into it again because it was my nosiest app by far.
