Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[error] the specified device at 00:1a:22:0f:07:67 has not been found yet #3

Open
janvda opened this issue Mar 24, 2019 · 3 comments
Open

Comments

@janvda
Copy link
Owner

janvda commented Mar 24, 2019

From time to time we get the below error in the log file:

24.03.19 14:11:40 (+0100)  nodered  24 Mar 13:11:40 - [error] the specified device at 00:1a:22:0f:07:67 has not been found yet
24.03.19 14:11:40 (+0100)  nodered  24 Mar 13:11:40 - [warn] list of all available addressess will be retrieved...
@janvda
Copy link
Owner Author

janvda commented Mar 24, 2019

Rebooting didn't fix it. I got the same error.

@janvda
Copy link
Owner Author

janvda commented Mar 24, 2019

using bluetoothctl in Host OS shell and then scan on showed the following after some time

[NEW] Device 00:1A:22:0F:07:67 00-1A-22-0F-07-67
...
[CHG] Device 00:1A:22:0F:07:67 RSSI: -97
[CHG] Device 00:1A:22:0F:07:67 Name: CC-RT-BLE
[CHG] Device 00:1A:22:0F:07:67 Alias: CC-RT-BLE
CHG] Device 00:1A:22:0F:07:67 ManufacturerData Key: 0x0000
[CHG] Device 00:1A:22:0F:07:67 ManufacturerData Value:
  00 00 00 00 00 00 00 00 00                       .........       
[CHG] Device 00:1A:22:0F:07:67 AdvertisingFlags:
  00                                               .    

So most likely the received signal (RSSI) is way to weak to setup a proper connection.
(the device was located in bed room ste.. and the eq-3 is located one floor lower bur...)

The strange thing is that we didn't have this issue this morning.

@janvda
Copy link
Owner Author

janvda commented Mar 24, 2019

I have moved the raspberry pi one floor down (so the same floor as the eq3 device but in a different room = our bedroom ) and I no longer got the above issue.

using bluetoothctl in Host OS shell and then scan on showed the following after some time

[CHG] Device 00:1A:22:0F:07:67 Connected: no
[DEL] Device 00:1A:22:0F:07:67 00-1A-22-0F-07-67
...
...
[NEW] Device 00:1A:22:0F:07:67 CC-RT-BLE
[CHG] Device 58:F6:E1:27:F1:5F RSSI: -75
[CHG] Device 00:1A:22:0F:07:67 RSSI: -74
[CHG] Device 00:1A:22:0F:07:67 RSSI: -90
[CHG] Device 00:1A:22:0F:07:67 AdvertisingFlags:
  00                                            
[CHG] Device 58:F6:E1:27:F1:5F RSSI: -67
[CHG] Device 58:F6:E1:27:F1:5F RSSI: -84
[CHG] Device 58:F6:E1:27:F1:5F AdvertisingFlags:
  00                                               .               
[NEW] Device 54:1A:25:47:C9:4E 54-1A-25-47-C9-4E
[CHG] Device 00:1A:22:0F:07:67 RSSI: -76
[CHG] Device 00:1A:22:0F:07:67 AdvertisingFlags:
  05                                               .               
[NEW] Device 79:93:11:44:B7:01 79-93-11-44-B7-01
[CHG] Device 00:1A:22:0F:07:67 RSSI: -91
[CHG] Device 00:1A:22:0F:07:67 AdvertisingFlags:
  00                                               .               
[CHG] Device 00:1A:22:0F:07:67 Connected: yes
[CHG] Device 58:F6:E1:27:F1:5F RSSI: -70
...

So most likely the stronger received signal (RSSI) fixed the problem !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant