using openhabian-config i’ve updated OH, and rebooted. however the screen shot is misreporting, i think? is it a bug?
Your screenshot shows OH 4.2.3, which is the most recent version.
Least thing you would need to do is to tell what you actually think is wrong (i.e. “misreported”).
Uptime misreported.
You did not reboot.
If you had rebooted, your screenshot would not look like this.
my var/log/messages seems to indicate there was a reboot? unless im reading this incorrectly, which is possible.
The “report” seems to be generated after logging in. This happens after you see the login screen (on my systems since login it seems to work like this since long). Try “cat .firemotd” some seconds later and you will see the updated report. If you are impatient, you see an empty report. Just try again.
1 Like
thanks for explaining. sounds like a minor bug then and nothing to worry about.
This behaviour extends IMHO to all information - and is not only connected to a reboot.
If you e.g. apt upgrade the system (regardless if via console directly or with openHABian menu), it still shows available upgrades, even though you upgraded a few minutes/hours ago.
seems like a bug in firemotd, that’s still here after some time (initially experienced this like a year or longer ago?). but it seems firemotd is abondened?
1 Like
Same reason, see above. What you see at login is old info generated at last login saved in ~/.firemotd (as part of openhabian scripts). I was told by someone, this is because of my system is not ok.
1 Like
Firemotd is broken and abandoned.
There’s plans but not enough volunteer’s time for a replacement.
even if it can’t be replaced, would it be better to remove the motd and have nothing, rather than reporting out of date/incorrect data? just a suggestion, not sure how easy it would be.
Check your .bash_profile file.
if [ -f ~/.firemotd-cache ]; then
cat ~/.firemotd-cache
fi
(FireMotD --theme Gray > ~/.firemotd-cache &) &>/dev/null # does not use cache; might get removed in the near future