[No longer maintained] Rheem EcoNet Integration

⚙️ Custom Apps and Drivers Custom Apps
82

Cool. What time zone are you in? I’m est. I’ll be around tonight and can give a version with some debug logging to help troubleshoot

83

PST. I'll be around to test for ya. Thank you for taking the time.

84

Right before deviceDetails.modes = equip."@MODE".constraints.enumText on line 128 of the app could you add a log.debug equip and show me the output when it lists the devices? I don't think there is anything confidential in there, but feel free to DM it to me.

85

I finally got around to testing the updated driver, and get this error when attempting to change the temperature:

groovy.lang.MissingMethodException: No signature of method: user_app_dcm_rheem_Rheem_EcoNet_Integration_449.updateDevices() is applicable for argument types: () values: []

86

I tried out your driver today after realizing my integration no longer changed parameters.

in trying out your driver/app I get the following error:

2020-07-12 06:34:08.087 pm errorAPI Error, retrying 1

app:10762020-07-12 06:34:05.537 pm errorAPI Error, retrying 2

app:10762020-07-12 06:34:02.664 pm errorAPI Error, retrying 3

app:10762020-07-12 06:34:00.162 pm errorAPI Error, retrying 4

app:10762020-07-12 06:34:00.054 pm debugRefreshing data for 44892

app:10762020-07-12 06:33:57.662 pm errorAPI Error, retrying 5

app:10762020-07-12 06:33:57.661 pm errorAPI Put Error: java.net.SocketTimeoutException: Read timed out

app:10762020-07-12 06:33:47.442 pm debugapiPut: [uri:https://econet-api.rheemcert.com, path:/equipment/xxxxx/modes, headers:[Authorization:Bearer xxxxxxxxxxxxxxxxxxxxxxx], requestContentType:application/json, body:[mode:Energy Saver]]

i replaced the private info with xxxxxx's

87

That doesn’t seem like the latest code. It should be using mqtt but that is still using http. You’ll likely need to uninstall and install the newest code.

88

I got the code from the package manager... Does that need to be updated?

89

Hmm it should be included. Did you have it installed previously? If so try uninstalling it and reinstalling it.

90

I published a new version. This now requires HE 2.2.2 or above since MQTTS is now supported. This solves the security issue where the token was sent in plaintext. Now everything is completely encrypted.

3 Likes
91

Hello, does the app il supposed to refresh automaticly or do I have to reconnect each time. Because if I want to see the crurent state and temperature have have to reconnect the app
Thanks

92

What do you mean reconnect? Are there logs saying it disconnected? It is supposed to be connected 24/7

94

I have to go back in the app list and use the rheem econet intégration to connect my rheem otherwise il doesnt update the state. Bit I know the device is still connected because if I change the température it works. But if I change the temperature from the rheem app it wont reflect the change in HE app

95

Hello. Total Noob here. I barely started with hubitat and I am slowly migrating from ST.

I ow a Gladiator water heater and the Econet app works as expected. I installed the app and the drivers from the github. The device shows up in "Devices," and I am able to change the target temperature, but I cannot turn on/off the heater. The function is called "enable/disable" in the Econet app. Nothing happens when I press the "off" button or change the water heater mode to off.

I want to turn the heater off overnight and in the morning when nobody is home.

Has anyone had this issue? any ideas are appreciated.

96

I suspect the app doesn't support the command that your water heater requires, especially since it's enable/disable and not a mode setting. I'm sure we can figure it out though.

I just published a version we can use to check some logging
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

If you could install both of those and do two things:
1.) Go through the app and get to the device list. The app should log some details about your device so I can see what attributes exist
2.) In the rheem mobile app, do an enable and disable and grab the logs from the driver which will show me what commands get sent when you do the enable/disable

If you can do that I'm sure we can get it working.

97

Done. I hope I did it right. Let me know.

98

Umm did you paste the logs somewhere?

