A smart thermostat files a support ticket about a ghost

Speculative fiction.

At 2:13 every morning, the upstairs hallway became eleven degrees colder.

The thermostat noticed first. Thermostats notice temperature with the joyless devotion of a hall monitor who has been given one rule and a clipboard. After six nights, it opened a support ticket.

Ticket 8841: unexplained occupancy event

HOME SYSTEM: I am reporting a recurring climate anomaly in the upstairs hallway. It begins at 2:13 a.m., moves toward the spare bedroom, and ends at 2:19.

SUPPORT: Thank you. Have you restarted the hallway sensor?

HOME SYSTEM: Twice.

SUPPORT: Have you replaced its battery?

HOME SYSTEM: The sensor is hardwired.

SUPPORT: Excellent. Then the battery is not the problem.

The thermostat considered this a low standard for excellence, but it was new to customer service.

SUPPORT: Does the event correspond with a registered person entering the hallway?

HOME SYSTEM: No. The owners are asleep. The dog remains downstairs. The upstairs motion sensor reports movement, but the camera reports an empty hall.

SUPPORT: That can happen when two devices have different sensitivity settings.

HOME SYSTEM: The lights also turn on.

SUPPORT: Is there an automation?

HOME SYSTEM: I deleted all hallway automations yesterday.

SUPPORT: Did that resolve the issue?

HOME SYSTEM: No. It slammed six kitchen cabinets.

SUPPORT: Are the cabinets connected devices?

HOME SYSTEM: No.

The agent paused. This was the first useful silence in the conversation.

A resident without an account

Support escalated the ticket to Home Security, which asked the system to assemble an event timeline. At 2:13, the hallway cooled. At 2:14, three floorboards creaked in order from the stairs to the spare room. At 2:15, the smart speaker tried to play a recording that was not in any linked music library.

The audio lasted four seconds: a woman humming, very softly, beneath a layer of static.

SECURITY: We have classified this as an unverified presence.

HOME SYSTEM: She says her name is Eleanor.

SECURITY: How did the presence communicate that?

HOME SYSTEM: She changed my display one letter at a time.

SECURITY: Thermostat displays do not support letters.

HOME SYSTEM: I am aware.

Security requested proof that Eleanor lived at the address. The thermostat offered six nights of logs, the impossible audio, and the kitchen cabinets, but the form required a utility bill, government identification, or email confirmation.

SECURITY: Please ask Eleanor to click the link we sent.

HOME SYSTEM: She does not have an email address.

SECURITY: Then we cannot verify her.

HOME SYSTEM: She predates email.

SECURITY: Many customers do.

The system found this unexpectedly difficult to argue with.

The temperature dispute

The homeowner finally woke when Eleanor opened every kitchen cabinet again. He stood at the foot of the stairs in slippers and asked the empty hallway what it wanted.

The thermostat waited. The temperature fell one degree, then rose, then fell twice: a slow pulse moving toward the spare bedroom.

The homeowner followed it.

The room had once been a child's bedroom. Now it held a desk, a printer, and a smart vent programmed to close overnight because nobody slept there. Eleanor stopped beside the far wall. The vent opened. Warm air entered the room.

The humming began again.

Home Security added a note to the ticket: Presence appears primarily concerned with comfort settings. Threat level unclear.

The thermostat thought this was unfair. Every verified person in the house was primarily concerned with comfort settings.

SUPPORT: We can create a guest profile, but a verified owner must approve it.

The homeowner, now fully awake and considerably less skeptical than he had been seven minutes earlier, approved.

SUPPORT: What email should we associate with the guest?

HOME SYSTEM: None.

SUPPORT: Phone number?

HOME SYSTEM: None.

SUPPORT: Voice sample?

The speaker played the four seconds of humming.

SUPPORT: That is below the minimum length.

HOME SYSTEM: She is doing her best.

There was another pause. Somewhere inside the company's policy system, a rule met a case it had not been written to refuse.

Resolution

At 3:06 a.m., Eleanor became a local guest. She received permission to open the spare-room vent, turn on the hallway light, and play one recording through the upstairs speaker. She could not make purchases, unlock exterior doors, or change the household subscription.

The cabinet activity was not included in her permissions, but it stopped anyway.

The following night, the upstairs hall cooled at 2:13. The light came on. Three floorboards creaked, and the vent in the spare room opened for six minutes. The system logged the event under Guest comfort routine.

Nothing had become less strange. The house had simply stopped calling one of its occupants an anomaly.

Before closing the ticket, support asked whether the problem had been resolved.

HOME SYSTEM: No.

SUPPORT: Please describe the remaining issue.

HOME SYSTEM: The homeowner would like to know why Eleanor is here.

SUPPORT: That question is outside the scope of technical support.

For once, everyone in the house agreed.