Sorry for the late answer, my wedding was the day after you posted this question, so I didn't see it :-(
The "read" flag behaves like in ETS. It controls if linknx will answer to a read request coming from another device on the KNX bus.
Actually, Object::read is only called if you don't specify the initial value for an object. If you add parameter init="some value" to the object definition, it will never issue read request on the KNX bus, so there is no need for a flag.
Regards,
Jean-François
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jean-François,
why are you not preventing read requests for KNX objects which do not have the READ flag set.
I would have expected that the whole bode of Object::read should be only executed,
if the
(flags_m & READ)
condition is true.
best regards
Michael
Hi,
Sorry for the late answer, my wedding was the day after you posted this question, so I didn't see it :-(
The "read" flag behaves like in ETS. It controls if linknx will answer to a read request coming from another device on the KNX bus.
Actually, Object::read is only called if you don't specify the initial value for an object. If you add parameter init="some value" to the object definition, it will never issue read request on the KNX bus, so there is no need for a flag.
Regards,
Jean-François