Quote from ckruetze on November 7, 2018, 4:16 pm

Not sure if you want/need it but here is a bug report from me. After powering up the clock displays "oboo" instead of the time.

Someone (my daughter) pulled the plug from the clock, so it ran until the battery was empty. I just powered it up again. The clock is displaying "oboo" instead of the time. the cards did load properly and seem to work (only tried the timer and had a look at the weather).

Here are some outputs from the console

root@Oboo-Clock-546C:~# date
Wed Aug 27 02:23:08 CEST 2008
root@Oboo-Clock-546C:~# date
Wed Aug 27 02:28:09 CEST 2008
root@Oboo-Clock-546C:~# ps w
  PID USER       VSZ STAT COMMAND
    1 root      1528 S    /sbin/procd
    2 root         0 SW   [kthreadd]
    3 root         0 SW   [ksoftirqd/0]
    5 root         0 SW<  [kworker/0:0H]
    7 root         0 SW   [kworker/u2:1]
   45 root         0 SW   [kworker/u2:2]
   75 root         0 SW<  [writeback]
   76 root         0 SW<  [crypto]
   82 root         0 SW<  [bioset]
   83 root         0 SW<  [kblockd]
   85 root         0 SW   [kworker/0:1]
  126 root         0 SW   [kswapd0]
  177 root         0 SW   [fsnotify_mark]
  187 root         0 SW   [spi32766]
  217 root         0 SW<  [bioset]
  222 root         0 SW<  [bioset]
  227 root         0 SW<  [bioset]
  232 root         0 SW<  [bioset]
  237 root         0 SW<  [bioset]
  242 root         0 SW<  [bioset]
  247 root         0 SW<  [bioset]
  279 root         0 SW<  [ipv6_addrconf]
  285 root         0 SW<  [deferwq]
  288 root         0 SW<  [kworker/0:1H]
  353 root         0 SW   [kworker/0:2]
  406 root         0 SWN  [jffs2_gcd_mtd6]
  469 root      1180 S    /sbin/ubusd
  470 root       892 S    /sbin/askfirst /usr/libexec/login.sh
  607 root         0 SW<  [krfcommd]
  757 root      1224 S    /sbin/logd -S 64
  766 root      1784 S    /sbin/rpcd
  814 root      1700 S    /sbin/netifd
  832 root      1416 S    /usr/sbin/odhcpd
  870 root      1060 S    /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300
  894 root      1512 S    /usr/sbin/uhttpd -f -h /www -r Oboo-Clock-546C -x /cgi-bin -u /ubus -X -t 60 -T 30 -k 20 -A 1 -n 3 -N 100
  901 nobody    1564 S    avahi-daemon: running [Oboo-Clock-546C.local]
  910 root      1920 S    /usr/sbin/onion-helper
  941 mosquitt  3156 S    mosquitto -c /etc/mosquitto/mosquitto.conf
  955 root      1104 S    /sbin/mountd -f
  991 root      4528 S    /usr/bin/card-manager
 1007 root      1184 S    udhcpc -p /var/run/udhcpc-eth0.pid -s /lib/netifd/dhcp.script -f -t 0 -i eth0 -C -O 121
 1019 root         0 SW   [RtmpCmdQTask]
 1035 root         0 SW   [RtmpWscTask]
 1036 root         0 SW   [RtmpMlmeTask]
 1107 root      1184 S <  /usr/sbin/ntpd -n -N -S /usr/sbin/ntpd-hotplug -p 0.lede.pool.ntp.org -p 1.lede.pool.ntp.org -p 2.lede.po
 1142 root      9160 S    /usr/bin/ort /usr/bin/js/mcu.js
 1143 root      7036 S    /usr/bin/ort /usr/bin/js/weather.js
 1144 root      6380 S    /usr/bin/ort /usr/bin/js/timer.js
 1145 root      7492 S    /usr/bin/ort /usr/bin/js/audio.js
 1146 root      5304 S    /usr/bin/ort /usr/bin/js/music.js
 1147 root      6148 S    /usr/bin/ort /usr/bin/js/system.js
 1271 root       928 S    /sbin/ap_client preference ra0 apcli0 -1,-1,-1,-1,-1,-1 MCLS  letmeHarrislee2day     0
 1380 root      1184 S    udhcpc -p /var/run/udhcpc-apcli0.pid -s /lib/netifd/dhcp.script -f -t 0 -i apcli0 -C -O 121
 1473 dnsmasq   1052 S    /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg02411c -k -x /var/run/dnsmasq/dnsmasq.cfg02411c.pid
 1475 root      1128 S    /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300
 1476 root      1188 S    -ash
 1486 root      1184 R    ps w

And now I tried a "sh /usr/bin/configUpdate.sh" that did the trick and the clock is showing again. Followed by an "onion time sync" to also get the correct date and time.

I'm not 100% sure but I think the current firmware version lacks some stuff that should happen at boot time. To get the clock to show the time and then actually to get the correct one to display.