home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.18k stars 30.2k forks source link

Vacation Mode missing from EcoNet #90243

Open skipnyip opened 1 year ago

skipnyip commented 1 year ago

The problem

In the "Operation" section, the mode "Off" is listed twice, and there is no option to switch the Water Heater to Vacation Mode. image

What version of Home Assistant Core has the issue?

core-2023.3.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

EcoNet

Link to integration documentation on our website

https://www.home-assistant.io/integrations/econet#water-heater

Diagnostics information

home-assistant_econet_2023-03-24T19-28-19.853Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Selecting either "Off" will turn the Water Heater off. Setting it to Vacation from the physical water heater does not appear to show up in Home Assistant at all.

Appears to be the same issue as https://github.com/home-assistant/core/issues/72159.

home-assistant[bot] commented 1 year ago

Hey there @vangorra, @w1ll1am23, mind taking a look at this issue as it has been labeled with an integration (econet) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `econet` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign econet` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


econet documentation econet source (message by IssueLinks)

barndawgie commented 1 year ago

Would be great to get this working - I'd like to be able to automate moving the water heater in and out of vacation mode alongside some of my other components. Even read-only would be helpful as I'd like to disable the hot water circulator whenever the heater is in Vacation mode.

skipnyip commented 1 year ago

Logger: homeassistant.util.logging Source: util/logging.py:168 First occurred: 11:17:15 PM (1 occurrences) Last logged: 11:17:15 PM

Exception in on_update_received when dispatching 'econet.push_update': () Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/econet/water_heater.py", line 77, in on_update_received self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 590, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 654, in _async_write_ha_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 596, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/water_heater/init.py", line 179, in state return self.current_operation ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/econet/water_heater.py", line 90, in current_operation _current_op = ECONET_STATE_TO_HA[econet_mode] ~~~~~~^^^^^^^^^^^^^ KeyError: <WaterHeaterOperationMode.VACATION: 9>

skipnyip commented 1 year ago

Logger: homeassistant.util.logging Source: util/logging.py:168 First occurred: 11:17:15 PM (1 occurrences) Last logged: 11:17:15 PM

Exception in on_update_received when dispatching 'econet.push_update': () Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/econet/water_heater.py", line 77, in on_update_received self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 590, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 654, in _async_write_ha_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 596, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/water_heater/init.py", line 179, in state return self.current_operation ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/econet/water_heater.py", line 90, in current_operation _current_op = ECONET_STATE_TO_HA[econet_mode] ~~~~~~^^^^^^^^^^^^^ KeyError: <WaterHeaterOperationMode.VACATION: 9>

4romany commented 1 year ago

Does not look like anyone taking ownership of this problem. While trying to use this integration in Home Assistant I can verify that "OFF" is listed twice - and no vacation mode. Now - when I issue an OFF command - to turn off all heating options - what happens is that the app (and the Rheem display) shows DISABLED. I have never saw DISABLED before. I purposely only heat with the heat pump - and only during certain afternoon hours. Outside of these hours I have the unit set to OFF. Has worked perfectly (this is via the scheduling Echonet app). Fast forward with trying to automate this via Home Assistant. When Rheems is in this DISABLED mode - if the water temp drops way down - it turns on and uses the electric strips. If the unit is ENABLED and OFF it never turns on. I was hoping if I placed it in VACATION mode that would also keep it off - but that's not an option. So bottom line I can't use HA to replace my scheduling function on the android app.

EDIT: Bit of a correction. There is a button in the android app called DISABLED/ENABLED - so it is a valid mode. There is another button that gives you OFF/ENERGY SAVER/HEATPUMP/HIGH DEMAND/ELECTRIC/VACATION" choices. They are separate selections - picking OFF does not place the unit in DISABLED - or vice versa. The HA/Rheems add-on appears to flip both of those switches when you use it to OFF the compressor (i.e. it also goes into DISABLED mode)...

LondonBenji commented 1 year ago

I have a Rheem water heater as well but it's not a heat pump version. I only have three options in the "Operation" menu: Eco/Performance/Off.

These all seem to work, along with being able to set the temperature however, the away mode switch does not set 'vacation mode' on the water heater either. When I try and set away, I don't think anything appears in the logs, but I DO see this occurred in the logs at some point, but I am not sure what I was doing at the time -

Logger: pyeconet.equipment.water_heater Source: components/econet/water_heater.py:133 First occurred: 5:20:44 PM (2 occurrences) Last logged: 5:37:30 PM

Could not find a matching mode string to set.

4romany commented 1 year ago

If folks are having issues with this intergration I would suggest/recommend you look into this solution:

https://github.com/Daniel-dev22/esphome-econet

I've been very pleased with this - I can now see what the temp of the water actually is (upper and lower) - and I have full control of the operation. The RS485 dongle has a ESP32 built in - the yaml code to configure it is provided in the github. Works great.

barndawgie commented 1 year ago

If folks are having issues with this intergration I would suggest/recommend you look into this solution:

https://github.com/Daniel-dev22/esphome-econet

I've been very pleased with this - I can now see what the temp of the water actually is (upper and lower) - and I have full control of the operation. The RS485 dongle has a ESP32 built in - the yaml code to configure it is provided in the github. Works great.

Thanks for the pointer! I got 95% of the way there but can't actually seem to get any data out of the water heater - all of my sensors just show as 0 readings with that and there is no way to file issues.

LondonBenji commented 1 year ago

If folks are having issues with this intergration I would suggest/recommend you look into this solution:

https://github.com/Daniel-dev22/esphome-econet

I've been very pleased with this - I can now see what the temp of the water actually is (upper and lower) - and I have full control of the operation. The RS485 dongle has a ESP32 built in - the yaml code to configure it is provided in the github. Works great.

"Electric Water Heater - Not Currently Supported"

Whoomp whoomp 😢

Would have loved this for two reasons:

  1. Local control
  2. Potential to use Ethernet based ESP32 to satisfy my hatred for WiFi.

Oh well, thanks for the suggestion anyway.

4romany commented 1 year ago

EDIT: I need to mention in my message below I'm referring to the Rheems Hybrid water heater - NOT Rheems heat pump HVAC. There has been progress made with the heat pump HVAC - I think some are function now - but that discussion I have not really followed. Look at the discord "Econet API Learning" to any an all discussions with Rheems integrations.


Hey barndawgie, londonbenji - don't give up quite yet. There is a discord channel where this new ESPhome integration is discussed called "Econet API Learning" - that a resource that might help. It is still very active as they are working on integrating other Rheem products. And compare my ESPhome yaml file with yours. Its a bit different than the example yaml file - some tweaks that dan1002 recommended that fixed one minor issue for me (at the very bottom you will see 2 lines commented out). Also notice I'm pulling directly from his github location. Those should be the only difference. Double check your RJ11 wiring. I'm using the ATOM RS485 DC/DC Voltage Converter as described in the github readme. This integration has been rock solid for the 3 weeks I've been using it. I've removed the econet app from my phone and disabled wifi on the rheems water heater. Not quite time to give up yet guys :-) econet.yaml.txt

issue-triage-workflows[bot] commented 10 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

barndawgie commented 10 months ago

For those tracking this issue: We support Vacation mode and many other features not supported by the EcoNet integration, all without any Cloud requirements, via the https://github.com/esphome-econet/esphome-econet integration. All you need is an easy to assemble and install ESP32 Microcomputer that costs ~$25.

skipnyip commented 10 months ago

Issue still not resolved as of Home Assistant Core 2023.11.2

image

issue-triage-workflows[bot] commented 7 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

rexbron commented 7 months ago

Still an issue with 2024.2.1

dualtronic commented 6 months ago

Still a problem. Been a year since issue was opened.

issue-triage-workflows[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

rexbron commented 3 months ago

Bump

issue-triage-workflows[bot] commented 2 weeks ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

skipnyip commented 2 weeks ago

Still an issue as of 2024.9.1

image