System Uptime shellsensor device

---

Here’s a device that tells you the actual system uptime.
The idea came from n3rogit at issue pimatic/pimatic#546

create a script in your homedirectory called uptime.sh :

#!/bin/bash
# uptime.sh
# get uptime from /proc/uptime

uptime=$(</proc/uptime)
uptime=${uptime%%.*}

seconds=$(( uptime%60 ))
minutes=$(( uptime/60%60 ))
hours=$(( uptime/60/60%24 ))
days=$(( uptime/60/60/24 ))

echo "$days days $hours hours $minutes minutes $seconds seconds"

then you can use your device like this :

    {
      "id": "system-uptime",
      "name": "System uptime",
      "class": "ShellSensor",
      "attributeName": "Uptime",
      "attributeType": "string",
      "attributeUnit": "",
      "command": "sudo bash /home/pi/uptime.sh",
      "interval": 60000
    }

you can leave the seconds away at the echo in the script.
the gui will show up more cheerful on mobile devices.

@leader21 Is this written to the database? If so, is there a way to stop that (reducing writes).

@sweebee
no it’s not written to the DB. the attribute type is “sting”, therefore no logging

if using systemsensor devices have a look here : http://forum.pimatic.org/topic/14/database-tips/3 to reduce database writings

@leader21 is it possible to display hours and minutes, too? actually uptime-days are displayed. This is a little bit unaccurate
or is the misstake on my side?

ok i see. need to check the sed and the match i guess
will have a look at this later - or if you want to, feel free to play around a bit on your own.
if you’ve found out, go ahead and let us know.

i’ve tried a bit, but it seems too difficult for my “sed-skills”, because matching the first 24 hours is different to them after…

ok think i got it.
try this please and tell me if it worked (since my uptime is below 1day)

"command": "/usr/bin/uptime | /bin/sed 's/.*up \\([^user]*\\), .*/\\1/'",

nope, in that case i get the full “uptime-output”

 17:51:05 up 5 days,  1:03,  2 users,  load average: 0,43, 0,36, 0,29

(in terminal without the escaped backslashes tested)

hm … the command works that way on another pi without pimatic.

on my pimatic pi it has this output :

and the gui

please doublecheck at the shell if this matches your command :
usr/bin/uptime | /bin/sed 's/.*up \([^user]*\), .*/\1/'

root@bananapi ~ # /usr/bin/uptime | /bin/sed 's/.*up \([^user]*\), .*/\1/'
 18:16:03 up 5 days,  1:28,  2 users,  load average: 0,32, 0,32, 0,27
root@bananapi ~ #

sorry, no success

@jensebub
ok bananapi
remove the /bin/ in front of sed. should work globally.
could it be that sed isn’t stored there (guess you’re using bananian?)
but usually you would get an error if sed wouldn’t be found

nice try, but same result
i have tried before i post
it’s not the reason,… the old command with “sed” is working, but not right

@jensebub
but why does it work on a debian / pi then?
argh! sed, awk, regexp …

i’ll try some more.

@leader21 i’ve no clou,…
a second try on a pi without pimatic:

root@raspicam:~# /usr/bin/uptime | /bin/sed 's/.*up \([^user]*\), .*/\1/'
 18:38:17 up 22 days, 9 min,  1 user,  load average: 0,04, 0,04, 0,05
root@raspicam:~#

it’s not a bananapi issue,…
thx for helping

very interesting!
i see the difference now (do you see it too )

yours
load average: 0***,32, 0,32, 0,27
mine
load average: 0.32, 0.32, 0.***27

guess the new kernel 3.14 has something to do with it maybe.
i tried another pi now with raspbian 7.6 and Kernel 3.12, there it’s the same output as you have with comma as decimal separator! on my new pis with raspbian 7.8 and kernel 3.14 it’s with a point as decimal separator.

can you check cat proc/version please just to be sure.

and in the newer it is again the comma ?!

root@raspicam:~# cat /proc/version
Linux version 3.18.3+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #741 PREEMPT Fri Jan 23 13:32:52 GMT 2015
root@raspicam:~# uptime
 19:33:36 up 22 days,  1:04,  2 users,  load average: 0,01, 0,03, 0,05
root@raspicam:~#

and

root@bananapi ~ # cat /proc/version
Linux version 3.4.104+ (root@nico-desktop) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-16ubuntu4) ) #1 SMP PREEMPT Thu Jan 8 15:40:40 CET 2015
root@bananapi ~ # uptime
 19:52:13 up 5 days,  3:04,  2 users,  load average: 0,28, 0,27, 0,25
root@bananapi ~ #

what about the systemlanguage?!

damn it! ok, very last try with awk.
uptime | grep -ohe 'up .*' | sed 's/,//g' | awk '{ print $2 $3 $4}'
should bring you

but only if uptime is below 1 day, otherwise you will see the users, since the parameters $ are shifting over.

tested on three different systems with the same result
i’ll try to get a space after days. if this fails, it’s a cosmetic bug

not nice but right

root@bananapi ~ # uptime | grep -ohe 'up .*' | sed 's/,//g' | awk '{ print $2 $3 $4}'
5days3:10
root@bananapi ~ #

thx

isn’t it much easier to go ahead with:
cat /proc/uptime and calculate the days, hours and minutes?

yes it is
thought about it some minutes ago.

what about this here :

create a script :

#!/bin/bash
# uptime.sh
# get uptime from /proc/uptime

uptime=$(</proc/uptime)
uptime=${uptime%%.*}

seconds=$(( uptime%60 ))
minutes=$(( uptime/60%60 ))
hours=$(( uptime/60/60%24 ))
days=$(( uptime/60/60/24 ))

echo "$days days, $hours hours, $minutes minutes, $seconds seconds"

then you can use your device like this :

    {
      "id": "system-uptime",
      "name": "System uptime",
      "class": "ShellSensor",
      "attributeName": "Uptime",
      "attributeType": "string",
      "attributeUnit": "",
      "command": "sudo bash /home/pi/uptime.sh",
      "interval": 60000
    }

guess this will do it.
Well, I’m done for today

p.s.: leave the seconds away at the echo in the script. the gui will show up more cheerful on mobile devices

much more komfortable

Thx