BT CSR 8150 A10 problem need help

[EldarF1]

I bought a BT CSR 8150 A10 USB ID is identical

1.zadig successfully installed the driver

2.when starting setup.bat I get the following problem

TypeError: Cannot read property 'on' of undefined at BluetoothHciSocket.start (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:191:29) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:101:18) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes TypeError: Cannot read property 'on' of undefined at BluetoothHciSocket.start (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:191:29) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:101:18) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47

where am i wrong? @mplutka thank you for the support

[mplutka]

Are you using the pre built version with the tm-bt-led.exe in the same folder?

[mplutka]

Are you using the stick at a hub? Try it directly in a usb port of your pc

[EldarF1]

I downloaded this and put it in an empty folder.

Download current version here and extract the files into an empty folder.

is there anything else i need besides 3.1.7 version?

The USB BT is plugged directly into the PC behind the computer

[mplutka]

https://github.com/mplutka/tm-bt-led/issues/8 seems to be the same issue. Chipset is of correct type but still slightly different and therefore not 100% compatible

[EldarF1]

What safe alternatives do I have? Tp link ub 400 will not now this CSR 4.0 won't either..

How can I check if BT is compatible before buying?

[EldarF1]

"aliexpress" maybe you have a link to buy one that work

does the Asus BT-400 have multiple models like the tp link 400 or just one..

[mplutka]

I'm sorry but I can't help you with that. As I stated in the readme clearly, I can't provide any support. All I can tell you is that people got good results with a TP-Link UB400 (not the Nano!)

Maybe going through the issues here, also the closed ones, will give you a hint what others where using

[mplutka]

Realtek Bluetooth 8761B (USB VID: 0x0bda, USB PID: 0x8771, e.g. MPOW Bluetooth 5.0 stick

This was one working model too. Don’t know the exact model name for this

[EldarF1]

does every Asus BT-400 model fit? or is it the same thing as with TP link ub400 has more models

[mplutka]

Do you still have the tp link model at your hand? Could you write me the usb vid and pid? I will try something

[mplutka]

It seems that the ub400 nano uses the same chipset as the mpow but with an different id. I could just try to add it to the list of compatible devices and you try it out

[mplutka]

https://github.com/mplutka/node-bluetooth-hci-socket?tab=readme-ov-file#force-adapter-usb-vid-and-pid this is something you could try right now Open a command prompt cmd.exe Set those two environment variables and check that they got applied correctly Open setup.bat from that same command prompt

[EldarF1]

TP-link ub400 zadig shows USB ID 2357 0604

I install the Zadiga driver properly

[mplutka]

Open cmd.exe cd into dir of tm-bt-led Type: set BLUETOOTH_HCI_SOCKET_USB_VID=0x2357 set BLUETOOTH_HCI_SOCKET_USB_PID=0x0604 Then run: setup.bat

[EldarF1]

when I open tm bt led.exe, the program shuts down in a second.

I'll try via cmd.exe again this with usb id parameters, if I don't succeed then try the third luck with ASUS bt ub400, is there only one model of the mentioned stick 4.0 version?

[mplutka]

Open cmd.exe, traverse to your extracted folder and proceed with the steps from above

[EldarF1]

C:\Users\eldar\Desktop\bt led>"tm-bt-led.exe" Using imperial units Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes

[EldarF1]

C:\Users\eldar\Desktop\bt led>"tm-bt-led.exe" set BLUETOOTH_HCI_SOCKET_USB_VID=0x2357 set BLUETOOTH_HCI_SOCKET_USB_PID=0x0604 Using imperial units Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes

C:\Users\eldar\Desktop\bt led>

[EldarF1]

C:\Users\eldar\Desktop\bt led>"tm-bt-led.exe" Type:set BLUETOOTH_HCI_SOCKET_USB_VID=0x2357set BLUETOOTH_HCI_SOCKET_USB_PID=0x0604 Using imperial units Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes

C:\Users\eldar\Desktop\bt led>

[mplutka]

Did you run the two separate set commands before running tm-bt-led.exe? To make sure, just run „set“ and look for those two environment variables being set correctly

[EldarF1]

have you any desk to try ? od timeviewer.. sorry not to good in CMD

[EldarF1]

C:\Users\eldar\Desktop\bt led>"tm-bt-led.exe" "set BLUETOOTH_HCI_SOCKET_USB_VID=0x2357" Using imperial units Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes

[EldarF1]

C:\Users\eldar\Desktop\bt led>"set"C:\Users\eldar\Desktop\bt led>"tm-bt-led.exe" "set BLUETOOTH_HCI_SOCKET_USB_VID=0x2357" The filename, directory name, or volume label syntax is incorrect.

C:\Users\eldar\Desktop\bt led>Using imperial units 'Using' is not recognized as an internal or external command, operable program or batch file.

C:\Users\eldar\Desktop\bt led>Error: No compatible USB Bluetooth device found! 'Error:' is not recognized as an internal or external command, operable program or batch file.

C:\Users\eldar\Desktop\bt led> at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at processTicksAndRejections (internal/process/task_queues.js:77:11) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at Function.runMain (pkg/prelude/bootstrap.js:1980:13) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at internal/main/run_main_module.js:17:47 The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led>Ran for 0.0 minutes 'Ran' is not recognized as an internal or external command, operable program or batch file.

C:\Users\eldar\Desktop\bt led>Error: No compatible USB Bluetooth device found! 'Error:' is not recognized as an internal or external command, operable program or batch file.

C:\Users\eldar\Desktop\bt led> at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at processTicksAndRejections (internal/process/task_queues.js:77:11) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at Function.runMain (pkg/prelude/bootstrap.js:1980:13) The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

C:\Users\eldar\Desktop\bt led> at internal/main/run_main_module.js:17:47 The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\computername] [ [id] [/DELETE] | /DELETE [/YES]] AT [\computername] time [/INTERACTIVE] [ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted. id Is an identification number assigned to a scheduled command. /delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled. /yes Used with cancel all jobs command when no further confirmation is desired. time Specifies the time when command is to run. /interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs. /every:date[,...] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed. /next:date[,...] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed. "command" Is the Windows NT command, or batch program to be run.

[mplutka]

tm-bt-led.zip

Unzip the exe inside the archive and give it a try please. It has forced support for the tp link ub400 nano

[EldarF1]

C:\Users\eldar\Desktop\New folder>"C:\Users\eldar\Desktop\New folder\tm-bt-led.exe" Using imperial units Starting scan...

and nothing happens 3-5 minutes

[mplutka]

Did you put the new exe inside the folder with the other files from the previous archive? Did you run setup.bat successfully?

[EldarF1]

setup.bat

Error: LIBUSB_ERROR_ACCESS at Device.open (C:\snapshot\tm-bt-led\node_modules\usb\dist\usb\device.js:63:14) at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:83:19) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:49:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 { errno: -3 } Ran for 0.0 minutes Error: LIBUSB_ERROR_ACCESS at Device.open (C:\snapshot\tm-bt-led\node_modules\usb\dist\usb\device.js:63:14) at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:83:19) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:49:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 { errno: -3

[EldarF1]

C:\Users\eldar>cd "C:\Users\eldar\Desktop\bt led"

C:\Users\eldar\Desktop\bt led>setup.bat Starting scan...

in the old folder with forced support for the tp link ub400 nano

[mplutka]

From you previous posts that must be Folder "bt led" on your desktop. Put the new tm-bt-led.exe there and try again. Maybe unplug and replug the usb stick if it still doesnt work. setup.bat must have run successfully

[mplutka]

Sometimes it helps to try another usb port or to reboot the pc.

[EldarF1]

I started from the beginning. Restart the computer another usb port Installed the original TP link driver, later Zadig installed his driver cmd then cd "C:\Users\eldar\Desktop\bt led" I run setup.bat and it starts with a message starting scan.....

Unfortunately, it stands like this for 5 minutes and nothing happens.

If I start the original 3.1.7, then it reports the same error

Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw (C:\snapshot\tm-bt-led\node_modules\@abandonware\bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init (C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\hci-socket\bindings.js:82:13) at C:\snapshot\tm-bt-led\node_modules\@abandonware\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47

Do you have any other ideas or should I try the Asus ub400 bt 4.0

[mplutka]

sure give it a try. I don’t see any other option right now.

EldarF1 @.***> schrieb am Mi. 2. Okt. 2024 um 23:23:

I started from the beginning. Restart the computer another usb port Installed the original TP link driver, later Zadig installed his driver cmd then cd "C:\Users\eldar\Desktop\bt led" I run setup.bat and it starts with a message starting scan.....

Unfortunately, it stands like this for 5 minutes and nothing happens.

If I start the original 3.1.7, then it reports the same error

Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser @. \bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw @. \bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init @. \noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init @. \noble\lib\hci-socket\bindings.js:82:13) at @.\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47 Ran for 0.0 minutes Error: No compatible USB Bluetooth device found! at BluetoothHciSocket.bindUser @. \bluetooth-hci-socket\lib\usb.js:79:11) at BluetoothHciSocket.bindRaw @. \bluetooth-hci-socket\lib\usb.js:48:8) at Hci.init @. \noble\lib\hci-socket\hci.js:100:35) at NobleBindings.init @. \noble\lib\hci-socket\bindings.js:82:13) at @.\noble\lib\noble.js:63:24 at processTicksAndRejections (internal/process/task_queues.js:77:11) at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:64:3) at Function.runMain (pkg/prelude/bootstrap.js:1980:13) at internal/main/run_main_module.js:17:47

