# RuuviTagSensor and Debian laptop
**URL:** https://f.ruuvi.com/t/ruuvitagsensor-and-debian-laptop/3654
**Category:** 🇬🇧 Development projects with Ruuvi products
**Created:** [25 July 2019 07:09 UTC](https://f.ruuvi.com/t/ruuvitagsensor-and-debian-laptop/3654 "2019-07-25T07:09:23Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@pasiol](https://f.ruuvi.com/u/pasiol)
#### Post date: [25 July 2019 07:09 UTC](https://f.ruuvi.com/t/ruuvitagsensor-and-debian-laptop/3654/1 "2019-07-25T07:09:23Z")
I can not connect to my Ruuvi tag from a Debian laptop. Connection working from Android phone, so the tag is alive.
For scanning tags, I tried to use Python and NodeJS libraries. Nothing works. I am not experienced in conf Bluetooth settings. The laptop is also rather old Lenovo T420. Is it possible that Bluetooth chip is incompatible with the Ruuvi tag?
Here are some clipboard data from cli.
hcitool dev
Devices:
hci0 NN:NN:NN:NN:NN:NN
hciconfig
```
hci0: Type: Primary Bus: USB
BD Address: NN:NN:NN:NN:NN:NN ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN INQUIRY
RX bytes:6588 acl:0 sco:0 events:527 errors:0
TX bytes:10256 acl:0 sco:0 commands:397 errors:0
root@lpt2:~# hcidump
```
HCI sniffer - Bluetooth packet analyzer ver 5.50
device: hci0 snap\_len: 1500 filter: 0xffffffffffffffff
\< HCI Command: Reset (0x03|0x0003) plen 0
> HCI Event: Command Complete (0x0e) plen 4
> Reset (0x03|0x0003) ncmd 1
> status 0x00
> \< HCI Command: Read Local Supported Features (0x04|0x0003) plen 0
> HCI Event: Command Complete (0x0e) plen 12
> Read Local Supported Features (0x04|0x0003) ncmd 1
> status 0x00
> Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
> \< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> HCI Event: Command Complete (0x0e) plen 12
> Read Local Version Information (0x04|0x0001) ncmd 1
> status 0x00
> HCI Version: 3.0 (0x5) HCI Revision: 0x2ec
> LMP Version: 3.0 (0x5) LMP Subversion: 0x4203
> Manufacturer: Broadcom Corporation (15)
> \< HCI Command: Read BD ADDR (0x04|0x0009) plen 0
> HCI Event: Command Complete (0x0e) plen 10
> Read BD ADDR (0x04|0x0009) ncmd 1
> status 0x00 bdaddr E4:D5:3D:C7:37:E3
> \< HCI Command: Read Buffer Size (0x04|0x0005) plen 0
> HCI Event: Command Complete (0x0e) plen 11
> Read Buffer Size (0x04|0x0005) ncmd 1
> status 0x00
> ACL MTU 1021:8 SCO MTU 64:1
> \< HCI Command: Read Class of Device (0x03|0x0023) plen 0
> HCI Event: Command Complete (0x0e) plen 7
> Read Class of Device (0x03|0x0023) ncmd 1
> status 0x00 class 0x000000
> \< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
> Read Local Name (0x03|0x0014) ncmd 1
> status 0x00 name ‘lpt2’
> \< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Command Complete (0x0e) plen 6
> Read Voice Setting (0x03|0x0025) ncmd 1
> status 0x00 voice setting 0x0060
> \< HCI Command: Read Number of Supported IAC (0x03|0x0038) plen 0
> HCI Event: Command Complete (0x0e) plen 5
> Read Number of Supported IAC (0x03|0x0038) ncmd 1
> \< HCI Command: Read Current IAC LAP (0x03|0x0039) plen 0
> HCI Event: Command Complete (0x0e) plen 8
> Read Current IAC LAP (0x03|0x0039) ncmd 1
> IAC 0x9e8b33 (General Inquiry Access Code)
> \< HCI Command: Set Event Filter (0x03|0x0005) plen 1
> type 0 condition 0
> Clear all filters
> HCI Event: Command Complete (0x0e) plen 4
> Set Event Filter (0x03|0x0005) ncmd 1
> status 0x00
> \< HCI Command: Write Connection Accept Timeout (0x03|0x0016) plen 2
> timeout 32000
> HCI Event: Command Complete (0x0e) plen 4
> Write Connection Accept Timeout (0x03|0x0016) ncmd 1
> status 0x00
> \< HCI Command: Read Local Supported Commands (0x04|0x0002) plen 0
> HCI Event: Command Complete (0x0e) plen 68
> Read Local Supported Commands (0x04|0x0002) ncmd 1
> status 0x00
> Commands: ffffff03feffefffffffef1ff20fe8fe3ff78fff1c00000001
> \< HCI Command: Write Simple Pairing Mode (0x03|0x0056) plen 1
> mode 0x01
> HCI Event: Command Complete (0x0e) plen 4
> Write Simple Pairing Mode (0x03|0x0056) ncmd 1
> status 0x00
> \< HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1
> mode 2
> HCI Event: Command Complete (0x0e) plen 4
> Write Inquiry Mode (0x03|0x0045) ncmd 1
> status 0x00
> \< HCI Command: Read Inquiry Response Transmit Power Level (0x03|0x0058) plen 0
> HCI Event: Command Complete (0x0e) plen 5
> Read Inquiry Response Transmit Power Level (0x03|0x0058) ncmd 1
> status 0x00 level 0
> \< HCI Command: Read Local Extended Features (0x04|0x0004) plen 1
> page 1
> HCI Event: Command Complete (0x0e) plen 14
> Read Local Extended Features (0x04|0x0004) ncmd 1
> status 0x00 page 1 max 1
> Features: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> \< HCI Command: Set Event Mask (0x03|0x0001) plen 8
> Mask: 0xfffffbff07f8bf1d
> HCI Event: Command Complete (0x0e) plen 4
> Set Event Mask (0x03|0x0001) ncmd 1
> status 0x00
> \< HCI Command: Read Stored Link Key (0x03|0x000d) plen 7
> bdaddr 00:00:00:00:00:00 all 1
> HCI Event: Command Complete (0x0e) plen 8
> Read Stored Link Key (0x03|0x000d) ncmd 1
> status 0x00 max 1 num 0
> \< HCI Command: Write Default Link Policy Settings (0x02|0x000f) plen 2
> policy 0x0f
> Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Command Complete (0x0e) plen 4
> Write Default Link Policy Settings (0x02|0x000f) ncmd 1
> status 0x00
> \< HCI Command: Read Page Scan Activity (0x03|0x001b) plen 0
> HCI Event: Command Complete (0x0e) plen 8
> Read Page Scan Activity (0x03|0x001b) ncmd 1
> status 0x00 interval 2048 window 18
> \< HCI Command: Read Page Scan Type (0x03|0x0046) plen 0
> HCI Event: Command Complete (0x0e) plen 5
> Read Page Scan Type (0x03|0x0046) ncmd 1
> \< HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7
> bdaddr 00:00:00:00:00:00 all 1
> HCI Event: Command Complete (0x0e) plen 6
> Delete Stored Link Key (0x03|0x0012) ncmd 1
> status 0x00 deleted 0
> \< HCI Command: Write Scan Enable (0x03|0x001a) plen 1
> enable 3
> HCI Event: Command Complete (0x0e) plen 4
> Write Scan Enable (0x03|0x001a) ncmd 1
> status 0x00
> \< HCI Command: Write Class of Device (0x03|0x0024) plen 3
> class 0x1c010c
> HCI Event: Command Complete (0x0e) plen 4
> Write Class of Device (0x03|0x0024) ncmd 1
> status 0x00
> \< HCI Command: Write Local Name (0x03|0x0013) plen 248
> name ‘lpt2’
> HCI Event: Command Complete (0x0e) plen 4
> Write Local Name (0x03|0x0013) ncmd 1
> status 0x00
> \< HCI Command: Write Extended Inquiry Response (0x03|0x0052) plen 241
> fec 0x00
> Complete local name: ‘lpt2’
> TX power level: 0
> Unknown type 0x10 with 8 bytes data
> Complete service classes: 0x110e 0x110c 0x1112 0x1108 0x1133 0x1132 0x112f 0x1104 0x1106 0x1105 0x110a 0x110b
> Unknown type 0x07 with 16 bytes data
> HCI Event: Command Complete (0x0e) plen 4
> Write Extended Inquiry Response (0x03|0x0052) ncmd 1
> status 0x00
> \< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7
> type 0x01 (active)
> interval 10.000ms window 10.000ms
> own address: 0x00 (Public) policy: All
> HCI Event: Command Complete (0x0e) plen 4
> LE Set Scan Parameters (0x08|0x000b) ncmd 1
> status 0x01
> Error: Unknown HCI Command
> \< HCI Command: Inquiry (0x01|0x0001) plen 5
> lap 0x9e8b33 len 8 num 0
> HCI Event: Command Status (0x0f) plen 4
> Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
---
### Author:  [@otso](https://f.ruuvi.com/u/otso)
#### Post date: [28 July 2019 12:23 UTC](https://f.ruuvi.com/t/ruuvitagsensor-and-debian-laptop/3654/2 "2019-07-28T12:23:47Z")
Hello,
Some really old devices don’t support Bluetooth LE, this could be one cause of the error. Can you read other BLE devices with your laptop?
---
### Author:  [@pasiol](https://f.ruuvi.com/u/pasiol)
#### Post date: [30 July 2019 16:23 UTC](https://f.ruuvi.com/t/ruuvitagsensor-and-debian-laptop/3654/3 "2019-07-30T16:23:09Z")
I don’t have any other devices than Ruuvi. When I have more time, I would install Rasberry pi and try it. Until that, I can use the old phone and app.