Open miner90027 opened 2 years ago
Thanks for the bug report. What is the latitude of your station? Are you particularly far north and therefore not seeing a sunset at the moment?
The latitude of the station is 61.56555 roughly Wasilla, AK. About this time of year the sun never fully sets, rather it stays at a dusk/dawn light level.
Ok, that's the issue. I will need to edit the code so it can handle locations where the sun does not set (or rise) for a period of the year. This may take a little time, so I will have a look into quick workarounds to get you up and running again asap. Bear with me!
Thanks. It works great during the winter when there is very little sun.
If you comment out lines 439 and 443 of main.py
the console should start, just without the solar information. You should be able to use the console in this way until a roll out an update to fix the bug
Alright, that temp workaround works.
Is there an update on this bug? quickfix works, but want it to work the right way
I'm still working on this, unfortunately. It has turned into a much bigger re-write of the code as it was never originally designed to cope with locations where the sun never rises or sets (my fault, I know!).
I'm still working on this, unfortunately. It has turned into a much bigger re-write of the code as it was never originally designed to cope with locations where the sun never rises or sets (my fault, I know!).
Perfect :) The error does not only apply to sunrise/sunset. but also moonrise/moonset. if this is two different coding in the program
As the name implies, the console crashes immediately upon starting. With auto-start enabled, the console attempts to start but immediately closes. Using the start command results in the following output shown below.
Fresh install of OS & console did not resolve the issue. The recommended file permissions change listed here did not work: https://community.weatherflow.com/t/weatherflow-piconsole/1933/2549
Unknow as to when the issue started, just suddenly stopped working. Ruled out the possibility of auto-update script causing the issue when fresh install resulted in the same issue. Unknown how to reproduce.
Hardware/OS/Version: