Something Is Moving In My Mirror Logs Stories Tell in the dark

Something Is Moving In My Mirror Logs Stories

Tell in the dark 

The Chilling Evidence Reveal. I left my smart mirror recording while I slept, but the data logs show something that shouldn't exist. The sensors tracked a rhythmic thermal silhouette pacing my empty room at 3:00 AM. When I checked the footage, the hardware synced with a distorted figure standing directly behind my reflection. Look, I’ve been in systems integration and smart home hardware for about twelve years now. I’m the guy companies call when the high-end consumer tech starts acting up in ways the tier-one support guys can’t wrap their heads around. I’ve seen it all—bad firmware, cross-talk between wireless frequencies, moisture getting into the sensors, you name it. I live in a pretty standard two-bedroom in the suburbs, and because of what I do, my place is basically a beta-testing lab. I’ve got the latest smart glass, automated HVAC, and this specific smart mirror prototype that I’d been running for about six months. It’s supposed to be the "all-in-one" health hub—tracks your sleep, checks your vitals while you brush your teeth, even does thermal mapping to see if you’re coming down with a fever before you actually feel it. The thing is, I’m a creature of habit. I’m up at 6:30, I have my coffee—usually cold because I forget about it while checking emails—and I head to whatever site I’m auditing. About three months ago, I started noticing some weird lag on my home network. My internal pings were spiking around 3:00 AM. Normally, that’s just a scheduled backup or a cloud sync, so I didn't think much of it. I just figured the mirror was dumping its daily data to the server and the compression was hitting the CPU hard. I remember one Tuesday night specifically. I’d had a long day at a data center in Jersey, and I was just beat. I’d stopped at a gas station on the way home and bought one of those pre-packaged sandwiches, and the plastic zipper on the bag was broken, so I was struggling with that while trying to get my keys in the door. Just one of those annoying, mundane nights. I got ready for bed, did the usual routine. The mirror in the bedroom was in "standby," which means the display is off but the sensors are still active. It’s got these high-end FLIR sensors and a LiDAR array for depth tracking. I fell asleep pretty fast, but around 3:15, I woke up because the room felt… I don’t know, just different. Like the AC had kicked off, but when I checked the app on my phone, the HVAC was running fine. I was tired, so I just rolled over and went back to sleep. I didn’t hear anything. No floorboards creaking, no breathing, nothing. Just the hum of the fridge in the kitchen. The next morning, I’m sitting there with my coffee, and I get a notification on my laptop. It was an automated system alert from my home server. Basically, the mirror had triggered a "Critical Resource Usage" flag at 3:14 AM. That’s a lot of processing power for a device that’s supposed to be idle. I figured it was a memory leak in the latest firmware update, so I pulled the logs to see what was eating the cycles. So anyway, I start digging into the CSV exports. The thing about these mirrors is they don’t just record video; they record metadata. You’ve got your thermal map, your heart rate via micro-fluctuations in skin tone, and the LiDAR depth map. I’m looking at the thermal logs first, and I see this spike. According to the sensors, at 3:00 AM sharp, there’s a heat signature in the room. It’s consistent. It’s about 98.6 degrees—human standard—and the algorithm estimated it as a 115-pound mass. The weird part was where it was. The logs showed this mass sitting right at the foot of my bed. I live alone. No pets, no kids, nothing. I’m looking at the data, and I’m like, "Okay, maybe it’s a heat vent or a reflection off the window from a neighbor’s car." But the mass was moving. The sensors tracked it standing up and pacing. It wasn’t a random drift; it was a rhythmic, deliberate walk from the bed to the mirror and back. I was like, "Okay, this is sketchy." I check the security footage from the camera I have in the corner of the room—a standard optical lens. I scrub to 3:00 AM. The room is empty. It’s just me, asleep, not moving. The footage is totally still. No one is there. But then I go back to the mirror’s internal logs. The LiDAR is the tie-breaker. LiDAR doesn’t care about light or heat; it just bounces lasers off physical objects to measure distance. I pull the raw point-cloud data from the mirror at 3:14 AM, the exact moment the CPU maxed out. The thing is, the mirror’s "Face ID" module had engaged. This is the part that’s supposed to recognize me so it can display my personal health stats. The log showed it was trying to run a dual-recognition. It had me, tagged as "User 1," asleep in the bed. But it was also trying to process a second face. The CPU was redlining because it couldn't get a "clear lock" on the second set of features. I’m being dead serious, I sat there for like twenty minutes just staring at the terminal. I told myself the hardware was just bugging out. It happens. You get a "ghosting" effect in the sensors if the calibration is off. So, I did what I always do—I kept working. I had a 10:00 AM meeting with a client, so I just closed the laptop, finished my coffee, and went to work. I figured I’d just factory reset the thing when I got home. But I couldn't stop thinking about that 3:14 AM timestamp. Why that specific time? And why did the thermal mass sit at the foot of the bed for fourteen minutes before moving to the mirror? When I got home that evening, I didn't reset it right away. I wanted to see the visual overlay. I synced the optical footage with the thermal and LiDAR data. It took a while to render because the files were huge. While I waited, I noticed a spam notification on my phone from some random "Smart Life" app I don't even remember downloading, asking for permission to "Sync Room Profiles." I swiped it away. Next thing I know, the render is finished. I hit play. On the left side of the screen is the standard video—me sleeping, the room dark and quiet. On the right side is the "Sensor View." In that view, there’s a bright yellow-orange shape sitting on the edge of my mattress. It’s clear as day. It’s a person-shaped heat signature. It stays there, perfectly still, for exactly fourteen minutes. Then, it stands up. It walks over to the mirror. In the optical footage, the space in front of the mirror is empty. But in the sensor view, this thermal silhouette is standing right there, inches away from the glass. And because of how the mirror’s internal camera works, I could see the reflection of the room within the sensor data. There was a figure standing directly behind my reflection in the mirror’s "eye." It was distorted, like the sensor couldn't quite decide where the edges of the body ended. It just stood there, staring into the lens, which is why the CPU was freaking out. It was trying to map a face that had no clear boundaries. I checked the protocol for hardware malfunctions. I called the lead engineer on the project—a guy named Marcus, though I think I called him Mike because I was so rattled. I told him I was seeing some major artifacts in the LiDAR stream and asked if they’d had any reports of "phantom tracking." He told me it was probably just a localized interference or maybe a bug in the spatial mapping where it was "looping" a previous day's data. That made sense. It explained most of it. A data loop would account for the heat signature and the movement. It was just replaying a ghost of a recording from another time, right? Except, I’ve only had the mirror for six months. And the silhouette in the log… it was only 115 pounds. I’m 190. I’ve never had anyone else in this apartment. Not a girlfriend, not a friend staying over. Nobody. I ended up unhooking the mirror that night. I told myself I was just going to return it for a "sensor recalibration." I put it in the guest closet and went to bed. The thing is, I still live here. I still have all my other smart gear running. Everything works fine. No more pings at 3:00 AM. No more CPU spikes. It was just a bad piece of hardware. A weird, one-off glitch in a prototype. That’s what I tell people when they ask why I don’t have the mirror up anymore. But sometimes, when I’m getting ready for bed, I’ll look at the spot on the wall where the mirror used to be. And honestly, the thing that still doesn't sit right with me isn't the thermal silhouette or the LiDAR data. It’s that when I finally packed the mirror into its box, I noticed a small smudge on the glass. It was on the inside of the casing, right over the sensor array. It looked like a fingerprint. A small one. Like someone had pressed their hand against the glass from the other side. I’m lowkey still shook whenever I have to check data logs at night. To be honest, I’ve started sleeping with my bedroom door locked. I know it doesn't do anything against a "sensor glitch," but it makes it easier to close my eyes. I still drink my coffee cold, though. Some habits you just can't shake.

Something Is Moving In My Sealed Attic Stories

Tell in the dark