WatchDog rule?

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
User avatar
uxhamby
Normal user
Posts: 132
Joined: 29 Dec 2016, 18:13
Location: Toronto Canada

WatchDog rule?

#1 Post by uxhamby » 01 Feb 2021, 16:38

Hi.

Is it possible to fashion a rule to reboot the ESP, if it can no longer see itself on the network or in the UDP list?

Thanks,

Brian H.

TD-er
Core team member
Posts: 8750
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: WatchDog rule?

#2 Post by TD-er » 01 Feb 2021, 18:22

We have the ping plugin, so you could act on the events generated by a task running the ping plugin.
For example to ping the gateway.

User avatar
uxhamby
Normal user
Posts: 132
Joined: 29 Dec 2016, 18:13
Location: Toronto Canada

Re: WatchDog rule?

#3 Post by uxhamby » 02 Feb 2021, 21:19

Thanks, but can I elicit some more detail on its use?

Where is this documented?

If I put "ping" on the command line, I get as follows:
Command unknown: ping 192.168.55.1
Is the "ping plugin" part of the prebuilt packages, or do I need to compile it in myself?

Thanks,

Brian H.

TD-er
Core team member
Posts: 8750
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: WatchDog rule?

#4 Post by TD-er » 02 Feb 2021, 21:59

Plugin 89
Should be part of the "testing" build (currently ESP8266 only so it seems)

And this documentation is probably not going to help you very much, I'm afraid.... https://espeasy.readthedocs.io/en/lates ... #p089-page

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 110 guests