Software and hardware
Meshtastic-bot Version: 2.0.0
Meshtastic Hardware: HELTEC_V4
Meshtastic firmware version: 2.7.20
Deployment method: Docker
Issue
While beginning to test #74 on the latest release of the bot, I've noticed that when starting the docker container, I'm seeing StorageAPI.store_node errors flood the terminal. These look to be occurring when the bot is cycling through the node database on startup for data to publish to the API.
meshtastic-bot | 2026-05-22 07:40:02,734 - [INFO] bot._on_packet - Skipping API submission for packet with portnum ROUTING_APP (in IGNORE_PORTNUMS)
meshtastic-bot | 2026-05-22 07:40:05,933 - [INFO] bot._on_packet - Skipping API submission for packet with portnum ROUTING_APP (in IGNORE_PORTNUMS)
meshtastic-bot | 2026-05-22 07:40:34,251 - [INFO] bot._on_packet - Skipping API submission for packet with portnum 345 (in IGNORE_PORTNUMS)
meshtastic-bot | 2026-05-22 07:42:25,838 - [INFO] packet_dump.<module> - Not dumping packets - set DUMP_PACKETS_PORTNUMS to comma separated list of portnums to dump
meshtastic-bot | 2026-05-22 07:42:25,901 - [INFO] __init__.__init__ - Connected to SqliteUserPrefsPersistence DB at data/user_prefs.sqlite
meshtastic-bot | 2026-05-22 07:42:25,903 - [INFO] __init__.__init__ - Connected to SqliteCommandLogger DB at data/user_cmds.sqlite
meshtastic-bot | 2026-05-22 07:42:25,904 - [INFO] __init__.__init__ - Connected to SqliteNodeDB DB at data/node_db.sqlite
meshtastic-bot | 2026-05-22 07:42:25,904 - [INFO] radio.connect - MeshtasticRadio: connecting to 192.168.178.174...
meshtastic-bot | 2026-05-22 07:42:26,799 - [INFO] radio.connect - MeshtasticRadio: TCP interface created; awaiting library connect event
meshtastic-bot | 2026-05-22 07:42:27,006 - [ERROR] StorageAPI.store_node - HTTP error storing node: {"position":{"meshtastic_location_source":["This field may not be null."]},"device_metrics":{"meshtastic_channel_utilization":["This field may not be null."],"meshtastic_air_util_tx":["This field may not be null."]}}
meshtastic-bot | 2026-05-22 07:42:27,343 - [ERROR] StorageAPI.store_node - HTTP error storing node: {"position":{"meshtastic_location_source":["This field may not be null."]},"device_metrics":{"meshtastic_channel_utilization":["This field may not be null."],"meshtastic_air_util_tx":["This field may not be null."]}}
meshtastic-bot | 2026-05-22 07:42:27,718 - [ERROR] StorageAPI.store_node - HTTP error storing node: {"position":{"meshtastic_location_source":["This field may not be null."]},"device_metrics":{"meshtastic_channel_utilization":["This field may not be null."],"meshtastic_air_util_tx":["This field may not be null."]}}
meshtastic-bot | 2026-05-22 07:42:28,079 - [ERROR] StorageAPI.store_node - HTTP error storing node: {"position":{"meshtastic_location_source":["This field may not be null."]},"device_metrics":{"meshtastic_channel_utilization":["This field may not be null."],"meshtastic_air_util_tx":["This field may not be null."]}}
...
meshtastic-bot | 2026-05-22 07:31:47,452 - [INFO] radio._on_connection_established - MeshtasticRadio: connection established (!b2a7c318)
meshtastic-bot | 2026-05-22 07:31:47,452 - [INFO] bot._on_connection_established - Connected as !b2a7c318 (nodenum=2997338904)
meshtastic-bot | 2026-05-22 07:31:47,588 - [INFO] StorageAPI.report_bot_version - Reported bot version 2.0.0 to API
This does eventually stop once the nodes have been cycled through. I've been running for an hour and a half so far and haven't seen the error pop up again. There are 56 nodes online at the moment, so I'm assuming (I assume a lot, it's a me problem) that the error only occurs on startup, but not when receiving live packets over the radio.
Would it just be adding noise to things if the impacted node was detailed in the error?
Software and hardware
Meshtastic-bot Version: 2.0.0
Meshtastic Hardware: HELTEC_V4
Meshtastic firmware version: 2.7.20
Deployment method: Docker
Issue
While beginning to test #74 on the latest release of the bot, I've noticed that when starting the docker container, I'm seeing
StorageAPI.store_nodeerrors flood the terminal. These look to be occurring when the bot is cycling through the node database on startup for data to publish to the API.This does eventually stop once the nodes have been cycled through. I've been running for an hour and a half so far and haven't seen the error pop up again. There are 56 nodes online at the moment, so I'm assuming (I assume a lot, it's a me problem) that the error only occurs on startup, but not when receiving live packets over the radio.
Would it just be adding noise to things if the impacted node was detailed in the error?