It seems I have a working cluster, but only one member reporting presence. Why!?

[scstraus]

Hi all,

I had one node (living-room) working fine with a simple no-cluster config, but as soon as I added the cluster config and added the second member, the second member (kitchen) took over and is now the only one reporting presence, so the presence of the device tracker is always set to that room or not_home if I go far enough away (such as into the living room where the other pi is). Any idea why this is happening? Even if I put the device on top of the living room device, it doesn't work.

living room config:

global:
  instanceName: living_room
  integrations:
    - homeAssistant
    - bluetoothClassic

cluster:
  autoDiscovery: false
  networkInterface: wlan0
  port: 6425
  peerAddresses:
    - 192.168.1.21:6425

homeAssistant:
  mqttUrl: 'mqtt://REDACTED:1883'
  mqttOptions:
    username: REDACTED
    password: REDACTED

bluetoothClassic:
  minRssi: -20
  hciDeviceId: 0
  addresses:
    - REDACTED

config of second device (kitchen):

global:
  instanceName: kitchen
  integrations:
    - homeAssistant
    - bluetoothClassic

cluster:
  autoDiscovery: false
  networkInterface: wlan0
  port: 6425
  peerAddresses:
    - 192.168.1.22:6425

homeAssistant:
  mqttUrl: 'REDACTED:1883'
  mqttOptions:
    username: REDACTED
    password: REDACTED

bluetoothClassic:
  minRssi: -20
  hciDeviceId: 0
  addresses:
    - REDACTED

From API: 

