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

new Events not viewable #131

Closed
ghost opened this issue Sep 12, 2022 · 7 comments
Closed

new Events not viewable #131

ghost opened this issue Sep 12, 2022 · 7 comments

Comments

@ghost
Copy link

ghost commented Sep 12, 2022

I have two HM-1500 (West, Ost) connected to the OpenDTU. I can see the red numbers for both of the inverters in case of new events.
If the numbers exceed a certain number of events they are not listed when trying to open them, it's just an empty list. If there are only small number of events it works without any problem. I do not exactly know what is the breaking number. I must be someting greater than 3 or so. My impression is also it works more stable for the first inverter, I have seen on West more that 10 events listed without any problems. On the 2nd inverter Ost the list is always empty when there more than 3-4 events.
Stefan

image

@tbnobody
Copy link
Owner

Could you please open the URL: http://<OpenDTU IP>/api/eventlog/status in a browser and post the output? I assume that maybe the buffer for the json output is to small and therefor the entries get cut off.

@ghost
Copy link
Author

ghost commented Sep 12, 2022

{"116180204736":{"count":13,"events":[{"message_id":1,"message":"Inverter start","start_time":22526,"end_time":22526},{"message_id":12,"message":"Unknown","start_time":27684,"end_time":27684},{"message_id":14,"message":"Unknown","start_time":27813,"end_time":27813},{"message_id":148,"message":"Grid disconnection","start_time":27814,"end_time":27900},{"message_id":12,"message":"Unknown","start_time":28024,"end_time":28024},{"message_id":12,"message":"Unknown","start_time":28116,"end_time":28116},{"message_id":12,"message":"Unknown","start_time":28147,"end_time":28147},{"message_id":12,"message":"Unknown","start_time":29115,"end_time":29115},{"message_id":12,"message":"Unknown","start_time":29279,"end_time":29279},{"message_id":12,"message":"Unknown","start_time":29403,"end_time":29403},{"message_id":12,"message":"Unknown"}]}}

@tbnobody
Copy link
Owner

If you have already compiled it yourself and if you want to test it you can try to replace the line:

AsyncJsonResponse* response = new AsyncJsonResponse();

by the following:
AsyncJsonResponse* response = new AsyncJsonResponse(false, 2048);

This is only a workaround as for more (up to 10 supported inverters) inverters the 2048 will be also to small. I think I have to rework the API a bit.

@ghost
Copy link
Author

ghost commented Sep 12, 2022

Ok, I will test that and update here, thanks for the great support and your work!

@ghost
Copy link
Author

ghost commented Sep 12, 2022

Looks good now....I will post again here if there are any issues.
image

madmartin pushed a commit to madmartin/OpenDTU that referenced this issue Apr 30, 2023
This was referenced Oct 8, 2023
@stefan123t
Copy link
Contributor

@locke981 Danke für die Meldung, ja es gibt noch ein paar Unbekannte / unknown Fehlermeldungen.
U.a.

Ich bin in den assets/warn_code.json der Hoymiles S-Miles Installer App fündig geworden. 🥳

Hier mal die bisher aufgetretenen Fehler oder Warnings aus dem in #121 angehängten warn_code.json (GitHub versteht nur ZIP ?).

11: Grid voltage surge
12: Grid voltage sharp drop
13: Grid frequency mutation
14: Grid phase mutation
36: INV overvoltage or overcurrent
46: FB overvoltage
47: FB overcurrent
71: VW function enable
72: FW function enable
73: TW function enable

Es wird von @tbnobody im Rahmen von #121 in OpenDTU implementiert und daher kann dieses Issue als Duplicate geschlossen werden.

Copy link

github-actions bot commented Apr 3, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants