When I deleted the IF statement and removed line 247 (return 4) it worked. But obviously that would make the driver incompatible with standard non-heat pump devices.
1 Like
Well at least it’s good to know that’s the cause. I’ll take a closer look tomorrow.
If you get a few minutes, could you try this app/driver and tell me if it works?
Still didn't work, it switched to electric again. When I removed the IF statement it did work properly.
Oops, my change didn't put. Could you try now? There is a change to both the app and driver. I added a debug log line so if it's not working it should show us somethign useful.
Yes that worked. Thanks
1 Like
I’ll try to find time to look at vacation this weekend. What’s interesting is you have a vacation mode but I have a separate away command. Not sure what the difference is
1 Like
It seems that Rheem has changed another field that I was using to monitor if the Hybrid Hot water heater I have is actually in the running state (on and actively heating) or not. That field was "thermostatOperatingState". It used to change from Off to Heating and back. That field now stays set to Heating all the time. This is not just in your integration. It also shows that all the time in the EcoNet app. Is there another field that reflects whether or not the Hot water hear heater is actually heating, which you can reflect in your integration?
LJ
I'm not experiencing this issue, it's working fine for me so I don't think anything has changed with the API. That said, no, there is a single attribute called @RUNNING that I read. If that's inaccurate, there's nothing else I can do, I'm simply displaying what the API is sending. It's possible there is an issue with your water heater reporting incorrectly. For anyone else using this integration, is it working for you? (FYI thermostatOperatingState is not sent by Rheem, that's a Hubitat field that the integration populates based on the value read from @RUNNING)
For some reason, the thermostatOperatingMode event has not triggered since 10/22/2020. It was working fine until then. I did do a Repair two days ago using Hubitat Package Manager and no change.
LJ
Does changing setpoint or mode still work? If not the connection may have died, try clicking the Initialize button on the device.
I had been checking the app. that works. But from Hubitat it does not seems to work.
I will PM to you the App Log when trying to change mode.
LJ
Hello,
Thanks for your work on this @dman2306.
I am currently trying to setup a rule in rule machine to change the device from heatpump mode and high demand at certain times of the day. However i don;t seem to have Heat pump mode or high demand mode showing under rule machine>thermostats
.
I can see all the modes under devices,
I guess my question is how do i access "set water heater mode" in rule machine?
The way this works is it has to use the Thermostat properties in Hubitat. So there are equivalent names for all these heat pump names that might be found on an ordinary thermostat.
For example, (off the top of my head, so please double check me) Emergency Heat is the same as High Demand mode on the heat pump, so you would select Emergency Heat in the thermostat properties of Rule Machine if you want High Demand.
Again from memory,
- Auto mode = Energy Saving (Eco?)
- Heat = Heat Pump only
- Emergency Heat = High Demand
Anyway, use the equivalent thermostat mode, and it works. It is confusing though to have a different name in Hubitat than what the actual Rheem name is.
2 Likes
Thanks! i have it set it up
lets hope it works!
1 Like
Were you able to figure out how to trigger vacation mode?
I actually completely forgot. I’ll see if I can figure it out this weekend.
@dman2306 While you are looking at things, here is something that I noticed recently. I used the Rheem app to cycle through the possible modes, and watched Hubitat's response.
Hubitat thermostat mode=Rheem app mode
- Off = Off
- Auto=Energy Saving
- Heat=Heat Pump Only
- Emergency Heat = High Demand
- Heat=Electric Only
I don't remember it working that way before, maybe I am not remembering correctly? But if you command Heat in Hubitat (or I guess the reverse, Electric Only in Rheem), you have two possible outcomes, or an undesirable outcome depending upon what the code does.
In this case we get Rheem heat pump only when selecting Hubitat Heat. So could or should "cool" be the other missing mode?
Sure wish we had a way to rename all this to be more clear and/or custom thermostat modes (are you listening Hubitat?).
This is the way it always worked. I think using "cool" for a device that is a "heater" would be rather confusing. You then get even more confusing because that then implies there would be a cooling setpoint. It just seems like a bit of a hack to me.
The problem here is the inflexibility of the Hubitat thermostat implementation. I really wish they'd remove some of these vestiges of the ST platform and make some improvements in the way capabilities work, but I don't believe they've even touched the capabilities functionality in over a year now... oh well 
This is why I created a custom command, setWaterHeaterMode. However, I suspect you want to do something like use it on a dashboard tile which hubitat doesn't support. While I do agree with you, I can't come up with any solution that isn't a hack. The real solution, in my opinion, is for Hubitat to improve the thermostat implementation. Not sure when/if that will happen, or for that matter if anyone has even actually suggested such a change!
1 Like
