Merkury

Merkury Home Assistant Integration Fails? These Fixes Worked

Struggling with Merkury Home Assistant integration? Discover targeted fixes for RTSP/ONVIF setup, MQTT configuration, and automation issues. Expert guidance for UK users.

Is this your issue?

Home Assistant fails to detect Merkury camera via RTSP/ONVIF
MQTT messages from Merkury camera not appearing in Home Assistant
Home Assistant automation not triggering on Merkury camera motion
Geeni App shows Merkury camera as 'Offline' during Home Assistant integration
Incorrect RTSP stream URL causing Home Assistant to freeze
Merkury camera not responding to Home Assistant commands via MQTT

Sound familiar? The guide below will help you fix it.

Merkury Home Assistant Integration Problems: Step-by-Step Fix Guide

If your Merkury cameras fail to integrate with Home Assistant, the issue often stems from RTSP/ONVIF stream configuration, MQTT setup, or firmware compatibility. This guide provides brand-specific solutions for Merkury models like the CW054 PTZ Indoor, CW055 Outdoor, and CW051 Indoor, focusing on Geeni App diagnostics and model-specific settings.

Quick Fixes for Merkury Home Assistant Integration

Before diving into complex troubleshooting, try these 30-second checks:

Restart the Geeni App and re-add your camera via Add Device → Merkury → Re-pair
Check LED status on your Merkury camera: a solid green light indicates proper WiFi connection
Verify power supply for wired models: Merkury CW051 Indoor requires 16-24V AC at the junction box
Ensure Home Assistant is updated to the latest version (check Core Integration → System Info)
Clear Home Assistant cache by restarting the supervisor container in Supervisor → Host → System → Reboot

Deep Troubleshooting for Merkury Home Assistant Integration

1. Configure RTSP/ONVIF Streams Correctly

For Merkury CW054 PTZ Indoor models, ensure your Home Assistant configuration uses the correct RTSP URL format: rtsp://[username]:[password]@[camera_ip]:554/cam/realmonitor?channel=1&stream=1. In the Geeni App, navigate to Device Settings → RTSP Settings to confirm the username, password, and port (554) match your setup. For ONVIF, check Device Settings → ONVIF Configuration and input the correct device address: http://[camera_ip]:80/onvif/device_service.

2. Set Up MQTT with Merkury-Specific Topics

Merkury cameras use distinct MQTT topics depending on the model. For Merkury CW055 Outdoor, set your MQTT broker to subscribe to merkury/cw055/+/doorbell. In the Geeni App, enable MQTT → Advanced Settings → Enable MQTT and input your broker details. For Merkury CW051 Indoor, use the topic merkury/cw051/+/motion and ensure the broker is accessible via port 1883.

3. Fix Home Assistant Automation Triggers

Merkury's motion detection zones must align with Home Assistant automation rules. For Merkury CW054 PTZ Indoor models, enable Motion Detection → Advanced Settings → Enable Zone Detection in the Geeni App. Configure your Home Assistant automation to trigger on specific zones (e.g. zone_1 or zone_2) rather than full-motion detection. Check the Geeni App's Device Health → Motion Sensitivity to ensure it's set to 'High' for reliable triggers.

4. Resolve Firmware and Integration Conflicts

Merkury's firmware updates can impact Home Assistant compatibility. In the Geeni App, navigate to Device Settings → Firmware Update and ensure your camera is on the latest version. If using HACS, verify the integration is compatible with your Merkury model. For Merkury CW051 Indoor, check the HACS repository for the correct integration version. Restart both the camera and Home Assistant after updating.

5. Use Merkury's Diagnostic Tools

Merkury's Device Health feature in the Geeni App provides critical insights. Check Network Connection → Signal Strength to ensure your camera is on 2.4GHz WiFi (as per Merkury's model specs). For Merkury CW055 Outdoor models, use Motion Detection Settings → Advanced → Enable Edge AI if your automation relies on object recognition. If diagnostics show weak signal strength (below -70dBm), move the camera closer to the router or use a WiFi extender.

Merkury Home: When a Factory Reset Is Needed

If basic fixes fail, perform a model-specific factory reset:

Merkury CW051 Indoor: Press the reset button for 3-4 seconds for a quick reset or hold for 10 seconds for a full factory reset
Merkury CW054 PTZ Indoor: Press and hold the reset button for 5-10 seconds until the LED blinks blue
Merkury CW055 Outdoor: Hold the reset button for 10 seconds until the LED blinks slowly and quickly

