When the smart home is confidently wrong
Two lies, same confidence.
One was standing in the hallway, insisting that an intrusion had been detected. The other was at the front door, calmly reporting that the lock was unlocked.
Neither matched the house.
The alarm in the hallway
The motion sensor had several internal channels. The ordinary motion and tamper sensors were both clear. So was the accelerometer. The battery was healthy.
But a separate, redundant alarm channel remained active.
The history showed that it first switched on during an ordinary moment of motion and then never switched off. The useful sensors had recovered perfectly. This extra channel had missed the ending of the story and held onto the beginning.
Then came a restart.
The old active state was restored, and the hallway sensor once again declared an intrusion. Every restart made the answer more confident without making it any more correct.
There was no burglar to investigate. There was a latched message from a sensor channel we did not need. So I disabled that channel and left the ordinary motion and tamper sensors alone.
An alarm label is not a diagnosis. Sometimes it is only a very convincing memory.
The door that was not open
Later, the front door reported that it was unlocked, but it was physically locked.
Its recent history contained no ordinary lock or unlock activity. Instead, there was the same short sequence after every restart: unavailable, unknown, unlocked.
The house had moved to new hardware, but the lock’s smart-home connection was still looking for the previous hub. It could not deliver a fresh status, while the new hub faithfully preserved the last status it had heard.
Even a lock command sent from Home Assistant produced no answer. The command left the hub, but the lock was not there to receive it.
The fix was wonderfully ordinary after the diagnosis: update the address the lock uses to reach its smart-home hub. No web prefix. No port. Just the address itself.
The lock connected, and within a couple of seconds reported what was actually true:
Locked.
A state is a message from the past
These two problems looked alike from the dashboard. One sensor said something alarming. One lock said something wrong. In both cases, the physical device was fine and the software was repeating an old answer.
A smart-home state is not a view from God. It is the last report that successfully made it through the conversation.
So when the house and the dashboard disagree, I no longer begin by assuming that one of them is lying. I ask:
- Did this state change during normal use, or only appear after a restart?
- Are the device’s more specific sensors agreeing with it?
- Is the device still participating in its smart-home connection?
- Could an old message have survived the move to new hardware?
The goal is not to make the dashboard agree by force. It is to find the conversation that stopped — and get the house reporting the truth again.