I’m sure you’re right but when I tried just using the HA integration in R2 the furthest I got was a listing of the entities during the steps to use the integration and then selecting all of them only to go to the next step and the Available Entities were empty - VERY frustrating! I did see using the UC repository inside of HA would expose some info on R2 within HA but as soon as I did the steps for the UC repository in HA everything else worked.
I really wish there was a little more documentation which would have made the overall process easier.
But, at least now I have the R2 doing all the stuff I wanted it to so whatever steps I had to take were worth it!.
no, don’t think that is possible yet. When I’m using the HA remote control I keep the R2 in the dock… than it’s no problem.
My use case for this is that my R2 is on a gallery and I’m using HA when I’m on another floor… It also increases acceptance with Wife and kids I have to say
With a lot of help from this forum I now have R2 controlling my dimmers and ceiling fans via HA. I have Wi Fi enabled thermostats which were showing up in HA so I decided to see what I can do with them via R2. I was able to configure one of them in HA and indeed they show up in R2. However the only thing I can do in R2 is to turn it on or off or change the heat/cool mode while in HA I can control the temp setting with a graphical interface.
Is there anyway to set up something in R2 that can control the temperature with some kind of graphical interface similar to what’s in HA?
To control/use the remote from Home Assistant, I use the rest API of the remote which is halfway documented under <IP-address-of-remote>/doc/core-rest/.
I then created the commands I need as rest_command in YAML.
I’m having the same problem in that HA shows “Connecting” versus “Active” for the other integrations. Was this resolved? Any other suggestions from the community, I have restarted the remote?
Harvey is referring to the Home assistant component that let’s access to the remote and control it from Home assistant. By the way this is not true : you don’t need to reconfigure the pin code at each restart of HA, because when you configure the component, it will register a token to the remote and the pin code is no longer necessary then.
The other problem concerns the home assistant integration that let’s control HA devices (lights, media players…) from your remote. I guess that you didn’t configure the integration properly. You need to fill in the home assistant URL and port (usually homeassistant.local:8123) and a long life token to be created from Home assistant.
To create this token : click on your profile avatar/icon from HA, go to security tab, and at the bottom of the page create a long life token. Copy / paste it to the setup page on the remote.
If you are stuck, delete the integration and reconfigure it from start
@albator Thanks for your reply concerning the other problem concerning HA integration control of devices via the UCR. I followed the instruction exactly to add a Life Long Token and get an error ’ Service Unavailable’ followed by the ‘Connecting’ instead of ‘Active’ with other integrations (Apple, Sony TV). Seems that HA and the remote are not connecting. The URL is the default. Thoughts on the error and the problem in the configuration? I have deleted the integrations multiple times and started from the beginning with the same result.
@Trial_Master Thanks you for your response. Yes, I have tried to deleting the Long Lived Token several times and populating with a new one, without improvement. I have generated about 5 Long Lived Tokens.
@albator Thank you for your response. Yes, both the Raspberry PI 5 (RPI5) with Home Assistant installed, Remote, and Dock are on the same subnet, I only have one subnet for the moment. Additional ideas are welcomed.
RPI5 IP Address (Wired) - 192.168.254.55
UCR2 IP Address - IP Address 192.168.254.41
UC Dock IP Address (Wired) - 192.168.254.31
