My Solar App History 3 days behind

I had noticed there had been a problem with the History section within the My Solar App on Emoncms for sometime. However I have only just realised that the issue is the data showing in the History section is at least 3 days behind. Is this normal?

I am running basically an updated emonSD image at 10.1.5

Screen shot taken on 3rd Sept 2019.

Server Information

Server Information

Services

  • emonhub :- Active Running
  • emoncms_mqtt :- Active Running
  • feedwriter :- Active Running - sleep 60s 92 feed points pending write
  • service-runner :- Active Running
  • emonPiLCD :- Active Exited
  • redis-server :- Active Running
  • mosquitto :- Active Running

Emoncms

Server

  • OS :- Linux 4.19.66-v7+
  • Host :- emonpi | emonpi | (192.168.1.122)
  • Date :- 2019-09-03 04:46:59 UTC
  • Uptime :- 04:46:59 up 10 days, 44 min, 0 users, load average: 0.06, 0.03, 0.05

Memory

  • RAM :- Used: 18.88%
    • Total :- 975.62 MB
    • Used :- 184.16 MB
    • Free :- 791.46 MB
  • Swap :- Used: 0.00%
    • Total :- 100 MB
    • Used :- 0 B
    • Free :- 100 MB

Disk

  • / :- Used: 44.65%
    • Total :- 3.81 GB
    • Used :- 1.7 GB
    • Free :- 1.93 GB
  • /boot :- Used: 52.50%
    • Total :- 42.52 MB
    • Used :- 22.32 MB
    • Free :- 20.19 MB
  • /home/pi/data :- Used: 12.98%
    • Total :- 10.73 GB
    • Used :- 1.39 GB
    • Free :- 8.8 GB

HTTP

  • Server :- Apache/2.4.25 (Raspbian) HTTP/1.1 CGI/1.1 80

MySQL

  • Version :- 5.5.5-10.1.38-MariaDB-0+deb9u1
  • Host :- localhost:6379 (127.0.0.1)
  • Date :- 2019-09-03 04:46:59 (UTC 00:00‌​)
  • Stats :- Uptime: 866655 Threads: 3 Questions: 3676351 Slow queries: 0 Opens: 32 Flush tables: 1 Open tables: 26 Queries per second avg: 4.242

Redis

  • Version :- 3.2.6
  • Host :- localhost:6379
  • Size :- 311 keys (843.12K)
  • Uptime :- 10 days

MQTT Server

  • Version :- Mosquitto 1.4.10
  • Host :- localhost:1883 (127.0.0.1)

PHP

  • Version :- 7.0.33-0+deb9u3 (Zend Version 3.0.0)
  • Modules :- apache2handler | calendar v7.0.33-0+deb9u3 | Core v7.0.33-0+deb9u3 | ctype v7.0.33-0+deb9u3 | curl v7.0.33-0+deb9u3 | date v7.0.33-0+deb9u3 | dom v20031129 | exif v7.0.33-0+deb9u3 | fileinfo v1.0.5 | filter v7.0.33-0+deb9u3 | ftp v7.0.33-0+deb9u3 | gd v7.0.33-0+deb9u3 | gettext v7.0.33-0+deb9u3 | hash v1.0 | iconv v7.0.33-0+deb9u3 | igbinary v2.0.1 | json v1.4.0 | libxml v7.0.33-0+deb9u3 | mbstring v7.0.33-0+deb9u3 | mcrypt v7.0.33-0+deb9u3 | mosquitto v0.4.0 | mysqli v7.0.33-0+deb9u3 | mysqlnd vmysqlnd 5.0.12-dev - 20150407 - $Id: b5c5906d452ec590732a93b051f3827e02749b83 $ | openssl v7.0.33-0+deb9u3 | pcre v7.0.33-0+deb9u3 | PDO v7.0.33-0+deb9u3 | pdo_mysql v7.0.33-0+deb9u3 | Phar v2.0.2 | posix v7.0.33-0+deb9u3 | readline v7.0.33-0+deb9u3 | redis v4.1.1 | Reflection v7.0.33-0+deb9u3 | session v7.0.33-0+deb9u3 | shmop v7.0.33-0+deb9u3 | SimpleXML v7.0.33-0+deb9u3 | sockets v7.0.33-0+deb9u3 | SPL v7.0.33-0+deb9u3 | standard v7.0.33-0+deb9u3 | sysvmsg v7.0.33-0+deb9u3 | sysvsem v7.0.33-0+deb9u3 | sysvshm v7.0.33-0+deb9u3 | tokenizer v7.0.33-0+deb9u3 | wddx v7.0.33-0+deb9u3 | xml v7.0.33-0+deb9u3 | xmlreader v7.0.33-0+deb9u3 | xmlwriter v7.0.33-0+deb9u3 | xsl v7.0.33-0+deb9u3 | Zend OPcache v7.0.33-0+deb9u3 | zlib v7.0.33-0+deb9u3

Pi

  • Model :- Raspberry Pi 3 Model B+ Rev 1.3 - 1GB (Sony UK)
  • SoC :- Broadcom BCM2835
  • Serial num. :- A2DA3FB3
  • Temperature :- 56.92°C - 56.9°C
  • emonpiRelease :- emonSD-30Oct18
  • File-system :- read-write
Client Information

Client Information

HTTP

  • Browser :- Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36
  • Language :- en-GB,en-US;q=0.9,en;q=0.8

Window

  • Size :- 1903 x 1057

Screen

  • Resolution :- 1920 x 1200

Hello @whatsupskip looks like there are a number of issues with the latest mysolar app, we are looking into it.

I cant seem to replicate this issue here, I can see up to the 3rd of September here:

Have you set the timezone in the My Account section? It should correspond to the same timezone as your browser timezone.

How is the Solar data being passed to Emoncms? Via reading a CT or from another device? If from another device, are you including a timestamp? Could the Date on that device be incorrect?

Can you check the time and date of the machine from which you are viewing the data?

If there was a time issue at the server or at the source then it would show as “on-time” but with 3 empty days, the fact that the app thinks today is 3 days ago, demonstrated by the furthest right bar being 3 days old, means the browser date/time is most likely out.

I thought I had checked this, but it appears that simply closing the browser and reopening it updated the time/date and now it shows the up to date history.

Thank you for your help.

That’s odd, so are you saying the mysolar app’s history isn’t updated without refreshing the page? I can’t say I’ve ever noticed if I have kept it open for multiple days.

This morning I was able to get the history to update by forcing a refresh on the browser. Without doing so it wouldn’t show yesterday’s data.

Yes I leave the browser on the My Solar app for days at a time, but it is normally on the power section.

Has the logged in session expired? You can check by trying to go to the Admin page.