rvdbreemen / OTGW-firmware

A ESP8266 devkit firmware for the Nodoshop version of the Opentherm Gateway (OTGW)
MIT License
146 stars 34 forks source link

No web UI after clean flash 0.7.0 / related to NTP client Loop #15

Closed Nauttor closed 3 years ago

Nauttor commented 3 years ago

Hi, I flash both files on the 0.7.0 release on my nodemcu, it flash it as expected with no error. Afterwards I see the OTGW node active and I set the wifi successfully. I can ping it on my network and it response. Then I tried to connect to the web UI via IP address to setup the Mqtt but it does not response, like the web server is not active. Am I doing something wrong?

Thanks

Nauttor commented 3 years ago

OK, After a few hours looking around it, I discover that actually it's a bug.

The "problem" is that I have all my IoT devices in a segregated Vlan without access to the internet and firewalled(as it should be). Then after boot your firmware try to reach the NTP server, and if it does not reach the server it does not continue loading the web UI and every else it stay in a loop trying to connect to the ntp server.

As you can see only after I permit the traffic to the ntp in my firewall it continue.

Waiting for time sync Querying pool.ntp.org ... ERROR: Timeout Querying pool.ntp.org ... ERROR: Timeout Querying pool.ntp.org ... ERROR: Timeout Querying pool.ntp.org ... ERROR: Timeout Querying pool.ntp.org ... ERROR: Timeout Querying pool.ntp.org ... ERROR: Timeout Querying pool.ntp.org ... ERROR: Timeout Querying pool.ntp.org ... ERROR: Timeout Querying pool.ntp.org ... ERROR: Timeout Querying pool.ntp.org ... success (round trip 59 ms) Received time: Tuesday, 02-Feb-21 16:11:15.782 UTC Time is in sync Timezone lookup for: Europe/Amsterdam ... (round-trip 383 ms) success. Olson: Europe/Amsterdam Posix: CET-1CEST,M3.5.0,M10.5.0/3 UTC time: Tuesday, 02-Feb-2021 16:11:16 UTC CET time: Tuesday, 02-Feb-2021 17:11:16 CET Last reset reason: [External System] Gebruik 'telnet 172.16.77.167' voor verdere debugging

HTTP Server started

Assigned IP[172.016.77.167] Reboot count = [7] Setup finished!

___-

Please fix that when possible, and it would be great to have an option to set the NTP by han in the web ui.

Thanks

Nauttor commented 3 years ago

Hi,

I see that I can't either set the timezone by hand.

One more thing, there is a common deficiency related to the ESP8266 and is the lack of external Antenna to improve reception, only the ESP-01 and the ESP-07 have it but those have only 1 MB. However the ESP32 have plenty of memory and some of them have the external antenna connector. Can you compile the binary for the ESP32 too in the next release please? I tried to compile it myself but I get a ton of error related to my Arduino environment being not well configured.

Thanks

rvdbreemen commented 3 years ago

The firmware behaves as needed.

Two feature requests:

  1. Optional NTP synchronisation. For planned InfluxDB it is a requirement, but I guess we can disable features if dependencies are not matched.
  2. Port to ESP32. I could do that ofcourse, then you have to design your own hardware. Do you have a ESP32 version of the OTGW gateway at this point? I have ported another project over to ESP32, so it's doable.
Nauttor commented 3 years ago

The firmware behaves as needed.

Two feature requests:

  1. Optional NTP synchronisation. For planned InfluxDB it is a requirement, but I guess we can disable features if dependencies are not matched.
  2. Port to ESP32. I could do that ofcourse, then you have to design your own hardware. Do you have a ESP32 version of the OTGW gateway at this point? I have ported another project over to ESP32, so it's doable.

Hi @rvdbreemen ,

Thanks for your reply. Let me disagree on the NTP, it does behave as you want to behave, not as it should. The ntp as you said can be a requisite for influxdb to work, but not all the people want to use that feature, the "main" feature of a OTGW wifi node firmware should be give access to the Ser2net or mqtt access to the OTGW. So in order to work the OTGW wifi firmware does not need to access NTP, and in this case if it does not connect, you are hang in a loop indefinitely. At least, as you said it would be great to have the option to configure the NTP manually AFTER the node finished the boot sequence and you can access to the web page. So, optional NTP should be great.

About ESP32, I have 2 esp32 modules, one ESP32-WROOM-DEVKIT and one ESP32-Cam which is a great module because it have an external antenna connector which enables you to extend the range. In my case my boiler is far away from my AP and server and I can't install an ethernet cable, so I need to use an external antenna to make it stable. At the moment I connect the ESP32 with tiny dupont cables to the NodoShop board for testing, and it works with ESPEasy firmware on the esp32. It would be great to have a compilation for that board too as Is a more capable hardware. Thanks.

rvdbreemen commented 3 years ago

You have a good point. I will add a NTP enable/disable feature in a future release.

Nauttor commented 3 years ago

You have a good point. I will add a NTP enable/disable feature in a future release.

6a00d8341c7a9753ef016302a843b9970d-800wi

Hahahaha, thanks for your consideration :)

rvdbreemen commented 3 years ago

Feature will be in 0.7.6, currently in dev. Added another much wanted feature, enablement of setting up the TZ itself.

Nauttor commented 3 years ago

@rvdbreemen , the ESP32 port milestone appears as 100% complete it's an error or the 0.7.5 will be esp32 compatible?

rvdbreemen commented 3 years ago

That's a mistake. As I closed this ticket because of TZ not of ESP. I will try and correct it.