Action | id | SDTE | time | INV | I1V | I1A | I1P | I1Ratio | I2V | I2A | I2P | I2Ratio | GV | GA | GP | FRQ | EFF | INVT | BOOT | KWHT | pvoutput | dayNum | pvoutputErrorMessage | deviceId | I3V | I3A | I3P | I3Ratio | GV2 | GA2 | GP2 | GV3 | GA3 | GP3 | IP | ACP | pvoutputSend | pvoutputSendTime |
514350 | 20140314-13:18:00 | 1394799480 | 4 | 327.505 | 4.644 | 1521.024 | 66.904 | 304.232 | 2.473 | 752.424 | 33.096 | 228.355 | 9.691 | 2196.028 | 49.995 | 96.595 | 41.288 | 36.188 | 3127.362 | 1 | 73 | 0 | 4 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1394799536 | |
514359 | 20140314-13:45:00 | 1394801100 | 4 | 316.477 | 5.098 | 1613.346 | 75.405 | 310.021 | 1.697 | 526.229 | 24.595 | 228.497 | 9.05 | 2074.432 | 49.987 | 96.955 | 40.835 | 36.566 | 3128.306 | 0 | 73 | 0 | 4 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
Thanx for your feedback!
1. What do you mean less DB updates?
2. As far is a know, WSL isn't polling the inverter when its power-down. What give you the idea that WSL is still polling the device when its powered down?
3. I do not understand what you're trying to say here
4. If you hover the date it should show the time ;-) (same as "weather" on the index.php)
True about the GPS coordinates, it is not a big privacy issue but it shows where you live nearby :) With this information if one wants to harm you, they will/can find your exact house based on your inverter output and public websolar page (if it is publicly accessible of course and the bluetooth password is still on default 0000).
@Paolo: sorry for kidnapping your topic :)
Ok, it could happen that intervals are missing. But you said that when this happens, also the daily totals change or are not the same as the inverter reports.
Please come with examples where the the missing intervals could be linked to total values that are off.WSL is working with tot TotalKWH value of all thirdparty reported software so its near impossible that WSL's TotalKWH is off in the month,year and/or overall value. It could be that there is a calculation problem, but then i still need examples to fix this issue. This because there are tons of calculations and its very time consuming to check them all and hopefully find a bug.
Daily Energy = 10.620 kWhWeekly Energy = 159.910 kWhMonthly Energy = 284.156 kWhYearly Energy = 735.354 kWhTotal Energy = 3831.201 kWhPartial Energy = 3831.098 kWh
Daily Energy = 10.877 kWhWeekly Energy = 160.167 kWhMonthly Energy = 284.413 kWhYearly Energy = 735.611 kWhTotal Energy = 3831.458 kWhPartial Energy = 3831.355 kWh
The daily values i will take a look on and see if i can fix this (could you make a ticket for me?)!
This evening i made a small piece of code that does;//** here we do 2 checks;* 1. is (current KWHT - last['KWHT']) > 0* 2. is (sunrise['time'] - last['time']) > 18000 (5 hours)** if these checks are good; we are probably started later with logging and so make a dummy record to fix the graph and daily production*/We then create a "dummy history record" with the last known KWHT (kWh total) value and the time of today sunrise minus 30 minutes.
Concerning writing data on the flash memory card, what I did was moving the entire WSL environment to my NAS share and running it from there. This way it won't produce a lot of write actions on the flash memory card and you don't have to make backup occasionally.
I see activity all night as well. There aren't database entries added, but I do see activity and polling of the inverter (which is off). When I add current monitoring at the service inlet, I'll have activity all day and night, so this isn't that much of a concern. Though Flash memory will eventually wear out, I've got a sufficiently large enough card in my raspi that I'm not concerned about the life of the card. I just need to back up to my NAS occasionally.
Concerning writing data on the flash memory card, what I did was moving the entire WSL environment to my NAS share and running it from there. This way it won't produce a lot of write actions on the flash memory card and you don't have to make backup occasionally.I'm using a Raspberry PI to save energy. It's a waste of energy to keep on both Raspberry and the NAS. I would have installed it all on the NAS. :)
Marco, keep up the good work (I keep seeing day-to-day improvements - and they are killing my SD card ;-), and everyone else - thanks for your input
Im reading this post and i want to thank you all for helping us out with good testing.
About the the nightly checks. I think that Marco is wrong, we check always. And that is my fault.
Because i thought this was implemented. The idea was that we should slow down the checking.
So instead off every 2/3 seconds we check ones every hour to check if we can get data.
When we approaches the calculated sun up we switch to a faster checking.
This is however never implemented. And we should do this.
Someone wanted to raise a ticket for this. Please do so.
Its very simple to say; WSL is wasting cpu, power and "destroying" my SD card...Give me data, point me to power/CPU/SD-card wasting/destroying processes of WSL and i will take a look at it.
It stand everyone free to use WSL, It stand everyone free to move to another solution, It stand everyone free to use to help with the development, It stand everyone free to speak, It stand everyone free to clone/modify/change/etc WSL......
Its very simple to say; WSL is wasting cpu, power and "destroying" my SD card...Give me data, point me to power/CPU/SD-card wasting/destroying processes of WSL and i will take a look at it.I agree! It just takes some time to collect every items. I will try to make some more investigation and will give you some feedback if I will find something interesting that's worth fixing.
i dont know why you think it is the queueitem table. Actually the queueItem table is almos always empty. We only use it for sending stuff from the frontend to the queueserver. Most used is when you do an update or test an device. So queueitem table cannot be that busy in writing.