yup … I was going through the setup, and must have started it first. Had been running ever since…
just saw my first realtime lighting strike. And rain started to fall shortly there after!
Very Nice.
yup … I was going through the setup, and must have started it first. Had been running ever since…
just saw my first realtime lighting strike. And rain started to fall shortly there after!
Very Nice.
Thank you for the compliments.
I will add code to inform the other processes to reload the config when it’s updated.
I have added Peak Sun time for those that have an interest in this value.
Oh, I didn’t realize that Panel didn’t grab it from the Config tab. It works now.
I had to run update files a couple of times. I guess it makes sense when the running script file is replaced during the script.
BTW, should this read Database rather than Datebase?
Yes it should. You found the third egg.
Currently running the PiConsole on a Pi3. Can I install ArchiveSW on the same Pi3 without any conflicts?
There should be no issue. ArchiveSW is written to play nice with other applications.
Thanks. Going to give it try once I get a chance. It shows more info on the screen then the PiConsole plus allows going back through the data.
And there are many more enhancements coming.
I pushed out more small changes. Please run Alter Tables and then run Update Files immediately after.
I’ve noticed every so often the date on the panel turns RED and flashes?
what does that indicate?
It means files were updated. You need to look at the About tab as you may need to run Alter Tables and you may need to reload the Display page.
And after you run Alter Tables you should run Update Files.
Hey Gary,
Just curious about the peak sun.
What does it represent? Total sun?
Today mine said 3h 30m 33s.
Also the “red date and time” for me flashes every time it
checks for updates, even when there aren’t any. Auto update is on.
A Peak Sun Hour is 1000 watt hour. So your Sky saw 3.5 hours so solar charging power.
The red flashing means an application was update. It can be a process or the Panel display.
Thanks! Great Info. Keep up,the great work!
Thank you. I want to provide useful information. This is good for those with solar panels at home on a RV.
cheers Ian
I need a little help getting my new sensor (DS18B20) working -
I wired to the GPIO - red lead to PIN#1 (3.3v +), black to PIN#9 (GND), yellow to PIN#7 (GPIO4). I have a 10k resistor between PIN#1 & PIN#7(GPIO4).
I ‘added’ Piio under Process manager - and under PiIO I checked ‘active’ all triggers not checked. (saved) I then started the process.
I don’t get any data on the panel display - and while the process is running - it continuously shows restarts increasing? (currently over 114) after refreshing screen.
can you help?
(edit) - also under PiIO screen on the right side - shows:
Sensors
28-0206924563d8
(running on an Rpi 3B V1.2)
Are you saying the Panel process is restarting?
Look for Panel.err in the Log tab and tell me what it shows.
No Panel has no errors. However the PiIO has errors the sample below just keeps repeating over and over …
Piio.err 2071762 Fri Mar 01 2019 11:37:56 GMT-0500 (EST)
Error: The module '/home/pi/archivesw/node_modules/epoll/build/Release/epoll.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 67. This version of Node.js requires
NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node (module.js:681:18)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at bindings (/home/pi/archivesw/node_modules/bindings/bindings.js:112:48)
at Object.<anonymous> (/home/pi/archivesw/node_modules/epoll/epoll.js:1:99)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
also Archive has errors (never had that before… perhaps related?)
TypeError: Cannot read property 'end' of undefined
at tcpExit (/home/pi/archivesw/archive.js:1252:12)
at onExit (/home/pi/archivesw/archive.js:1232:2)
at process.<anonymous> (/home/pi/archivesw/archive.js:1211:5)
at emitNone (events.js:111:20)
at process.emit (events.js:208:7)
at Signal.wrap.onsignal (internal/process.js:208:44)
This is the process that keeps restarting …