Do you have any other ideas or should I try the Asus ub400 bt 4.0

— Reply to this email directly, view it on GitHub https://github.com/mplutka/tm-bt-led/issues/23#issuecomment-2389719392, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMP7MKPLX276IVM77CLPNTZZRP4XAVCNFSM6AAAAABPEFB6YKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBZG4YTSMZZGI . You are receiving this because you were mentioned.Message ID: @.***>

[EldarF1]

is it this model

Asus-BT400 USB adapter bluetooth 4.0

[EldarF1]

thank you very much for your effort and help

[mplutka]

I found the Asus not to be so stable. Sorry :-( If you can return it, you can give it a try

[EldarF1]

I will try to order another CSR 8150 A10 from aliexpress maybe I'll have better luck, thank you

[EldarF1]

if you have a link of a bt device, write

[EldarF1]

I don't understand how many TP-Link UB400 models there are, aren't they all nano models?

[mplutka]

Seems like it. Here is a list of other csr based devices: https://github.com/sgothel/direct_bt/blob/master/doc/adapter/adapter.md

Maybe one of the logilink models?

[EldarF1]

I will try to find some of the above, I gave up on Asus-BT400 USB adapter bluetooth 4.0. I will order from aliexpress CSR 8150 A10 the worst that I have to wait a month for delivery at least. I will not surrender :)

[mplutka]

What was the problem with the ASUs? Are logilink not available on Amazon? Where are you from?

[mplutka]

Can you upload a picture of the engravings on the tplink?

[EldarF1]

I live in Europe, specifically Bosnia and Herzegovina (Balkans). We don't have amazon, aliexpress and local pc stores. I can quickly get the above Asus-BT400 USB adapter bluetooth 4.0, I am looking for other models on our ebay service and aliexpress.

[EldarF1]

I bought this model

[mplutka]

https://amzn.eu/d/4D5WBDO this is the exact model that it is working for me right now. Any chance to get it? Can i send it to you via Amazon or is it strictly not possible?

[mplutka]

I have the ASUS here and it doesnt work very good at all.

[EldarF1]

I wrote to you by email

[EldarF1]

Do you resive my email :-) 3.1.8 where can y download it? F1 24 support in this version?

[EldarF1]

github write not found when I go to download it "3.1.8"

[mplutka]

Link is fixed. Should support f1 udp version up to f1 23