"audio device connected" block doesn't see the smartwatch

63 views
Skip to first unread message

Ahmet K

unread,
Mar 4, 2026, 9:04:24 AM (9 days ago) Mar 4
to Automate for Android
Hi,
When the smartwatch is connected to the device via Bluetooth,
I tried all the options ("BT-A2DP", "BT-SCO", and others) in the "Device type" field. But the  'yes' path doesn't work. Smartwatchs: redmi, huawei.
Note: BT speakers works.

Henrik "The Developer" Lindqvist

unread,
Mar 4, 2026, 9:42:33 AM (9 days ago) Mar 4
to Automate for Android
The system decides if, and how, an audio device is classified, there's nothing an app can do about it.
Try leaving all input arguments empty then instead log all outputs to see what the what the device properties are.

Ahmet K

unread,
Mar 4, 2026, 10:27:19 AM (9 days ago) Mar 4
to Automate









4 Mar 2026 Çar 17:42 tarihinde Henrik "The Developer" Lindqvist <henrik.l...@gmail.com> şunu yazdı:
--
You received this message because you are subscribed to the Google Groups "Automate for Android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to automate-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/automate-user/10fb3929-1f04-4b6b-b142-957dac23123bn%40googlegroups.com.

Ahmet K

unread,
Mar 4, 2026, 10:41:04 AM (9 days ago) Mar 4
to Automate
It's as if it's displaying the phone's values ​​instead of the connected device's values. Because the values ​​are the same whether the smartwatch is connected or not.

4 Mar 2026 Çar 18:26 tarihinde Ahmet K <ahka...@gmail.com> şunu yazdı:

Ahmet K

unread,
Mar 4, 2026, 11:11:19 AM (9 days ago) Mar 4
to Automate




4 Mar 2026 Çar 18:40 tarihinde Ahmet K <ahka...@gmail.com> şunu yazdı:

Henrik "The Developer" Lindqvist

unread,
Mar 4, 2026, 6:10:15 PM (8 days ago) Mar 4
to Automate for Android
That just logged the built-in speakers. Try using Proceed=When changed then connect/disconnect the smartwatch..

Henrik "The Developer" Lindqvist

unread,
Mar 4, 2026, 6:13:27 PM (8 days ago) Mar 4
to Automate for Android
An device type 1796 is "Wearable: Wrist watch".

Ahmet K

unread,
Mar 4, 2026, 11:20:28 PM (8 days ago) Mar 4
to Automate
That's very interesting. The "No" path doesn't work either. In other words, when the smartwatch is connected/disconnected, the block doesn't react at all.
But the Bluetooth speaker is working.






5 Mar 2026 Per 02:10 tarihinde Henrik "The Developer" Lindqvist <henrik.l...@gmail.com> şunu yazdı:

Henrik "The Developer" Lindqvist

unread,
Mar 5, 2026, 9:00:46 AM (8 days ago) Mar 5
to Automate for Android
As for the Audio device connected block, you need to specify some criteria, e.g. device type = 8, since there's always a audio device connected, the built-in speakers.

Ahmet K

unread,
Mar 5, 2026, 11:57:01 AM (7 days ago) Mar 5
to Automate
Ok,  but, the problem is: When the smartwatch is connected/disconnected, the block doesn't respond at all. (devtype= a2dp, sco etc)

5 Mar 2026 Per 17:01 tarihinde Henrik "The Developer" Lindqvist <henrik.l...@gmail.com> şunu yazdı:

Henrik "The Developer" Lindqvist

unread,
Mar 5, 2026, 1:32:48 PM (7 days ago) Mar 5
to Automate for Android
That's odd since your screenshot say otherwise.

Ahmet K

unread,
Mar 5, 2026, 1:38:09 PM (7 days ago) Mar 5
to Automate
The screenshot is for the Bluetooth speaker. It's to show that the block is working normally for the Bluetooth speaker.

5 Mar 2026 Per 21:32 tarihinde Henrik "The Developer" Lindqvist <henrik.l...@gmail.com> şunu yazdı:

Henrik "The Developer" Lindqvist

