Is the API documented online somewhere? I've not been able to find is so far.
On Tuesday, February 16, 2021 at 7:41:36 AM UTC-8 [email protected] wrote: > If 'reset' does a factory reset, I think I agree with you - not too much > value in that for me. OTOH, being able to reboot remotely, at least in my > case, might be a benefit. > > While I understand the ability of Weewx and the GW1000 driver to attempt > to reconnect to the gateway. Unfortunately, that doesn't solve the problem > if it's alive but unresponsive. > > Thanks for the reply. > > Sean > On Monday, February 15, 2021 at 8:51:52 PM UTC-8 gjr80 wrote: > >> Can't speak for Monit, haven't used it and only briefly skimmed an >> article on it a year or two back. Whilst the GW1000API has commands to >> reset and reboot the device I have not implemented them int he GW1000 >> driver and I have been loathed to do so. I really don't see much point in >> giving the driver the ability to factory reset the GW1000; if the device is >> factory reset you need to use the WS View app to pair/configure the device >> again so you might as well goto the device or use the WS View app to >> factory reset if such action is warranted. I could see some utility in >> being able to reboot the GW1000, but I suspect that in almost all >> situations where you would want to take such action you have lost contact >> with the GW1000 and I doubt you will be able to command the GW1000 to >> reboot via the API. >> >> That being said WeeWX and the GW1000 driver have a couple of features >> that attempt recovery if contact with the GW1000 is lost. Firstly, if a >> driver cannot be loaded WeeWX has the ability to keep trying to load the >> driver every 60 seconds rather than exiting (refer loop_on_init config >> option <http://weewx.com/docs/usersguide.htm#General> in weewx.conf). >> Secondly, if the GW1000 driver cannot contact the GW1000 on startup, or if >> contact is lost during normal operation, the driver re-attempts contact a >> number of times and if contact cannot be made the driver will attempt to >> re-discover the GW1000 on the network. These may or may not work depending >> on the issue, the log would be need to be checked to see what the symptoms >> were and what WeeWX/the driver did. >> >> Ultimately if the GW1000 cannot be contacted and cannot be discovered >> then there is not much that can be done short of notifying you to go and >> hit the reset button. >> >> Gary >> >> On Tuesday, 16 February 2021 at 11:56:49 UTC+10 [email protected] >> wrote: >> >>> Not bothering to post logs, etc., because this isn't a "problem" with >>> the software. >>> >>> Been using Weewx for a few years with Acurite 01525 but finally got fed >>> up with the horribly flaky RF from sensors to console and recently >>> transitioned to Ecowitt and the GW1000 with temp, wind, and rain sensors. >>> Loving it so far although the WS View app on Android apparently had a bug >>> that initially prevented me from configuring the gateway properly. Kudos to >>> the Ecowitt team who were very responsive ([email protected]). >>> >>> Browsing the weewx-user group I found >>> https://github.com/gjr80/weewx-gw1000 and that's a delightful piece of >>> code, every bit as good an useful as Weewx itself. >>> >>> The gateway has gone offline a couple of times in the past 48 hours for >>> reasons unknown. Its leds are flashing as if it's online, and it can >>> sometimes be pinged so it's on the wlan, but it doesn't respond to API >>> requests for the driver. I'd like to monitor the gateway from a monit >>> server that I have running on my network and while I can test for the host >>> alive and send an alert, I'd really like to monitor the gateway function >>> itself somehow. >>> >>> If it were a linux box under the covers and had access, I could script a >>> solution on the gateway itself but I don't think that's possible. I note in >>> the GW1000 driver that the command list has a "reset" and "reboot" command >>> and wonder if the driver will allow me to send either one of those by >>> itself? >>> >>> Any other suggestions? >>> >>> Thanks! >>> >>> Sean >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f20485e9-5da2-48ab-bcc3-43b152f92e2an%40googlegroups.com.
