What this guide covers
If your Shelly Pro 3EM shows a device that was never installed, it is usually a configuration, pairing, or topology issue rather than a hardware fault.
This guide explains how to remove an incorrectly detected device from Shelly Pro 3EM and prevent it from coming back.
Why Shelly Pro 3EM may detect the wrong device
Shelly Pro 3EM is a three-phase energy meter that uses current transformers, network services, and cloud or local integrations to identify and report loads.
When it misidentifies a device, the cause is often tied to the data source rather than the physical meter itself.
- Stale device records in the Shelly app or Shelly Cloud
- Duplicate entities created by Home Assistant, MQTT, or another integration
- Incorrect phase wiring or swapped current transformers
- Old discovery data from mDNS, DHCP, or static IP changes
- Cached automation rules that still reference a deleted device
Before you remove anything
Confirm whether the device is truly incorrect.
Compare the Shelly Pro 3EM readings with the connected load, then check whether the “detected device” appears in the Shelly app, in a third-party platform, or both.
That distinction matters because the fix may need to happen in the app, the integration, or the automation system.
- Note the exact device name as shown in Shelly or your smart home platform.
- Check whether the issue appears on all dashboards or only one.
- Review whether the device was recently renamed, moved, or replaced.
- Verify firmware version on the Shelly Pro 3EM.
How to remove an incorrectly detected device from Shelly Pro 3EM
The removal process depends on where the incorrect device is being shown.
In many cases, you are not removing a physical device from the meter; you are deleting a discovered entity, clearing a stale association, or resetting a network record.
1. Remove it from the Shelly app or Shelly Cloud
If the incorrect device appears inside the Shelly ecosystem, start by checking the device list and any assigned scenes or rooms.
Remove the entry only after confirming it is not active in an automation.
- Open the Shelly app or Shelly Cloud dashboard.
- Navigate to the Shelly Pro 3EM device page.
- Look for linked subdevices, channel entities, or discovered items.
- Delete the incorrect entry if the interface allows it.
- Refresh the device list and confirm the entry no longer appears.
If the interface does not offer a direct delete option, the stale item may be controlled by another system such as Home Assistant or MQTT discovery.
2. Clear the entity in Home Assistant or another smart home platform
Home Assistant, openHAB, Node-RED, and similar systems can retain old Shelly entities even after the source has changed.
If the wrong device is visible there, remove it from the integration rather than from the physical Shelly device.
- Open the integration that manages Shelly devices.
- Find the obsolete entity linked to the Shelly Pro 3EM.
- Remove the entity or disable its discovery entry.
- Restart the integration if required.
- Reload entities and verify that the incorrect device is gone.
In Home Assistant, it is common to need a reload of the Shelly integration or a manual entity cleanup if the device has been renamed, re-added, or restored from backup.
3. Delete stale MQTT discovery data
If Shelly Pro 3EM publishes through MQTT, the wrong device may persist because of retained discovery messages.
A retained topic can keep showing an entity long after the physical device is gone.
- Check your MQTT broker for retained discovery topics.
- Delete retained messages for the obsolete Shelly entity.
- Restart the broker or client if necessary.
- Re-run discovery so only current entities are published.
This step is especially important when you have replaced a meter, changed its hostname, or moved it to a new network segment.
4. Reboot the Shelly Pro 3EM and refresh the network record
A simple reboot can clear temporary discovery errors, especially if the meter was assigned a new IP address or recently lost network connectivity.
After rebooting, verify that your router shows the correct DHCP lease and that no duplicate hostname exists.
- Power-cycle the Shelly Pro 3EM safely.
- Wait for the device to reconnect to Wi-Fi or Ethernet.
- Check the router’s client list for duplicate entries.
- Refresh the app or platform that showed the wrong device.
5. Factory reset only if the configuration is corrupted
A factory reset is usually unnecessary, but it can help when discovery data, local settings, or integration state have become inconsistent.
Use this step only after exporting or documenting your current configuration.
- Back up important settings, if available.
- Reset the device from its local interface or hardware method.
- Reconfigure the Shelly Pro 3EM from scratch.
- Reconnect only the integrations you actually use.
How to prevent the wrong device from returning
Once the incorrect device is removed, fix the underlying cause so it does not reappear after the next scan, reboot, or automation sync.
Use stable network settings
Assign a consistent hostname and, if appropriate, a DHCP reservation for the Shelly Pro 3EM.
Stable addressing reduces duplicate discovery and helps platforms map the right meter to the right entity.
Keep firmware current
Shelly firmware updates often improve compatibility with local API behavior, discovery, and integrations.
Check the manufacturer’s release notes and update only after confirming compatibility with your setup.
Review automation and integration cleanup
When you remove or replace a device, delete its automations, dashboards, scripts, and retained topics at the same time.
Leftover references are a common reason an incorrectly detected device returns after re-discovery.
Verify CT placement and phase mapping
Wrong clamp placement or phase order can make the meter appear to report impossible loads, which some systems then label incorrectly.
Confirm that each current transformer matches the correct phase and load path.
Signs the issue is not just a bad device entry
Sometimes the problem looks like a duplicate device, but the real issue is bad measurement data.
Watch for these warning signs:
- Power values change when no load is connected.
- Phase readings are assigned to the wrong circuit.
- The same device appears with different names in different apps.
- Discovery returns after every restart.
- Energy totals do not match the expected electrical load.
When these symptoms appear, inspect wiring, network discovery, and integration settings together rather than assuming the device list alone is wrong.
When to contact support
If you cannot remove the incorrect device after cleaning up integrations, retained MQTT data, and app entries, contact Shelly support or the support team for your smart home platform.
Provide the firmware version, screenshots of the incorrect entity, and a description of where the device appears.
- Shelly Pro 3EM model and firmware version
- Network method used: Wi-Fi or Ethernet
- Integration platform and version
- Whether the issue is local, cloud-based, or both
- Any recent changes to hostname, IP address, or automations
That information helps isolate whether you are dealing with a discovery cache, an integration bug, or a genuine configuration problem on the Shelly Pro 3EM.
