Notify/watchdog regexp matching

[Mario]

Hello,

Is there possibility to match with watchdog/notify on event source device which is part of event line ?
I need to catch events coming from HMCCU (or HMCCUDEV or FHT) without just relying on device naming,

In regexp regarding notify there is stated that regexp is joined with ^ $  but it I belive it is matched against on part starting with device name, 
so not whole as seen in event monitor (or output from inform on)

on event in event monitor there can be seen
TIMESPEC  DEVICE_MODULE  Matching_part_with_device_name:  VALUE

or I'm missunderstanding something ?

[Beta-User]

Hi Mario,

sorry for the late answer.

It's a little hard for me to understand what you are looking for, and mixing questions about different device types also makes it much more complicated to answer.

So for now, I'd concentrate on notify:
In general, at least that module will add ^and $ to the "Expression" regex, so finally something like =~ /^Expression$/ will be used. If you want notify to watch out for a middle part, let's say  "press", you just have to add some ".*" patterns, so in notify you'd write ".*press.*".

Helpfull?

Btw.: for "Starters questions" like this one (?), I'd recommend to use the "english" corner. That's where some special guy's and other english-speaking users most likely will have a look to provide more timely answers.

[Mario]

Hello, thank you for answer,

I will try to clarify, I'm addressing fact that from my tests and understanding of documentation,

watchdog and notify share the same matching scheme  -  and are not capable on matching FHEM module name

so ~/^Expression$/ is matched starting from user device name e.g. on event monitor you get (e.g. inform on):

Code Auswählen Erweitern


FS20       sCWU_pump off
LaCrosse WeatherHome rain: 8998


but matching is started at second word (user device name sCWU_pump or WeatherHome in above example)

and this is enough and handful in case of notify,
but I believe watchdog is sharing the same scheme
and it would be more useful to have matching starting from FHEM source module for watchdog,
e.g. I need today to match stall/missing events from HMCCU FHEM module

[Beta-User]

Hmm, you are right: The module Type is not part of the event at all, at least as far as notify and watchdog are concerned.

Esp. watchdog isn't really capable for "generalisation" (watch on the same reading for multiple devices and keep track of each of the readings), seems you are looking for something doing that?

You could try to differenciate reaction after triggering (especially with notify) by checking device's TYPE afterwards, but that's rather complicated aas well.

So in general it's easier to use some kind of naming sheme allowing to restrict eventhandler devices like notify to only the desired devices.

Wrt. to HMCCU (esp. at startup) afai understood, there's some changes in behaviour to come, you'd better ask for help on that specific issue in the homematic part of the forum and check recent forum posts for the keyword "4.4". That might keep private efforts on supervision much smaller than expected. (I'm not using HMCCU, so I'm not able to discuss in detail).