Lot's of unknown hidden clients, until I restart the ingestor... #85

New Issue

2026-10-04T23:00:13+02:00

adam commented

2026-10-04 23:00:13 +02:00

Hey.
Strange bug: After some time (an hour or more), potatomesh starts showing lots of new client_hidden nodes...
this fills the node list, and sometimes map.
Our mesh is small , so new nodes do not appear all that often, and the node that the ingestor connects to certainly does not see that many new nodes with no userinfo.

a restart of the ingestor docker solves this, but only temporarily...

the installation is here:
https://potato.theldti.com/

Hey. Strange bug: After some time (an hour or more), potatomesh starts showing lots of new client_hidden nodes... this fills the node list, and sometimes map. Our mesh is small , so new nodes do not appear all that often, and the node that the ingestor connects to certainly does not see that many new nodes with no userinfo. a restart of the ingestor docker solves this, but only temporarily... the installation is here: https://potato.theldti.com/

adam closed this issue

2026-10-04 23:00:13 +02:00

adam commented

2026-10-04 23:00:14 +02:00

this is an analysis from Gemini - it may very well be completely incorrect:

The Python ingestor inserts nodes into the database using their raw Integer ID (e.g., 3735928559) instead of the standard Meshtastic Hex ID (e.g., !deadbeef). This occurs when the ingestor receives a message or telemetry packet from a node for which it has not yet processed a NodeInfo packet in the current session.

These "ghost" nodes often appear with the default client_hidden role and do not merge with the correct node entry once the actual NodeInfo eventually arrives, causing duplicate and confusing data in the web UI.

To Reproduce
Steps to reproduce the behavior:

Start the potato-mesh Python ingestor.
Have a Meshtastic node (Node A) send a text message or telemetry packet before it broadcasts its NodeInfo packet (or restart the ingestor so its local cache is clear).
Observe the logs or the Web UI.
A new node is created using the integer value of Node A's ID (e.g., 123456789) instead of the Hex ID (!075bcd15).
The node has no LongName/ShortName and is set to client_hidden.

Expected behavior
The ingestor should:

Always convert the raw Integer ID from a packet header into the standard Hex format before performing a database upsert.
Check interface.nodes (the local radio's existing DB) to resolve metadata for the ID, even if a NodeInfo packet hasn't been received "live" over the air during the current script session.

Additional context
It appears the ingestor logic reacts to packet['from'] (which is an int) directly. Since the Meshtastic Python library may not have the NodeInfo cached in RAM yet, the ingestor defaults to using the Int as the key. Converting this Int to Hex logic (e.g., strip('!') or standard hex formatting) before the API call would likely resolve the duplication issue.

this is an analysis from Gemini - it may very well be completely incorrect: The Python ingestor inserts nodes into the database using their raw Integer ID (e.g., `3735928559`) instead of the standard Meshtastic Hex ID (e.g., `!deadbeef`). This occurs when the ingestor receives a message or telemetry packet from a node for which it has not yet processed a `NodeInfo` packet in the current session. These "ghost" nodes often appear with the default `client_hidden` role and do not merge with the correct node entry once the actual `NodeInfo` eventually arrives, causing duplicate and confusing data in the web UI. **To Reproduce** Steps to reproduce the behavior: 1. Start the `potato-mesh` Python ingestor. 2. Have a Meshtastic node (Node A) send a text message or telemetry packet *before* it broadcasts its `NodeInfo` packet (or restart the ingestor so its local cache is clear). 3. Observe the logs or the Web UI. 4. A new node is created using the integer value of Node A's ID (e.g., `123456789`) instead of the Hex ID (`!075bcd15`). 5. The node has no LongName/ShortName and is set to `client_hidden`. **Expected behavior** The ingestor should: 1. Always convert the raw Integer ID from a packet header into the standard Hex format before performing a database upsert. 2. Check `interface.nodes` (the local radio's existing DB) to resolve metadata for the ID, even if a `NodeInfo` packet hasn't been received "live" over the air during the current script session. **Additional context** It appears the ingestor logic reacts to `packet['from']` (which is an `int`) directly. Since the Meshtastic Python library may not have the `NodeInfo` cached in RAM yet, the ingestor defaults to using the Int as the key. Converting this Int to Hex logic (e.g., `strip('!')` or standard hex formatting) before the API call would likely resolve the duplication issue.

