what happens if you try it again? I assume the Firmware: rpi-pico 2.0.4.46d7b82 has something to do with this as I can't understand how this happened. I am checking for nodes if not respond, how there is a none here is curious.
what happens if you try it a second time? do you have any other nodes in the area or is there nothing but the bot? @Hailo1999
what happens if you try it again? I assume the Firmware: rpi-pico 2.0.4.46d7b82 has something to do with this as I can't understand how this happened. I am checking for nodes if not respond, how there is a none here is curious.
what happens if you try it a second time? do you have any other nodes in the area or is there nothing but the bot? @Hailo1999
<!-- github-comment-id:2274252143 -->
The 2nd attempt leads to the error in the last line. I already have a heltec that I could connect to meshing-around, but I wanted to use the Pico Pi for this. I can also flash the Pico Pi back to 2.3.15. I have a little more time to test again on Friday
The 2nd attempt leads to the error in the last line. I already have a heltec that I could connect to meshing-around, but I wanted to use the Pico Pi for this. I can also flash the Pico Pi back to 2.3.15. I have a little more time to test again on Friday
<!-- github-comment-id:2274286572 -->
@tavdog are you running official firmware? if so I assume your node was so new, I will try and trap this better
> then just started working randomly.
@tavdog are you running official firmware? if so I assume your node was so new, I will try and trap this better
<!-- github-comment-id:2274437964 -->
The 2nd attempt leads to the error in the last line. I already have a heltec that I could connect to meshing-around, but I wanted to use the Pico Pi for this. I can also flash the Pico Pi back to 2.3.15. I have a little more time to test again on Friday
@Hailo1999 I would be interested to know if updating firmware resolves this
> The 2nd attempt leads to the error in the last line. I already have a heltec that I could connect to meshing-around, but I wanted to use the Pico Pi for this. I can also flash the Pico Pi back to 2.3.15. I have a little more time to test again on Friday
@Hailo1999 I would be interested to know if updating firmware resolves this
<!-- github-comment-id:2274438503 -->
@Hailo1999 and @tavdog if you can pull the latest, and if by chance you can recreate the error would like to see what its putting in the node table
@Hailo1999 and @tavdog if you can pull the latest, and if by chance you can recreate the error would like to see what its putting in the node table
<!-- github-comment-id:2274495616 -->
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.
I tried the sitrep command, unfortunately the error occurs again. If I'm not mistaken, we've had this before.
Hardware: Pico Pi
Firmware: rpi-pico 2.0.4.46d7b82
what happens if you try it again? I assume the Firmware: rpi-pico 2.0.4.46d7b82 has something to do with this as I can't understand how this happened. I am checking for nodes if not respond, how there is a none here is curious.
what happens if you try it a second time? do you have any other nodes in the area or is there nothing but the bot? @Hailo1999
The 2nd attempt leads to the error in the last line. I already have a heltec that I could connect to meshing-around, but I wanted to use the Pico Pi for this. I can also flash the Pico Pi back to 2.3.15. I have a little more time to test again on Friday
I'm seeing this too on esp32 station-g1
then just started working randomly.
@tavdog are you running official firmware? if so I assume your node was so new, I will try and trap this better
@Hailo1999 I would be interested to know if updating firmware resolves this
patched for better errors for this
@Hailo1999 and @tavdog if you can pull the latest, and if by chance you can recreate the error would like to see what its putting in the node table
I deleted the pkl files and reset node db. This is the error . Still seemed to work though. That Kulamalu node might have slightly older firmware.
thank you @tavdog appears it has a value of None for new nodes with no last heard value.