-
-
Notifications
You must be signed in to change notification settings - Fork 488
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
Temporary poor connection to HMS-400-1T #2082
Comments
Ich kann nach umfangreichen Tests bestätigen dass bei mir für mein Problem HoymilesZeroExport mit openDTU - hängt in der Früh "reserve85/HoymilesZeroExport#211" Mit Ahoy 0.8.84 funktioniert es ohne Probleme mit den Hoymiles WR und auch mit HoymilesZeroExport! |
It would have been usefull to know that you are sending limits in the first place. Commands inserted by the API or by the WebUI have always a higher priority than automatically inserted commands (like statistics data). That means if you are sending limits to often, there is no chance to execute the statistics command anymore. |
But that has nothing to do with my bug report. I have a suspicion that if I set the transmit power to -2 dBm it seems to work, but I still have to watch it a bit. |
There were problems again this morning, after lowering to -5 it is running again for the time being. |
That's not it either. |
I have now replaced the power supply unit and the USB cable. |
It was the power supply. |
What power supply do you use now? |
It has improved a lot, but it still happens from time to time. |
I can see from your report that you are using the default frequency of 865 MHz for the communication with the HMS inverter. Could you please adjust the frequency to a higher value, i.e. 868.25 MHz and report if it makes a difference or not. |
I will and will report back in a few days. |
Unfortunately, this did not help either. |
Mit dem Netzteil vom Raspberry 5 läuft es jetzt relativ stabil. |
OK, now it works with the Raspberry Pi power supply. |
Just when you think all is well... |
@MichaMEG Do you have the condensators close to the NRF/CMT Module ? Can you post an image of your hardware ? |
It is the original from this website: and with 1306 Display |
@MichaMEG why don’t you try OpenDTU-OnBattery and use the built in Dynamic Power Limiter with that. I assume the reserve85 solution is sending too frequent ActivePowerLimit commands to the OpenDTU and does not wait for confirmation of the new Power Limit through the REST API before sending the next command. This can render the inverter unresponsive for at least 15 minutes. |
Sorry, I'm not setting a power limit, that must be a misunderstanding. |
@MichaMEG i must have mistaken this because in your first post you mentioned the 100%/400W Active Power Limit and crisi-solar mentioned his use of the reserve85 tool which indeed sets the Active Power Limit. So you do have 2x HM-600 and 1x HMS-400-T1 connected / configured in your OpenDTU Fusion board from Alliance Apps. Can you please send us the first seven digits of your serial ID plus a screenshot / copy of your Inverter Info as it contains a couple of details, e.g. model type, build date / week, HW Version, etc. which we need to further analyse the issue. |
Also see #2137 for another similar issue with HMS models with Firmware-Version 1.0.27 and Firmware-Build Date 2023-06-05 10:24:00 or later. |
What happened?
Sometimes the connection works well, but occasionally the data displayed is not fully updated.
To Reproduce Bug
Sometimes the connection works well, but occasionally the data displayed is not fully updated:
"Aktuelles Limit: 400 W | 100 %
Letzte Aktualisierung: vor 455 Sekunden"
At the same time, we read out too 600-HM without any problems.
Strangely enough, the performance data is still sometimes updated. Sometimes there are no problems for hours.
Expected Behavior
I would have expected a smooth display
Install Method
Pre-Compiled binary from GitHub
What git-hash/version of OpenDTU?
c144b68
Relevant log/trace output
Anything else?
generic_esp32s3
Please confirm the following
The text was updated successfully, but these errors were encountered: