@mfalkvidd Thank you for your valuable suggestions - they all look very relevant.

Perhaps I am overlooking something in the documentation, but I wonder if any existing controllers out there will get the node's relay outputs in the right state again after a node restart, if it always starts up in off state.

Besides that, how can I reliably detect communication in the node, such as I_HEARTBEAT/I_HEARTBEAT_RESPONSE? As far as I know, such internal messages do not arrive through the recieve(...) API function. I will need to see some incoming messages (also from existing controller implementations) - otherwise I would get timeouts.

Best regards
Lasse

I wonder what would happen for a Relay Actuator (as shown among the examples) if the communication with the controller is lost. Then the outputs may be active forever.

So, I believe an actuator like this should not be trusted to activate anything critical (heaters, pumps etc.) unless I add functionality to turn off the output in case of communication timeout. I guess I can not count on existing controllers to keep sending regular updates to the output state, so I don't know how I could even detect communcation timeout. What do you recommend?

Hi,

I have a sensor receiving the DCF77 time signal from Germany. It is used at a remote site without Internet access.

I could just transfer the date/time as custom values, but perhaps date/time could be relevant as a future sensor type/value? Other relevant information:

• Time source or general reliability/precision
• Current status/precision (time OK? OK but needs external sync? Unknown?)
• UTC or time zone?
• Daylight saving time?

Thanks,
Lasse