Hey! When someone says their Smart TV device changed after an update, it usually means the TV’s “identity” or saved profiles got refreshed — not that the hardware actually turned into a different TV.

This can show up as:
• Duplicate TV entries in Google Home / Alexa (“Living Room TV” and “Living Room TV (2)”).
• Device name changed in the casting list (Chromecast / Google Cast) or in your smart home app.
• HDMI-CEC acting different (TV boots to the wrong HDMI, turns on when a console wakes, soundbar powers up unexpectedly).
• Picture/audio settings reset (brightness, motion smoothing, audio output, lip sync, HDMI input labels).

Before we do anything risky: what’s the most annoying part right now — the duplicate device, the wrong HDMI input, or the soundbar/CEC wake-ups?

That timing helps. Updates can refresh the TV’s Google Cast / device registration, and smart home apps may keep the older entry around — so you get a “new” device plus the old remembered one.

The HDMI switching is often a separate layer: HDMI-CEC (sometimes called device control, Simplink, Anynet+, Bravia Sync) reacting to another device waking or polling the HDMI port.

I’m going to ask a few questions in a weird order on purpose, because the fastest diagnosis depends on the trigger:

1) What TV platform is it (Android TV / Google TV / Roku / Samsung / LG webOS)?
2) Is anything connected to HDMI 1 (console, cable box, streaming stick, soundbar via ARC/eARC)?
3) When it switches to HDMI 1, do you notice a click from a soundbar/receiver, or a console light turning on?

Related phrases you might recognize: “Google Home duplicate TV after update”, “TV appears as new cast device”, “TV keeps switching inputs”, “HDMI-CEC input switching after update”.

That’s a strong clue. If the console “stirs” in sleep mode, the TV can interpret it as an HDMI-CEC event and jump to that input — especially after a firmware update that re-enabled or re-tuned CEC behavior.

I don’t want you to disable things blindly (because you’ll lose one-touch volume control or auto power if we flip the wrong toggle). Instead, we do safe checks that don’t erase setup:

• Check A: Confirm what actually changed in Google Home. Do both TV entries show the same icon and room, or does one look like a generic “Cast device”?
• Check B: Confirm the update context. What’s the TV’s current system software/build version (just read it, no changes)?
• Check C: Identify the trigger. Is the HDMI switch happening around the time your phone auto-connects for casting, or mainly when the PlayStation wakes? (Your answer can be “I’m not sure” — that still helps.)

Secondary/related keywords that fit your case: “TV wakes up by itself”, “soundbar turns on randomly eARC”, “cast device duplicate”, “console turns on TV CEC”.

Night-time wake-ups + the soundbar click makes me think the chain is: console wake or HDMI handshake → TV wakes → eARC wakes the soundbar. Not guaranteed, but that pattern is common.

About Google Home: duplicates aren’t unusual after updates because the TV’s Cast identity can be re-registered. The mistake people make is deleting the “wrong” one before confirming which is active — then voice/casting acts weird for a day.

A couple safe questions (no settings changes required):
• Do you use voice control (“Hey Google, turn on the TV”)? If yes, which entry responds right now — the normal name or the “(2)” one?
• Is your TV on Wi-Fi or Ethernet? (Duplicate discovery happens more on some mesh Wi-Fi setups.)

Also, did the update change anything else — home screen layout, apps rearranged, picture mode reset, or a “remote pairing” message?

Mesh Wi-Fi is relevant. After updates, some TVs briefly look like two devices on the network because discovery packets travel differently across mesh nodes — that can cause duplicate TVs in Google Home and inconsistent voice control (“can’t find device”).

The UI/picture change suggests the update refreshed multiple profiles (UI + picture presets + connectivity services). That doesn’t mean something is “wrong,” but it explains why it feels like the TV became a different device overnight.

Here’s the diagnostic logic (still not telling you to delete anything yet):

1) Identify the active smart-home entry. The “real” one is the one that can reliably adjust volume or launch an app.
2) Confirm if the TV is hopping between mesh nodes. If your phone is on one node and the TV is on another, device discovery can look duplicated.
3) Confirm whether HDMI-CEC was re-enabled or behavior changed. Updates sometimes flip “auto power on/off” while keeping volume control working — which is confusing.

If you want, you can share a screenshot of just the Google Home device list (names/icons only). That’s often enough to label “current” vs “stale” without touching settings.

Totally fair — and you don’t need to share anything you’re not comfortable with.

The safest first move is usually a clean restart + observation, because it doesn’t erase apps/accounts and it can calm down post-update background services. After that, you watch for the trigger (casting vs console vs HDMI handshake).

A simple “safe checklist” for tonight/tomorrow (no deep menu diving):
• Note the time the TV wakes/switches to HDMI 1.
• Check if the console light flashes at the same time.
• See if your phone was on the same Wi-Fi node or if it moved around the house (mesh roaming).

If the “connect” entry in Google Home isn’t controlling anything, it’s often a leftover registration. But I’d confirm the active one stays stable for a day before removing the stale entry — just to avoid voice/casting confusion.

Exactly — gather details first, then act. Here’s what helps support diagnose “Smart TV device changed after update” without guesswork:

1) TV brand + model and whether it’s Google TV or Android TV UI.
2) Current system software/build version (just the numbers).
3) What changed: duplicate devices, device name changed, voice control inconsistent, HDMI input switching, soundbar wake-ups, picture mode resets.
4) Your connections: mesh Wi-Fi (brand if you know), TV on Wi-Fi or Ethernet, and what’s plugged into each HDMI (console, soundbar eARC, box).
5) The trigger pattern: does it happen when the phone casts, when the console wakes, or randomly at night.

With that, it becomes much easier to separate device identity problems from HDMI-CEC/ARC behavior — without jumping to a factory reset.