This is odd! I’ve just checked my log file and it is appending to the end as usual. Are you using the wfpiconsole start command to start the console manually, or do you have it setup to autostart at boot?
Of course it is! Writing the newest entry to the top of a log file is extremely write-intensive, and would kill the SD card’s write lifetime in short order. That’s why logs in the Unix/Linux world always append to the end of files, and why logrotate routines rename/delete old log files rather than trim old entries from the top of an existing file as they expire…
Auto starting on boot @peter . Happy to send you a log to prove it’s logging in reverse for me.
Thanks so much for this excellent program, I’m displaying on a 20" monitor…I’m having the same issue, the mouse does not work.Is there any update on this?
Not yet, sorry! It completely slipped my mind. Are you also using a pi3?
Yes a PI 3 B+
thanks!
Hello,
I’ve been using PiConsole for a couple years now and it’s been great. I have it running on two devices in two different rooms, both connected to the same Tempest.
As of a couple days ago, they stopped displaying data and say “Station Status: Offline”.
Looking at the logs when starting the service, it says “AUTHORIZATION REQUIRED - Rate limit exceed or your API Key or Oauth2 Access token missing”.
What could cause me to exceed the rate limit all of a sudden? My usage hasn’t changed. Maybe the rate limit was moved down?
Thanks in advance.
most probably you are using the generic API key we all used at start. You have now to generate your personal key in the app and use that one in the config file.
2 Likes
Hey Eric,
I have been using a personal use token for awhile. I also tried deleting and creating a new one, but get the same results.
I see one key created yesterday and never used (or at least it never asked anything on servers)
Sure there is no space before or after (happens often via copy/paste)
Confirmed there was no space, it is pasted in the config correctly.
can you open the error log and see if there is something that could help narrow the problem (same dir as config file)
Indeed. Just a followup, they swapped out my tempest. Super painless, history follows. Support was 5 out of 5
1 Like
Error: Unable to update local package cache. Please check your internet connection
The connection to the internet is fine. Any assistance is greatly apriciated
Thanks
Gregg
Welcome @greggmarco7,
I moved your question here where some one may help you.
It might pay to read earlier replies to learn what other information you could supply to help people to understand your situation.
Personally I do not have a solution for you sorry.
Good luck cheers Ian 
Sorry you are having issues. Can you open a terminal and run this command
sudo apt update
and let me know what errors you see printed to the screen?
Did you manage to solve this? Someone else face this issue last week - see their post here.
I’ve had a good look into this and I cannot recreate the behaviour you see. Sorry! Everything for me is logging to the bottom of the file as expected. When using the auto start function, all the logging is handled by systemd (I just tell it where to do the logging), so perhaps you have a system setting that has reversed the logging order? Sorry I can’t be of more help!
Thank you so much, that resolved my issue as well. I turned off PiConsole for a couple hours, restarted and everything is working again. Must have been some issue that caused me to disconnect and then timeout, with the failure causing me to get rate limited by the API.
Maybe if the check fails, it should retry at decreasing rates over time. Once every minute for 10 minutes, every 5 minutes for 30 minutes, 30 minutes for 2 hours, etc.
I got this as well “Error: Unable to update local package cache. Please check your internet connection”
I did an apt-get update and got this:
Repository ‘Index of /raspbian buster InRelease’ changed its ‘Suite’ value from ‘stable’ to ‘oldstable’
Researching that lead me to a post saying:
It’s nothing to worry about. The main Raspbian repository tracks the Debian repositories . Debian has just upgraded from Buster to Bullseye.
Which lead me to another post that had this as a solution:
Solution 1. sudo apt-get update --allow-releaseinfo-change
I did this and was able to perform updates as needed
1 Like