This is the list os status we can have. Documentation link is https://developers.home-assistant.io/docs/core/entity/water-heater/#properties
To get the list of status updated to include Auto you will need to propose a change in the Home Assistant architecture repository in Github.
The documentation claims that you can:
You can use the service hive.boost_heating to set your heating to boost for a period of time at a certain target temperatureā. Individual TRVs can also be boosted in the same way, using this service.
I have raised a feature request to add operation mode āAutoā to the water-heater component
Before it broke I used the inbuilt ha integration (still have the hive hub), so only installed this full add on to solve the problem. However afterwards Iāve noticed the hive app schedules for thermostat temperature arenāt being applied. Eg hive app scheduled to set 18 degrees @10pm but thermostats stayed at 20 as per set manually earlier that day. Is this a known bug or something new? Thanks
Heads up, not sure if just me, but the latest best version 2020.1_b6 seems to break the integration again. Bringing back the āUnavailableā status 
2020.1_b6 is working here for multiple thermostats but not for water heater (dev is aware of issue on Github)
Iāve just noticed that my Hive is āUnavailableā too. Looks like itās a known issue?
Hi
Donāt update to the beta, only use the 2020 stable one.
If you upgrade to the beta, it renames your heating to the name you use on the hive app, it uses a token instead of logging in every 15 mins (from what Iāve read) I also lost my state entityās.
Many thanks for your reply on this. It would be very helpful and happy to test for you if you release this feature in the future.
Is this fixed in core 116 ? I do not see any mention in the release notes
I wonder the sameā¦ Glad I fixed it myself lol
Looks like it got missed form 0.116.0, should be included in 0.116.1
Version 0.116.1 is released and the hive fix is in the release notes
I can confirm upgrading to 0.116.1 has fixed the Unavailable issue for me.
Hi All,
As mentioned further up 2020.1 is beta software and revamps most of the hive backend. This is in early stages of beta testing and has plenty of bugs within it.
Once I get it more stable I will be looking for help with testing this upgrade to 2020.1.
2020.0 is the latest production version which fixes the issue with the Hive Authentication change but please remember there is no support for 2FA yet so this integration will only work if 2FA is switched off.
I have had a brief look at 2fa and it doesnāt look straight forward as hive seems to be moving more of there APIās through AWS.
I set up this integration via HACs (Having initially dropped the python scripts from the 1st post in this thread into custom_components before realising they were deprecated)
I have the entities displayed on lovelace OK, so the next step was to use them in automations I want to turn off water & heating when no one is home and put them back to scheduled as soon as the first person comes home. I call the following services for āno one homeā :
# Turn off water
service: water_heater.turn_off
data: {}
# Turn off heating
service: climate.turn_off
data: {}
entity_id: climate.heating_2
and for resuming hot water to schedule when someone returns, I have :
# Set water back to scheduled
service: water_heater.set_operation_mode
data: {}
entity_id: water_heater.hot_water
But I canāt seem to find what service to call to get heating back to scheduled. Iāve found āheating onā and āboost heatingā services but nothing to return to scheduled. Most of the climate.* services seem to be US HVAC oriented.
Any idea what service i need to call to get heating back to scheduled ?
Thanks
Is the HIVE_API.urls.global_login issue back again? I just upgraded from .115 to .117 and I got the Unavailable issue. The HIVE_API.urls.global_login value was the old version not the new one. Changing it again fixed the issue.
Using the .117 docker image.
Are you using the built in version from HA or the custom component. The built in one hasnāt changed since it was fixed. Iāll have a look in the code now
I have looked at the code in GitHub for the built in home assistant, nothing has changed and it should be the new URL. Iāll have a play tonight and see if I get any issues.