Vaskivskyi / ha-chroma

Control your Chroma-enabled devices from Home Assistant
Apache License 2.0
23 stars 0 forks source link

[Bug] 'Cannot connect to the Chroma SDK', None #70

Open soggypete opened 7 months ago

soggypete commented 7 months ago

The problem

I had this working some time ago but recently it has stopped. Unfortunately I did not notice how or why it stopped working. It has perhaps stopped working after updating the integration or HA version

The integration has started showing Failed Setup, will retry with the above error when hovered over.

I have followed the instructions and uninstalled chroma connect and reinstalled it. I even reinstalled Synapse 3

Your device(s) with a problem

No response

Firmware version

3.9.229.22700

Integration version with the issue

3.0

Method of the integration installation

HACS

What version and type of Home Assistant installation do you use

Core 2024.2.5

Is there anything useful in the logs?

2024-03-08 01:16:07.821 DEBUG (MainThread) [custom_components.chroma.chroma] Connecting to Chroma SDK on 192.x.x.x
2024-03-08 01:16:10.909 DEBUG (MainThread) [custom_components.chroma.chroma] Connecting to Chroma SDK on 192.x.x.x

Additional information

No response

Vaskivskyi commented 6 months ago

Hello. Sorry for the late reply.

Can you connect to the chroma SDK from the device running it (Synapse) using the address https://chromasdk.io:54236/razer/chromasdk (or its own IP address instead of chromasdk.io, but be sure to keep the correct port and https)

It should show chroma versions:

{
    "core": "3.34.02",
    "device": "3.34.02",
    "version": "3.34.02"
}

But it might be that your Synapse / Chroma instance has troubles with the SSL - not only a certificate from an untrusted issuer (which is not a problem), but rather a protocol error. Your browser will tell you that with a ERR_SSL_PROTOCOL_ERROR message in this case.

Let me know what you find

Tomanic-glitch commented 6 months ago

I do have the same issue and I get the this error when trying both with https://chromasdk.io:54236/razer/chromasdk or the IP address - NET::ERR_CERT_INVALID

On the other hand, when trying with https://localhost:54235/razer/chromasdk the Chroma versions show up.

ChromaSDK io Failed_setup_will_retry IP_address localhost_54235

comi8903 commented 6 months ago

I have the exact same circumstances as @Tomanic-glitch. My Chroma was working before I updated Home Assistant. I was about a year behind on updates and it worked flawlessly. After the update to 2024.3.1, it started exhibiting this behavior.

joebar38 commented 6 months ago

Same problem here, problem comes from synapse or integration? image image

n8acl commented 5 months ago

Same issue. I am able to connect to the SDK using http://localhost:54235/razer/chromasdk and get the following for the SDK version. I am running the most recent version of Synapse on the machine.

One note, I did try to access it from a separate machine using the IP of my gaming machine and it will not allow me to connect. I have all the Windows firewalls turned off on the gaming machine.

image

TheAlphaLaw commented 4 months ago

Seeing the same issue, assuming this is no longer supported.

AG1010101010 commented 3 months ago

Hey, I’m running into the same issue too. I’m wondering if it is that I am using the New Synapse Beta and that it might not work with it. Is there anyone that can confirm that it is unavailable or provide me with a fix?

jey-music commented 1 month ago

Also got the same issue. Still no fix/workaround?