adam commented

2026-10-04 23:00:14 +02:00

Hi, thanks for your feedback.

The AI analysis is not correct. Let me explain.

We only know about a node if they send a NODEINFO packet. This includes node user data such as Name, role, position, etc.

So after we receive this packet, we fill the database with that information.

However, sometimes we learn about a node before we receive a node info update, e.g., when someone sends Telemetry or a Traceroute or a Message even.

In that case, we create a node record and temporarily assume CLIENT_HIDDEN. Because a client that never broadcasts node info is a hidden client.

However, if we receive a NODEINFO packet later, we update the database record based on their node ID. So initially, you will see many hidden clients but that list will clean up after a couple of hours.

Hi, thanks for your feedback. The AI analysis is not correct. Let me explain. We only know about a node if they send a NODEINFO packet. This includes node user data such as Name, role, position, etc. So after we receive this packet, we fill the database with that information. However, sometimes we learn about a node before we receive a node info update, e.g., when someone sends Telemetry or a Traceroute or a Message even. In that case, we create a node record and temporarily assume CLIENT_HIDDEN. Because a client that never broadcasts node info is a hidden client. However, if we receive a NODEINFO packet later, we update the database record based on their node ID. So initially, you will see many hidden clients but that list will clean up after a couple of hours.

adam commented

2026-10-04 23:00:15 +02:00

Thanks for the reply .
Here's the thing on my install - even after a day or 2 I still get a lot of unknown nodes.. And our mesh is very static , so they can't be "real" new nodes.

Is it possible that the matching of user info to existing node isn't working well?

Also, why not use the node info the connected meshtastic node already has?

Sent from my Galaxy

-------- Original message --------
From: l5y @.>
Date: 20/11/2025 17:05 (GMT+02:00)
To: l5yth/potato-mesh @.>
Cc: Leonid Tsitalovski @.>, Author @.>
Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473)

[https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558542429

Hi, thanks for your feedback.

The AI analysis is not correct. Let me explain.

We only know about a node if they send a NODEINFO packet. This includes node user data such as Name, role, position, etc.

So after we receive this packet, we fill the database with that information.

However, sometimes we learn about a node before we receive a node info update, e.g., when someone sends Telemetry or a Traceroute or a Message even.

In that case, we create a node record and temporarily assume CLIENT_HIDDEN. Because a client that never broadcasts node info is a hidden client.

However, if we receive a NODEINFO packet later, we update the database record based on their node ID. So initially, you will see many hidden clients but that list will clean up after a couple of hours.

—
Reply to this email directly, view it on GitHubhttps://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558542429, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC3HYRNKFJUDW5ASH2W5EHT35XKDZAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYGU2DENBSHE.
You are receiving this because you authored the thread.Message ID: @.***>

Thanks for the reply . Here's the thing on my install - even after a day or 2 I still get a lot of unknown nodes.. And our mesh is very static , so they can't be "real" new nodes. Is it possible that the matching of user info to existing node isn't working well? Also, why not use the node info the connected meshtastic node already has? Sent from my Galaxy -------- Original message -------- From: l5y ***@***.***> Date: 20/11/2025 17:05 (GMT+02:00) To: l5yth/potato-mesh ***@***.***> Cc: Leonid Tsitalovski ***@***.***>, Author ***@***.***> Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473) [https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558542429> Hi, thanks for your feedback. The AI analysis is not correct. Let me explain. We only know about a node if they send a NODEINFO packet. This includes node user data such as Name, role, position, etc. So after we receive this packet, we fill the database with that information. However, sometimes we learn about a node before we receive a node info update, e.g., when someone sends Telemetry or a Traceroute or a Message even. In that case, we create a node record and temporarily assume CLIENT_HIDDEN. Because a client that never broadcasts node info is a hidden client. However, if we receive a NODEINFO packet later, we update the database record based on their node ID. So initially, you will see many hidden clients but that list will clean up after a couple of hours. — Reply to this email directly, view it on GitHub<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558542429>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC3HYRNKFJUDW5ASH2W5EHT35XKDZAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYGU2DENBSHE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

adam commented

2026-10-04 23:00:16 +02:00

Thanks again for reporting.

I can confirm this is a regression. Sorry for that. Can you install 0.5.5 while I work on a fix?

Thanks again for reporting. I can confirm this is a regression. Sorry for that. Can you install 0.5.5 while I work on a fix?

adam commented

2026-10-04 23:00:17 +02:00

I did.. I don't think that helped. Should I clear the DB as well?

Also, on the web server or on the ingestor?

Sent from my Galaxy

-------- Original message --------
From: l5y @.>
Date: 20/11/2025 17:15 (GMT+02:00)
To: l5yth/potato-mesh @.>
Cc: Leonid Tsitalovski @.>, Author @.>
Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473)

