Hi!
In the next FOSHKplugin version, there will be a new function that might appeal to some people.
I at least use FOSHKplugin here for dozens of forwarding destinations. It works without having to worry about it. It simply runs.
The problem is more with the remote stations that are supposed to accept and process the weather data. If they are (temporarily) unavailable, it is difficult to notice.
FOSHKplugin then simply tries to send the valid data at the next interval.
Any errors are logged in the log file, but who looks at it every day without a reason?
I certainly don't!
In order to still receive information relatively promptly if a forward destination is not reachable for a longer period of time, as of v0.10 there is the possibility to be informed via push notification (Pushover).
After a configurable number of successive unsuccessful attempts, a push message is sent:
FOSHKplugin
From FOSHKplugin on 2022-11-09 at 19:10
forward FWD-17 (EW - PWT @Leo Tablet) was unsuccessful 10 times since FOSHKplugin start (last result: TIMEOUT)
* 192.168.15.236 for ws@192.168.15.215; 11-09-2022 19:10:32 *
or
FOSHKplugin
From FOSHKplugin on 2022-11-09 at 17:21
forward FWD-53 (INFLUX2MET - InfluxDB 2.x-Forward of metric values to LoxBerry) was unsuccessful 10 times since 09.11.2022 17:15:35 (last result: : Failed to establish a new connection: [Errno 113] No route to host)
* 192.168.15.237 for ws@192.168.15.221; 09.11.2022 17:21:13 *
Included are the forward designation (Forward-nn), the forward type (FWD_TYPE) and any forward comment (FWD_CMT) - together with the error message and the time of the last successful transmission.
This message is sent exactly ONCE after the number of failed attempts specified in the config file under Warning\FWD_WARNINT. The default value is 10.
With each successful attempt, the internal counter is reset - so you really only get a warning if the specified number of failed attempts occur after each other.
After a push message, another message is only generated for this forward if at least one forward was successful before and thus the internal counter was reset.
This function can be deactivated via Warning\FWD_WARNING = False in the config file.
As usual, however, this can also be deactivated at runtime via http (http://ipaddress:port/FOSHKplugin/fwdwarning=disable) or via UDP (Plugin.fwdwarning=disable) or activated via enable.
In addition, there is also a simple html page at http://ipaddress:port/FOSHKplugin/fwdstat that shows the status of all activated forwards. There you can see at a glance whether and since when a forward has been hanging and, if so, with what error message.
The dimensioning of FWD_WARNINT is not yet completely clear. The default is currently 10 - i.e. 10 unsuccessful attempts.
With a transmission interval to the target of 30 seconds, a warning would come after 5 minutes (10*30 seconds) - if the target could not be reached continuously.
If, however, the interval is 1 minute, the warning will only come after 10 minutes of uninterrupted inaccessibility.
And if the transmission interval is 10 minutes, a warning is only given after 10*10 minutes = 100 minutes.
Perhaps I should not specify FWD_WARNINT globally for all forwards, but allow a setting option per forward?
Or would it perhaps make more sense to specify a fixed time (such as 15 or 30 or 60 minutes) as a global setting?
What do you think? What do you think makes sense? What would you wish for?
And would you use this feature at all?
I don't know how many users actually use the
push function of FOSHKplugin - I like the notification that a sensor's battery needs to be changed or a thunderstorm is coming or that a sensor no longer reports (e.g. because the cap of a WH51 has come off again).
Regards, Oliver