Well, it’s uploading data to both CWOP and PWS again, so that’s all good. Out logs for both show three entries again.
I did do a restart of the server process. Maybe that is what got the CWOP going again. So, moral of the story is that things work fine, just that the .out log files are 3x as big as they probably should be. 
Are you doing a save on the Upload tab? Doing that may be causing the issue. I’m trying to find the problem.
Yeah. Hitting save on the upload tab after turning debug on. But I only did that once and it was a while ago.
I just uploaded a new server.js file. That may have a fix for the issue if you want to set. Run UpdateFiles and restart the Server process.
That seems to have fixed the multiple entry issue. Well done!
How’s that for rapid-fire debugging on the fly?
I’m going to sign off for a while to do some router maintenance. My data will go offline for a while as a result.
Thanks for the quick support!
So the Lux value started showing up on the CWOP page. The data seems weird. There’s two bumps each day. I’m wondering if it has something to do with the scaling of upper and lower case “L”. The data you are sending seems very reasonable so I’m not sure what’s going on here. I have a feeling it has more to do with how data is digested at CWOP rather than how the data is regurgitated from the hub by ArchiveSW. 
I do know that we haven’t had a full solar eclipse in the middle of every day, lasting for a few hours each day, for the last 5 days…
And it’s entirely possible I am doing it incorrectly. It’s unfortunate there is no clear documentation and no one to ask questions of.
Looking at the graph, and thinking about it a bit more, my guess would be that the difference between the “L” and “l” have to do with a scaling factor of 100. I know you saw documentation that said to switch over at 999, but, the graphs just don’t make sense.
My peak lux value from the SW web viewer on 12/13 was 54279, which looks to be just about a factor of 100 off from the CWOP site graph I posted above. Maybe it’s worth a try to send un-scaled values and see if that fixes things?? So, try either no scaling to the lux value and send it with an upper case “L” or divide the values by 100 and send them with a lower case “l”. In other words, keep the scale the same for the whole range and let’s see what the graph looks like.
Just a thought…
I’m not scaling the data. I am sending the actual value to the server. “L” is limited to three places. The only reason I use “l” is if it is over three places.
Yeah, I know you aren’t scaling the data. I probably wasn’t clear in my explanation.
My thought is that the “L” and “l” identifiers are somehow meant to induce some scaling on the CWOP end of things. So my suggestion is to not swap between “L” and “l” at the 999 transition. So just use “l” for all values and see what happens.
Okay. I can do that and see what happens.
The new file on the server. Version .030.
Thanks. I just updated. We’ll see what happens.
I figured we might as well try it because the illumination data they were showing on the web page was garbage anyways. What’s weird is the fact that sometimes the illumination doesn’t even show up when I go to the webpage. I think that’s a separate issue, and nothing you could do about that.
My hypothesis is that the data will show up in a smooth curve, with either the last two (or maybe three) digits lopped off. So 50000 lux will display as 500 (or 50) at the peak.
It’s mostly cloudy today so it might not be a nice curve. Tomorrow is supposed to be clearer.
The latest updates have been stable and no errors have shown up for over 24 hours. I will be preparing to release the stable version as 1.8.15. If you have any bugs or need any enhancements, please let me know ASAP.
Latest up date seems to have removed moon “Raise and Set” times
It broke because the moon does not set today. I have uploaded a new file to handle that issue. I foresee additional issues with the moon is always up or always down so I’ll have to handle that later.
Set the Rise and Set time to --:-- when the time is null.
After a few more hours researching, I think I have the “L” figured out with CWOP. CWOP really wants solar radiation. So I changed it back to “L” and passed on the solar radiation value and it showed up after one packet. Go figure.
CWOP is a mess and I hope NOAA doesn’t make it worse.
That makes sense. Illumination isn’t really as useful as radiation. The scale they use on the graph also suggests that they want radiation. It goes up to 1400 (with no units label). It also is labeled illumination, which is misleading.
Good work. It seems like it’s updating properly since you made the change…
Now I want to find out exactly what “l” is used to represent.
found another nasty bug under the devices tab I have
I had a warning today for device today (the famous drop to 0.02V and back to normal)
When I push on the first link first time ever, it ran something and came back, and now whatever link I choose hangs
server.err log
TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:5612) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:5612) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
(node:5612) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)
(node:5612) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5)
(node:5612) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
(node:5612) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 7)
(node:5612) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 8)
(node:5612) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 9)
(node:5612) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'warning' of undefined
at /home/eric/archivesw/server.js:247:32
at <anonymous>
(node:5612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 10)
have fun @GaryFunk