[https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558604027

Thanks again for reporting.

I can confirm this is a regression. Sorry for that. Can you install 0.5.5 while I work on a fix?

—
Reply to this email directly, view it on GitHubhttps://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558604027, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC3HYRI5DJ4F7ZRWIWWQ4Z335XLJZAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYGYYDIMBSG4.
You are receiving this because you authored the thread.Message ID: @.***>

I did.. I don't think that helped. Should I clear the DB as well? Also, on the web server or on the ingestor? Sent from my Galaxy -------- Original message -------- From: l5y ***@***.***> Date: 20/11/2025 17:15 (GMT+02:00) To: l5yth/potato-mesh ***@***.***> Cc: Leonid Tsitalovski ***@***.***>, Author ***@***.***> Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473) [https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558604027> Thanks again for reporting. I can confirm this is a regression. Sorry for that. Can you install 0.5.5 while I work on a fix? — Reply to this email directly, view it on GitHub<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558604027>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC3HYRI5DJ4F7ZRWIWWQ4Z335XLJZAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYGYYDIMBSG4>. You are receiving this because you authored the thread.Message ID: ***@***.***>

adam commented

2026-10-04 23:00:17 +02:00

Thanks again for reporting.

I can confirm this is a regression. Sorry for that. Can you install 0.5.5 while I work on a fix?

same problem here with v0.5.6-rc0

> Thanks again for reporting. > > I can confirm this is a regression. Sorry for that. Can you install 0.5.5 while I work on a fix? same problem here with v0.5.6-rc0

adam commented

2026-10-04 23:00:18 +02:00

I have not yet identified the issue but I confirmed that I see the same problem on my instance.

I'm still investigating but I know already that this issue has been introduced after the latest release, so you are safe as long as you stick to the official releases, e.g., 0.5.5

I have not yet identified the issue but I confirmed that I see the same problem on my instance. I'm still investigating but I know already that this issue has been introduced after the latest release, so you are safe as long as you stick to the official releases, e.g., 0.5.5

adam commented

2026-10-04 23:00:19 +02:00

OK.. So should I clear the DB and regress both web and ingestor to 0.5.5 ?

Sent from my Galaxy

-------- Original message --------
From: l5y @.>
Date: 20/11/2025 17:27 (GMT+02:00)
To: l5yth/potato-mesh @.>
Cc: Leonid Tsitalovski @.>, Author @.>
Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473)

