Has Neighbor_Info changed in 2.4.0 to 2.5.4?

1

I see where they make the default to be 6 hours on a pull from on Aug 17. However, i am not getting any Neighbor_Info packets that are filled with neighbors (which i have seven in my my mesh and they all see each other) since going to 2.5.4. I have verified that using:

meshtastic --get neighbor_info

I get a return of enabled being true and update_interval is 900 seconds (15 mins).

Suggestions?

2

There was a bug introduced for the NeighborInfo Module, which is fixed in firmware 2.5.5: cleanupNeighbors() time difference fix by gitbisector · Pull Request #4941 · meshtastic/firmware · GitHub

1 Like
3

So looking at the alpha release, which package do I download to install into my RAKS and T-Beams?

4

That would be firmware-nrf52840-2.5.5.e182ae7.zip and firmware-esp32-2.5.5.e182ae7.zip, respectively.

1 Like
5

So i have installed the new firmware given above, verified that the neighbor_info.enabled is set to True and neighbor_info.updateInterval is set to 900. I am only getting one node to send out the neighbor_info packet. Any other suggestions?

6

I’m sorry, I wouldn’t know why only one node sends its NeighborInfo if you run the same firmware with the same settings.

7

Could there still be a bug in the software? How do i look at the source code on github that shows the differences with V 2.4.0.46d7b82 (which works as expected) and the Alpha-firmware-esp32-2.5.5.e182ae7 as well as Alpha-firmware-nrf52840-2.5.5.e182ae7

So looking at the code in NodeDB.cpp, if you set the time interval to 900 it sets it to 0, which turns it off… why is that?

Thanks

8

A bit above it says “2.4.X - configuration migration to update new default intervals”. Setting it to 0 means the default and the new default in 2.5.X is 1800.

9

Any suggestions as where to look to determine why the neighbor_info packet is not being sent as commanded by the updateInterval value? This command does not seem to be working as expected.

11

I have installed the latest version (2.5.5.e182ae7) into both T-Beams and RAKS. i change ONLY (keeping everything else set to default) the channel url, set the neighbor_info. enabled to true as well as neighbor_info.update_interval (from anywhere from 120 to 900 seconds) and I cannot get the Neighbor packet to come across the MQTT network.

Are you SURE the neighbor_info packet is working???

12

You can’t set the interval too low, just leave it at the default (set it back to 0).

Also, the node that is uplinking it to MQTT must have the NeighborInfo enabled, otherwise it will ignore those packets.