This would be somewhat cumbersome but not impossible. You'd need to save the device attribute (battery, in this case) value to a variable, then use that variable to build a string you'd send in a notification or whatever mechanism you want. As an example:
Trigger: (whatever weekly schedule you want)
Actions to run:
Set variable tmpBattery to device attribute: Sensor 1 battery
Set notifyText to "Sensor 1 battery: %tmpBattery% "
Set variable tmpBattery to device attribute: Sensor 2 battery
Set notifyText to "%notifyText% Sensor 2 battery: %tmpBattery% "
Set variable tmpBattery to device attribute: Sensor 3 battery
Set notifyText to "%notifyText% Sensor 3 battery: %tmpBattery% "
Notify (your phone): '%notifyText%'
This rule also requires you to create two variables. To do it as I do above, you'll make one called tmpBattery of type Number and one called notifyText of type String. Local variables (in the rule) would probably be best, though there's no reason you could use a hub variable if you have a use for them outside the rule too (unlikely).
My "cumbersome" comment above refers to the facts that:
- each device requires two actions of its own, even though it's nearly the same thing for all of them
- the second of these actions requires you to manually type the device name and match what you've selected in the previous action (if you want it to make sense, ha)
Also, I think you'll get a new line between each if you just press Enter or Return at the end of the text in the "Set variable..." actions above, though I haven't tested that for sure. (A comma or whatever you want in between would also work.)
This would probably be easier with a custom app. I have one that can almost do what you want, though my intent was for it to notify only of batteries below a certain level (I guess you could set it to 100?) and the battery feature was really secondary to the "Last Activity At" check that I wrote the app for. There may be something more specific out there. Otherwise, you certainly can do it with a rule... 