Why can't you change the device type for a Matter switch?

Short answer

With Matter, the device itself declares what it is — switch, light, plug, dimmer — as part of the standard. Ecosystem apps read that declaration, and many of them, Google Home included, offer little or no ability to override it for Matter devices. The first thing to check is whether the manufacturer's own app or a firmware update lets the device present itself differently. If not, the practical fix is usually to change what you automate: control the lights themselves instead of fighting the switch's label.

Why the type is stuck

Before Matter, the integration between a brand and an ecosystem was custom, and the app owned the metadata — that is why you could re-label a smart plug as a light in Google Home or Alexa. Matter moves that decision into the device: it ships with a standardized description of its own type, and controllers are expected to trust it. That consistency is good for reliability, but it means the device-type option in the app is often grayed out or missing for Matter gear. The app is not being stubborn; it is reporting what the device says it is.

What to try first

1. Open the manufacturer's own app and look for a setting that changes how the device is exposed — some switch and relay modules let you choose between presenting as a switch or as a light.
2. Update the device firmware; type declarations are occasionally corrected in updates.
3. If you change the exposed type, remove the device from the ecosystem and re-pair it so the new declaration is read fresh.

Best path for Rhythm

Rhythm organizes by room and behavior, not by device-category labels, so a switch that insists on being called a switch does not break anything. What matters is what the switch actually powers:

• Switch controlling regular bulbs: the switch effectively is the room's light. Pair the switch or in-wall module with Rhythm and let the room's daily curve drive it — dimming included, if the module supports dimming.
• Switch wired in front of smart bulbs: the switch should stay on so the bulbs keep power. Pair the bulbs with Rhythm, and treat the switch as a trigger, not as the light.

If it still shows wrong

• Remove the device and re-pair it once cleanly — stale records keep stale declarations
• If the device lives in two ecosystems via multi-admin, check whether the vendor's own fabric shows it correctly
• Rename the device so voice commands stay natural even if the icon is wrong — the label is cosmetic; the behavior is what counts

Known gotchas from real users

• Names and rooms do not sync between ecosystems — renaming in the vendor app does not fix Google Home, and vice versa.
• Device type affects voice behavior: turn off the lights may skip a device that is typed as a switch.
• A wrong-typed device can also fall out of lighting-specific routines and home/away rules in the ecosystem apps.

After it works

Once the right thing — switch or bulbs — is paired into Rhythm, the label stops mattering: set up a daily curve nobody notices and let the room follow it.

The goal is not to manage another device. The goal is to get the light into Rhythm once, then let the room run.