Configured hostname is not used

[mrtnbr]

Since updating to 0.10.0 the hostname I configure in settings is not actually used, it seems to be "esp-" with the last few digits of the MAC address added.

I have tried resetting all settings to default and then reconfiguring, rebooting, power cycling the ESP and OTGW, but nothing seems to make a difference.

Config file has the right setting, I see the right setting in the UI but the actual hostname is different.

Some more info: - NTP also does not seem to work NTP Not working was a configuration error on my network, my DHCP server was giving out a non-working NTP server

• Telnet works
• MQTT/HA works

settings.ini.txt debug.txt

[rvdbreemen]

I assume that you also have rebooted the ESP? Or turned off and on? Just to make sure you tried that too.

[mrtnbr]

Yes, I unplugged the power and plugged it back in after a minute.

[rvdbreemen]

What’s you upgrade path so far. You went from 0.9.5 to 0.10.0 and now to 0.10.1?

Also what’s your network setup, it kind of sounds like there is a network issue to me at this point.

Could you share some logs from the esp?

[mrtnbr]

Yes, 0.9.5 (and before that older), then 0.10.0, then 0.10.1

WiFi access point is a MikroTik cAP, router is a MikroTik RB5009. The ESP connects and shows up in the router, MQTT works well. Hostname just seems to not change.

I have flashed an unused spare ESP with the firmware, and it show the same behaviour. It might still be a network issue, or something in my workflow, but I guess that rules out any old stuff from previous versions.

Where can I find the ESP logs?

[DaveDavenport]

I just tested this on mine. Changed it from OTGW -> OTGW2. Using avahi I see it on otgw2.local. So it should resolve fine under otgw2.local. But indeed my accesspoint reports esp-{numbers}.

NTP works fine for me, but I redirect all ntp traffic to my own ntp server.

[Roos-AID]

Robert, I just flashed 0.10.1+56994f1 and the hostname on the AP changed to ESP-xxxxxx The configured (OTGWELGA) Hostname still resolves when http://otgwelga.local is used.

It seems only to be related to the Wifi AP connection.

With 0.10.0 it shows the correct hostname in the Wifi AP logs.

[rvdbreemen]

As I have MikroTik here as well. I will go an check to see what my MikroTik sees. Not sure why this is happening now, as there has been no change in the last binary. So it must be introduced when going to 0.10.x

[mrtnbr]

As I have MikroTik here as well. I will go an check to see what my MikroTik sees. Not sure why this is happening now, as there has been no change in the last binary. So it must be introduced when going to 0.10.x

Thanks. Yes, for me 0.9.5 worked as expected, when I upgraded to 0.10.0 it changed. 0.10.1 did not make a difference from 0.10.0

EDIT: added logging from MikroTik

And a ping to .local:

[rvdbreemen]

@mrtnbr Thanks for reporting this. I have to look into this myself, there is only once change that I can think off to be honest. In the mean time I can confirm myself too that I see this issue.

We will figure this out.

[mrtnbr]

@mrtnbr Thanks for reporting this. I have to look into this myself, there is only once change that I can think off to be honest. In the mean time I can confirm myself too that I see this issue.

We will figure this out.

Thank you! I have updated the opening post, my NTP not working was caused by a misconfiguration on my DHCP server, it was giving out a non-working NTP server.

[Roos-AID]

Robert, I think it has to do with Wifi library version. I have my test unit still running on 0.10.0 compiled by myself and this one does not show the behaviour. Unfortunatly I migrated my VSC environment to latest versions so I cannot check which Wifi lib version I used.

[rvdbreemen]

Well, it seems that it is indeed the wifi library issue. But also the order of things, because I moved the NTPstart() back after the Wifi Start... and it now works again. So I have a fix, but we lose overwritting the NTP setting using DHCP again.

[brhahlen]

I think this also affects me. I use authentication for MQTT, but since the upgrade to 0.10.0, I got an "client not authorized" error, and it showed "OTWG" as the requesting client, instead of OTGW, which I had defined.

[rvdbreemen]

This issue has been fixed. The next release will resolve the issue. If you like to help test / validate this. Please come to the discord and ask to be added to the beta channel (if your not already).

[mrtnbr]

This issue has been fixed. The next release will resolve the issue. If you like to help test / validate this. Please come to the discord and ask to be added to the beta channel (if your not already).

I have tested the new build and I can confirm the problem is fixed for me. Thank you!

[rvdbreemen]

Thanks @mrtnbr I will go and do a release soon, with just this single fix.