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

Nrw device wont work #66

Open
shaeser opened this issue Apr 12, 2024 · 14 comments
Open

Nrw device wont work #66

shaeser opened this issue Apr 12, 2024 · 14 comments

Comments

@shaeser
Copy link

shaeser commented Apr 12, 2024

Dear,

I have an ELK-BLEDOM device (pool light rgb) from amazon / https://www.amazon.nl/-/en/dp/B0BX53X749?ref=ppx_yo2ov_dt_b_product_details&th=1

with uuid: 0000FFF0-0000-1000-8000-00805F9B3fBB as an primary service
Custom characteristic: uuid: 0000FFF4 (notify) and 0000FFF3

Its not recognized, and if i add it manual also not.

@shaeser
Copy link
Author

shaeser commented Apr 12, 2024

Screenshot_20240412-081829

At 1meter distance from the coördinator

@dave-code-ruiz
Copy link
Owner

I need debug log to know more about.

You can see readme.md to know how to enable debug mode

@dave-code-ruiz
Copy link
Owner

@shaeser
Copy link
Author

shaeser commented Apr 21, 2024 via email

@shaeser
Copy link
Author

shaeser commented Apr 21, 2024

Screenshot_20240421-191626

@dave-code-ruiz
Copy link
Owner

dave-code-ruiz commented Apr 21, 2024

I've put the code in configuration.yaml but wont get an log message.

Sorry, Without log information is not possible to help you

My integration detect most of suppotted les, it is possible it is not supported

Try to Pushkin disconnect and restart HA

@shaeser
Copy link
Author

shaeser commented Apr 21, 2024

Screenshot_20240421-192023

Is this ok?

@Soundgeek7
Copy link

home-assistant_elkbledom_2024-04-24T12-48-59.434Z.log

I am having same problem here my log hope it helps

@dave-code-ruiz
Copy link
Owner

2024-04-23 20:36:32.078 ERROR (MainThread) [custom_components.elkbledom.elkbledom] Error getting status: ELK-BLEDOM - BE:59:EF:01:2D:61: Failed to connect after 9 attempt(s): No backend with an available connection slot that can reach address BE:59:EF:01:2D:61 was found: The proxy/adapter is out of connection slots or the device is no longer reachable; Add additional proxies

Our led strip have only one slot connection , if another device is connected you will receive this Error, disconnect all device connected

@dave-code-ruiz
Copy link
Owner

Push DISCONNECT and restart HA

@Soundgeek7
Copy link

Where do I push disconnect? What do I disconnect?

@dave-code-ruiz
Copy link
Owner

you say you have same issue, if you use mobile app to connect to strip, you need to disconnect it ,

Only one device can be connected over bluetooth

image

@Soundgeek7
Copy link

I had gone around and turn off Bluetooth on all my devices and still getting the same error.

@rgnyldz
Copy link

rgnyldz commented Jul 27, 2024

I too have the same issue. It was working in the past but now I always get "Unable to connect to Elkbledom" error. Below is my log;

This error originated from a custom integration.

Logger: custom_components.elkbledom.elkbledom
Source: custom_components/elkbledom/elkbledom.py:435
integration: elkbledom (documentation, issues)
First occurred: 21:08:28 (3 occurrences)
Last logged: 21:27:27

Error getting status: ELK-BLEDOB - BE:60:4C:00:1C:50: Failed to connect after 4 attempt(s): TimeoutError

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants