Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2W power at night #21

Closed
dsteinkopf opened this issue Jan 10, 2023 · 7 comments · Fixed by #22
Closed

2W power at night #21

dsteinkopf opened this issue Jan 10, 2023 · 7 comments · Fixed by #22

Comments

@dsteinkopf
Copy link
Collaborator

At the moment the script is sending 2.2W to venus/VRM because of this JSON result from Ahoy:

{
  "menu": {
    "name": [
...
    ],
    "link": [
...
    ],
    "trgt": [
...
    ]
  },
  "generic": {
    "version": "0.5.66",
    "build": "f8fe044",
    "wifi_rssi": -64,
    "ts_uptime": 30499,
    "esp_type": "ESP8266"
  },
  "inverter": [
    {
      "enabled": true,
      "name": "hoymiles1",
      "channels": 1,
      "power_limit_read": 100,
      "last_alarm": "Inverter start",
      "ts_last_success": 1673365160,
      "ch": [
        [
          231.3,
          0.01,
          2.2,
          49.99,
          1.005,
          8,
          90.185,
          327,
          2.3,
          95.652,
          0
        ],
        [
          30,
          0.08,
          2.3,
          327,
          90.185,
          2.3
        ]
      ],
      "ch_names": [
        "AC",
        "einzel"
      ]
    },
    {
      "enabled": true,
      "name": "hoymiles2",
      "channels": 4,
      "power_limit_read": 100,
      "last_alarm": "Inverter start",
      "ts_last_success": 1673365165,
      "ch": [
        [
          230.7,
          0,
          0,
          49.99,
          0,
          6.4,
          1.153,
          631,
          3.5,
          0,
          20.7
        ],
        [
          31.7,
          0.02,
          0.6,
          193,
          0.362,
          0.16
        ],
        [
          31.7,
          0.01,
          0.5,
          3,
          0.007,
          0
        ],
        [
          31.9,
          0.04,
          1.2,
          199,
          0.37,
          0.32
        ],
        [
          31.9,
          0.04,
          1.2,
          236,
          0.414,
          0.32
        ]
      ],
      "ch_names": [
        "AC",
        "M1",
        "no",
        "M3",
        "M4"
      ]
    }
  ],
  "refresh_interval": 5,
  "ch0_fld_units": [
    "V",
    "A",
    "W",
    "Hz",
    "",
    "°C",
    "kWh",
    "Wh",
    "W",
    "%",
    "var"
  ],
  "ch0_fld_names": [
    "U_AC",
    "I_AC",
    "P_AC",
    "F_AC",
    "PF_AC",
    "Temp",
    "YieldTotal",
    "YieldDay",
    "P_DC",
    "Efficiency",
    "Q_AC"
  ],
  "fld_units": [
    "V",
    "A",
    "W",
    "Wh",
    "kWh",
    "%"
  ],
  "fld_names": [
    "U_DC",
    "I_DC",
    "P_DC",
    "YieldDay",
    "YieldTotal",
    "Irradiation"
  ]
}
@dsteinkopf
Copy link
Collaborator Author

dsteinkopf commented Jan 10, 2023

I think the problem is that we don't read and use the ts_last_success.

I propose to not send any value if ts_last_success is older than - let's say - 10 minutes.

@henne49
Copy link
Owner

henne49 commented Jan 10, 2023

that makes sense, but the hoymiles is also simply wrong, let‘s include this a feature request.

Very well spotted

@henne49
Copy link
Owner

henne49 commented Jan 10, 2023

We should then send none, because we have to update, otherwise we stay at 2W. On the other hand it has no impact on energy reporting. It is rather cosmetic

@dsteinkopf
Copy link
Collaborator Author

I've prepared a branch in my fork of this repo: https://github.com/dsteinkopf/dbus-opendtu/tree/check_ts_last_success
... will create a PR after the values tomorrow arrive correctly.

@dsteinkopf
Copy link
Collaborator Author

that makes sense, but the hoymiles is also simply wrong, let‘s include this a feature request.

I am not sure if this should be seen as a bug in Ahoy. The data is correct, just a bit old. But the age (timestamp) is in the data.

@dsteinkopf
Copy link
Collaborator Author

Yes, it IS a bug in ahoy - at least at some other place: Latest value sent via MQTT also is 2.2.

This was referenced Jan 11, 2023
@dsteinkopf
Copy link
Collaborator Author

I've just created an Ahoy issue: lumapu/ahoy#575

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants