search

meshtastic / python

The Python CLI and API for talking to Meshtastic devices
https://meshtastic.org
335 stars 151 forks source link

If we receive node updates, we must create missing DB entries #2

Closed geeksville closed 4 years ago

geeksville commented 4 years ago

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/3-device-mesh-error-on-device-connected-via-usb/450/2

nicetechguy commented 4 years ago

Error at end of log appears when second node is powered on in range. Just a guess..Could this be due to each device being upgraded/reflashed one at a time from 0.7.4 to 0.7.5 and not being recongised correctly even though it had the same ID?

log-error-meshtastic-202006180839.txt

geeksville commented 4 years ago

oh thanks! No it is a bug in the python library. It is the libaries responsibility to update the nodedb when new nodes show up and it isn't doing that I'll fix now.

geeksville commented 4 years ago

Thank you for the report @nicetechguy. Fixed in 0.7.5 just released to pypi.

nicetechguy commented 4 years ago

Thank you for the prompt assist!

Excited to see how this project progresses going forwards - hoping it will be the best fit for our use case :)

nicetechguy commented 4 years ago

updated just now and encountering another error:

ERROR:root:Node not found for fromId ERROR:root:Error handling FromRadio, possibly corrupted? name 'num' is not defined

log-error-meshtastic-202006181030.txt

nicetechguy commented 4 years ago

Looks good now on 0.7.6 - thanks :)