[
{"attributes":{},"id":"bluetooth-classic-inquiries-switch","name":"kitchen Bluetooth Inquiries","distributed":false,"stateLocked":true,"state":true}
,{"attributes":{"nodes":["living-room","kitchen"]},"
id":"status-cluster-size","name":"kitchen Cluster Size","distributed":false,"stateLocked":true,"state":2},
{"attributes":{"quorumReached":true},
"id":"status-cluster-leader","name":"kitchen Cluster Leader","distributed":false,"stateLocked":true,"state":"living-room"}
,{"attributes":{},
"id":"bluetooth-classic-dc-REDACTED-tracker","name":"Sean's iPhone 12 Tracker","distributed":true,"stateLocked":true,"state":"home"},
{"attributes":{"distance":4.5,"lastUpdatedAt":"2021-03-26T00:23:37.013Z"},"id":"bluetooth-classic-REDACTED","name":"Sean's iPhone 12 Room Presence","distributed":true,"stateLocked":true,"distances":
{"kitchen":
{"lastUpdatedAt":"2021-03-26T00:23:37.013Z","distance":4.5,"outOfRange":false}}
,"timeout":40,"state":"kitchen"}]

in log of living room I have:

Mar 26 00:43:12 raspberrypi systemd[1]: Started room-assistant service.
Mar 26 00:43:26 raspberrypi room-assistant[2901]: *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
Mar 26 00:43:26 raspberrypi room-assistant[2901]: *** WARNING *** Please fix your application to use the native API of Avahi!
Mar 26 00:43:26 raspberrypi room-assistant[2901]: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
Mar 26 00:43:26 raspberrypi room-assistant[2901]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
Mar 26 00:43:26 raspberrypi room-assistant[2901]: *** WARNING *** Please fix your application to use the native API of Avahi!
Mar 26 00:43:26 raspberrypi room-assistant[2901]: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
Mar 26 00:43:26 raspberrypi node[2901]: *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
Mar 26 00:43:26 raspberrypi node[2901]: *** WARNING *** Please fix your application to use the native API of Avahi!
Mar 26 00:43:26 raspberrypi node[2901]: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
Mar 26 00:43:26 raspberrypi node[2901]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
Mar 26 00:43:26 raspberrypi node[2901]: *** WARNING *** Please fix your application to use the native API of Avahi!
Mar 26 00:43:26 raspberrypi node[2901]: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
Mar 26 00:43:40 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:40 - info - InstanceLoader: StatusModule dependencies initialized
Mar 26 00:43:44 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:44 - info - RoutesResolver: EntitiesController {/entities}:
Mar 26 00:43:44 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:44 - info - RouterExplorer: Mapped {/entities, GET} route
Mar 26 00:43:44 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:44 - info - RoutesResolver: StatusController {/status}:
Mar 26 00:43:44 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:44 - info - RouterExplorer: Mapped {/status, GET} route
Mar 26 00:43:44 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:44 - info - RoutesResolver: PrometheusController {/metrics}:
Mar 26 00:43:44 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:44 - info - RouterExplorer: Mapped {/metrics, GET} route
Mar 26 00:43:46 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:46 - info - HomeAssistantService: Successfully connected to MQTT broker at REDACTED:1883
Mar 26 00:43:47 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:47 - info - ConfigService: Loading configuration from /opt/nodejs/lib/node_modules/room-assistant/dist/config/definitions/default.js, config/local.yml (Current: /home/pi/room-assistant)
Mar 26 00:43:47 raspberrypi room-assistant[2901]: 26/03/2021, 00:43:47 - info - NestApplication: Nest application successfully started
Mar 26 00:55:47 raspberrypi room-assistant[3601]: 26/03/2021, 01:53:27 - info - ClusterService: Added 192.168.1.21:6425 to the cluster with id kitchen
Mar 26 00:55:48 raspberrypi room-assistant[3601]: 26/03/2021, 01:53:28 - info - ClusterService: kitchen has been elected as leader

Also, I tried this:

pi@living-room:~ $ hcitool cc REDACTED && hcitool rssi REDACTED
Can't create connection: Connection timed out
Read RSSI failed: Input/output error

But maybe that only works for bluetooth-classic? How do I test BLE?

I'm still getting messages like this in the logs

Mar 28 20:49:04 living-room room-assistant[264]: 28/03/2021, 20:49:04 - info - BluetoothLowEnergyService: Discovered new BLE peripheral REDACTED with ID REDACTED and RSSI -56

What does it all mean? If I reboot it works for 12-24 hours and then goes back to this state.

What does it all mean?

[mKeRix]

The hcitool commands are for BT Classic only indeed, however you seem to be using Bluetooth Classic for your tracking (as per the config and entities) - is that intended? The Bluetooth Low Energy logs are confusing, as those should only be printed if you have the bluetoothLowEnergy integration enabled somewhere... which I don't see in the configs you posted here.

Could you double check that you really use the same integrations on both instances (loaded integrations will also be logged at start-up)? For iPhones I'd recommend to use BLE with the companion app if possible.

[scstraus]

Hi, thanks for the reply. Sorry I forgot to send an updated config after I moved to BLE, but the logs are indeed from BLE and I am using the companion app. I will send the new config soon.

[scstraus]

Here is my current BLE config file which matches the above log. I'm pretty sure I'm doing everything right..?

global:
  instanceName: living_room
  integrations:
    - homeAssistant
    - bluetoothLowEnergy

cluster:
  autoDiscovery: false
  networkInterface: wlan0
  port: 6425
  peerAddresses:
    - 192.168.1.21:6425

homeAssistant:
  mqttUrl: 'mqtt://REDACTED:1883'
  mqttOptions:
    username: REDACTED
    password: REDACTED

bluetoothLowEnergy:
  timeout: 60
  allowlist:
  - REDACTED

[mwolter805]

Either there's a typo when posting the config or an issue with the peerAddress IP address. Second octet has four digits.

peerAddresses:
- 192.1681.21:6425

Probably should be:

peerAddresses:
- 192.168.21:6425

[scstraus]

I’m actually changing the IP addresses when I post it so it’s a typo on my part. The real IP addresses match and as you can see in the log it connects fine.

[mKeRix]

The configs you posted look fine to me, Bluetooth itself also seems to work okay if the living-room node reports discovery events as well. Is your device ever listed as discovered in the living-room logs? I assume you've already done so, but also double check that the allowlist is the same on both instances.

You can also do hcitool lescan directly on the hardware to check if device is found by the adapter, but there is an issue with passing it to NodeJS or something. Sometimes a simple reboot of the machine can also solve the strangest issues.