MQTT settings are reset to defaults when module restarts

[silvanverschuur]

Describe the bug
The MQTT settings are restored to default values when the module restarts. This happens when restarting the device from the web page but also when the cable between the Itho WPU and the module is disconnected. The MQTT settings are saved using the 'Save' button on the MQTT page

Device information

• Firmware version: 2.9.0-beta1
• Hardware revision: non-cve
• CC1101 RF module enabled: yes

[arjenhiemstra]

Thanks for reporting this! I also noticed a reset of the system settings yesterday, trying to find out what causes this.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[silvanverschuur]

@arjenhiemstra I'm wondering if you have found the issue? If so, is it possible to release a beta to test it?

[printplaatreparatie]

It took me a long time to find that this was the issue for me. Let me give some background information so others that use tls can find this issue (and fix) easier.

I noticed that the Itho box was no longer communicating with Home Assistant. The mosquitto logs were showing these two errors:

New connection from 192.168.xxx.xxx:xxxxx on port 8883.
OpenSSL Error[0]: error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2024-08-15 23:29:04: Client <unknown> disconnected: Protocol error.

Not helpful and even misleading. The fix is easy: After every reboot, change the port number to 1883 in the ngr-itho webinterface. Save, change it back to 8883, save.

[arjenhiemstra]

@arjenhiemstra I'm wondering if you have found the issue? If so, is it possible to release a beta to test it?

Yes, found it!
The config is wrongly saved prior to loading during startup. I'll remove it in the next update.
This is the affected line:

ithowifi/software/NRG_itho_wifi/main/tasks/task_cc1101.cpp

Line 252 in 5f9915a

saveSystemConfigflag = true;

[silvanverschuur]

@arjenhiemstra Do you know when a new (beta) version is released with this fix?

[arjenhiemstra]

Hopefully this will not happen anymore with the latest 2.9.0-beta5 release. I suspect the config was somehow saved before being loaded properly. This should be prevented from happing since this beta.