On the map there are currently 2 nodes with type set to 0.
Valid node types should be 1–4 (companion, repeater, room server, sensor).
These nodes appear to advertise this type by the devices themselves with flags & 0x0F == 0(ADV_TYPE_NONE), likely due to bad or custom firmware.
The map cannot display these nodes because there is no valid icon for this type.
How other MeshCore applications handle type 0 nodes has not been verified.
Should we allow type: 0 nodes on map.meshcore.dev? Is there any need for it?
If not, can be fixed:
Uploader-side: Filter them out by skipping adverts where parsed.type === 'NONE' (in map.meshcore.dev-uploader) ?
API-side: Reject or normalize type: 0 when processing uploads (would cover uploader, app, (and I guess, depreciated web uploads?))
If so, this should be reported in different repo
On the map there are currently 2 nodes with `type` set to `0`.
Valid node types should be 1–4 (companion, repeater, room server, sensor).
These nodes appear to advertise this type by the devices themselves with `flags & 0x0F == 0` `(ADV_TYPE_NONE)`, likely due to bad or custom firmware.
The map cannot display these nodes because there is no valid icon for this type.
How other MeshCore applications handle type 0 nodes has not been verified.
- Should we allow `type: 0` nodes on [map.meshcore.dev](https://map.meshcore.dev)? Is there any need for it?
If not, can be fixed:
- Uploader-side: Filter them out by skipping adverts where `parsed.type === 'NONE'` (in map.meshcore.dev-uploader) ?
- API-side: Reject or normalize `type: 0` when processing uploads (would cover uploader, app, (and I guess, depreciated web uploads?))
If so, this should be reported in [different repo](https://github.com/meshcore-dev/map.meshcore.dev)
<!-- github-sync-id:4018929510 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On the map there are currently 2 nodes with
typeset to0.Valid node types should be 1–4 (companion, repeater, room server, sensor).
These nodes appear to advertise this type by the devices themselves with
flags & 0x0F == 0(ADV_TYPE_NONE), likely due to bad or custom firmware.The map cannot display these nodes because there is no valid icon for this type.
How other MeshCore applications handle type 0 nodes has not been verified.
type: 0nodes on map.meshcore.dev? Is there any need for it?If not, can be fixed:
parsed.type === 'NONE'(in map.meshcore.dev-uploader) ?type: 0when processing uploads (would cover uploader, app, (and I guess, depreciated web uploads?))If so, this should be reported in different repo
type 0 adverts are now blocked in the map.meshcore.dev api