notification for sensor malfunction not sent

Discussion of the Meteohub software package

Moderator: Mattk

Post Reply
web_smith
Fresh Boarder
Fresh Boarder
Posts: 16
Joined: Mon Jan 07, 2008 11:02 am

notification for sensor malfunction not sent

Post by web_smith »

Hi,

upon malfunction - here: not recognized transmissions/weak signal - of a sensor no mail as immediate action is sent.

I received a message after 5 hours of no transmission of the rain sensor.

Is there a possibility to configure the time limit, after which the sensor is treated as missing?

In that turn: is there a possibility to create an additional port, where upon connection just the information of the total number of available sensors for a defined time range in the past is printed? Additionally there might be printed the names of the sensors or just the name of the missing sensor. This would make it easily possible to create a check for monitoring systems like Nagios et al.

Greetings,

Stefan
User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 7878
Joined: Mon Oct 01, 2007 10:51 pm

Re:notification for sensor malfunction not sent

Post by admin »

If you like you can ask Meteohub on port 5556. ON my heavy sensored rfxcom meteohub a \"netcat meteohub 5556\" returns:

Code: Select all

rfxcom
t1      THWR288 2       4       0xea4c  0x3f    0       -177    1
th4     THGR228N        4       3       0x1a2d  0x0f    14      79_74_36        0
th0     THGR918 1       3       0x1a3d  0xae    31      94_73_48        0
th1     THGR228N        1       3       0x1a2d  0x94    3       213_44_86       1
t0      THR128  1       4       0x0a4d  0x07    27      109     1
thb0    BTHR918N        0       2       0x5a6d  0xb1    6       228_40_85_9970_10002    0
th3     THGR228N        4       3       0x1a2d  0x6f    42      93_84_67        0
uv0     UVR138  0       6       0xea7c  0xa8    60      0       0
th2     THGR228N        2       3       0x1a2d  0xd4    24      278_26_65       0
th6     THGR328N        1       3       0x9acc  0x77    168     232_39_85       0
uv1     UVN800  0       6       0xda78  0xae    46      0       0
wind0   STR918  0       0       0x3a0d  0x4a    30      0_0_353_N       0
rain0   RGR126  0       1       0x2a1d  0xb6    42      0_21410 0
The last Number is \"1\" for lowbat (\"0\" for ok), the third last number tells you the seconds since last sensor signal. above data corresponds to a screen like this (numbers may have varied between netcat and screen shot):

Image
web_smith
Fresh Boarder
Fresh Boarder
Posts: 16
Joined: Mon Jan 07, 2008 11:02 am

Re:notification for sensor malfunction not sent

Post by web_smith »

I will try to work something out on that output.

But nevertheless it troubles me, that the \"immediate\" mail w/r to the sensor fail is not sent, but 5 hours later.

Stefan
Post Reply