v0.5.1

Changed

• The integration is in the HACS default list: the README and the installation page say to search
  for it in HACS instead of adding a custom repository.
  #38

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256:

ecd5d35dfd7d39870b89fe5304445e8db2920612a24a607d5737021396e2c99d

v0.5.0

Added

• Repairs for router settings that weaken a router, each with a page in the docs that says what to
  change in SRM: access to SRM allowed from the internet, the auto block switched off, a firewall
  default policy that allows traffic from the internet. Checked with the slow update; a repair
  goes once the setting is safe. Read only, as everything else.
  #35
• Discovery: routers and access points that announce themselves on the network (mDNS) are offered
  in Home Assistant with host and HTTPS port filled in; a Synology NAS announcing itself the same
  way is left out, and a device already set up keeps its host.
  #36

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256:

95dcfdb892434cc72e38b57297cd28851a6fbb4784d47c669a8c7100342b5cca

v0.4.0

Added

• An IPv6 prefix sensor on routers: the prefix the provider delegated to the LAN, with the prefix
  of every local network as an attribute.
• A Router events entity on routers: it fires when the IPv6 prefix of a local network changes and
  when the firewall changes (rules added, removed, switched, moved, or a default policy changed),
  once per read with everything that changed. The last state is stored, so a change made while
  Home Assistant was off fires after its start. A blueprint sends notifications.
  #34

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256:

e9b67a3ceab772091a66fc32f8c5b36e96424dad705a4a4d6457d552db1f88ee

v0.3.0

Added

• Ethernet ports per device: a link sensor (connectivity) and the link speed (Mbit/s, diagnostic)
  for every port, WAN and LAN 1, 2, ..., read with the fast update. In a mesh only the device's own
  ports. #32

• A New clients event entity per device: it fires when a client is online for the first time,
  with its name, addresses, connection and band, and whether its MAC address is a private (random)
  one. A client counts as new once; clients present at the first start, or appearing while a
  device's lists are missing, are taken in without an event. A blueprint sends notifications and
  leaves out private addresses unless you include them.
  #31

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256:

8725c01fca6ac28c9a0fc1a3381fec0068e996d4c6bb0537d9ea5019b96c4a93

v0.2.1

Added

• A Wi-Fi events entity per device: it fires when a radio set to a fixed channel runs on
  another one (on 5 GHz usually a radar switch) and when a Wi-Fi network is switched off or on,
  once per network. A radio on automatic channel selection changing its channel is no event. A
  blueprint sends notifications for them.
  #54

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256:

42bbacfca76cf07f9d5ab8e947811afa6627b4e44049a7963060caaa1d526c2a

v0.2.0

Added

• Wi-Fi per device: the channel of each radio (with the channel set in SRM), the allowed channel
  width as a diagnostic, transmit power and Wi-Fi mode (disabled by default), and a binary sensor
  per Wi-Fi network and band that says whether it is on, for every network SRM has (primary,
  guest, ...). With Smart Connect on, its switch decides for all bands. The Wi-Fi passwords that
  SRM sends along never reach Home Assistant (aiosynologysrm 0.10.0 keeps only known fields).
  #33

Fixed

• Old trackers can be deleted in Home Assistant. With Track all clients, a tracker of a client
  that no longer matters is no longer provided at setup, unless you chose its client or changed the
  tracker or its device (name, area, label, icon, category, alias, hidden, used by a person). Home
  Assistant then shows it as unavailable and offers Delete; until now it said away and could not
  be deleted. It comes back with the same entity ID when its client does.
  #14,
  #45
• A client device left without its tracker is removed at the next setup. Devices of other
  integrations for the same client stay.

Changed

• Automations, templates and dashboards that read such an old tracker see unavailable instead of
  not_home.

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256:

27d6a6da3da430548d77fa85790c08a4abdaa46ad29f28c6b24fdeb97972897d

v0.1.3

Fixed

• No more warning from Home Assistant about DeviceEntry.config_entries when a tracker names its
  device; that access stops working in Home Assistant 2027.10.

Changed

• Every tracker is the main entity of a device of its own, which carries the client's name from
  SRM and its MAC address, as Home Assistant 2026.11 expects; it warned that trackers without
  device info stop working in 2028.11. On Home Assistant 2026.10 this adds a device for each
  tracked client; until now only clients another integration knows had one. Entity IDs stay; a
  name you gave a tracker's device stays too. #47
• When a single read fails while the others work (the values it feeds show as unknown), the log
  says so once at info level, naming the read and the device, and again when it works. Before, only
  the debug log showed it.

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256:

d42fca502a4997cbf80cb02a6e7562d10a0eb942fa49c71ca38530161e9511d4

v0.1.2

Fixed

• A tracker's device keeps the client's name from SRM. When another integration knows the same
  MAC address (a Sonos speaker, a vacuum), Home Assistant renamed it to the host name the client
  reports on every load, and the tracker showed as <host name> <name>. Names you gave in Home
  Assistant stay. #30

Changed

• Release notes show the zip's SHA-256 in a block of its own, readable on phones.
• Docs: which entity IDs differ when Home Assistant runs in German, for the example dashboard; a
  roadmap in the README.

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256:

91b979252ec3ea860dcf8daeff40f72e1496421b841ee7e64ecf72d6c8c97772

v0.1.1

Fixed

• The icon is readable on light themes: transparent, with a variant for dark themes.
• Smaller screenshots in the README, side by side.

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256 14900fd6983b99781c91a81d4c4eebb8a02c3661590fdb686bbddca868416cda

v0.1.0

Your Synology routers and access points in Home Assistant. The first release of Synology SRM Router: load, traffic, WAN, clients per Wi-Fi band, DHCP, firewall rules with their hits, USB storage, and device trackers that know which router or access point, and which radio, each client uses. Read only: it never changes a setting.

• Set up in the UI, one entry per router and access point; their client lists are combined.
• Checked certificates: Let's Encrypt and other public authorities by name, so renewals need nothing; SRM's own certificate is pinned.
• Ready-made dashboards: who is where, by radio, DHCP leases, unknown devices, firewall rules (templates).
• Tested on RT2600ac and MR2200ac with SRM 1.3.2; other SRM 1.3 models are expected to work. Reports welcome.

Install from HACS as a custom repository, or unpack the zip below (installation). Requires Home Assistant 2026.10.3 or newer.

Everything in 0.1.0

Added

• First version: one device per Synology router or access point (SRM), configured in the UI with
  certificate pinning, reauthentication and reconfiguration. Without a checked certificate the
  account step warns before the password is entered; adding a pinned device again keeps its pin.
  A certificate from a public authority (for example Let's Encrypt) is checked against the
  authorities and a name the user gives (the host name, or a name entered for a device added by
  its IP address; never a name read from the certificate), so its renewals need no
  confirmation; SRM's own certificate is pinned, and pinning stays available for the other kind.
  Reauthentication and Reconfigure name what was trusted so far and never switch between name
  and pin on their own. A checked device whose name or fingerprint is missing is refused and
  asks to confirm the certificate again, instead of connecting unchecked. Reconfigure warns
  before a checked device is switched to an unchecked certificate or to HTTP.
• Sensors for CPU load, memory, download and upload rate, clients (all, per Wi-Fi band and wired)
  and last boot; on routers WAN connection, public IPv4 and IPv6 address, WAN address type and
  whether the router is behind NAT.
• Device trackers that combine the client lists of all routers and access points, with the
  device, connection and radio a client uses; they keep their last reliable location for a while
  when the device a client was on cannot be read. After a restart, trackers of clients SRM no
  longer lists come back as away, with their last name.
• A repair when SRM's auto block locks out Home Assistant, also during setup (at the login or
  the first update), with a new login attempt every 15 minutes; it goes away with the entry.
• On routers: DHCP leases and reservations, the usage of each network's DHCP pool, and the number
  of firewall rules with a hash that changes with every rule change; the lists behind them as
  attributes (who holds an address and whether it is unknown, reservations not seen for 30 days,
  the rule table with hits and duplicates) on sensors that are disabled by default, with Markdown
  card templates that escape names from the devices (line breaks included), and dashboard views. A
  hits sensor per firewall rule on request (option Sensor per firewall rule). On every device:
  used and free space per USB volume.
• Diagnostics without addresses, names or secrets; the docs list what is stored and who can see
  it.
• English and German.
• Documentation website at https://ha-synology-srm-router.eize.dev/, with one page per repair
  (linked from the repair) and Markdown card templates for dashboards; screenshots and an example
  dashboard to download; a page of ideas and tested example automations.
• The tracker choice offers the clients that matter first (online, named in SRM, with an IPv4 DHCP
  lease or reservation, or seen in the last 30 days); all known clients on request. "Track all" covers
  exactly those, and new clients as they appear.
• Trackers carry the name given in SRM, also for clients on an access point, and count a client
  as away only after a configurable time (3 minutes by default), also right after a restart of
  Home Assistant. The Wi-Fi signal is left out of the recorded history, so the database does not
  grow with every change of a few dB.
• "Last seen" keeps clients for 30 days and is deleted with the last router or access point.
• Routers of separate networks each keep the trackers of their own clients; an access point keeps
  trackers when no configured router knows its clients, or when chosen in its menu.
• Trackers carry the client's IPv6 address (ip6_address, not link-local), and both addresses
  fall back to the router's DHCP leases and reservations: SRM's client list leaves out many
  addresses its own DHCP server handed out.
• Each Home Assistant installation logs in under its own session name, so its sessions can be told
  apart in SRM.

Documentation: https://ha-synology-srm-router.eize.dev/

Manual install: synology_srm_router.zip, SHA-256 cf2d0908183e92b85cd36348eba833af2edce7f369be16cd27ee307341a3fcd0