After resetting, re-pair the camera via the Geeni App and reconfigure Home Assistant integration settings. If issues persist, check Merkury's diagnostic logs in the Geeni App under Device Settings → Logs → Export Logs and share them with Merkury support via https://support.merkurysmart.com.

Understanding Merkury Home Assistant Integration Issues

Common causes of Merkury Home Assistant integration problems include:

Incorrect RTSP/ONVIF stream URLs or MQTT topics
Firmware versions incompatible with HACS or Core Integration
Motion detection zones misaligned with Home Assistant automation rules
Weak WiFi signal strength (especially for Merkury models using 2.4GHz only)
UK-specific ISP router configurations (e.g. Virgin Media Hub 5x double NAT)

UK users may face additional challenges with ISP routers using single SSID for both bands. For Merkury cameras, temporarily disable 5GHz in your router settings or create separate SSIDs if supported. Merkury's 2.4GHz-only models may struggle with signal degradation in buildings with thick walls or metal construction.

Preventing Future Merkury Home Assistant Integration Issues

To avoid recurring problems:

Regularly check for firmware updates in the Geeni App
Monitor WiFi signal strength using the Device Health → Network Connection feature
Use Merkury's MQTT → Advanced Settings to ensure topics match your Home Assistant configuration
Enable Edge AI in motion detection settings for Merkury CW055 Outdoor models

Full disclosure: we built scOS to address exactly this—the frustration of Merkury cameras failing to integrate with Home Assistant due to misconfigured MQTT topics or incompatible firmware. scOS uses permanently powered cameras connected via Ethernet, eliminating the need for Merkury's 2.4GHz-only WiFi and firmware update dependencies.

When to Replace Your Merkury Camera

Merkury cameras typically last 5-8 years for wired models (like CW051 Indoor) and 3-5 years for battery-powered models. If your Merkury camera is over 5 years old and Home Assistant integration issues persist despite following these steps, consider replacement. UK consumers have up to 6 years to claim faulty goods under the Consumer Rights Act 2015 (5 years in Scotland). Always check Merkury's warranty terms at https://support.merkurysmart.com before replacing.

What if this wasn't your problem to solve?

scOS detects suspicious activity — not motion. It only alerts you when something matters, like a person would. Designed to be left alone. All features included.

Detects Suspicious Activity

Not motion — actual suspicious behaviour. Like a person would notice.

Designed to Be Left Alone

No settings to tweak. No app to check. It just works.

All Features Included

No subscriptions. No tiers. Everything works from day one.

See why this keeps happening

Works with any wired camera brand. See all features

Frequently Asked Questions

Merkury cameras may fail to integrate with Home Assistant due to incorrect RTSP/ONVIF stream configuration. For Merkury CW054 PTZ Indoor models, ensure you're using the correct RTSP URL format: rtsp://[username]:[password]@[camera_ip]:554/cam/realmonitor?channel=1&stream=1. Verify the ONVIF device address in the Geeni App under Device Settings → ONVIF Configuration. If using MQTT, confirm your broker settings match the camera's MQTT topic: merkury/cw054/+/motion. Restart the camera and Home Assistant after changes.

For Merkury CW055 Outdoor models, factory reset procedures differ from other models. Hold the reset button for 10 seconds until the LED blinks slowly and quickly, then re-pair via the Geeni App. Ensure your Home Assistant integration uses the correct MQTT topic: merkury/cw055/+/doorbell. If the issue persists, check for firmware updates in the Geeni App under Device Settings → Firmware Update. Older firmware versions may lack required MQTT support.

Merkury's HACS integration requires specific YAML configurations. For Merkury CW051 Indoor models, add the following to your configuration.yaml: camera: - platform: ffmpeg streams: - rtsp://[username]:[password]@[camera_ip]:554/cam/realmonitor?channel=1&stream=1 name: Merkury CW051. Ensure your camera is on 2.4GHz WiFi only (as per Merkury's model specs). If using MQTT, verify your broker is accessible via port 1883 and the topic is correctly set to merkury/cw051/+/motion.

Merkury's motion detection settings in the Geeni App must align with Home Assistant automation rules. For Merkury CW054 PTZ Indoor models, enable Motion Detection → Advanced Settings → Enable Zone Detection. Configure your Home Assistant automation to trigger on zone_1 or zone_2 rather than full-motion detection. Check the Geeni App's Device Health → Motion Sensitivity to ensure it's set to 'High' for reliable automation triggers.

All Troubleshooting Guides