Once again, this scattering of posts in different topics is making things hard to keep track of...
I assume you're talking about this other post where someone showed you how to add the healthStatus attribute to the driver? If so, you are missing the other part of what this poster mentioned:
Adding this attribute alone won't do anything. You would need logic in the driver to set the attribute to the desired value based on whatever criteria you want. This would often be a time-based reporting thing.
Or, again, you can use an app like Device Activity Check that does this for you at the app level. 
Personally, I do not think it would be a good use of your time to try to replace every driver in use on your hub with a custom driver that is modified to support this attribute. That is a goal that will likely never be accomplished (maybe for an instant, but then what if you add a new device?), and whatever reward there may be for the ones that do is unlikely to be worth the effort given the other solutions.
That is why many people use an approach like the one I suggested (and has also been suggested to you by others in other topics).
And it doesn't have to be either-or; you can use such an app with attributes for devices that do offer it.
