Sensors
MikroTik Extended
Csontikka/ha-mikrotik-extended · vv0.14.0
HACSLocal polling
Full RouterOS management for Home Assistant: monitor, control and automate your entire MikroTik network
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) | |
device_tracker | Presence (as an occupancy sensor) |
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Details
| Installs (analytics) | 205 (0.03%) |
|---|---|
| GitHub stars | 37 |
| Latest version | v0.14.0 (2026-10-20) |
| Set up in the UI | Yes |
| Maintainers | @Csontikka |
| License | Apache-2.0 |
Limitations from the README
- RouterOS 7 is the target. The integration is tested on RouterOS 7; it starts on RouterOS 6, but menus that only exist on 7 (WireGuard, containers, the wifi stack, netwatch statistics, routes with routing tables, LTE 5G fields) are skipped or empty there. No RouterOS 6 device is in the test setup, so reports from one …
- One device per host, per integration. Every tracked host gets its own device in Home Assistant, named after the router's view of it. A device that another integration also knows, a Shelly or an ESPHome node for example, appears twice in the device list, once from each integration; Home Assistant does not merge them.
- The device tracker follows the router's tables, not the device. A host that stops answering ARP pings, a phone in deep sleep for instance, is marked away after the Host tracking timeout even while it is still associated to WiFi. A device behind a separate access point or mesh that the router does not see in a …
- Entities follow the router's configuration. A firewall rule, a netwatch probe or a WireGuard peer deleted on the router loses its entity after a few polls; renaming one keeps the entity. Turning a sensor category off removes its entities and their devices, and a name or an area given to them in Home Assistant is not …
- One API user, its permissions decide. Writes need the write policy, scripts test, the backup sensitive, the reboot and shutdown reboot; an action the account is not allowed to do fails with an error that says so. The integration cannot do more than the account it logs in with; the full policy list is under …
- CHR and switches without PoE report no PoE selectors; a port's PoE entities exist only where the hardware reports poe-out. The PoE power, voltage and current sensors of a port appear once the port has sent a reading, which hardware that supplies power without measuring it never does.
- Polling cost grows with the router. A switch with 48 ports and a large firewall produces many entities and several API queries per poll. Turn off Interface entities on such a device, pick the Core preset, or raise the scan interval; the Performance & Database Tips section has the details.
- No local push, no cloud. State changes made on the router show up at the next poll, up to one scan interval later.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
