Posts made by iLusion

@martinhjelmare

The NodeID could be the least common denominator here, I'd think.

@dpressle ofcourse! I appreciate your help and I am sure, so does anyone who'd benefit from this thread. This is the power of open source and community supported projects!

Sending the same state over and over again won't be ideal. Here is why -

Assumptions

1. Node is not interrupt driven

Scenario

1. Loop 0 - Door closed, send state Door close as of T
2. Loop 1 - Door open, send state Door open as of T+1
3. Loop 2 - Door open, send state Door open as of T+2

Now, the door was actually, open at T+1, if HA processes, force updates then HA would show that door is open as of T+2 - We cannot now determine that the door was actually open since T+1 as oppose to T+2.

Hope this helps.

@martinhjelmare @dpressle Thanks guys for keeping the thread active.

The last time stamp of state change is not sufficient, e.g. The node status in HA shows as door closed as of T days ago but the node may have crashed at T+1 and door may have opened after that.

The force update of binary sensors may partially solve this but not really a good alternative as if HA processed force updates, information would be lost about when exactly the state had changed.

If HA shows last time stamp of Heartbeat then we could deterministically display the last status time stamp as well as last known state of the node itself. This needs to be configurable for nodes which do not generate heartbeats.

Thanks @martinhjelmare. My use case is as follows. I have nodes with binary sensors for door/window. These nodes send status information 1 or 0 upon events, say door opened or closed. They also send the heartbeat message at regular interval. I'd like to see the time when last heartbeat was received by the HA. This way, when I see the status of the Node in HA, I could determine if the Node is active or not. As of now, if the node crashed, I have no idea as HA simply shows the last status.

@Boots33 Duh! Should have read the comparison chart. Well, now search for another controller begins, unless any of the brilliant minds have any workarounds.

Thanks for such a wonderful platform.

I am trying out HA with My Sensors GW on RPi. My sensor node publish heartbeats at regular interval. How do I see the last heartbeat time in HA? Without this, there is no way to know if the node is alive. I have two nodes, which are offline and HA simply shows the last status, which is misleading.

Also, how do I configure HA to force process updates from nodes even if the new state is same as previous state?