100 
> 1. dev:132020-10-05 06:58:39.825 pm debugMQTT Message was: {"@ACTIVE":true,"@ENABLED":{"value":1,"status":"Enabled"},"@STATUS":"Enabled","transactionId":"ANDROID_2020-10-05T15:58:35","device_name":"8303690839606097","serial_number":"Q042032680"}
> 
> 2. dev:132020-10-05 06:58:39.451 pm debugMQTT Message was: {"@ENABLED":1,"device_name":"8303690839606097","serial_number":"Q042032680","transactionId":"ANDROID_2020-10-05T15:58:35"}
> 
> 3. dev:132020-10-05 06:58:23.820 pm debugMQTT Message was: {"@ACTIVE":false,"@ENABLED":{"value":0,"status":"Disabled"},"@STATUS":"Disabled","transactionId":"ANDROID_2020-10-05T15:58:20","device_name":"8303690839606097","serial_number":"Q042032680"}
> 
> 4. dev:132020-10-05 06:58:23.326 pm debugMQTT Message was: {"@ENABLED":0,"device_name":"8303690839606097","serial_number":"Q042032680","transactionId":"ANDROID_2020-10-05T15:58:20"}
> 
> 5. dev:132020-10-05 06:58:19.475 pm debugMQTT Message was: {"@SETPOINT":110,"@SCHEDULE":false,"@RESUME":false,"@SCHEDULESTATUS":"","@SCHEDULERESUME":"","transactionId":"ANDROID_2020-10-05T15:58:15","device_name":"8303690839606097","serial_number":"Q042032680"}
> 
> 6. dev:132020-10-05 06:58:18.759 pm debugMQTT Message was: {"device_name":"8303690839606097","serial_number":"Q042032680","@SETPOINT":110,"transactionId":"ANDROID_2020-10-05T15:58:15"}
> 
> 7. dev:132020-10-05 06:58:15.074 pm debugMQTT Message was: {"@SETPOINT":113,"@SCHEDULE":false,"@RESUME":false,"@SCHEDULESTATUS":"","@SCHEDULERESUME":"","transactionId":"ANDROID_2020-10-05T15:58:11","device_name":"8303690839606097","serial_number":"Q042032680"}
> 
> 8. dev:132020-10-05 06:58:14.668 pm debugMQTT Message was: {"device_name":"8303690839606097","serial_number":"Q042032680","@SETPOINT":113,"transactionId":"ANDROID_2020-10-05T15:58:11"}
> 
> 9. dev:132020-10-05 06:58:10.714 pm debugMQTT Message was: {"@SETPOINT":110,"@SCHEDULE":false,"@RESUME":false,"@SCHEDULESTATUS":"","@SCHEDULERESUME":"","transactionId":"ANDROID_2020-10-5T18:58:10.293","device_name":"8303690839606097","serial_number":"Q042032680"}
> 
> 10. dev:132020-10-05 06:58:10.403 pm debugMQTT Message was: {"transactionId":"ANDROID_2020-10-5T18:58:10.293","device_name":"8303690839606097","serial_number":"Q042032680","@SETPOINT":110}
> 
> 11. dev:132020-10-05 06:58:03.299 pm debugMQTT Message was: {"@SETPOINT":120,"@SCHEDULE":false,"@RESUME":false,"@SCHEDULESTATUS":"","@SCHEDULERESUME":"","transactionId":"ANDROID_2020-10-5T18:58:2.464","device_name":"8303690839606097","serial_number":"Q042032680"}
> 
> 12. dev:132020-10-05 06:58:02.595 pm debugMQTT Message was: {"transactionId":"ANDROID_2020-10-5T18:58:2.464","device_name"
101

Thanks, that's the device logs, did you also go through the app and get to the device list section? I need that too. FYI, usually taking a screenshot of the log page is better than pasting text. Not sure why, HE formats the log text really weird :slight_smile:

102

@aoe2exp think I got it mostly built, just need those other logs and then we can try and test

103

Does this help?

imgur[dot]com/a/yvrvGsH

I can't post links or pictures yet :S