New CUtils website

[AndyKF650]

After months of development and learning I have eventually sorted out my local website sufficiently to publish it on a hosted site.

The work done in getting it over the line has been assisted by HansR who has made many helpful suggestions. The web hosting with HostPresto was easy and inexpensive.

[HansR]

My compliments for what your did , changing about everything I set up, even the moon, which has not always been an easy task I suppose. I think it is a site which deserves the public eye, it really looks good.

Is the site still running on your Raspberry or is it with a provider?
I assume the Raspberry.

Well done!

[HansR]

And btw: your Graphs=>Temp Graphs really shows extreme climate change in ten years
Can't remember any other site producing such charts.

[AndyKF650]

Hi Hans

Thanks for your comments, in reply the web site is hosted externally but the RPi v4 still acts as the primary node in the system with the Davis VP2 plus acting as data collector inputting to the RPi via a meteoPi link. The CMX/CUtils programming then provides the data for FTP to the HostPresto site being updated every 15 secs for realtime and every 15 mins for the graph/forecasts.

Using crontab, I run a sysinfo routine every 6 hrs and a thrifty website routine daily, both of which routines keep the site clean and updated. The thrifty update is modified by making a copy of the current index.html to indexA.html prior to the thrifty website and then returning the indexA.html back to index.html, this ensures my modification of the index.html remains in place

Looking at your coding comment I have changed to the <img id="Moon" src="/Generalicons/moon.png";> but as you say nothing much changed. In fact the similar coding on the CMX site requires the " <img src= " code. My understanding is not good enough to see a difference when both seem to work.

The other comment you made regarding the temperature trends over time can probably be explained by the fact that pre 2018 I was using an Oregon system which seemed to have rather marginal stability and accuracy but the data was recorded and is enclosed for completeness. On that chart the long term black line is the 20 year average from the UK Met Office records for Jersey.

I think this has addressed your comments. I am just pleased to have got this far away from the rather grim meteohub/ oregon system of pre 2018.

[PaulMy]

Looks great, well done

Enjoy,
Paul

[rogerthn]

Looks great, well done

+1
PS
If you like share your SolarEdge with others you need to use a https://monitoringpublic.solaredge.com link
e.g.
https://monitoringpublic.solaredge.com/ ... /dashboard

[AndyKF650]

Thanks for that advice, I had forgotten that that site is really a private maintenance site for me. Site amended

[HansR]

Thanks for your comments, in reply the web site is hosted externally but the RPi v4 still acts as the primary node in the system with the Davis VP2 plus acting as data collector inputting to the RPi via a meteoPi link. The CMX/CUtils programming then provides the data for FTP to the HostPresto site being updated every 15 secs for realtime and every 15 mins for the graph/forecasts.

Sounds good.

Using crontab, I run a sysinfo routine every 6 hrs and a thrifty website routine daily, both of which routines keep the site clean and updated. The thrifty update is modified by making a copy of the current index.html to indexA.html prior to the thrifty website and then returning the indexA.html back to index.html, this ensures my modification of the index.html remains in place

I hope this will stand the test of time
The generated code will not change often nor much but at some point...

Looking at your coding comment I have changed to the <img id="Moon" src="/Generalicons/moon.png";> but as you say nothing much changed. In fact the similar coding on the CMX site requires the " <img src= " code. My understanding is not good enough to see a difference when both seem to work.

A lot within HTML / javascript appears to be selfcorrecting in the sense that syntactical errors are masked and interpreted: often as you would have wanted, sometimes it can be pretty unexpected result.

The other comment you made regarding the temperature trends over time can probably be explained by the fact that pre 2018 I was using an Oregon system which seemed to have rather marginal stability and accuracy but the data was recorded and is enclosed for completeness. On that chart the long term black line is the 20 year average from the UK Met Office records for Jersey.

Aha... that means that major changes in measurement technique require indications somewhere. Calibrating is an art for the amateur meteorologist

I think this has addressed your comments. I am just pleased to have got this far away from the rather grim meteohub/ oregon system of pre 2018.

Yes it did, this is where hard work brings you
Well done again.

[rogerthn]

Thanks for that advice, I had forgotten that that site is really a private maintenance site for me. Site amended

(y)

[AndyKF650]

Having worked with the new website for a couple of days, I have seen some background problems.

The first was the fact that my dashboard customisation did not last following the daily .exe thrifty website execution. Initially I solved this with my local website solution using crontab by first creating a copy index file, running the thrifty website and replacing the generated index file with the copy, this then required a filezilla ftp of the index file. Not slick enough, if not very tedious.

The solution for this was to get my head around the cumulusutils.ini file section relating to panel order, something I had looked at but ignored as I then had a different solution. So if you order the panels in your preferred order ie Panel1=RainText Panel2=RainGauge ......... Panel 19=PressureGauge. I have the remaining 5 panels blank at the moment but that may change. Now if I run the Thrifty Website update my preferred order is retained and the appropriate graphs are clickable from the panel.

My second issue was understanding just what files needed to be on the website, when I first set it up the file transfer was a bit random with quite a few duplications. This was solved by cleaning down and deleting all the website files via Filezilla and then rebuilding the website more selectively by reviewing it at each stage and adding the missing files.

The last issue was the non performance of the NOAA reports, something that initially caused me issues on my local website. The solution is to use the correct instruction in the administration settings for the NOAA FTP address which for me is /public_html/Reports rather than any other variation I may have though of.

So I am happy with CUtils and my website for now, there will always be tweaks and upgrades to keep me interested.

[HansR]

The first was the fact that my dashboard customisation did not last following the daily .exe thrifty website execution. Initially I solved this with my local website solution using crontab by first creating a copy index file, running the thrifty website and replacing the generated index file with the copy, this then required a filezilla ftp of the index file. Not slick enough, if not very tedious.

The solution for this was to get my head around the cumulusutils.ini file section relating to panel order, something I had looked at but ignored as I then had a different solution. So if you order the panels in your preferred order ie Panel1=RainText Panel2=RainGauge ......... Panel 19=PressureGauge. I have the remaining 5 panels blank at the moment but that may change. Now if I run the Thrifty Website update my preferred order is retained and the appropriate graphs are clickable from the panel.

I was already afraid this might happen
Glad my solution suits you still looks very good.

I see you lost the moon though (pun intended).
I'll put that on the todo list and when the dust has settled on other developments I'll add the possibility to use the CMX moon image (unless you got used to my artists impression of the moon).

[EDIT]

My second issue was understanding just what files needed to be on the website, when I first set it up the file transfer was a bit random with quite a few duplications. This was solved by cleaning down and deleting all the website files via Filezilla and then rebuilding the website more selectively by reviewing it at each stage and adding the missing files.

True that no files are ever deleted so sometimes deleting and restarting can be a good idea.
It is not required though as references are never to old files and the txt files are always replaced.
Efficiency is supposed to be reached by the THRIFTY qualifier.