Nikkit logo NikkitSmart home, explained simply
Smart Lighting

Who Still Controls Your Smart Lights After You Move

A reader wrote to me in September about the second week in her new flat. At 11pm the hallway light came on, stayed on for about ninety seconds, and went off again. It did this most nights.

A hallway ceiling light glowing at night beside a phone showing a lighting app schedule screen with an unknown shared user

A reader wrote to me in September about the second week in her new flat. At 11pm the hallway light came on, stayed on for about ninety seconds, and went off again. It did this most nights. She had checked her own app, found no schedule, and had started wondering about the wiring. The wiring was fine. The previous tenant had left a sunset routine running in an account she had never had access to, on bulbs that were now screwed into her ceiling.

I spent six years fitting alarm systems before I started writing, and the handover was the part we were strictest about. Codes changed, fobs were collected, the panel was wiped on site with the new owner watching. Smart lighting has quietly reintroduced the problem we solved decades ago, except nobody treats a light bulb as an access control device. It is one. Anyone who can switch a bulb can tell whether you are home, and in some setups can read a month of your movements.

What actually transfers with the hardware

A bulb has two separate things inside it that matter here: the pairing and the account binding. The pairing is local, stored on the bulb, and says which hub or which Wi-Fi network it talks to. The account binding lives on a server and says which human owns the thing.

Unscrewing a bulb and screwing it in somewhere else changes neither. A cloud connected Wi-Fi bulb that still holds credentials for a network it cannot find will sit there announcing itself and waiting. The moment that network reappears, or the previous owner's router comes back online within range because they moved next door, the bulb reconnects and the old schedules resume. I have seen that happen in a terraced house.

Hub based bulbs behave differently and usually better. A Zigbee or Thread bulb paired to a bridge that has left the building is orphaned, and orphaned is a safe state: it responds to the wall switch and to nothing else until something pairs it. The failure mode is annoying rather than dangerous.

The ways control gets left behind

These are the leftovers I look for, roughly in the order they cause trouble.

What is left behindWhat the old occupant can still doWhere to clear it
Cloud account still bound to the bulbSwitch lights, read the full on and off log, set schedulesFactory reset the bulb, then pair it to your own account
Hub left in the house, old owner still an adminEverything, including adding new usersReset the hub to factory, not just remove devices
Guest or member access in the lighting appSwitch and schedule, often without appearing in the device listThe household or sharing screen inside the app
Voice assistant household memberVoice control of anything linked to that homeRemove the person from the home in the assistant app
Routines stored in the cloud, not on the bulbNothing active, but lights keep firing on the old timetableGoes away only when the account link is broken
A spare wall remote or dimmer switchLocal control, and it still works if they kept the pairCollect the hardware, then re pair it

The sharing screen is the one professional installers would flag immediately, because it is the equivalent of an uncollected key fob. Most lighting apps let an owner invite a second person with full control and show that invitation nowhere near the device settings. In the three apps I checked last month, the shared user list sat four taps deep under a heading called Home, Family or Members depending on the brand.

Why a factory reset on its own is not a handover

The advice you will get in any forum is to factory reset every device and move on. It is the right instinct and the wrong order, and I think it gives people a confidence they have not earned.

A reset clears the bulb. It does not clear what the cloud already holds. If the previous owner's account recorded eight months of lighting events for the property, those records persist on a server after your reset, and the account that owns them still exists. That matters less for you than for them, but it tells you something useful: the device is not the record keeper. The account is.

The reset also fails in the specific case that catches the most people. If the bulb is attached to a hub or bridge that stays in the house, resetting individual bulbs while the hub keeps its original owner leaves the owner in place. They lose sight of the bulbs you reset and keep administrative rights over everything else, including the ability to re add devices and to invite new users. Reset the hub first, then the bulbs, then build your own setup. Doing it the other way round means doing the bulbs twice.

One more thing worth saying plainly: for bulbs that will not respond at all after a move, resetting repeatedly is not diagnosis. Our guide on resetting a smart bulb when it stops responding explains why a reset can mask a genuine fault, and that applies doubly to second hand hardware with unknown history.

A handover that takes about forty minutes

Count the controllable things before you touch anything. Walk every room with a notepad. Bulbs, strips, plugs, wall remotes, motion sensors, any hub with an ethernet cable in the back. In a two bedroom flat this is usually between four and eleven devices, and people routinely miss the one in a cupboard.

Cut power at the board and watch what stays alive. Flip the lighting circuit off for five minutes. Anything that keeps reporting, a battery sensor or a hub on a separate socket, is on your list of things to find. This takes two minutes and saves an hour of guessing.

Reset in the right sequence. Hub to factory defaults, then each bulb, then the remotes. Brand reset procedures vary more than you would hope: five power cycles for some, a hold of twelve seconds for others, a pinhole and a paperclip for one Thread bridge I dealt with in August. Look up each model rather than assuming the generic flick on and off five times will do it.

Change the Wi-Fi name, not only the password. This is the step people skip, and it is the one that stops a bulb silently rejoining an old network. A new SSID makes every stored credential in the house useless at once. Ten seconds in the router admin page.

Pair everything to one account you control, then check the sharing list. Not the device list, the sharing list. If the app shows anyone you do not recognise, remove them and change the account password, because an invitation can be re sent.

Replace anything with a camera or a lock outright. I will not reuse either. A bulb I can reason about. A device with a lens and unknown firmware history is not worth the forty pounds it saves you, and that judgement comes from the home security side of this job rather than the lighting side.

If you are the one leaving

Unbind before you unscrew. Delete the devices from your account while they are still powered and connected, because removing a device the app can no longer reach often leaves a stale binding on the server that you then cannot clear. Five minutes in the old flat, versus a support ticket and a photograph of a serial number later.

Then take a decision about the hardware. Bulbs and strips travel badly and are worth about a third of their price second hand, so leaving them often makes more sense than packing them. If you leave them, tell the new occupant which app they use and that you have unbound them. Nobody has ever been annoyed to receive that note. What annoys people is a hallway light that switches itself on at 11pm, and a lighting log that doubles as an occupancy record for a house that is no longer yours.

FAQ

Can the previous owner really control my lights from another house?

If the bulb is cloud connected and still bound to their account, yes, from anywhere with a signal. Distance is irrelevant for Wi-Fi bulbs, because the command travels through a server rather than through the air between buildings. For Zigbee or Thread devices they would need to be within range of a hub they control, which in practice means next door or closer.

How do I tell whether a bulb is Wi-Fi or Zigbee?

Check whether there is a hub. If the house has a bridge box wired to the router, the bulbs are almost certainly Zigbee or Thread. With no hub anywhere, they talk to the router directly. The model number printed on the collar of the bulb settles it in one search, and it is worth reading before you buy a property's gear second hand.

Should I just take the bulbs out and fit ordinary ones?

It is the fastest clean answer and costs perhaps fifteen pounds a fitting. I would do it in a rental where I cannot reset a hub I do not own. In a house I had bought, I would rather reset properly and keep the function, because good schedules on a porch and a hallway earn their place within a week.

Does changing my router password stop old devices connecting?

It stops them rejoining that network, which is most of the risk. It does not break the cloud binding, so the moment somebody pairs that bulb to any network again the old account may reappear. Change the network name as well, and reset the devices regardless.

AK
Ada Kessler

Ada installed physical security systems professionally for six years before switching to writing about the smart version of the same job. She reads a device's privacy policy before she reads its feature list.

More posts by Ada

More in Smart Lighting

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto ankertoto