MQTT stalls and makes addon reboot about ithowifi HOT 8 CLOSED

Ok, there are probably two issues here. If the MQTT server is not reachable the add-on reboots. Need to look into it further but most probably this is a stupid bug somewhere.
Second, the zero in front of the 37. This was added automatically?? That's weird and probably the reason you cannot connect to the MQTT server.

For now there are two possible ways the solve the immediate issue.
Downgrade to v2.1 or manually edit the config file to remove the zero. First switch off MQTT to prevent the reboots. Then go to http://[IP or DNS]/edit login/pw admin and edit system.json to remove the zero.

from ithowifi.

Regarding the 0 in front of 37.
I added the IP as 192.168.178.37 using Edge chromium and after clicking save it came back with the leading zero in the display.

from ithowifi.

Edit the config.json as there is no system.json
It then indeed connected correctly !
Now to find out where this bloody zero is coming from ...
thanks for the quick solution!

from ithowifi.

Sorry config.json is what I meant indeed!
Are you using Edge on windows? Do you have for example chrome to test wether you observe the same behaviour?

from ithowifi.

Indeed using Edge on win10.
Tried now using firefox and edge one after the other.
both switch off mqtt, save
both switch on and retype the IP, save
both work as expected, that is no extra 0 on edge.
do I need to change the config.json inbetween stop / start ?

from ithowifi.

the config.json file is not removed when you switch MQTT off. Best is to delete the config.json file (menu reset -> reset system config) and try it again.
Your wifi settings will be unaffected by this.

from ithowifi.

hi arjen,
did that and all mqtt settings are gone, filled them out again and it worked on both firefox and win10 edge.
No clue what went wrong yesterday.
the whole system seems more responsive now than it was yesterday even prior to setting the mqtt settings, maybe it was still doing something after starting up.
Anyhow shouldn't put to much thoughts into it for now and for me this issue can be closed.
I learned a lot more about the system now, going into the edit-section and doing all this.
Thanks for the quick responses and helping me out.

from ithowifi.

Strange, I cannot reproduce it either. But still two interesting glitches found, thanks for that!
The MQTT task timeout is shorter than the MQTT connection timeout, this caused the reboot. I will fix that in the next version.
I will also look at input validation for the IP address fields.

from ithowifi.