I had a look at Nick’s proposed handler. There are quite a number of changes in it that I wouldn’t want to roll in without further evaluation as to the side effects.
For starters, it publishes always, i.e. StateChangeType.CHANGED is now StateChangeType.ALWAYS. That would defeat the whole duplicate removal, which some users wanted.
Then it actively queries the battery life. This is usually only done for battery-operated devices, and for those we have the “*SleepingContactHandler”. I’m confused now why we are using the handler for the hardwired devices.
Nick, do you still remember what the story was there?