GithubHelp home page GithubHelp logo

Comments (6)

jedie avatar jedie commented on June 10, 2024

Yes, a good idea!
Also because i have the SUN600 and he is also offline at night...

from inverter-connect.

jedie avatar jedie commented on June 10, 2024

One Problem: What's if the status is lost? e.g.: The computer was rebooted or the services restarts by some other reason.

So you can't just init with "no reset made today" and toggle this boolean flag. Because every restart will reset the daily production, too.

So we have to store the state on disk to avoid this. Maybe just the date of the last reset into e.g.: ~/.config/inverter-connect/lastreset

from inverter-connect.

jedie avatar jedie commented on June 10, 2024

I implement the idea in #61

We will see tomorrow if it's work ;)

from inverter-connect.

jedie avatar jedie commented on June 10, 2024

Hm. Doesn't work, today:

grafik

But the reset was made, today:

cat ~/.config/inverter-connect/daily_reset_state.txt 
2023-05-27

Hm...

from inverter-connect.

CarstenGrohmann avatar CarstenGrohmann commented on June 10, 2024

The original firmware resets the "daily production" at the first connection with the central server. With this implementation, you lose production between the first sun and the time you connect home. Yesterday, I re-enabled communication with the internet for the inverter, and the inverter resets the day's production immediately after.

What do you think about a similar approach by running "Set-Time" once a day, just after the software was able to connect to the inverter for the first time?

Using the status file to ensure that "Set-Time" is only run once a day, even if the software has been restarted.

The result would be very similar to the original firmware when the inverter is connected to the internet. There will always be a small amount not reported. If the software runs continuously, the amount is very small probably under 5 minutes of harvested energy at the beginning of each day.

from inverter-connect.

jedie avatar jedie commented on June 10, 2024

What do you think about a similar approach by running "Set-Time" once a day, just after the software was able to connect to the inverter for the first time?
Using the status file to ensure that "Set-Time" is only run once a day, even if the software has been restarted.

This is exactly how it's implemented, now ;) But doesn't work. Don't know why.

from inverter-connect.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.