Hi Angelo, I have just now upgraded my Pi and I am going to test the imeplemrntation in the coming weeks. Thank you very much to take the time and spend effort to this implementation. Ciao Giuseppe

Hi Angelo, the whole idea is to have a pushed and not pulled mechanism in normal operations (in a restart use case depending on who restarts the signalling would change) therefore considerting the example you made Hydrosys4 sends a message when a pin status changes at time zero and at time 5 minutes elapsed. If I have understood the software implementation correctely a first ON message could be sent at pin activation and a OFF could be sent once the callback de-activate the pin. Of course having a regular (and even configurable) status update interval time would be a top solution but of course the imeplemtnation complexity increases as you need to keep track of the timing in between callbacks ( ... well the call back could simply subtrack the interval from the remaining time then call a new one :) ) as well as have additional gadget to handle the config. I think a first step would be to have an instant picture then we could on top implement the regular update of the status to reflect also the history.

Hi Angelo, nice to read I am adding some value to the project. For the actuators I think we should look at the use case we are trying to implement. As owner of an automation system my basic interest is to check if something is ongoing or open/closed . Therefore when integrating towards an external system I believe the basic info needed is "ON/OFF" and "OPEN/CLOSED" information. Time of activation and position are additional information which can be used for use cases where I could implement feature like "progression" of an event which also would mean sending more messages during the ongoing action ... nice to have but not first priority in my eyes. What is your view on my point 3 about "restart" use cases. Most of the time, when a system restarts, it looses status information and I beleive it is useful to have those features to allow an update in those cases. What do you think? About testing, yes I think it is the minimum I can do as contribution to the project .... of course time allowing ....