2W at night #575
Assignees
Labels
bug
Something isn't working
Comments
|
please check the latest development firmware which includes options to zero values by different triggers. They can be set inside the settings window inside the MQTT region. Dev build download: |
|
I do Not use mqtt, Just mystrom and have this too over night |
|
@TB-79 I consider your problem with mystrom a measurement issue of the mystrom device you are plugging between the HM-Inverter and your wall-wart. This is measuring the AC side of the Inverter and therefor it may account some power detected by small power factor changes in the grid. The problem that we are focusing on here and that @dsteinkopf had raised is the messages via MQTT are sent with a retained flag and therefor could not be zeroed during disabled night communication (the inverter will not be able to send any new data after sunset) and/or the yield daily can now also be reset at midnight (in case you are running a battery to power your inverter). |
|
I've now updated to dev version BTW. I was not able to do an OTA. For debugging I connected a serial cable and saw it was an OOM exception. So I uploaded the firmware manually via serial cable. All settings were lost. Is that expected? Also I was not able to upload the previously downloaded |
|
Similar (same?) problem during the day after a reboot of Ahoy: |
|
Sending out values with ts_last_success being 0 might qualify as a bug/issue. |
|
I have the same issue with Ahoy DTU not resetting the values with no updated data.
|
|
for second check issue #620 The third one is sometimes seen during development but was never reported to me |
|
for the third point there is an individual issue now: #660 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Platform
ESP8266
Model name
Wemos D1 mini
nRF24L01+ Module
nRF24L01+ plus
Antenna
circuit board
Power Stabilization
~100uF Elko
Connection diagram
"Normal" - as described in the readme + default config.
Connection picture
Version
0.5.66
Github Hash
f8fe044
Build & Flash Method
ESP Tools (flash)
Desktop
Mac OS
Setup
Does this matter for the described problem? I'll add this here if needed.
Debug Serial Log output
No response
Error description
Last night I had the issue that my inverter seemed to constantly produce 2.2W. I assume, this was because the night came "too quickly" and the inverter stopped responding before sending "0W" at least once. This also was an issue here: henne49/dbus-opendtu#21. But we'd consider this also a bug in Ahoy:
In
http://ahoy/api/livethets_last_successis correctly showing that the values are old. One could discuss if is acceptable that the old values (2.2W in this case) are sent out through the hole night. - In my eyes this is ok as we have the timestamp.The problem I see is that the latest value which is sent via MQTT is also 2.2W. So e.g. HomeAssistant constantly shows this value - which is wrong.
The text was updated successfully, but these errors were encountered: