I took some time yesterday to try out the development branch, and I must say that it seems to be a great step forward. I love how all configuration now is in one file, and that you now get direct access to the Sensors' objects. Also, the FEATURE_ constants really simplify configuration.
One thing that surprised me, which probably was the same in the previous versions, is that the interrupt driven sensors (
SensorInterrupt and its derivatives), define an empty
onLoop. This way, it is not possible to get them to report it's status after a given interval, despite not having received an interrupt. Something like the Force Update Timer in Conditional Report mode.
That's a feature I would like to have: a sensor that responds to interrupts (so has an immediate response to change, but sleeps a lot), but also sends a confirmation of its status every now and then.
I imagine you have thought about this yourself: how would you feel if I tried to formuate a pull request for this feature?
I suspect that this may also explain some strange behaviour that I see on
SensorInterrupt sensors when
FEATURE_CONDITIONAL_REPORT == 1. In that case, it seems that the
SensorInterrupt never manages to send an update message. See my logfile here. This works fine with conditional reporting switched off.
Or am I just interpreting things wrong? I have to admit that I'm quite new to MySensors.