Hi @230delphi
We have released the custom component into the default hacs repository now. Please could you remove the custom repo in the hacs settings and use the new one.
You should be able to find by searching for hive.
2 Likes
yup. that fixed it. thanks.
For other folks that miss it - in HACS,
-> click for extra settings āā¦ā
-> āCustom Repositoriesā
-> delete the old one if it exists!
I just installed a hive multizone heating system and installed this custom component via HACs to homeassistant 112.4 but it is not finding my devices:
My configuration.yaml contains:
hive:
username: [email protected]
password: "mypassword"
scan_interval: 2
*Note: my password starts with an ā!ā, that is why I have it in inverted commas.
HomeAssistant log on start:
2020-07-29 23:13:45 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hive which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
No other mention of hive in the log after this, no hive entities or states in developer options.
Any advice?
Hi @CaptInsano
If you have your setup with just the hive entry in your configuration.yaml (as you have detailed already) but not have the custom component, do you see all your devices?
What entities are added for hive when you have just the configuration.yaml?
(should have āHive Hub Statusā sensor, āHeatingā climate entity for each zone and āHot Waterā if you have the hotwater version of Hive)
I have removed the Hive custom component but left the entry in the configuration.yaml. There is now no mention of hive in the log when starting up. It still does not list any of my devices (Active Heating: 3 thermostats/receivers (1 has hot water controls also))
I can access all of these items via the app and https://my.hivehome.com/dashboard with the username and password in the configuration.yaml. I also changed the password to not start with ā!ā and removed the quotation marks in case there was a bug but still not finding my devices.
hive:
username: [email protected]
password: passwordtext
scan_interval: 2
I presume my location does not affect this from working? I am based in Ireland.
Hi @CaptInsano
If there are no errors or new entities added when you add the hive bits to configuration.yaml, then maybe it could be that there is a separate version for Ireland, there is a dedicated section of the hive home website for Ireland.
We would need to see and extract of your API data from hive to determine any differences, hopefully it is just a device ID change if anything.
I am so sorry for the delay in getting back to you after your replies. I was away for the last 2 weeks but am now back at home and eager to get my hive setup working in HomeAssistant!
Still no luck getting it working here but also no errors in the log as per my previous posts.
Is there anything I can do to help you debug the system if it is different for Irish users? Should I start an issue ticket in the github for this integration?
Thanks
I removed all references of hive from my configuration.yaml, updated to the most recent beta of this integration and tried to set it up via the integrations UI and I got some errors that may aid in debugging this issue:
2020-08-19 21:04:00 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 73, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 145, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 60, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 106, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 153, in async_configure
result = await self._async_handle_step(flow, cur_step["step_id"], user_input)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 201, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File "/config/custom_components/hive/config_flow.py", line 68, in async_step_user
token_request = await self.hive.create_token(login_token)
File "/usr/local/lib/python3.8/site-packages/pyhiveapi/hive_async_api.py", line 85, in create_token
await self.request('post', url, data=j)
File "/usr/local/lib/python3.8/site-packages/pyhiveapi/hive_async_api.py", line 44, in request
await resp.json()
File "/usr/local/lib/python3.8/site-packages/aiohttp/client_reqrep.py", line 1026, in json
raise ContentTypeError(
aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: application/*+json;charset=utf-8', url=URL('https://api.prod.bgchprod.info/omnia/accessTokens')
I also created a github issue if it helps here:
I have a couple of questions
a) What does this custom component give me that I donāt get from the standard integration
b) If I install this custom component, what happens to the entities I currently have using the standard integration?
The documentation at https://github.com/Pyhive/HA-Hive-Custom-Component is not clear on this.
Iām looking at trying out this extension mainly because using the standard integration offline hive lights show as āonā - an issue I have been patiently waiting to be fixed but nothing seems to be happening ( https://github.com/home-assistant/core/issues/21208 )
Will offline hive lights show as āoffā if I use this custom component?
Is anyone else having issues with the Hive integration today? I noticed this morning that I couldnāt control my heating and when I tried to restart HA I noticed that is now showing as Unavailableā¦ tried to upgrade HA to the latest version and tried both the custom integration beta and non Betaā¦
Nothing on the logs 
Any ideas?
Thanks for the help.
Yup same problem here. Stopped working about 11pm UK time last night.
Same issue here, 11pm last night. Glad to see Iām not the only one.
1 Like
Ah, so its not just me. Iāll stop messing with my settings.
1 Like
Yep I was the same 
Checked the api status on the Hive page and all seems to be working, wondering if Hive will be the next in line to ālockdownā their api like most of the iot products these days? Iām starting to see a trendā¦
Similar issues reported over on the Smartthings integration forums:
looks like the API has been closed GRR https://beekeeper-uk.hivehome.com = {āmessageā:āForbiddenā}
As with others - stopped working for me tooā¦
That Forbidden might be expected since Iām getting this
{āmessageā:āMissing Authentication Tokenā}
on
https://beekeeper-uk.hivehome.com/1.0/global/login
But wouldnāt surprise me that they would close itā¦ after all it is a āUnofficial APIā 
Missing Authentication Token is an AWS message when thereās a fault (by design or accidental) with the domain linking through to the running code.
The question is whether it was intentional or not.
1 Like
I thought Iād give their online support a try.
Me: āI was wanting to find out if you have switched off the API? My home automations that use it have stopped working.ā
Them: āPlease elaborate what is an API?ā
Sheesh!
Frustratingly this appears dead for me today too. Just as weāre approaching the heating season, so a perfect reminder of why I chose Home Assistant and why the cloud-only thermostat needs to go.