Unable to turn on the mi stick

[Riyaz-creative]

Thank you for writing this script. Unfortunately I am unable to make it work. When the Mi stick is in on status I get the pairing request after turning on the switch "switch.mibox_socket_switch", however, nothing happens when the device is in off status. Below is my setup

Raspberry Pi 4
Home assistant OS
Onboard Bluetooth device
Mi Stick 4K

Log details

Logger: custom_components.mibox_socket.switch
Source: custom_components/mibox_socket/switch.py:78
integration: mibox_socket (documentation)
First occurred: 1:21:10 pm (5 occurrences)
Last logged: 3:25:16 pm

Error pairing with Bluetooth device: Timeout exceeded. <pexpect.pty_spawn.spawn object at 0xabb8f1e0> command: /usr/bin/bluetoothctl args: ['/usr/bin/bluetoothctl'] buffer (last 100 chars): b'equest confirmation\r\n\x1b[0;94m[MiTV-AYFR0]\x1b[0m# \r\x1b[1;39m[agent] Confirm passkey 371239 (yes/no): \x1b[0m\r' before (last 100 chars): b'equest confirmation\r\n\x1b[0;94m[MiTV-AYFR0]\x1b[0m# \r\x1b[1;39m[agent] Confirm passkey 371239 (yes/no): \x1b[0m\r' after: <class 'pexpect.exceptions.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 145 child_fd: 16 closed: False timeout: 10 delimiter: <class 'pexpect.exceptions.EOF'> logfile: None logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 searcher: searcher_re: 0: re.compile(b'bluetoothctl>')

Please help. Thank you in advance

[frlequ]

Try documentation:

Before using the Mibox Socket HA integration, ensure that your RPI is not already paired with the Mibox. If it is, unpair it on the Mibox device itself.

[Riyaz-creative]

Thank you for your response. Yes, I made sure it is not paired as per the documentation. Also, when I trigger the switch when the mi stick is on, I get the pairing message. Which is expected as per your documentation. Not sure why it is not able to turn on the device when it is in the deep sleep mode.

[Grifindorec]

have the same problem.
But i don't see bluetooth device in mi stick bluetooth menu for delete it, even i accept pair.

[Boldfor]

+1

To be fair, I'm using a Raspberry Pi 5 and a Mi Laser Projector instead, but Raspi 4 and 5 are similar, and the Mi Laser Projector probably runs the same android TV, and even emulating the remote (see here works identical.

But even though bluetoothctl scan on shows my projector (if it's switched on, so the physical connection should be there), if I then use bluetoothctl pair XX:XX:XX:XX:XX:XX nothing happens (independent from the projector being switched on or off).

When it's off, it should switch on (which it doesn't). And when it's on, a pairing request should show up (which is also not the case).

Anyone having an idea?

[I-G-1-1]

Anyone having an idea?

I don't know if it's the case, but to work mibox_socket needs that the bluetooth of your raspberry pi and your Mi Laser Projector are NOT paired.

[Boldfor]

Thanks for your comment. Yes, Inread about this online too. Both devices have never „seen“ each other before on BT.

What‘s a bit of a mystery is why some buttons appear to have such a special nature that they cannot be emulated. It‘s not only the power button on the remote that would switch on the projector, it’s also the Netflix button that would do the job. But also that one cannot be emulated? It’s really weird, but I do not know the BT protocol enough…

[I-G-1-1]

Do you read this? It seems that for Rapsberry pi 4 was suggested by frlequ that the bluetooth stack has to be not in use by any other components/integration.

I'm using a Raspberry pi 3 so I can't test it.

[I-G-1-1]

@Boldfor you could check if this bluetooth fix for raspberry pi 4 on old RaspberryPiOS could help.

[frlequ]

To test what mibox_socket actually does:

Go to Advanced SSH & Web Terminal and write:

1. bluetoothctl
2. scan on
3. see if your device shows up
4. pair XX:XX:XX:XX:XX:XX

Don't do anything afterwards — The Mibox should start. Again: DO NOT confirm pairing on Mibox or TV.
As you attempt to pair (without completing the process), the Mibox should start. If it doesn't, then your stick or TV may use a different power-on logic.

[Boldfor]

Thanks @I-G-1-1 & @frlequ !

@frlequ , I already did what you propose (test what mibox-socket does by manually executing the pair XX:XX:XX:XX:XX:XX). To make sure I'm not looking at some dumb bluetooth-problem of my raspberry 5, I executed it with the MAC-address of my iPhone, which perfectly resulted in the pairing-dialogue popping up on the iPhone. So the Raspi and the BT compoment seems to be doing what it should be doing. It's just that when I do the same with the BT-Mac-Address of the Mi projector, I get the response Device XX:XX:XX:XX:XX:XX not available (idependently of the projector being off or already on or even in pairing mode), and obviously the projector does not switch on.

Does that makese sense to you?

@I-G-1-1, I so far refrained from the fix which you proposed, mainly because, assuming that the fix is needed, I would not be able to trigger a pairing dialogue on my iPhone, right?

To me it seems as if the projector does not allow to be paired (maybe different version that yours? Which projector do you have?). It does pair in "Bluetooth-Speaker-Mode" though, so the physical BT connection seems to work (and also the physical remote does work)...