If you want help you should post more details : logs from the remote would be helpful.
And try to the procedure with the websocket client to help diagnose
This is not a common issue, probably related to the network configuration or a misconfiguration
@albator Thanks for the Chrome Extension suggestion. This particular one was no longer available, but I tired a few of the others that are similar. However, Iām not really sure Iām filling in the details correctly and therefore not sure of the output. See screen shot below, and please make suggestions. For the URL, I tried ws:// and wss:// and neither made a difference.
I tried to attach the remote logs as a .txt file and this format is not accepted, only picture formats.
is your homeassistant in local network with DNS āhomeassistantā? Try to use IP instead. Also, not sure if this is true anymore but i believe you cannot use wss, you need to use ws.
This is correct except the first argument : should be ws instead of wss
Then click on Open and you should get a status set to āOpenedā and an auth message displayed below
@TeroS and @albator , Thank you both for taking the time to respond. Looks like using the IP address and ws worked for an āOpenedā response. Iām unsure what to do with this now. I started a new HA Integration on the Remote, using the IP address in the URL, with new Long Lived Token and still I get āservice unavailableā. What about the authorization message, āauth_requiredāā¦? This is the same message as @albator posted in his example.
I added the Remote log to gitbub page (shows as a open bug): [bug] Unable to connect with Home Assistant Ā· Issue #243 Ā· unfoldedcircle/feature-and-bug-tracker Ā· GitHub.
URL needs to be ws://192.168.254.55:8123, remove the .local from there.
This is not correct, remove the .local in your IP.
This is strange that the standard URL doesnāt work : ws://homeassistant.local:8123/api/websocket
For an IP it will be ws://w.x.y.z:8123/api/websocket
This URL can be set and changed from HA itself : HA settings / network. You will find 2 fields, one for internet, one for home network. They should be set to automatic. Also the hostname (top field) should be set to āhomeassistantā.
Also from the logs it seems that the new URL (with IP) is not taken into account. Try to reboot the remote also
@TeroS and @albator Thanks again for your suggestions. So it seems to have worked to use the IP address and Reboot the remote, and now the HA Integration is āActiveā., Awesome and thank you!!
I can see 9 entities, but not all the Integrations that are visible in HA are visible in the Remote. Should the Entities exposed by the integration be visible, what am I missing here?
I am not sure, but I assume the entities would have to be setup in home assistant before they can be exposed to the remote. Do you use home assistant for anything else?
It looks like the only available entities are the default entities like"Sun next rising" in the basic home assistant install. I would suggest you conifigure an entity in home assistant then reload the remote to see if its available.
It may be a UI refresh issue : from your first capture, try to type in some entity name in the upper right search field to trigger a UI refresh of available entities.
Otherwise you can reboot the remote
@LewLRX and @albator Thank you both. Yes, I was able to configure the Lutron Integration and all of my lights and their locations showed up as entities. Iām just getting started with HA, so the Lutron integration, the Anthem MRX1140 are the first two HA integrations Iām working with and starting to learn how to configure in UCR2.
Thanks again to all those who so gracefully helped me troubleshoot and learned how to resolve this issue. Itās a perfect example of how the community helps. Much Appreciated. Hopefully we left enough cookies crumbs to help the next user that finds themselves with this issue. Until the next issue.
