Cluster Won't Agree on a Leader

[pkscout]

My cluster never seems to agree on a leader. The bedroom thinks it's the lead of a 3 instance cluster. The study things it's the lead of a 3 instance cluster. And the living room thinks it's in an anarchist cluster of 3 instances where there is no leader. I've tried everything I can think of to make this work to no avail. Here's my ansible config:

all:
  hosts:
    'xxx.xxx.xxx.xxx':
      ansible_user: xxxxxx
      ansible_password: xxxxx
      room_assistant_config: 
        global:
          instanceName: livingroom
        cluster:
          weight: 100
          quorum: 2
    'xxx.xxx.xxx.xxx':
      ansible_user: xxxxxx
      ansible_password: xxxxx
      room_assistant_config: 
        global:
          instanceName: study
        cluster:
          weight: 1000
          quorum: 2
        bluetoothLowEnergy:
          maxDistance: 3
    'xxx.xxx.xxx.xxx':
      ansible_user: xxxxxx
      ansible_password: xxxxx
      room_assistant_config: 
        global:
          instanceName: bedroom
        cluster:
          weight: 10
          quorum: 2
        bluetoothLowEnergy:
          maxDistance: 5.5
  vars:
    room_assistant_version: latest
    room_assistant_global_config:
      global:
        integrations:
          - homeAssistant
          - bluetoothLowEnergy
      homeAssistant:
        mqttUrl: mqtt://xxx.xxx.xxx.xxx:1883
      bluetoothLowEnergy:
        timeout: 60
        updateFrequency: 30
        allowlist:
        - xxx
        - xxxx
        - xxxxx
        tagOverrides:
          xxx:
            name: xxx iBeacon
          xxxx:
            name: xxxx iBeacon
          xxxxx:
            name: xxxxx iBeacon

[pkscout]

Three and a half months later, still having this problem. Really wonder if anyone monitors this place at all.

[anthonymkz]

I'm having the same problem and it's driving me nuts. When I set the quorum option it made it even worse because if even one instance is in it's own separate cluster none of them can make a majority and so my presence shows as not_home or unavailable. Maddening

[lorenzothurman]

Have you tried setting all others except the desired leader to a weight of 1? I've also noticed that the desired leader should be the last to restart RA, otherwise I might see mixed leaders, or none, across my six nodes.

[pkscout]

@lorenzothurman thanks for the suggestions. One of those two things seems to have helped. Not sure you have to set the ones you don't want leading to 1, but whatever. One of my nodes was still reporting none, but restarting the cluster leader seemed to fix that. I don't know how long this will really last, as it seems like the cluster leader stuff seems super fragile.

Since Lorenz replied to the thread, it looks like I can't mark his suggestion as the solution, so I'm marking this as the solution, but here's a reference to the actual solution: #1272 (reply in thread)

[lorenzothurman]

Setting things to 1 and restarting the preferred leader was a bit of sanity check. That should give you what you want. At least, this is my experience. You can try assigning higher weights to the other nodes, but restart your preferred leader last and see what happens. "My Break-Dancing days are over, but there's always the Funky Chicken" -- The Full MontyOn Feb 12, 2023, at 5:48 AM, Kyle Johnson ***@***.***> wrote: @lorenzothurman thanks for the suggestions. One of those two things seems to have helped. Not sure you have to set the ones you don't want leading to 1, but whatever. One of my nodes was still reporting none, but restarting the cluster leader seemed to fix that. I don't know how long this will really last, as it seems like the cluster leader stuff seems super fragile. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[idantene]

Has this solution lasted for you @pkscout? I have a rogue node that just won't select anything other than itself as cluster leader. Other three nodes are fine.

[pkscout]

It did. At least until I gave up on this at all and moved to ESPresence on some ESP32 boards. And then gave up on Bluetooth tracking altogether and moved to time of flight threshold sensors to detect transitions from room to room.

[idantene]

Well color me interested. Could you elaborate on this time-of-flight threshold sensors?

[pkscout]

Here's the short version. I'm using ESPHome with this custom module:

https://github.com/Lyr3x/Roode

And this hardware:

ESP32 board: https://www.adafruit.com/product/5477
Time of Flight sensor: https://www.adafruit.com/product/3967

The code/sensor define entry and exit zones for a threshold and then add or delete people as they pass the threshold.

The examples and readme aren't 100% right, so here's where I keep my config:

https://github.com/pkscout/ESPHome

Look in the configs directory for the one called people-counter.yaml. At some point I'm going to add some pages to the wiki for my ESPHome configs with more details. Hopefully this is enough to get you started. I kind of don't what to hijack this thread here further.