Hoymiles HM600 Inverter lost after Firmware flash with OpenDTU-OnBattery

[gonzo8855]

Hi,

I bought a Fusion Board with Open DTU installed.
In a first test as it was my Inverter was detected.

Now I flashed with opendtu-onbattery-generic_esp32s3_usb.factory.bin (newest version). Start 0x0 because of factory
System starts and I can adjust everything in Browswer.
Unfotunately the inverter is not found any more.

Inverter serial number is correct.

Anyone an idea.

Best Regards Bernd

[gonzo8855]

[gonzo8855]

Well, I found very alone with my problem. Nobody in the discussion felt motivated to have a look on my data and gave me feedback.
Fortunately I found another article with a hint what could be my problem.

In DTU setup the polling intervall was set to 5000s instead of 5s. So no values came from the inverter in reasonable time.

I assume this issue others should have had, too.
Here my way I came to my solution.
I just flashed OpenDTU-OnBattery on a new fusion Board with OpenDTU (wich was runnig well).
I flashed with the factory version (somwhere I red to flash starting 0x0 with factory versions, now I don't find this hint anymore)
Before flashing I downloaded config.json and pin_mapping.json in order to be able to compare later.
After Flashing the OpenDTU-OnBattery started well, only the inverter did not come.
I checked if pin mapping canged. But this was the same as on the running OpenDTU system before.

Then I feard that I killed the HW. I was not sure if flashin at 0x0 was ok becaus the flash tool proposed another s´tartung value.

In the end thie hint with zhe polling intervall was great. Thanks.

Next szeps foe me is getting the other system componets connected: Battery, Victron MPPT and enregy sensor.
For Battery and Victron MPPT I want to use Fusion CAN/ISO Shield and I already added the pins for them in the mapping shown in my original screen shots.

Lets see, if this works and how I come throug these new tasks.

[gonzo8855]

Thanks for the comment. I did not downgrade from OpenDTU-OnBattery to OpenDTU. I only upgraded from OpenDTU to OpenDTU-OnBattery. First flash OpenDTU-OnBattery with Community WebFlasher. After this everything worked except finding inverter. Then I did a second Flashing with Espressive Web Flasher. Same result. Then I detected the changed poll interval. -- Are there other parameters than poll intervall which could have been compromised?

[schlimmchen]

It is a bad user experience that you encountered this issue, and I believe you that you encountered it. However, I simply cannot imagine how this would have happend if you only upgraded from OpenDTU to OpenDTU-OnBattery.

Let me tell you, how this happens: The firmware finds a firmware in the flash memory which has either no OpenDTU-OnBattery version or a version smaller than 3. Then, and only then, the firmware multiplies the internal value by 1000, so it becomes milliseconds. Afterwards, this version is updated to the version the firmware understands. If you downgrade to an older OpenDTU-OnBattery or any version of OpenDTU, the setting is now "5000", but seconds. If you upgrade again to OpenDTU-OnBattery, it will do the migration again, so the internal value is 5000000 milliseconds or 5000 seconds.

So, are you sure that you did nothing that triggered the migration twice?

[gonzo8855]

No I am totally sure. First I came from OpenDTU v25.2.3. (Konfigurationsversion 0.1.29). Then I flashed 2 times OpenDTU-OnBattery. First with the Community Web Flasher, then Espressive Web Flasher.

Again my question: Are there other parameters than poll intervall which could have been compromised?

[schlimmchen]

Again my question: Are there other parameters than poll intervall which could have been compromised?

I don't think so, as they have been the same for a long time now, and other than the poll interval there is no difference between the upstream version of the config and OpenDTU-OnBattery.

[gonzo8855]

Thanks :-), it is really great if you get answeres to your questions.