I have about 20 Homematic devices connected to a Homegear controller. I have always been puzzled, why a dead battery in one device (Thermostat) is followed shortly after by dead batteries in the connected device (Valve drive) but this is explained here: https://homegear.eu/index.php/BidCoS_Packet_-_General_Information
even though I don’t know if HM-TC-IT-WM-W-EU and HM-CC-RT-DN behaves the same as the old controller valve combination. The window contacts are not drained.
What I not understand is why the smoke detectors which are not paired to heating are also drained terribly fast (1 week from new batteries). Does the central unit go into panic mode trying to reach the devices with dead batteries waking up everybody else?
all mentioned devices use a mode called wake on radio (WOR) or “burst”. It works by listening for a long (about 360 ms) preamble signal. If such signal occurs the device wakes up. The advantage is that a battery powered device can respond immediately to a sent packet. But it comes with in my opinion huge disadvantage: The wake up is not specific. All devices having this mode enabled wake up even if they are not addressed. For some devices (e. g. HM-TC-IT-WM-W-EU and HM-CC-RT-DN) WOR can be (partly) disabled. I. e. Homegear doesn’t use WOR any more to contact these devices then but they still wake up from WOR packets. Still that might help a lot.
I thank you very much for the information. Is WOR only sent by the central unit or could any device send a WOR? Does the WOR turn up in the log on the central unit?
In any case I will make sure that all devices can reach all paired devices at all times, which means another central unit because of too much reinforced concrete.
I had also polling disabled on all devices. So it seems to have been the same problem. The latest nightly is installed. Now I have only to get some fresh batteries.