meshtastic
[Bug]: No last seen time Raspberry PI with Waveshare Hat
Category
Other
Hardware
Other
Firmware Version
2.4.1.394e0e1
Description
On the Raspberry PI version the time since seen does not change from "Never". You can see in the image, at least 5 of the nodes have been contacted in the last couple of minutes.
Relevant log output
No response
I'm not seeing that problem on a Pi4. Times seem to update about every 5 seconds.
What OS and hardware are you running?
It is A Pi4 running Bookworm Lite I also have a Pi3 also running Bookworm Lite with the same issue. If I look at the app it does show time until I disconnect then reconnect and the last seen reset to never. When I look at the web page it never give a time on the last seen. I have reinstalled the Pi4 and it makes no difference.
It is A Pi4 running Bookworm Lite I also have a Pi3 also running Bookworm Lite with the same issue. If I look at the app it does show time until I disconnect then reconnect and the last seen reset to never. When I look at the web page it never give a time on the last seen. I have reinstalled the Pi4 and it makes no difference.
Are you able to see if it works with RaspberryPi OS? Seems like it could be an OS issue since both of your Pis are running Bookworm Lite. Another thing to try would be building from source if you don't have a spare SD card and don't want to nuke your current OS.
I also just noticed that 5 of the nodes on your list are from MQTT. You aren't using the default channel right...?
Hello, yes bookworm is one of the standard Raspberry Pi OS I just use the one without the desktop as I only connect via SSH and do not have a screen or keyboard attached. I will try compiling from source I will have to do that tomorrow. I have no issue nuking the card as it is all that is on the Pi4 except for MQTT server.
The MQTT server is running on the Pi4 I have my 4 connected locally and my brother in law is running a couple connected via MQTT and a 433MHz node connected via MQTT. I am using the default channel as channel 1, 2 custom channels.
The MQTT is a custom server that is running on the Pi4.
Strange occurrence for some reason a couple of days ago it started to work as expected. I have up dated to 2.4.3.efc27f2 and the problem is back. If you look at the image the ones at the top with times are from before the up date then the ones with never are the ones after the update.
As soon as I have time I will start to look through the code to see if I can spot the problem.
Raspberry PI Pico w with waveshare lora here does not get last seen either, and wifi is not working and its not showing a bluetooth (I need to look again if this thing even has bluetooth, i dont remember) but i can see it when i hook up to serial port and bring up the web interface and send messages through that.
On Fri, Aug 16, 2024 at 8:55 AM Spogster @.***> wrote:
Strange occurrence for some reason a couple of days ago it started to work as expected. I have up dated to 2.4.3.efc27f2 and the problem is back. If you look at the image the ones at the top with times are from before the up date then the ones with never are the ones after the update.
As soon as I have time I will start to look through the code to see if I can spot the problem.
meshtastic.2.jpg (view on web)
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
I have some Picos and never had an issue with no last seen. As for the WIFI that works great but never tried bluetooth.
Ok i will try again to get it online with wifi, I just cannot see the bluetooth even though the config says it is turned on.... The web console does not seem to work well for most of my devices so I prefer to configure things on my android through bluetooth when I can.
On Fri, Aug 16, 2024 at 12:42 PM Spogster @.***> wrote:
I have some Picos and never had an issue with no last seen. As for the WIFI that works great but never tried bluetooth.
— Reply to this email directly, view it on GitHub https://github.com/meshtastic/firmware/issues/4416#issuecomment-2293353470, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEVF3FPXAASWXEXDQAFZ3S3ZRXQSLAVCNFSM6AAAAABMF5ZDEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJTGM2TGNBXGA . You are receiving this because you commented.Message ID: @.***>
If you have WiFi turned on it will turn off the Bluetooth. I always configure my devices initially with the python script on the serial then via WiFi using the app on IP.
Seems like this is probably fixed. Please re-open if it's still an issue.
