Need some help with my first rule

Thanks, but the second one will not be triggered. This is why I need to get an trigger to the thing itself. Maybe it is not solvable.

See this post:

What sensor is it? A door sensor?
What channels for this thing get updated when you open/close the door?

My problem is, that I want to detect z-wave devices which are no longer sending datas.

For all of them I check battery item update event date. I get this configured for mostly all of my devices that they send this latest every 6h. Only for devices from aeon this is not relyable. They report battery item update randomly.
To detect item update on door open/close event does not fix it too because some doors are opened only some times a year. And event then I will notice or not, that the sensor does not report any more.

Hopefully it is clear what I want to reach.

In habmin I can see the last wakeon time, but donā€™t know how to get this into a rule.

So you want to see which things are onlineā€¦
According the thread you have posted above:

This works for me (for online/offline state):

when 
	Thing "zwave:device:15ca6a108b9:node26" changed
then

Notice the double quotesā€¦
Try that

yes, this will work for me too. But the thing is not changed, it is only updated :wink:

Changed is only from online to offline. And the device stays online even if it does not report any longer.

Only relyable from my point of view is to catch this message in a rule: But my rule does not get fired

2018-03-14 10:06:42.146 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:15a7a49f3a6:node3' has been updated.

none of this works:

when
  Thing 'zwave_device_15a7a49f3a6_node3' received update or // from habmin
  Thing "zwave_device_15a7a49f3a6_node3" received update or // from habmin
  Thing 'zwave:device:15a7a49f3a6:node3' received update or // from log
  Thing "zwave:device:15a7a49f3a6:node3" received update // from log
then
...

I have read the previous thread regarding this.
There appear that there is no direct solution to you problem.

Reading the log file and catching the lines seems to be a way to go

See: