You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the Firmware update on my HM-1500 from ...0018 V01.00.30 done by Hoymiles support:
Starting the openDTU and setting the limit to 800W results in showing the dayly harvest to 0 (all strings) so total also stays freezed, this also shows up via the Hoymiles DTU/APP. Nevertheless you can see in the graph of the Hoymiles App that power is collected.
I then called hoymiles to set the limit and after this everything is fine again.
I let the open DTU unconnected now, to avoid this problem showing up again, but i need the data for Home Assistant - set the opendtu in the inverter menu to 'no commands' and activated it again hope that helps
btw: with the old HM-Firmware there was no such problem, The update triggerwas sporadic unspecific HW-errors.
The text was updated successfully, but these errors were encountered:
Hi the problem seems to be that if the openDTU request of the actual data, after every request a reset of the actual data is made, i suspended now the open DTU an furtheron the HM-accounting works well, Up to the firmwareupdate of the HM-1500 this was not the case;
yzffrog
changed the title
openDTU - Hoymiles HM-1500 set limit
openDTU - Hoymiles HM-1500 with fw V01.00.30 not working properly
Mar 22, 2024
After the Firmware update on my HM-1500 from ...0018 V01.00.30 done by Hoymiles support:
Starting the openDTU and setting the limit to 800W results in showing the dayly harvest to 0 (all strings) so total also stays freezed, this also shows up via the Hoymiles DTU/APP. Nevertheless you can see in the graph of the Hoymiles App that power is collected.
I then called hoymiles to set the limit and after this everything is fine again.
I let the open DTU unconnected now, to avoid this problem showing up again, but i need the data for Home Assistant - set the opendtu in the inverter menu to 'no commands' and activated it again hope that helps
btw: with the old HM-Firmware there was no such problem, The update triggerwas sporadic unspecific HW-errors.
The text was updated successfully, but these errors were encountered: