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
73.81k stars 30.91k forks source link

Hive integration could not authenticate #70465

Closed julianjd-uk closed 2 years ago

julianjd-uk commented 2 years ago

The problem

After restarting Home Assistant the Hive integration works for a while, from a few minutes to maybe 30 minutes, and then stops with an authentication error in the core logs. This happens with and without 2FA enabled.

I'm UK based so Hive is still available to me.

What version of Home Assistant Core has the issue?

core-2022.4.6

What was the last working version of Home Assistant Core?

core-2022.4.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Hive

Link to integration documentation on our website

https://www.home-assistant.io/integrations/hive/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Log data:
Logger: homeassistant.config_entries
Source: config_entries.py:349
First occurred: April 22, 2022, 8:46:51 PM (1 occurrences)
Last logged: April 22, 2022, 8:46:51 PM

Config entry 'xxxxxx@xxxxx.xxx' for hive integration could not authenticate

Core log data:
2022-04-23 06:36:35.748 | ERROR    | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401
2022-04-23 06:36:35.886 | ERROR    | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401
2022-04-23 06:36:35.986 | ERROR    | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401
2022-04-23 06:36:36.075 | ERROR    | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

hive documentation hive source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

Hey there @rendili, @kjonline, mind taking a look at this issue as it has been labeled with an integration (hive) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

ukgaz1987 commented 2 years ago

Glad i'm not the only person having this issue. Spent hours yesterday trying to get it working and when I originally checked there were no known issues until this morning.

Mojo-Pinn commented 2 years ago

Glad I’m not the only one too. I’m new to HA and thought it was definitely something I was doing wrong.

KJonline commented 2 years ago

Are you using the owner account when logging into Hive?

ukgaz1987 commented 2 years ago

I am, I’ve also tried to disable 2FA on my account in case it was that but made no difference.

Shall I try to create a sub account and log in with that?

julianjd-uk commented 2 years ago

Yes, I only have a single account with Hive I have also tried with and without 2FA and logging out of the app on my phone.

KJonline commented 2 years ago

No it has to be the owner account

EpicWimpo commented 2 years ago

Same problem here. Just been setting up from scratch the last couple of days so can’t say when this started.

Problem has been tested using two hive accounts (separately, not both at the same time) and happens on both of them, one of which is very basic and only has heating and hot water while the other has multiple TRVs as well. Both accounts are the owner accounts and both are without 2FA.

The problem starts occurring after almost exactly an hour of adding and configuring the integration. It appears to add an error line per number of entities (so for my ‘basic’ account with 5 entities it adds 5 instances of the error but for my account with the TRVs it adds 37 lines for the 37 entities) and then repeats this every 15 seconds. Due to the large number of failed requests caused by the number of entities on the account with multiple TRVs, this is causing my IP address to be temporarily blocked by Hive (which also stops me from using the Hive app) until the integration is disabled.

2022-04-23 18:10:08.808 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/cognito/refresh-token - HTTP status is - 401 2022-04-23 18:10:08.876 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401 2022-04-23 18:10:08.943 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401 2022-04-23 18:10:08.983 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401 2022-04-23 18:10:09.043 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401 2022-04-23 18:10:09.106 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401

Dopeyr commented 2 years ago

My hunch on this is that Hive has enabled device tracking / remembered devices in AWS Cognito.

There is a new(?) option in the Hive app under "Account Security" called "Trusted Devices". When I login with a browser at https://my.hivehome.com, my browser appears here in the app.

See https://aws.amazon.com/blogs/mobile/tracking-and-remembering-devices-using-amazon-cognito-your-user-pools/

The bit that stands out from the above link is:

The access token only works for one hour, but a new one can be retrieved with the refresh token, as long as the refresh token is valid. With device tracking, these tokens are linked to a single device. If a refresh token is used on any other device, the call fails.

My hunch is as the refresh token API call is not specifying a device_key (AFAIK) it's treated as a new device, and as refresh tokens are linked to devices, the API call fails.

The Hive integration works for 1 hour until the token expires, the refresh token API is called but fails, and integration stops working.

I don't know how to confirm if this is correct, but a separate integration I have (PHP-based, unrelated to HA) started failing too at the refresh API call.

KJonline commented 2 years ago

This would make sense as to why its effecting new users with the HA integration. As existing users will have logged in prior to the change being rolled out by Hive allowing them to keep using the integration under the old mechanism. New logins will get issued the device token where the integration is breaking.

ukgaz1987 commented 2 years ago

Do you think it’ll be able to be fixed or should we start looking at alternatives to Hive? It’s a big part of my wall mounted dashboard so pretty useless in its current state 😞

julianjd-uk commented 2 years ago

I had to do a restart and decided to look at the logs as it got to an hour after the restart. As you can see below, the first error comes from a different URL to the rest of them. That one only seems to happen after an hour and not on subsequent runs.

2022-04-26 20:02:27.958 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/cognito/refresh-token - HTTP status is - 401 2022-04-26 20:02:28.029 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401 2022-04-26 20:02:28.133 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401 2022-04-26 20:02:28.240 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401 2022-04-26 20:02:28.299 | ERROR | apyhiveapi.api.hive_async_api:request:74 - Hive token has expired when calling https://beekeeper.hivehome.com/1.0/nodes/all?products=true&devices=true&actions=true - HTTP status is - 401

KJonline commented 2 years ago

Thanks All,

I have done some digging and found a lot of information around device authentication that Hive have implemented. I believe we should be able mimic their changes and implement device authentication into the integration.

ukgaz1987 commented 2 years ago

Thanks All,

I have done some digging and found a lot of information around device authentication that Hive have implemented. I believe we should be able mimic their changes and implement device authentication into the integration.

That’s brilliant news. Really appreciate the time you put in 🙂

julianjd-uk commented 2 years ago

That's great news @KJonline, thanks for all your hard work.

Mojo-Pinn commented 2 years ago

Thanks All,

I have done some digging and found a lot of information around device authentication that Hive have implemented. I believe we should be able mimic their changes and implement device authentication into the integration.

Excellent news! Thanks

RageInvader commented 2 years ago

I stupidly decided to re-setup my hive integration and now it's broke, I can't seem to disable 2fa on hive website anywhere, I can setup the integration using the 2fa when setting it up but after about an hour it stops working.

KJonline commented 2 years ago

@RageInvader sorry to hear that.

Just a update for everyone I have done the backend changes to the pyhiveapi library and they are complete. I just need to do an update the home assistant library now

ukgaz1987 commented 2 years ago

That’s brilliant thanks. Does it get included in a home assistant update or will it just start working again? Sorry never had a fault like this before so unsure.

KJonline commented 2 years ago

@ukgaz1987 sorry if I didn’t make it clear I haven’t done the home assistant change yet that’s next up. All the backend logic lives in a python library called pyhiveapi and that is complete.

When I do the home assistant work though and it gets approved it will come through a home assistant update. Once updated you will need to login to hive within home assistant again.

ukgaz1987 commented 2 years ago

@ukgaz1987 sorry if I didn’t make it clear I haven’t done the home assistant change yet that’s next up. All the backend logic lives in a python library called pyhiveapi and that is complete.

When I do the home assistant work though and it gets approved it will come through a home assistant update. Once updated you will need to login to hive within home assistant again.

brilliant. Thanks again.

julianjd-uk commented 2 years ago

@KJonline, this is great news, good luck in getting the HA side completed and approved, looking forward to seeing this in an update.

jeffreysmc commented 2 years ago

@ukgaz1987 I have been having this problem since Friday, before I saw this chat I contacted Hive and they said my IP was blocked by the server for constantly sending requests from my home assistant instance. Is a fix now in place? really appreciate your help fixing this.

ukgaz1987 commented 2 years ago

@ukgaz1987 I have been having this problem since Friday, before I saw this chat I contacted Hive and they said my IP was blocked by the server for constantly sending requests from my home assistant instance. Is a fix now in place? really appreciate your help fixing this.

The developer is currently finalising the changes for it to work again then it will be included in a HA update. Shouldn’t be too long.

chrispsoft commented 2 years ago

I've only just found this thread after battling with this issue for about two weeks. I'd concluded it failed for me around the time that Hive updated the Hive App to version 10.48.2 which I assume included some backend changes. Really hoping a fix will become available soon, HomeAssistant really speeded up my overall application.

Tylocco commented 2 years ago

There is some chat about this on the home assistant forum too: https://community.home-assistant.io/t/hive-integration-prevents-access-to-hive-from-any-device-on-my-home-network/413433/3

Two things worked for me:

  1. Initially I just restarted every 20mins ... call the service “Home Assistant Core Integration: Restart” from an automation every 20mins. Drastic and useless for some people I realise...

  2. Then I restored a backup from 4-April which seemed to have an authentication token to access Hive which still works. That is working fine for me still. I appreciate that won't work if you are trying to set up a new Hive integration now but might help some

That second bit seems (to my limited understanding) to validate @Dopeyr 's comment above and @KJonline 's response

