Choose the exact model and mode
Match the model code on the unit. Keep the standard and UL versions separate; their electrical and motor limits stay in each device’s manual and reviewed route.
Installation must be complete before software setup. Use the exact manufacturer instructions and a qualified installer where appropriate. The software guide does not establish regional availability or safety certification.
Choose your exact device guideConnect through the Shelly integration
Have Home Assistant running and the installed device on a reachable home network. This path uses the built-in Shelly integration, not Matter, MQTT or a cloud-linking method.
- Accept discovery, or open Settings → Devices & services → Add Integration → Shelly. Enter the device’s hostname or address from your router when asked.
- These Gen2 devices use RPC. Home Assistant documents firmware 1.0+ support and direct device communication without Shelly cloud. Gen1 CoIoT instructions are a different path.
- If device authentication is enabled, use the local device password. Shelly’s documented RPC username is
admin; a cloud login is separate. - Compare the available controls with the exact route before relying on them or building automations. Check the active profile and any conditional readings.
Firmware 2.0 security behavior and HTTPS/certificate handling have additional conditions. Use the current official integration and authentication instructions below; do not disable protections as a routine fix.
Local everyday control does not establish remote access, every update path or complete offline behavior.
Find the cause, starting with the symptom
These are diagnostic suggestions, not a claim that every symptom has the same cause. Keep the current configuration and collect useful evidence before changing it.
Device not discovered
Try adding its current host address manually. As a diagnostic check, confirm reachability from the Home Assistant network; reaching it from a phone alone does not establish that.
Authentication fails
Check the local device credentials against its interface. These are separate from a Shelly cloud login. Keep authentication enabled; use the official authentication guidance below.
Device becomes unavailable
Record the error and time, then check its current router address and reachability. If firmware or security settings changed, check the current integration instructions before changing ports or certificates.
Power or energy readings are missing
First check the exact PM model and active profile in its reviewed guide. Home Assistant documents reachable configured SNTP as a requirement for power measurement. Missing data does not establish complete offline metering or Energy dashboard suitability.
A cover has no percentage control
Check the calibration conditions in its exact cover guide. Keep motor suitability and supervised calibration tied to that variant. Repeated motor movement is not a substitute for diagnosis.
A feature is still unverified
Use the feature table in the selected device route. Manufacturer-app features and a different profile do not establish what Home Assistant exposes through this connection.
Collect useful logs and diagnostics
Open Settings → Devices & services and select Shelly. From its three-dot menu, enable debug logging, reproduce the problem, then disable logging and download the log. Download diagnostics if that integration offers them.
Keep the exact model, device firmware, Home Assistant version, active profile and error time with your report. Review files before sharing them publicly. The official troubleshooting reference gives the current menu steps.
Official instructions and scope
These shared references were checked October 15, 2026. Model-specific capability sources keep their own review and collection dates. Meter accuracy, complete offline metering, Energy dashboard suitability and hardware validation are not established by this guide.