Open I-am-not-a-number opened 3 years ago
ugh, I also experience this - did you find resolution?
@webash Could you show the btmon hci log as well? Do you have a rpi 4?
Not sure I remember it all but I did replace the battery and used an external USB BT dongle. Both solved some issues, I'm just not sure which ;-)
@webash Could you show the btmon hci log as well? Do you have a rpi 4?
I'm using a RPI3. Do you mean the btmon
logs? I'm getting a lot of output from that - like it fills the whole terminal buffer within a minute or so.
> HCI Event: LE Meta Event (0x3e) plen 39 #1062 [hci0] 29.384735
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Public (0x00)
Address: C0:28:8D:36:5B:B3 (Logitech, Inc)
Data length: 27
Flags: 0x1a
LE General Discoverable Mode
Simultaneous LE and BR/EDR (Controller)
Simultaneous LE and BR/EDR (Host)
Name (short):
16-bit Service UUIDs (complete): 1 entry
Logitech International SA (0xfe61)
Company: IBM Corp. (3)
Data: 00605100000a242934851a3c32
RSSI: -62 dBm (0xc2)
> HCI Event: LE Meta Event (0x3e) plen 30 #1063 [hci0] 29.398635
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: DB:57:E3:75:58:60 (Static)
Data length: 18
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
Company: not assigned (2409)
Data: db57e3755860320e001132
RSSI: -55 dBm (0xc9)
> HCI Event: LE Meta Event (0x3e) plen 39 #1064 [hci0] 29.471238
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Public (0x00)
Address: C0:28:8D:36:5B:B3 (Logitech, Inc)
Data length: 27
Flags: 0x1a
LE General Discoverable Mode
Simultaneous LE and BR/EDR (Controller)
Simultaneous LE and BR/EDR (Host)
Name (short):
16-bit Service UUIDs (complete): 1 entry
Logitech International SA (0xfe61)
Company: IBM Corp. (3)
Data: 00605100000a242934851a3c32
RSSI: -63 dBm (0xc1)
> HCI Event: LE Meta Event (0x3e) plen 30 #1065 [hci0] 29.481133
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: F4:87:C1:D1:45:CD (Static)
Data length: 18
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
Company: not assigned (2409)
Data: f487c1d145cdf60b361105
RSSI: -60 dBm (0xc4)
> HCI Event: LE Meta Event (0x3e) plen 30 #1066 [hci0] 29.499548
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: DB:57:E3:75:58:60 (Static)
Data length: 18
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
Company: not assigned (2409)
Data: db57e3755860320e001132
RSSI: -55 dBm (0xc9)
> HCI Event: LE Meta Event (0x3e) plen 30 #1067 [hci0] 29.582304
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: F4:87:C1:D1:45:CD (Static)
Data length: 18
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
Company: not assigned (2409)
Data: f487c1d145cdf60b361105
RSSI: -60 dBm (0xc4)
> HCI Event: LE Meta Event (0x3e) plen 30 #1068 [hci0] 29.606041
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: DB:57:E3:75:58:60 (Static)
Data length: 18
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
Company: not assigned (2409)
Data: db57e3755860320e001132
RSSI: -58 dBm (0xc6)
> HCI Event: LE Meta Event (0x3e) plen 39 #1069 [hci0] 29.641225
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Public (0x00)
Address: C0:28:8D:36:5B:B3 (Logitech, Inc)
Data length: 27
Flags: 0x1a
LE General Discoverable Mode
Simultaneous LE and BR/EDR (Controller)
Simultaneous LE and BR/EDR (Host)
Name (short):
16-bit Service UUIDs (complete): 1 entry
Logitech International SA (0xfe61)
Company: IBM Corp. (3)
Data: 00605100000a242934851a3c32
RSSI: -64 dBm (0xc0)
> HCI Event: LE Meta Event (0x3e) plen 30 #1070 [hci0] 29.681646
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: F4:87:C1:D1:45:CD (Static)
Data length: 18
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
Company: not assigned (2409)
Data: f487c1d145cdf60b361105
RSSI: -59 dBm (0xc5)
> HCI Event: LE Meta Event (0x3e) plen 30 #1071 [hci0] 29.708407
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: DB:57:E3:75:58:60 (Static)
Data length: 18
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
Company: not assigned (2409)
Data: db57e3755860320e001132
RSSI: -60 dBm (0xc4)
Not sure if any of this helps. I've truncated to just a few events. I have quite a few broadcasting bluetooth devices of my own, and live in an apartment building in London - so there's going to be noise. But all other bluetooth devices (like the Switchbot devices through the esp32 bt proxy) work fine.
This is now the third Raspberry Pi (v3) I've used for this over the years. Sometimes it works just fine for a while, and then suddenly it'll just stop and I'll have to reboot the Pi or restart flicd
, and then typically I have to manually restart Home Assistant too - otherwise it doesn't reconnect properly - even if flicd has logged that a client has connected after restart.
I finally thought I'd replace the Pi with a fresh install and nothing else running on it - but still seeing the same behaviours.
Not sure I remember it all but I did replace the battery and used an external USB BT dongle. Both solved some issues, I'm just not sure which ;-)
Any idea which adapter you've got? Thinking it must be the built-in Pi BT at this stage - it never has been great.
It seems like whatever integration you are running, it runs a scan continuously. Scanning should only be performed when pairing a new button, so try turn off this scanning.
Not sure but the Bluetooth controller (the cypress wifi/bt chip in a RPi) could be confused of all those advertisements maybe.
Also Flic buttons will not work reliably when the battery is low (they often drop connections in that case).
It seems like whatever integration you are running, it runs a scan continuously. Scanning should only be performed when pairing a new button, so try turn off this scanning.
Understood; wasn't aware that discovery was quite that intensive. I might push a change to the HA documentation to make that clearer.
Not sure but the Bluetooth controller (the cypress wifi/bt chip in a RPi) could be confused of all those advertisements maybe.
Yeah very true.
Also Flic buttons will not work reliably when the battery is low (they often drop connections in that case).
Yep; changed some batteries just to be sure it wasn't only that.
Hi there,
I'm turning my lights on and off with flic2 buttons connected to a Raspberry Pi 4, using the onboard Bluetooth. My problem is, that it often only works after three clicks.
first click : red flic2 led second click : orange flic2 led third click : green flic2 led, light is toggled two times (I think the click with the orange led was queued)
I already tried to reduce the baud rate (see Issue #90)
root 519 1 0 08:23 ? 00:00:00 /usr/bin/hciattach /dev/serial1 bcm43xx 230400 flow -
Any ideas?
Many thanks :-) Markus
btmon shows: