openDTU goes offline after some time

[Oliver11986]

Hi all, first attempt to use github Q&A so forgive me if I wont provide all necessary data.

Using openDTU on an ESP32 with PoE (Olimex board). openDTU did it's job for 3 months without any issues. Since 3 days I can go to openDTUs UI but it shows it cant reach the Hoymiles HMS 1600 inverter. After this happened the first time i tried the following steps:

saving the config
saving the pin layout
restarting the ESP32
resetting to factory default

Nothing of these things did help. So I wiped the board and reflashed it with the factory.bin for ESP32. After that I installed openDTU and reloaded the pin-layout and my config - as a result everything worked. the Next day it showed the same issues as above...

What I also found out: the nRF24 chip is shown as "not configured" wich would make the issue understandable for me...but after reflashing the ESP32 (and getting openDTU back to work) its also shown as "not configured".

Maybe anyone of you had similiar issues and can help.

Thanks in advance and if you need additional data/logs please tell me where to find these and I'll provide them.

Bye

[stefan123t]

Hi Oliver,
the NRF24L01+ is one of two RF chips used to communicate with the older MI- and HM- models from Hoymiles using the 443 MHz BLE Band.
Your inverter is a later HMS- model which can communicate using the CMT2300A operating at 868 MHz band.

So please double check the PinMapping.json matching your board, there are several known to work settings under Documentation / Devices afaik.

Also double check the config.json and compare the settings for your Inverter and NTP are setup all right.

Did you do an upgrade or cross-installation between OpenDTU and OpenDTU-OnBattery recently ? Double check the frequency / interval settings under Settings > DTU it may be set to 5000 seconds in the UI or 5.000.000 milliseconds in the config.json in such cases.

You can check and control the logs in your Info > Console switching to Verbose for further debugging or follow the documentation for proper USB serial molitoring.

[Oliver11986]

Thanks for your answer - pin mapping is correct since i reloaded the mapping from my backup. CMT2300A is configured - guess it was my mistake to think the nRF would be the correct chip.

I increased poll time and updatetime MQTT to 10 seconds and after some time i received data again - and until now (fingers crossed) everything works fine. Im just curious why it DID work for 3 months with 5 sec. updatetime...but maybe some questions shouldnt be ever asked :)

[Oliver11986]

Update: just stopped working 10min ago. Same issues although poll time has been increased. Could temperature be an issue?