-
Notifications
You must be signed in to change notification settings - Fork 16
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
Comments
I need debug log to know more about. You can see readme.md to know how to enable debug mode |
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 |
home-assistant_elkbledom_2024-04-24T12-48-59.434Z.log I am having same problem here my log hope it helps |
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 |
Push DISCONNECT and restart HA |
Where do I push disconnect? What do I disconnect? |
I had gone around and turn off Bluetooth on all my devices and still getting the same error. |
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;
|
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.
The text was updated successfully, but these errors were encountered: