The reason for the ask is fairly simple. There are a thousand different ways to do things in Hubitat with most folks using the KISS principle when designing rules. The test that was created is similar, but still very different, to what your actual goals are. For instance, we still do not know how you plan to trigger this rule before the conditions even become a factor. Full knowledge of your goals allows the community to be at its best and come up with ideas/solutions that might be simpler in nature.
With the above said, @hubitrep has a good idea. The one change I would recommend is you could use "in between" as your trigger rather than changed. Just set the in between to go from 0 to a very large number. Here is a tiny example using Lux that could possibly work for your needs:
Rule
Logs
You could also look at [RELEASE] Device Activity Check - Get notifications for "inactive" devices and other community apps that might be able to fill in the gaps.
This is important too. The more information and details provided, the better we all can help.
