Hi everyone, ive built a DIY board from the learning pages and its all working pretty well. Now i have downloaded Emoncms and setup the [[interfacers]] to accept the direct usb connection, using the following parameters:
And in the input section my two sensors for my node are there and successfully updating. I have followed the guide by creating two feeds āLog to feedā and āPower to kWhā.
When i go into feeds, my two feeds are there āuseā and āuse_kwhā, and show the values generated from the input, but i donāt get any graphs.
Even when i visualize the process. the scale adjusts to the amount of power being drawn, but nothing shows up.
I am trying to get a view of my household consumption as a nice little DIY project for myself.
I hope someone can tell me what i have missed or done wrong
Congrats and well done for setting everything up, it certainly looks like everything is set up right, youāve been doing a lot of reading up I guess.
Iām not understanding why yoy wouldnāt get graphs etc when the inputs and feeds are updating. How long ago did you create the feeds etc? Could it be that the feeds have only just been set up now and the graph window you are looking at is quite large, so the trace is too small to see yet? have you tried zooming in a bit? The fact the vertical scale is adjusting suggests it is reading data to be displayed.
Can you perhaps post the āserver infoā from the admin page of emoncms? Or you could just check the services eg redis-server and feedwriter are running ok.
First things first, why does your Pi thing itās Oct 2018?
This is most likely why your data is not showing. You are collecting data for April 2019 but when the data is saved it will have a Oct 2018 timestamp.Try scrolling back in the graph window or zooming out to 1year to try and see if there is any data being shown for a different time.
If the time has always been wrong, you might find the current data being saved back in Oct, but if the clock has recently gone back for some reason, your data will now be getting discarded as you cannot write data older than the laterset datapoint eg if you posted data correctly with the right timestamp last month, then posting data now with an oct 2018 timestamp will not stick.
Do you have an external network connection? Can the Pi reach the internet to update the clock?
Next, Iām confused by the version saying 9.9.8 at the top but v9.5.1 in the ādescribeā
Can you please post the full server info? Not a picture of part of it, use the download server information button and just paste it to your forum post.
So i found my little squiggly line of joy sitting in October
Ill have to check up on how to change the system time, i am currently on the same network as the device is and i personally dont have an issue. so i will read up on how to ammend the time
Attached is the ācopy server information to clipboardā
Itās bizarre that it thinks it is 30 Oct 2018 as that is the date the image was built. So the question is has it ever had the correct time? Has it suddenly dropped back to that date? or is it like groundhog day and always 30th Oct 2018?
Does the Pi have access to the Internet at all? If not, then it wont ever update its time. There is a fake hardware clock used by default, which saves the current time to the filesystem on shutdown and then reads that time on boot up (instead of booting up with the time set to epoch), but if you never get to the Internet the time service cannot update the time with the correct time.
You can manually set the date/time using (modify to the current UTC date/time): sudo date --utc --set "2 April 2019 01:22:00"
I have seen this before. Because the time is so far out the NNTP services will not correct it. I did a blog (so I remembered it as usual) - but that may be a little dated.
To force a sync;
sudo sntp -s time.google.com
I also got DietPi to put in a fix as again, Iād seen an issue with first boot for an old image.
You will also find any apt update will have failed.
If the -g switch is used, the NTP daemon will set the time correctly no matter how far off the system time is.
-g
Normally, ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default. This option allows the time to be set to any value without restriction; however, this can happen only once. If the threshold is exceeded after that, ntpd will exit with a message to the system log. This option can be used with the -q and -x options. See the tinker command for other options.
Just be wary everyone. We do not know what is or isnāt included in the Oct2018 image as there is no build guide despite significant changes.
This is the first Stretch image and it is no longer RO.
The older images used ntpd and had a custom ntp-backup utility installed to deal with the fact the OS was RO so the time was saved to disk each hour. There was also another āfixā added along the way to force a NTP time correction via a cronjob after bootup too. Since Stretch uses systemd-timesync by default and we have no idea how much of the older build guide was used in the new image itās not easy to know what exactly is required. Is ntp even installed? Should it even be installed if systemd-timesync is used?
This has also come up in passing on another thread a few hours ago too.
[edit] Actually that cronjob to force an update apparently ran every hour!
So that begs the question why isnāt the clock updated? Is it a network issue or is it a mismatched correction procedure? (rhetorical Q, just highlighting it may not be a simple network issue). Perhaps the ntp_update and/or ntp_backup utilities are failing because the rpi-rw command doesnāt exist? Just an example!
@Wesley_Phillip if you can ssh in is there any info at /var/log/ntp_update.log? (Iām not even sure itās still used, sorry)
Maybe I read too much into that, but āI am currently on the same network as the deviceā implies to me at least that its on its own network, possibly with no Internet connection.
Thus my suggestion to set the time manually using date.
Ha, different eyes see different things, I took that as a vague reassurance that the Pi had internet as he was talking to us and the Pi at the same time.
That might well work, but will it save? ie will it be available for the next reboot or will it still be 30 oct 2018? hence the groundhogday ref. I doubt we will ever see a build guide for this image now with a new incarnation on the horizon!
Never comfortable with the relationship between ntpd and timedatectl - there was a suggestion that the 2 should not both be installed on a system together.
[edit]
From the man page
The systemd-timesyncd service specifically implements only SNTP.
Which I think is why I ended up with the original command I posted - only sntp is installed where timedatectl is managing time (I think).