chrispsoft commented 2 years ago

Many thanks Tylocco, on more detailed reading of these two comments it does give the full picture and looks all in hand and look forward to the approved update when ready..

kingpotnoodle commented 2 years ago

I'm also having this issue since reinstalling the integration. I've also found that the Hive Android app stops working at the same time. I was wondering if Hive was blocking my IP as it starts working again after an ISP router restart and the app instantly works fine if I switch off wifi and use 4G/5G.

@ukgaz1987 I have been having this problem since Friday, before I saw this chat I contacted Hive and they said my IP was blocked by the server for constantly sending requests from my home assistant instance. Is a fix now in place? really appreciate your help fixing this.

@jeffreysmc Did they say if it was all requests or the failed authentication requests that caused the block? I'm hoping the latter...

@KJonline Thanks for your work on this!

landiuk commented 2 years ago

@kingpotnoodle Once the token refresh fails it retries every 15 seconds. It's the fails every 15 seconds that cause the Hive app and even the myhivehome website to fail to authenticate from the same IP address.

As you said, the moment you change the source IP there's no problems.

I've uninstalled the Hive integration for the moment, pending the updates that @KJonline is kindly working on, as I don't want to reboot core every 20 minutes

Strange thing is, I have a simple HA automation for a Hive plug and that's still operating correctly even though Hive integration is uninstalled and the Hive plug no longer shows as an entity.

kingpotnoodle commented 2 years ago

I've paired my Hive plugs with Zigbee2Mqtt so they report power draw, although there are non-functional sensors for cumulative power usage and temperature that show as well but I just disabled those.

I've currently disabled the integration, after a while the Hive app started to work again so appears the IP block is only temporary and expires, apparently just triggered by the failed authentication attempts and they aren't blocking the integration more generally.

KJonline commented 2 years ago

Just a quick update on this I’m hoping to get something submitted soon to the HA team for review.

ukgaz1987 commented 2 years ago

Just a quick update on this I’m hoping to get something submitted soon to the HA team for review.

Brilliant. Thanks for keeping us updated 🙂

jeffreysmc commented 2 years ago

Brilliant thank you for this.

KJonline commented 2 years ago

Hi all, the authentication fix should be in the next home assistant release as the PR has now been merged in

julianjd-uk commented 2 years ago

Hi all, the authentication fix should be in the next home assistant release as the PR has now been merged in

Great news @KJonline, thank you for all your hard work. Looking forward to the next release, I guess it will be 2022.06 :)

kingpotnoodle commented 2 years ago

Amazing, thanks for your hard work @KJonline!

KJonline commented 2 years ago

Hi all, the authentication fix should be in the next home assistant release as the PR has now been merged in

Great news @KJonline, thank you for all your hard work. Looking forward to the next release, I guess it will be 2022.06 :)

Yes I’m expecting it to be in the 2022.06 release next week

ukgaz1987 commented 2 years ago

Just a quick update on this I’m hoping to get something submitted soon to the HA team for review.

Brilliant. Thanks for getting it sorted 🙂

landiuk commented 2 years ago

Hi all, the authentication fix should be in the next home assistant release as the PR has now been merged in Yes I’m expecting it to be in the 2022.06 release next week

@KJonline Thanks for your effort in this

julianjd-uk commented 2 years ago

I've just upgraded to 2022.6.0 and now have a new error: Config flow could not be loaded: undefined

I don't get any message to provide the auth key or the text from Hive.

From the logs I have:

Logger: aiohttp.server Source: components/hive/config_flow.py:149 First occurred: 5:22:22 PM (1 occurrences) Last logged: 5:22:22 PM

Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request resp = await request_handler(request) File "/usr/local/lib/python3.9/site-packages/aiohttp/web_app.py", line 504, in _handle resp = await handler(request) File "/usr/local/lib/python3.9/site-packages/aiohttp/web_middlewares.py", line 117, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 222, in forwarded_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 79, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 220, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 137, in handle result = await result File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 243, in post return await super().post(request) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 62, in wrapper result = await method(view, request, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 70, in post result = await self._flow_mgr.async_init( File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 205, in async_init flow, result = await task File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 232, in _async_init result = await self._async_handle_step(flow, flow.init_step, data, init_done) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 335, in _async_handle_step result: FlowResult = await getattr(flow, method)(user_input) File "/usr/src/homeassistant/homeassistant/components/hive/config_flow.py", line 145, in async_step_init return await self.async_step_user() File "/usr/src/homeassistant/homeassistant/components/hive/config_flow.py", line 149, in async_step_user self.hive = self.hass.data["hive"][self.config_entry.entry_id] KeyError: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'

Logger: homeassistant.config_entries Source: components/hive/init.py:82 First occurred: 5:21:55 PM (1 occurrences) Last logged: 5:21:55 PM

Error setting up entry xxxxxxxxx@gmail.com for hive Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 339, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/hive/init.py", line 82, in async_setup_entry deviceGroupKey=hive_config["device_data"][0], KeyError: 'device_data'

neilsleightholm-paxton commented 2 years ago

I am getting an error too since upgrading to 2022.6.0 - it was ok before (I was only monitoring this thread as I thought I had an issue but a restart fixed it). I don't see an option to re-authenticate - probably staring me in the face!

Logger: homeassistant.config_entries Source: components/hive/init.py:82 First occurred: 17:28:41 (1 occurrences) Last logged: 17:28:41

Error setting up entry Hive for hive Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 339, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/hive/init.py", line 82, in async_setup_entry deviceGroupKey=hive_config["device_data"][0], KeyError: 'device_data'

ukgaz1987 commented 2 years ago

I'm getting errors too. I have tried with and without 2FA turned on. I have deleted the integration and re-added but with no luck. If I add it with 2FA turned on, when it comes to entering the 2FA code, I just get an unknown error and can't go any further, with 2FA turned off, I get the config flow can't be loaded too.

Log:

Logger: homeassistant.config_entries Source: components/hive/init.py:94 First occurred: 18:21:33 (1 occurrences) Last logged: 18:21:33

Error setting up entry email removed for hive Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 339, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/hive/init.py", line 94, in async_setup_entry devices = await hive.session.startSession(hive_config) File "/usr/local/lib/python3.9/site-packages/apyhiveapi/session.py", line 503, in startSession await self.getDevices("No_ID") File "/usr/local/lib/python3.9/site-packages/apyhiveapi/session.py", line 426, in getDevices await self.hiveRefreshTokens() File "/usr/local/lib/python3.9/site-packages/apyhiveapi/session.py", line 313, in hiveRefreshTokens result = await self.auth.refreshToken( File "/usr/local/lib/python3.9/site-packages/apyhiveapi/api/hive_auth_async.py", line 545, in refreshToken result = await self.loop.run_in_executor( File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/lib/python3.9/site-packages/botocore/client.py", line 391, in _api_call return self._make_api_call(operation_name, kwargs) File "/usr/local/lib/python3.9/site-packages/botocore/client.py", line 691, in _make_api_call request_dict = self._convert_to_request_dict( File "/usr/local/lib/python3.9/site-packages/botocore/client.py", line 739, in _convert_to_request_dict request_dict = self._serializer.serialize_to_request( File "/usr/local/lib/python3.9/site-packages/botocore/validate.py", line 360, in serialize_to_request raise ParamValidationError(report=report.generate_report()) botocore.exceptions.ParamValidationError: Parameter validation failed: Invalid type for parameter AuthParameters, value: ({'REFRESH_TOKEN': 'eyJjdHkiOiJKV1QiLCJlbmMiOiJBMjU2R0NNIiwiYWxnIjoiUlNBLU9BRVAifQ.DnJqtXIDcl6XNtwWMNM1qvh1Anmcru21fvyfRDadtQRkpOwx2WBmeegsDmqxpQWc_0dDqSC-N8IaUW35jMWCiKR_P3Azlcp8V6XICKY98AWKUn1bjx4-POeMFAtM8nCdSJKZQcpNoPlzIrVo7EsbrN_EW2Iu22gxzDrCcV1kIeVl2NcDKYO8qKX4aQhi9B59EqVsGwE-Oy_d3y6oZZPGMjULG228RxyoMLR5nyiMXQCbs7cSPeGaEN7N6mVviefC-BVrVijPOb7KbFQacS_fm3kC-A0xxzVxdEs17WOFQcbKpJmiXgsQC16QUak-69G3IbNTCmulDE5oznCPtXvVQA.O9EhM1ILYCfoaAhA.dehTckND5-Cumi2ovhuAS43NGkBATQX8Au4qB6nq3hz7ONNU0UqBZA7AVLnp98VghP4u7Lhs2XFFDFeRODuP_dEwaNfEPP6-iOPTZbdqgJAuIW4U5Z1YOVDb9YWYAmBvONv_qe1w2w1wfBO6txsxVmjTboaQo5E52dO2srPCM1wNCHfxN_iuIgJ2TFYa6-LB6RBW65_EmMc4P2p5RxxC92Qcxafm4lvM1N7BN-XgSKo1NPfmHkFnIRL2nGil3Hi30FXHnh_Xtbybiiqgc1iPjVooL8JUWop63drgDBJZFWRD7Y905ww5T8_cM9EPUIxBFQOgh72H5-GLupDwOwg4zrvCHQzE08Y2wySkthCkCW3fYvAexYZ7PJVQrz9UZFO7f0_z_krwwHohu83-NlB-w2dhClpbPjVoYoh0r8-B1DvOGA9yH7kIq1ARoO5uckIx07jPL6hhYlirFnmJBH3GuHhyXac-rcsQ2gO2qktVz8Oyav5pohQ8cgGyr-9ZP2hTpm9YKQ_JCaeLna1teMLOZKjDMRb0_8ejXAgPfIjfySoCT4k0nRxQikMh2MFmfLSnFP_53lYXVxMeMgKn65ti3CgvD7qPZddXAtL-aXlIj4BPKW_bSXvqa3th0lGJ_5hD6tKcG0sUi8mEIXzUwbm4LzX8g1g6KmugQr9BM9yaLuNXfWF1VeKwqD9PxjrXShEWJg97i0KqLVcKkqgwpvQHVBhbhc4i_QCqUeF12sTo3CIWTn1WCOXRVX7eIm52rJbG3quTdy5UQ8L5l1a9L8HIL-2WIf4Fe4RGpiDPq3ib0Glb4w142U-WGPqrucSD2XBGlTzC3RkyXAs10CFpI1Vp47EvvoFtxCmQ9wpevPI87XpyRJQucu3nFhD9100NL_FXOoONAgIP9g9kZmZ8WICUB391pHUuwvs0qx-InVOcnZ58sMTvy8GaVI4Ks0AlINF9p5foCfa_8pZfvYlQ4baCbp0fjyR60rxYFCv_LCcNGt9tmrby6MhjIq1z1gq85HmntB68YnzgHga38LbrmycINCvGH71WlQmsOOCUn37x2fL23jZu87tHT2iDiC4b4xPInjbG4IsjvKZwKNqMbtJlYqHJF6gOOcFFfLklkgJyYNcxyQmwgDWPn7QMTS5N1JXR84gPgFeXJBpPfwCjPRZgNIwu2aOKZv7H8_wWqC9V_DRvu--BFNS7ltnCXLp_ektuZV7arO9bmi16Y7F7zUSzmDlKcVjYtBTCWP_wNTuk-n8yOIp6csy1At3cQKLrlX3jjfq55Zc3OWERbwLKHG-3c4-dUaXuACgH-lLB-W1xhJab-6FfnLnCtWO2mv4tk3sOESlZ24FFYk4ATmRsiQ590khfwoOS7nfOOur_EZknAEBFzeUKVTs4_l6NtsiygqZlt9mz9hSFXQZXiz3HyDHD0eMmRnRsJuJ1-JfPPWhnNw.-zIN5BTXD-5FHBmWHt4zhg'},), type: <class 'tuple'>, valid types: <class 'dict'>

KJonline commented 2 years ago

Not sure about the last error @ukgaz1987 but for the other errors. This is a breaking change as mentioned in the pull request. Any existing users will to need to re-authenticate as the device needs to be remembered now

neilsleightholm-paxton commented 2 years ago

@KJonline sorry if this is a silly question but do you re-auth?

ukgaz1987 commented 2 years ago

Not sure about the last error @ukgaz1987 but for the other errors. This is a breaking change as mentioned in the pull request. Any existing users will to need to re-authenticate as the device needs to be remembered now

What is it we need to do then? i'm confused now haha. I'm not even sure what a pull request is lol. I have updated my last comment with the full log too.

KJonline commented 2 years ago

@KJonline sorry if this is a silly question but do you re-auth?

Yes only this once though

KJonline commented 2 years ago

Not sure about the last error @ukgaz1987 but for the other errors. This is a breaking change as mentioned in the pull request. Any existing users will to need to re-authenticate as the device needs to be remembered now

What is it we need to do then? i'm confused now haha. I'm not even sure what a pull request is lol. I have updated my last comment with the full log too.

The cleanest way is to remove the hive integration and re set it back up.

Another thing I need to check is that even though it has been merged in has it been built into the beta.

ukgaz1987 commented 2 years ago

@KJonline I've tried removing the integration and re-added but getting the above errors. 2022.6 is released now properly, I haven't got the beta version.

neilsleightholm-paxton commented 2 years ago

@KJonline thanks (I mis-typed was trying to ask how to re-auth but see you answer that).