Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to complete configuration with an API key #319

Open
fbutler opened this issue Jun 14, 2024 · 4 comments
Open

Unable to complete configuration with an API key #319

fbutler opened this issue Jun 14, 2024 · 4 comments
Labels

Comments

@fbutler
Copy link

fbutler commented Jun 14, 2024

Describe the bug
I am unable to complete configuration.

I enter the IP address of the TV, the name, and the API Key

I am then prompted to select the correct TV which I select and submit.

image

The next screen shows a "SmartThings TV deviceID not found" error

image

I enter the correct Device ID and submit it and the same "SmartThings TV deviceID not found" error screen is displayed

Expected behavior
Complete configuration successfully after entering the required details

Screenshots
Screenshots embedded above

Environment details:
Core 2024.6.2
Supervisor 2024.06.0
Operating System 12.3
Frontend 20240610.0
TV Model: UE43TU8000KXXU

Output of HA logs
This error originated from a custom integration.

Logger: custom_components.samsungtv_smart
Source: custom_components/samsungtv_smart/init.py:431
integration: SamsungTV Smart (documentation, issues)
First occurred: 11:16:44 (3 occurrences)
Last logged: 11:22:10

Connection to SmartThings TV not available.

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:184
First occurred: 11:10:05 (3 occurrences)
Last logged: 11:16:15

Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
Detected that custom integration 'samsungtv_smart' accesses hass.helpers.aiohttp_client. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from aiohttp_client directly at custom_components/samsungtv_smart/config_flow.py, line 200: session = self.hass.helpers.aiohttp_client.async_get_clientsession(), please create a bug report at https://github.com/ollo69/ha-samsungtv-smart/issues

Additional context
My VPN was disabled when attempting configuration

@Kahera
Copy link

Kahera commented Jul 27, 2024

Same issue here. Additional information - this is the only thing that shows up that seems relevant in my logs:

This error originated from a custom integration.

Logger: custom_components.samsungtv_smart
Source: custom_components/samsungtv_smart/__init__.py:443
integration: SamsungTV Smart (documentation, issues)
First occurred: 19:00:03 (3 occurrences)
Last logged: 19:00:57

Connection to SmartThings TV not available.

(I did attempt 3 times this go around).

When entering the deviceID I do get the popup on my screen asking to approve the connection, but it fails even on accept (but after a short wait, as if it's trying to connect). It immediately fails as expected when I try to deny the connection.

@plimo
Copy link

plimo commented Aug 19, 2024

Same issue as described by @Kahera also here.

@D4rk3rd
Copy link

D4rk3rd commented Aug 19, 2024

What worked for me was removing the device from SmartThings entirely and re-adding it. After the device worked perfectly.

Copy link

github-actions bot commented Oct 4, 2024

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants