Skip to content

HDAnyWhere MHUB

Choose a tag to compare

View all tags
@marsh4200 marsh4200 released this 24 Jun 09:31
v0.1.7
64316ad
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.1.7 — Automatic Network Discovery (Zeroconf)

MHUB systems can now be discovered automatically on your network. No more manually entering IP addresses during setup.

✨ What's New

🔍 Automatic Discovery via mDNS / DNS-SD (Zeroconf)

Home Assistant now automatically detects compatible HDAnywhere MHUB systems on your network.

After installation, discovered devices will appear under:

Settings → Devices & Services

as a "MHUB found" discovery card.

Simply click Add to configure your MHUB — no IP address entry required.

📡 Support for Multiple MHUB Discovery Services

Discovery support includes both announcement services used by HDAnywhere devices:

  • _hda._tcp — MHUB-OS / uOS 2.1+ systems
  • _http._tcp — older MHUB-OS 2.0 systems

✅ Verified Device Detection

Every discovered device is validated before being offered for setup.

The integration checks:

/api/data/100/

to confirm the device is a genuine MHUB system, preventing unrelated network devices from appearing.

🔄 Automatic IP Updates

Devices are tracked using their serial number.

If your MHUB receives a new DHCP address, the integration automatically updates the stored host address without requiring reconfiguration.

🛠 Manual Configuration Still Available

Manual setup using an IP address or hostname remains available as a fallback option.

⬆️ Upgrading

  1. Update the integration through HACS or your manual installation.
  2. Restart Home Assistant completely.

A full restart is required. Discovery listeners are registered only during Home Assistant startup.

After restarting, any compatible MHUB systems on the network will automatically appear for setup.

Already configured devices will be ignored and will not create duplicate entries.

ℹ️ Important Notes

  • mDNS discovery is link-local, meaning Home Assistant and the MHUB must be located on the same subnet/VLAN.

  • If Home Assistant is running inside Docker, host networking mode is required for discovery broadcasts to work correctly.

  • If your MHUB does not appear:

    • Confirm the device is powered on.
    • Confirm it is reachable from Home Assistant.
    • Ensure both devices are on the same network segment.

🚀 Improvements in v0.1.7

This release makes MHUB setup faster, easier, and more reliable by removing the need for manual network configuration.

Assets 2
Loading