[https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558663260

I have not yet identified the issue but I confirmed that I see the same problem on my instance.

I'm still investigating but I know already that this issue has been introduced after the latest release, so you are safe as long as you stick to the official releases, e.g., 0.5.5

—
Reply to this email directly, view it on GitHubhttps://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558663260, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC3HYROZNBB5VOUNXYJWY5T35XMXTAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYGY3DGMRWGA.
You are receiving this because you authored the thread.Message ID: @.***>

OK.. So should I clear the DB and regress both web and ingestor to 0.5.5 ? Sent from my Galaxy -------- Original message -------- From: l5y ***@***.***> Date: 20/11/2025 17:27 (GMT+02:00) To: l5yth/potato-mesh ***@***.***> Cc: Leonid Tsitalovski ***@***.***>, Author ***@***.***> Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473) [https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558663260> I have not yet identified the issue but I confirmed that I see the same problem on my instance. I'm still investigating but I know already that this issue has been introduced after the latest release, so you are safe as long as you stick to the official releases, e.g., 0.5.5 — Reply to this email directly, view it on GitHub<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558663260>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC3HYROZNBB5VOUNXYJWY5T35XMXTAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYGY3DGMRWGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

adam commented

2026-10-04 23:00:20 +02:00

I think the issue stems from the ingestor. Maybe just using the older version of an ingestor works for now.

I think the issue stems from the ingestor. Maybe just using the older version of an ingestor works for now.

adam commented

2026-10-04 23:00:21 +02:00

OK, will try.

Sent from my Galaxy

-------- Original message --------
From: l5y @.>
Date: 20/11/2025 18:06 (GMT+02:00)
To: l5yth/potato-mesh @.>
Cc: Leonid Tsitalovski @.>, Author @.>
Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473)

[https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558848646

I think the issue stems from the ingestor. Maybe just using the older version of an ingestor works for now.

—
Reply to this email directly, view it on GitHubhttps://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558848646, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC3HYRNRCMWKMRN6IZPV4BD35XRGTAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYHA2DQNRUGY.
You are receiving this because you authored the thread.Message ID: @.***>

OK, will try. Sent from my Galaxy -------- Original message -------- From: l5y ***@***.***> Date: 20/11/2025 18:06 (GMT+02:00) To: l5yth/potato-mesh ***@***.***> Cc: Leonid Tsitalovski ***@***.***>, Author ***@***.***> Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473) [https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558848646> I think the issue stems from the ingestor. Maybe just using the older version of an ingestor works for now. — Reply to this email directly, view it on GitHub<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558848646>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC3HYRNRCMWKMRN6IZPV4BD35XRGTAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYHA2DQNRUGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

adam commented

2026-10-04 23:00:21 +02:00

Please confirm if the behaviour stops using 0.5.5 if possible.

Please confirm if the behaviour stops using 0.5.5 if possible.

adam commented

2026-10-04 23:00:22 +02:00

Can't yet , as one of the ingestors is not under my control..

Sent from my Galaxy

-------- Original message --------
From: l5y @.>
Date: 20/11/2025 18:28 (GMT+02:00)
To: l5yth/potato-mesh @.>
Cc: Leonid Tsitalovski @.>, Author @.>
Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473)

[https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558963479

Please confirm if the behaviour stops using 0.5.5 if possible.

—
Reply to this email directly, view it on GitHubhttps://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558963479, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC3HYRIG3PEGAD3WP3ZUQT335XT2NAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYHE3DGNBXHE.
You are receiving this because you authored the thread.Message ID: @.***>

Can't yet , as one of the ingestors is not under my control.. Sent from my Galaxy -------- Original message -------- From: l5y ***@***.***> Date: 20/11/2025 18:28 (GMT+02:00) To: l5yth/potato-mesh ***@***.***> Cc: Leonid Tsitalovski ***@***.***>, Author ***@***.***> Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473) [https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558963479> Please confirm if the behaviour stops using 0.5.5 if possible. — Reply to this email directly, view it on GitHub<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3558963479>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC3HYRIG3PEGAD3WP3ZUQT335XT2NAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJYHE3DGNBXHE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

adam commented

2026-10-04 23:00:23 +02:00

The bug was introduced in #469 @YO3IBZ sorry - I have to revert this.

I'll do some more testing and then tag a new docker build for you to test.

The bug was introduced in #469 @YO3IBZ sorry - I have to revert this. I'll do some more testing and then tag a new docker build for you to test.

adam commented

2026-10-04 23:00:24 +02:00

Not sure if 0.5.5 solves it:

both are the same node...

Not sure if 0.5.5 solves it: <img width="565" height="264" alt="Image" src="https://github.com/user-attachments/assets/5d655107-6a86-49ae-9cb5-ab18eb709aa9" /> both are the same node...

adam commented

2026-10-04 23:00:24 +02:00

Yes, I cannot undo the damage, I can only patch the bug. Sorry.

You can either reset the database or wait seven days for those nodes to get flushed from the front end.

But staying on v0.5.5 helps to not add more incorrect node records.

Yes, I cannot undo the damage, I can only patch the bug. Sorry. You can either reset the database or wait seven days for those nodes to get flushed from the front end. But staying on v0.5.5 helps to not add more incorrect node records.

adam commented

2026-10-04 23:00:25 +02:00

Resetting DB now.

Sent from my Galaxy

-------- Original message --------
From: l5y @.>
Date: 20/11/2025 20:17 (GMT+02:00)
To: l5yth/potato-mesh @.>
Cc: Leonid Tsitalovski @.>, Author @.>
Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473)

