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

[Bug]: MQTT json feed does not contain neighbor node id #2755

Closed
bmidgley opened this issue Aug 31, 2023 · 0 comments · Fixed by #2756
Closed

[Bug]: MQTT json feed does not contain neighbor node id #2755

bmidgley opened this issue Aug 31, 2023 · 0 comments · Fixed by #2756
Labels
bug Something isn't working

Comments

@bmidgley
Copy link

bmidgley commented Aug 31, 2023

Category

WiFi

Hardware

T-Beam

Firmware Version

2.2.3

Description

The json mqtt feed contains a message to say neighborinfo was collected, but no information on who the neighbors are:

{
"channel": 0,
"from": 1166139310,
"id": 303656937,
"sender": "!6d00f4ac",
"timestamp": 1693503521,
"to": 4294967295,
"type": "neighborinfo"
}

Relevant log output

DEBUG | 17:53:14 938 [NeighborInfoModule] Removing neighbor with node ID 0x22192a24
INFO  | 17:53:14 938 [NeighborInfoModule] Saving /prefs/neighbors.proto
DEBUG | 17:53:14 938 [NeighborInfoModule] DBSTATE NODEDB SELECTION from Node 0x6d00f4ac:
DEBUG | 17:53:14 938 [NeighborInfoModule] ----------------
DEBUG | 17:53:14 938 [NeighborInfoModule] DB contains 15 nodes
DEBUG | 17:53:14 938 [NeighborInfoModule]      Node 0: node_id=0x6d00f4ac, snr=0.00
DEBUG | 17:53:14 938 [NeighborInfoModule]      Node 1: node_id=0x39cb1b55, snr=-19.50
DEBUG | 17:53:14 938 [NeighborInfoModule]      Node 2: node_id=0xced58391, snr=10.50
DEBUG | 17:53:14 938 [NeighborInfoModule]      Node 3: node_id=0x48bd657b, snr=12.00
DEBUG | 17:53:14 938 [NeighborInfoModule]      Node 4: node_id=0x22192a24, snr=13.75
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 5: node_id=0x215f357f, snr=-20.50
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 6: node_id=0x4, snr=13.75
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 7: node_id=0x55c7f79c, snr=11.75
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 8: node_id=0xabdddb28, snr=12.25
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 9: node_id=0x50d5cf0, snr=10.75
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 10: node_id=0x204337e8, snr=11.00
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 11: node_id=0x4ba4abb1, snr=-14.50
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 12: node_id=0x4581dfae, snr=10.75
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 13: node_id=0x11f16a8f, snr=11.25
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 14: node_id=0x3cb6fe3e, snr=0.00
DEBUG | 17:53:15 938 [NeighborInfoModule] ----------------
DEBUG | 17:53:15 938 [NeighborInfoModule] NEIGHBORS NODEDB SELECTION from Node 0x6d00f4ac:
DEBUG | 17:53:15 938 [NeighborInfoModule] ----------------
DEBUG | 17:53:15 938 [NeighborInfoModule] DB contains 1 neighbors
DEBUG | 17:53:15 938 [NeighborInfoModule]      Node 0: node_id=0x4581dfae, snr=10.25
DEBUG | 17:53:15 938 [NeighborInfoModule] ----------------
DEBUG | 17:53:15 938 [NeighborInfoModule] COLLECTED NODEDB SELECTION from Node 0x6d00f4ac:
DEBUG | 17:53:15 938 [NeighborInfoModule] ----------------
DEBUG | 17:53:15 938 [NeighborInfoModule] Selected 1 neighbors of 1 DB neighbors
DEBUG | 17:53:15 938 [NeighborInfoModule] ---> Node 0: neighbor=0x4581dfae, snr=10.25
DEBUG | 17:53:15 938 [NeighborInfoModule] ----------------
DEBUG | 17:53:15 938 [NeighborInfoModule] SENDING NEIGHBORINFO PACKET from Node 0x6d00f4ac to Node 0x6d00f4ac (last sent by 0x6d00f4ac)
DEBUG | 17:53:15 938 [NeighborInfoModule] ----------------
DEBUG | 17:53:15 938 [NeighborInfoModule] Packet contains 1 neighbors
DEBUG | 17:53:15 938 [NeighborInfoModule] Neighbor 0: node_id=0x4581dfae, snr=10.25
DEBUG | 17:53:15 938 [NeighborInfoModule] ----------------
DEBUG | 17:53:15 938 [NeighborInfoModule] Update DB node 0x6d00f4ac, rx_time=1693504395, channel=0
DEBUG | 17:53:15 938 [NeighborInfoModule] handleReceived(LOCAL) (id=0x6e61b801 fr=0xac to=0xff, WantAck=0, HopLim=3 Ch=0x0 Portnum=71 rxtime=1693504395)
DEBUG | 17:53:15 938 [NeighborInfoModule] No modules interested in portnum=71, src=LOCAL
DEBUG | 17:53:15 938 [NeighborInfoModule] localSend to channel 0
DEBUG | 17:53:15 938 [NeighborInfoModule] Add packet record (id=0x6e61b801 fr=0xac to=0xff, WantAck=0, HopLim=3 Ch=0x0 Portnum=71 rxtime=1693504395)
INFO  | 17:53:15 938 [NeighborInfoModule] Should encrypt MQTT?: 0
DEBUG | 17:53:15 938 [NeighborInfoModule] MQTT onSend - Publishing portnum 71 message
DEBUG | 17:53:15 938 [NeighborInfoModule] MQTT Publish msh/2/c/LongFast/!6d00f4ac, 79 bytes
INFO  | 17:53:15 938 [NeighborInfoModule] serialized json message: {"channel":0,"from":1828779180,"id":1851897857,"sender":"!6d00f4ac","timestamp":1693504395,"to":4294967295,"type":"neighborinfo"}
INFO  | 17:53:15 938 [NeighborInfoModule] JSON publish message to msh/2/json/LongFast/!6d00f4ac, 129 bytes: {"channel":0,"from":1828779180,"id":1851897857,"sender":"!6d00f4ac","timestamp":1693504395,"
DEBUG | 17:53:15 938 [NeighborInfoModule] Expanding short PSK #1
DEBUG | 17:53:15 938 [NeighborInfoModule] Using AES128 key!
DEBUG | 17:53:15 938 [NeighborInfoModule] ESP32 crypt fr=6d00f4ac, num=6e61b801, numBytes=32!
DEBUG | 17:53:15 938 [NeighborInfoModule] enqueuing for send (id=0x6e61b801 fr=0xac to=0xff, WantAck=0, HopLim=3 Ch=0x8 encrypted rxtime=1693504395)
DEBUG | 17:53:15 938 [NeighborInfoModule] txGood=23,rxGood=52,rxBad=1
DEBUG | 17:53:15 938 [NeighborInfoModule] Using channel 0 (hash 0x8)
DEBUG | 17:53:15 938 [NeighborInfoModule] Expanding short PSK #1
DEBUG | 17:53:15 938 [NeighborInfoModule] Using AES128 key!
@bmidgley bmidgley added the bug Something isn't working label Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant