Hello @GreenTurtwig, I’ve just upgraded to 0.40 and the issue still exists. I’m keen to benefit again from your sterling efforts. Any ideas? Thanks! Glen
I really don’t recommend using it until Hive puts out an official API, discovering devices e.t.c. is a really big mess. 
Anyway, that issue isn’t related to Home Assistant, it’s reporting that the “thermostat” you gave it doesn’t have a key named targetValue in the array activeScheduleLock, you sure you were using an actual thermostat and not some other device (The Hive API is really confusing… )?..
Hi @GreenTurtwig, thanks for the reply. I’m quite certain I was using the right thermostat as it worked perfectly well up until the recent update. Could it be possible that hive changed the ID? If so, perhaps I should have another play with postman.
Hi @GreenTurtwig! Issue solved (after much tinkering).
In the end, I only changed the status of hive to ‘off’ (on the app) and rebooted Home Assistant, and then it started working again! I guess it doesn’t like being in manual mode upon boot.
Great! I know this is all such a pain, sorry I can’t do much about it.
Just thought I’d let you guys know that I’ve rewritten everything from scratch today, still a little more to do, but the basics are there. All you’ll have to do is enter your username and password in the config and it’ll work fine (if British Gas doesn’t change their API…).
1 Like
Hi GreenTurtwig,
I should have posted something here straight away after jsock let me know about this post, but didn’t get round to it.
Basically after not performing a good search for hive integration I decided to create a custom component for hive heating and hotwater, which sounds like it does a similar thing to yours, I have posted about it here.
Tonight I should be updating the post with a new version (once the latest tests have gone successfully , so far so good) which is much more scalable and I am hoping should be able to integrate all the Hive components (heating, hot water, lights, plugs)
My fault for my dodgy search in the first place, but would you like to combine efforts on this?
Yeah, that would be fantastic, having two people working on it would be great. 
Just to let you know though, my re-write uses the “new” API Hive uses for their web dashboard. It’s much better in my opinion, but you can only get info on all devices at once, not individually like you could previously.
Anyway, having all this combined into one Hive platform would be great, just enter your username and password and we’ll discover all the devices on the account and add them to Home Assistant.
The only device/product I can think of that would be difficult to integrate though would be the the hot water/boiler, since Home Assistant doesn’t have a dedicated boiler platform yet, we could probably figure out a work around though (maybe an input_select?)
I hope we can get this implemented well. 
1 Like
Just thought I’d upload the latest re-write anyway, should be better than before. Controlling plus getting the status of your heating are both there.
climate:
username: [email]
password: [password]
Do you have any documentation for the new API? I have never seen that before, mine all runs from the 6.5 API
My new re-write works exactly as you described, just enter username and password on to a Hive platform and it does the rest adding all the devices it detects (so far only heating and hot water, plus sensors to separately get the different values out). To add more device types it should fairly straight forward, by adding a new custom component file in the relevant folder which talks to the same platform file
At the moment if you add the following config:
hive: username: YourHiveUserName password: YourHivePassword
it does the following:
with the hotwater added as a climate device at the moment, but I cant imagine it would take long to convert to another type.
I am struggling with a couple of annoying issues, maybe tomorrow I will post what I have if anyone is interested.
One is an error where I am not understanding how things are initialised when HASS loads the platform, but that one is not so important,
The other one is the feedback to HASS and the GUI after setting a new heating, hotwater mode or temp change, the change is not reflected in HASS / GUI, but the change is made in the Hive system and you have to wait for the next API call to get the correct data.
To be honest I am close to giving up with this, it does what I want it to do, which is mainly reporting back the various current states, but it could be expanded much further.
GreenTurtwig, if you do have some reference material for the new API then I could try and update to work with this, and maybe this will solve my issue.
rendili - I’ve followed your other thread (and now this one) and thanks to you have the heating setup and grouped in my dashboard. Unfortunately I can’t for the life of me figure out the alternative that GreenTurtwig has done in terms of setting up the groups (which may well be my lack of understanding) but yours was very straightforward.
As such, please don’t give up!
1 Like
Thank Syx for those encouraging words. I took another look fresh this morning, and I think I have something.
Here is the new version of what I have, it will replace my previous components, the configuration file for adding the components is different to before, but any group configuration is the same as before, and it will maintain history.
As this version is one integrated platform and not two individual customcomponents, it is quicker when starting up HASS, it is kinder on the overall CPU usage and there are less API calls as it makes only 1 API call for all.
To setup:
- Copy the hive.yaml (44.5 KB) file to “/custom_components/hive.py” taking care to change the file name from hive.yaml to hive.py
- Copy the hive_climate.yaml (4.8 KB) file to “/custom_components/climate/hive.py” taking care to change the file name from hive_climate.yaml to hive.py
- Copy the hive_sensor.yaml (10.1 KB) file to “/custom_components/sensor/hive.py” taking care to change the file name from hive_sensor.yaml to hive.py
- Remove from configuration.yaml any sensor or climate setup for my previous version
- Add the following to configuration.yaml to setup the new version
hive: username: YourHiveUserName password: YourHivePassword minutes_between_updates: 2 devices: - hive_heating - hive_hotwater - hive_thermostat_batterylevel - hive_heating_currenttemperature - hive_heating_targettemperature - hive_heating_state - hive_heating_mode - hive_heating_boost - hive_hotwater_mode - hive_hotwater_state - hive_hotwater_boost
As before, minutes_between_updates: is optional and actually does not work at the moment, it will always set 2 minutes between updates.
Also the devices: section is optional, if you do not add this it will add all devices it detects. if you add this to the config, then specify which devices you would like added
I have added all devices and then added to them all to a group as below :
HiveHeating:
name: Hive Heating
entities:
- sensor.hive_heating_mode
- sensor.hive_heating_boost
- sensor.hive_heating_state
- sensor.hive_hot_water_mode
- sensor.hive_hot_water_boost
- sensor.hive_hot_water_state
- sensor.hive_target_temperature
- sensor.hive_current_temperature
- sensor.hive_thermostat_battery_level
- climate.hive_heating
- climate.hive_hotwater
Once setup it should look like this:
At the moment the hotwater is set as a climate device, but as GreenTurtwig suggested it would probably be better as an input_select. I don’t know what component type that is, but I can work with GreenTurtwig to get that changed (If you are ok with that GreenTurtwig?)
Plus this is running from the same API as before, and not the new one that GreenTurtwig’s customcomponent is running from.
If anyone has other Hive devices such as lights, plugs, motion sensors, then hopefully working with GreenTurtwig we can update this platform to get them added
I hope this version works for those that are interested, please let me know either way if it works or not, it would be really great to know.
1 Like
Hi @rendili. I have tried your new scripts. They don’t seem to create any sensors for me. Looking through the logs I can see the following error:
17-04-21 12:17:18 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform hive
Traceback (most recent call last):
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 153, in _async_setup_platform
entity_platform.schedule_add_entities, discovery_info
File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
value = future.result()
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/home/homeassistant/.homeassistant/custom_components/sensor/hive.py", line 409, in setup_platform
HiveSession_Current.UserName = config[CONF_USERNAME]
KeyError: 'username'
My username and password are definitely correct. Any ideas?
Hi gr4z,
It looks like it could be setting up the Hive platform as a sensor in your configuration, plus maybe the old version file used instead of the three new files from the new version?
The Hive: entry is at the top level and is its own custom component type, not a custom sensor component
So instead of having:
sensor: - platform: hiveheating username: YourHiveUserName password: YourHivePassword climate: - platform: hiveheating username: YourHiveUserName password: YourHivePassword
You need to have instead:
hive: username: YourHiveUserName password: YourHivePassword
plus please could you double check that the 3 new files from this thread posted above have been copied to the correct folders and sub folders?
The hive.py file in the “/custom_components” folder should be the big main one at 44.5KB
The hive.py file in the “/custom_components/climate” folder should be the climate device file at 4.8KB
The hive.py file in the “/custom_components/sensor” folder should be the sensor device file at 10.1KB
I hope this helps, let me know 
If it is still erroring then please could you post the relevant section of your configuration.yaml file? (taking care to replace the username and password with dummy text )
Working as you describe - made the changes to the sensor/climate configuration and did not edit my group… all seems to be operating with a seamless transition. Thank you!
(Note, I’m only using a few of the sensors to save dashboard space)
1 Like
Excellent, good news 
glad to hear the change to the new version went smoothly and all is working
Thank you so much for letting me know
(also pleased to hear that adding the functionality for the optional device configuration to add certain devices is of use and being used )
Mmm, still the same error
17-04-21 15:57:11 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform hive
Traceback (most recent call last):
File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 153, in _async_setup_platform
entity_platform.schedule_add_entities, discovery_info
File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
value = future.result()
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/home/homeassistant/.homeassistant/custom_components/sensor/hive.py", line 409, in setup_platform
HiveSession_Current.UserName = config[CONF_USERNAME]
KeyError: 'username'
Definitely only have hive.py in custom_components, custom_components\climate and custom_components\sensor folder.
My configuration.yaml file has:
hive:
username: <redacted>
password: <redacted>
Will have another dig around.
Hi gr4z
Are you sure you downloaded the three new files and placed each one in the three different folders?
Line 409 from your error message with the UserName is where the old version file takes the username from the configuration and adds it to a variable.
Your configuration as you pasted it looks good.
it might be easier to delete all previous hive files from your custom component folder structure, then re-down load the new three different files and re-copy the correct file to the correct folder.
Just to confirm, that there are three file links above and each one is a different file that needs to be downloaded separately and needs to go in the correct folder for it to all work
