#Adding devices to Xiaomi/Android 14's "quick access menu" for smart home devices

1 messages ยท Page 1 of 1 (latest)

thin rain
#

Hey together,
I am running Android 14 on my phone, which also comes with a feature where you can directly access your smarthome apps in the settings menu (when swiping downwards).
When I want to use HomeAssistant there, it tells me to add new devices to this overview. When clicking on "add" it tells me that the homeassistant app is not providing any devices which can be added and it redirects me into the ha app directly.
I was not able to find WHERE I add such devices in the ha app, to be accessible via the quick access menu. Is this feature even usable with homeassistant?
What I have found: https://companion.home-assistant.io/docs/integrations/android-device-controls but I am not sure if the "Android device controls" is exactly applying in my case (I also tried the step provided in the article - didn't work)

I assume this quick access menu is a standard android feature, not just Xiaomi. Has anyone got this thing functioning?

The Android Android app will automatically integrate with the smart home device controls feature on devices running Android 11 or newer that support it. All that is required is that you are able to login to the app and use it remotely.

radiant fossil
#

can you try to check the app logs after trying to add a control? Settings > companion app > troubleshooting

#

maybe there is a failure

thin rain
#

@radiant fossil it doesnt even list any devices to add. As you can see on my last screenshot, it just refers to the HA app. Or should all the devices already be listed by default? I wasnt sure if I have to add them beforehand in HA, like with the widgets

radiant fossil
#

well only some devices will be listed like lights and such, but sensors will not show up. Only controlled devices are there

thin rain
#

Yea I dont see any, even tho I have lights and such configured. I'll check the log later and will give an update

thin rain
#

@radiant fossil
Okay, I now looked into the logs. Only thing that seems to be relevant in this case it the following exception.
Also HA constantly tries to connect to an IP ending in 200 with the port 8123, which is obviously not reachable. But idk why it tries to connect there. HA is running on a different IP

radiant fossil
thin rain
#

@radiant fossil the IP it constantly tries to connect to is strange. That IP doesnt exist in my network. Also its on port 8123, which would be the standard port of Homeassistant in docker.

This would be the while log. Its a bit hard to find out where exactly the moment is I tried to add the control

radiant fossil
thin rain
#

Ah yea, it gets the IP from another server. But I normally dont connect to that one, strange

thin rain
radiant fossil
#

01-16 23:03:46.743 8043 8277 E WebSocketRepository: java.net.SocketTimeoutException: failed to connect to /192.168.178.200 (port 8123) from /192.168.178.207 (port 47218) after 10000ms

#

some tme out error

#

01-16 23:03:47.418 8043 8587 E SensorReceiver: io.homeassistant.companion.android.common.data.integration.IntegrationException: java.net.ConnectException: Failed to connect to /192.168.178.200:8123

thin rain
#

yea but thats with the IP ending in .200, this IP is used on another HA Server instance

radiant fossil
#

did you confirm the URL?

#

you probably entered that URL for the app

#

we use whatever is in there from that it depends on your network setup where it ends up with proxy/dns etc...

thin rain
#

Yes, I have two server instances configured in my HA app, one is the main, where I am currently connected to, and one is another instance where I am not constantly connected to, only when I am in the right network. So the one ending is 200 is the one where I dont have a connection to right now, which isnt a problem, but rather normal, as I am not in the network of this HA instance right now

radiant fossil
#

ok yes can see one server succeeds 01-16 23:04:05.650 8043 8587 W SensorReceiver: Exception while updating sensors: IntegrationException: java.net.ConnectException 01-16 23:04:05.651 8043 8134 I SensorReceiver: Sensor updates and sync completed

#

try to activate theh server you are curety expcting to work from the same place you check the URL then try again

thin rain
#

Yes, the URL is set correctly. The HA app itself is working since many many months without any problem. Just that one feature is not working for me

radiant fossil
#

as of now we have get nothng back from the server 01-16 23:04:40.673 8043 8043 D HaConProService: publisherFor []

thin rain
#

how do I know which server that is?

radiant fossil
#

so what happens when you try to create an widget do you see the list of entities?

radiant fossil
thin rain
#

normal android widgets are workig perfectly fine! Also the ones which can be controlled in the "drawer menu" (The one where you can also active wifi, hotspot, flashlight and so on)

radiant fossil
#

so you can see your entities there?

#

hmm

thin rain
#

Yep

radiant fossil
#

i do see a bunch fo strange errors that may be from xiaomis implementation

#

01-16 23:03:56.794 8043 8134 W ControlsProviderService: onNext(): control is not stateless. Use the Control.StatelessBuilder() to build the control.

thin rain
#

yep, I wasnt sure if the ControlsProviderService is the one we are looking for right here

#

but after a quick google search it seems like it, yea

radiant fossil
#

ok lets try somethng else

#

from the app settings > companion app > manage device controls and set to use a dashboard

#

and enter a dashboard URL so we can see if that works

#

the error up above also shows up on my pixel so safe to ignore it seems

thin rain
#

Just for reference: I tried it on a different phone (another brand) and there it worked perfectly fine, without any extra configuration. Just logged into my HA instace in the app and instantly had all the entities available to be controlled from outside the app

radiant fossil
#

you can try to remove teh second server and try again?

thin rain
thin rain
radiant fossil
thin rain
#

ALRIGHTY

#

it worked yea

radiant fossil
#

worked?

thin rain
#

but kinda strange no?

radiant fossil
#

ok feel free to create a bug on github with those logs from above (the longer ones removing location/URL) and explain the steps and link to here so we can look into it

#

we shoudl at least show some results but maybe if teh timeout is too long device controls may not play well

#

not 100% sure teh cause there

#

if you ad teh second server it shoudl contnue to work i hope ๐Ÿ™‚

thin rain
thin rain
#

But thanks for helping me out!!!

radiant fossil
#

happy to help ๐Ÿ™‚