Author Topic: FOSHKplugin - brief introduction  (Read 1269 times)

WA4OPQ and 1 Guest are viewing this topic.

Offline olicat

  • Senior Contributor
  • ****
  • Posts: 201
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #25 on: September 16, 2020, 06:28:41 PM »
Hi!

Quote
I am experiencing the GW100 reconnecting to the WiFi every 10 minutes, apparently it is looking for a HTTP 200 OK from ecowitt.net
I haven't noticed that before. But after you wrote that, I took a closer look at it.

My test GW1000 with firmware v1.6.1 is configured via WS View in such a way that, apart from the custom server, all other Internet-pointing services (WU, EW, WC, WOW) are deactivated.
In addition, I blocked the Internet traffic via the firewall at the gateway. Requests from the GW1000 to the Internet would be logged at the gateway, but not forwarded.

In fact, this GW1000 cuts the WIFI connection every 10 minutes, only to re-establish it a short time later (12 seconds).
Of course, this also results in a DHCP request. I did not check further whether any packets were lost during the renegotiation of the IP address.

During the observation period, however, I did not find any attempts by the GW1000 to call up any external servers - apart from NTP!

After a reboot, the GW1000 has the time 08/22/2019 10:00:00 - without internet access it cannot get the current time from cn.pool.ntp.org via NTP due to lack of internet access.
The messages sent via custom server would therefore have the wrong time!
Thus, for proper operation - since you unfortunately cannot configure the NTP server in WS View - you would have to direct the hostname cn.pool.ntp.org to a local NTP server via a local DNS.
I also don't know whether the DHCP client of the ESP8266 would make use of option 042 (transmission of the time server via DHCP) - unfortunately my router (Fritzbox) cannot send this by itself.

So I have now forbidden internet access for the GW1000 on the firewall except for NTP. After a reboot, he receives the correct time (unfortunately from an external source).

I will ask Lucy to make the time server configurable in the future - but I have little hope of a quick implementation.
I will also ask why the GW1000 interrupts the WLAN connection every 10 minutes when ecowitt.net is deactivated.
Apparently the GW1000 is testing the WIFI-connection by checking every 10 minutes whether a connection to ecowitt.net was successful. If not, the WIFI connection will be re-established as a precaution.
That's not a bad idea in the beginning. However, at FOSHK they obviously did not think that someone might not want to use or cannot use ecowitt.net.
As soon as I enable sending to Ecowitt via firewall again, the WIFI connection remains stable.

For someone who plans to use the GW1000 completely without the Internet, the only thing left for the time being is the use of a local DNS server, which redirects requests from the GW1000 for cdnrtpdate.ecowitt.net and cn.pool.ntp.org to internal services.
DNSmasq could be suitable for this ...

Quote
FOSHKplugin states no internet is required. Have you solved this issue?
FOSHKplugin does not need the Internet to make the data available locally or to convert it between the different formats.
The GW1000 currently requires access to an external NTP server because of the time and a successful connection to Ecowitt in order to satisfy the watchdog in the GW1000. Otherwise the WIFI connection will be re-established every 10 minutes.

It would be interesting to know whether the HP2551C or other devices from FOSHK/Ecowitt also causes these problems.

Greetings, Oliver
« Last Edit: September 16, 2020, 06:36:03 PM by olicat »

Online WA4OPQ

  • Senior Contributor
  • ****
  • Posts: 193
  • 4 stations: 2902 array, GW1000, 3 on Meteobridge
Re: FOSHKplugin - brief introduction
« Reply #26 on: September 16, 2020, 07:51:30 PM »
Thank you for so thoroughly confirming my observations.

I send the GW1000 observation data to WeeWx which then creates a wxnow.txt type file which is sent to an application called aprx, which transmits the data about 20 km via ham radio.
WeeWx is using the correct time and date so the output is correct regardless of the wrong time and date from the GW1000

When I saw that FOSHKplugin included an integrated web server I incorrectly thought it could be used to send the HTTP 200 OK to the GW1000. But it is not that simple.

Thank you again for looking into this.

Offline olicat

  • Senior Contributor
  • ****
  • Posts: 201
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #27 on: September 17, 2020, 01:44:42 AM »
Hi!

Quote
When I saw that FOSHKplugin included an integrated web server I incorrectly thought it could be used to send the HTTP 200 OK to the GW1000.
It does.
But of course only if FOSHKplugin receives the data from the GW1000. It cannot send such a response to requests to external addresses because it does not normally receive these requests.
However, if you redirect the hostname cdnrtpdate.ecowitt.net to FOSHKplugin via the local DNS server, FOSHKplugin responds with 200 and this answer should be sufficient to satisfy the watchdog. The WIFI should remain stable.

Oliver

Online WA4OPQ

  • Senior Contributor
  • ****
  • Posts: 193
  • 4 stations: 2902 array, GW1000, 3 on Meteobridge
Re: FOSHKplugin - brief introduction
« Reply #28 on: September 17, 2020, 01:58:27 AM »

Ahhh.... this could work. Tomorrow I'll install FOSHKplugin and rename my hotspot to cdnrtpdate.ecowitt.net and play with dnsmasq.

Thanks!

Offline kd7eir

  • Senior Member
  • **
  • Posts: 98
Re: FOSHKplugin - brief introduction
« Reply #29 on: Yesterday at 06:08:27 PM »
As usual, I was overthinking everything and got hung up on what you were asking for the UDP port for in the setup script. Once my wife broke through my engineer's analysis paralysis I skipped it and now I have the plugin sending to two instances of PWT, Ecowitt, and WU. I'll soon be hosting my Meteotemplate site on my Pi and forwarding to that as well.

Thanks for the great plugin.
« Last Edit: Yesterday at 07:18:36 PM by kd7eir »

Offline olicat

  • Senior Contributor
  • ****
  • Posts: 201
  • DP1500 & FOSHKplugin
    • FOSHKplugin
Re: FOSHKplugin - brief introduction
« Reply #30 on: Yesterday at 07:09:51 PM »
Hi!

Congratulation!

Quote
hung up on what you were asking for the UDP port
Yes, unfortunately this is an omission in the current documentation, sorry! The UDP settings are not required for forward operation, so the default values are also empty. I'd better point it out. I will do that.

Quote
I'll soon be hosting my Meteotemplate site
Unfortunately, the forward to Meteotemplate is not yet possible with the currently available version v0.06. In the upcoming version v0.07, Meteotemplate will be fully supported via API interface. And there will be some other nice functions ...
Let me know if you can't wait and want to use a beta version of FOSHKplugin.

Oliver

Offline kd7eir

  • Senior Member
  • **
  • Posts: 98
Re: FOSHKplugin - brief introduction
« Reply #31 on: Yesterday at 07:17:29 PM »
Hi!

Congratulation!

Quote
hung up on what you were asking for the UDP port
Yes, unfortunately this is an omission in the current documentation, sorry! The UDP settings are not required for forward operation, so the default values are also empty. I'd better point it out. I will do that.

Quote
I'll soon be hosting my Meteotemplate site
Unfortunately, the forward to Meteotemplate is not yet possible with the currently available version v0.06. In the upcoming version v0.07, Meteotemplate will be fully supported via API interface. And there will be some other nice functions ...
Let me know if you can't wait and want to use a beta version of FOSHKplugin.

Oliver

I'm fine waiting for Meteotemplate compatibility as that's the lowest priority for me right now.

 

anything