[https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3559416380

Yes, I cannot undo the damage, I can only patch the bug. Sorry.

You can either reset the database or wait seven days for those nodes to get flushed from the front end.

But staying on v0.5.5 helps to not add more incorrect node records.

—
Reply to this email directly, view it on GitHubhttps://github.com/l5yth/potato-mesh/issues/473#issuecomment-3559416380, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC3HYRLUXPWH7V4JDALTXET35YATTAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJZGQYTMMZYGA.
You are receiving this because you authored the thread.Message ID: @.***>

Resetting DB now. Sent from my Galaxy -------- Original message -------- From: l5y ***@***.***> Date: 20/11/2025 20:17 (GMT+02:00) To: l5yth/potato-mesh ***@***.***> Cc: Leonid Tsitalovski ***@***.***>, Author ***@***.***> Subject: Re: [l5yth/potato-mesh] Lot's of unknown hidden clients, until I restart the ingestor... (Issue #473) [https://avatars.githubusercontent.com/u/220195275?s=20&v=4]l5yth left a comment (l5yth/potato-mesh#473)<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3559416380> Yes, I cannot undo the damage, I can only patch the bug. Sorry. You can either reset the database or wait seven days for those nodes to get flushed from the front end. But staying on v0.5.5 helps to not add more incorrect node records. — Reply to this email directly, view it on GitHub<https://github.com/l5yth/potato-mesh/issues/473#issuecomment-3559416380>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC3HYRLUXPWH7V4JDALTXET35YATTAVCNFSM6AAAAACMVRGCTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNJZGQYTMMZYGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

adam commented

2026-10-04 23:00:26 +02:00

It should be fixed. You can try to upgrade to tag v0.5.6-rc1.

Thanks again for reporting, I would have noticed this way too late. This regression actually caused some damage, unfortunately.

It was introduced in #469 which resolved #426 but regressed to the wrong IDs being created from the wrong ID field (using message ID as node ID, unforatunately).

It's imporant to note that the web app is not affected, only upgrading the ingestors is enough.

It should be fixed. You can try to upgrade to tag `v0.5.6-rc1`. Thanks again for reporting, I would have noticed this way too late. This regression actually caused some damage, unfortunately. It was introduced in #469 which resolved #426 but regressed to the wrong IDs being created from the wrong ID field (using message ID as node ID, unforatunately). It's imporant to note that the web app is not affected, only upgrading the ingestors is enough.

adam commented

2026-10-04 23:00:26 +02:00

Got it. will try it as soon as docker images are up.
" (using message ID as node ID, unforatunately)." this explains the strange IDs i was seeing!

Got it. will try it as soon as docker images are up. " (using message ID as node ID, unforatunately)." this explains the strange IDs i was seeing!

adam commented

2026-10-04 23:00:27 +02:00

Docker images are up 👍

Docker images are up 👍

adam commented

2026-10-04 23:00:28 +02:00

Already deployed 😄

Already deployed 😄

adam commented

2026-10-04 23:00:28 +02:00

I've run the query to clean nodes on sqlite like
DELETE FROM nodes WHERE long_name LIKE 'Meshtastic%' AND (hw_model IS NULL OR hw_model = '');

I think connected tables will be cleaned in a week so it should be ok.

I've run the query to clean nodes on sqlite like `DELETE FROM nodes WHERE long_name LIKE 'Meshtastic%' AND (hw_model IS NULL OR hw_model = ''); ` I think connected tables will be cleaned in a week so it should be ok.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/potato-mesh#85