unread,
Mar 5, 2026, 4:45:14 PM (7 days ago) Mar 5
to Automate for Android
This show the Audio device connected block working with device type = 8, but i don't know if that your smartwatch. If it doesn't report when you connect or disconnect your smartwatch then the system doesn't register/access it is as such so you have to find another way to detect it, e.g. using the Bluetooth device connected block.

On Thursday, March 5, 2026 at 5:20:28 AM UTC+1 ahka...@gmail.com wrote:

Ahmet K

unread,
Mar 6, 2026, 6:18:18 AM (7 days ago) Mar 6
to Automate
1) This show the Audio device connected block working with device type = 8, but i don't know if that your smartwatch.

Device type=8 for BT speaker, not smartwatch.

2) If it doesn't report when you connect or disconnect your smartwatch then the system doesn't register/access it is as such.

It's clear that this block doesn't work for smartwatches. Therefore, in my opinion, a new devtype needs to be defined for smartwatches.

3) So you have to find another way to detect it, e.g. using the Bluetooth device connected block.

Yes, I already tried that block. The result was negative. On the other hand, this block doesn't work for Bluetooth speakers either. Therefore, I opted for the "Audio device connected" block, and it works flawlessly for Bluetooth speakers. However, it doesn't work for smartwatches. Again, "Audio device connected" block doesn't work for smartwatches. Therefore, a new devtype needs to be defined for smartwatches. Additionally, issues with the "BT device connected" block need to be resolved.





6 Mar 2026 Cum 00:45 tarihinde Henrik "The Developer" Lindqvist <henrik.l...@gmail.com> şunu yazdı:

Henrik "The Developer" Lindqvist

unread,
Mar 6, 2026, 1:40:36 PM (6 days ago) Mar 6
to Automate for Android
2. If you tried with the Device type input argument empty and the block didn't work then it's because the system doesn't register it as an audio device, there's nothing that an app can do about that.
3. Like with #2, if the system doesn't report the device connecting/disconnecting then there's nothing an app can do about it.

Ahmet K

unread,
Mar 6, 2026, 1:44:15 PM (6 days ago) Mar 6
to Automate
Thanks.

6 Mar 2026 Cum 21:40 tarihinde Henrik "The Developer" Lindqvist <henrik.l...@gmail.com> şunu yazdı:

Ahmet K

unread,
Mar 6, 2026, 3:01:27 PM (6 days ago) Mar 6
to Automate
There's one last thing that's confusing me: "Audio device connected" block works on the Bluetooth speaker. Therefore there's no problem on the system side. But "BT device connected" block doesn't work on the Bluetooth speaker. Doesn't this result indicate that this block is faulty?

6 Mar 2026 Cum 21:40 tarihinde Henrik "The Developer" Lindqvist <henrik.l...@gmail.com> şunu yazdı:

Henrik "The Developer" Lindqvist

unread,
Mar 6, 2026, 3:27:31 PM (6 days ago) Mar 6
to Automate for Android
Not faulty. As said it depends on how the system register/connects to the device, and reports it to apps. It registers the BT speaker as speakers, but not the smartwatch.

Ahmet K

unread,
Mar 6, 2026, 4:26:46 PM (6 days ago) Mar 6
to Automate
No, I didn't mention smartwatch in the last question. What I meant was: Why does one block recognize the Bluetooth speaker while the other doesn't? Aren't both blocks looking at the same system log?

6 Mar 2026 Cum 23:27 tarihinde Henrik "The Developer" Lindqvist <henrik.l...@gmail.com> şunu yazdı:

Henrik "The Developer" Lindqvist

unread,
Mar 6, 2026, 4:41:12 PM (6 days ago) Mar 6
to Automate for Android
The Audio device connected block only "looks" for devices connected as an audio source or sink, e.g. a mic or speaker.
The Bluetooth device connected block only "looks" for devices communicating with the phone over Bluetooth, but they can be of any type, e.g. a headset, joystick, heart rate monitor, etc..

Ahmet K

unread,
Mar 7, 2026, 12:26:04 AM (6 days ago) Mar 7
to Automate
Thank you for the explanation. Have a nice day.

7 Mar 2026 Cmt 00:41 tarihinde Henrik "The Developer" Lindqvist <henrik.l...@gmail.com> şunu yazdı:
Reply all
Reply to author
Forward
0 new messages