Cant connect to Home Assistant

grahamk · September 12, 2023, 10:37pm

Hope someone can help with a problem I am having.

I am trying to add the Home Assistant intergration but it causes an Error.
I receive the following " Internal server error, please try later"

All I am doing is -

creating a Long Lived Access Token on Home Assistant
copy and paste the key into the box within the configurator
click next
Receive a pop-up stating “Internal server error, please try later”

Could someone please explain what I may be doing wrong?

Is it a Remote problem or Home Assistant problem?
Would there be something in the settings of Home Assistant that would be blocking the WebSocket API URL - ws://homeassistant.local:8123/api/websocket?

Any help would be much appreciated.

Freshhat · September 13, 2023, 7:30am

I had the same issue at the beginning, normally i would use my external DNS for that topic, but this also doesn’t solved it.

Therefore i have now switch to the static IP directly ws://<>:8123/api/websocket

grahamk · September 13, 2023, 7:36am

Thanks Freshhat

I will give that a try tonight once I have the remote to hand.

grahamk · September 14, 2023, 8:42am

Still no joy connecting to the Home Assistant intergration.
I am still getting the error message " Internal server error, please try later"

These are the URL’s I have tried and none seem to connect to my Home Assistant.

ws://homeassistant.local:8123/api/websocket
ws://:8123/api/websocket

wss://homeassistant.local:8123/api/websocket
wss://:8123/api/websocket

http://homeassistant.local:8123/api/websocket
http://:8123/api/websocket

https://homeassistant.local:8123/api/websocket
https://:8123/api/websocket

If i put any of these into a web browser the only ones that bring back a message on screen are the https:// addresses.
So I assume the “homeassistant.local” is working OK but there is something blocking the connection to my Home Assistant.

I remember a while back I had a problem connecting an old tablet to my Home Assistant using the Local address.

At that time I installed Nginx Proxy Manager add-on to try and connect the tablet and had a little bit of success but it still didn’t work properly connecting.
Unfortunately I don’t know much about networking, but would this be the problem?
or could it be a problem with the port forwarding on my router?
I tried turning off Nginx Proxy Manager add-on within Home Assistant but that didnt seem to help.

As I say, if I use https:// in the browser it does seem to have some success throwing up a message Re: websocket (sorry, didn’t make a note of the exact wording)

I was pulling my hair out yesterday trying every combination I could think of to try and install the Home Assistant intergration.

I have now exhausted the extent of my knowledge, which isn’t much!, and would appreciate any help.

I’m I going to have to completely uninstall Home Assistant and start from scratch? I hope not!!

Freshhat · September 14, 2023, 8:55am

For sure the ws:// will not give you any result in the browser as it’s used for the WebSocket Connection

Did you tried it also with the local IP Address where your HomeAssistant installation is running? Something like

ws://192.168.172.5:8123/api/websocket

grahamk · September 14, 2023, 9:37am

Yes, sorry Freshhat.

All those on the list below the homeassistant.local are supposed to show that I used the IP.

ws://192.168.0.xxx:8123/api/websocket
wss://192.168.0.xxx:8123/api/websocket
http://192.168.0.xxx:8123/api/websocket
https://192.168.0.xxx:8123/api/websocket

All to no avail.

If I put https://192.168.0.xxx:8123/api/websocket or https://homeassistant.local:8123/api/websocket into a browser I do get a message appear that mentions websocket (sorry, didn’t make a note of message) but at least it returns something.

All other URL’s I put into a browser return a 404 not connected.

I can get to the log in page for HA if I type…

https://192.168.0.xxx:8123 or https://homeassistant.local:8123

So I know https should work even though ws:// doesn’t seem too.

Just seems to be the /api/websocket part that has problems connecting to HA

Unfortunately I don’t know that much about these things and hope that you understand what I am trying to express.

Freshhat · September 14, 2023, 9:51am

You could first of all try to check if it’s an issue with the Remote Integration or if it’s a general Homeassistant issue.

There are Browser Extensions available for Chrome & Firefox in order to test a Websocket connection.

Chrome: WebSocket Test Client - Chrome Web Store
Firefox: Simple WebSocket Client – Get this Extension for 🦊 Firefox (en-US)

And then you can use ws://<>:8123/api/websocket in order to get something like this:

grahamk · September 14, 2023, 9:59am

Thanks Freshhat

I will give that a try tonight and see if that works.
I will let you know how I get on.

grahamk · September 14, 2023, 5:45pm

Used the websocket test client and seems to be open but still unable to connect

Tried so many ways to get into HA I am at the end of my tether!

Don’t know if its the Remote, Network or Home Assistant set up that seems to be blocking it?

Freshhat · September 14, 2023, 6:00pm

I guess without providing logs your final question cannot be answered. Maybe worth to open a new bug report here Issues · unfoldedcircle/bug-reports · GitHub

Sorry but i also don‘t have more ideas on that

pkscout · September 14, 2023, 8:56pm

But you did connect, at least according to that screenshot. You send it a web socket request, and HA properly responded that you need to authenticate to use that function. It’s an important distinction. The troubleshooting for “I can’t connect” is different than the troubleshooting for “I can’t authenticate.”

I don’t have a remote yet, so I can’t tell you why you can’t authenticate because I have no idea how the remote sets up the authentication. But that’s the problem you’re trying to solve.