Mikrotik: users are reported "away" while they are at home

jeroenrnl commented 11 months ago

The problem

I have 5 different Mikrotik Accesspoints, all of them are connected to Home Assistant and all of them are reporting connected devices (i.e. the AP's are reachable, the user has sufficient rights and the integration is working correctly).

However, when a user moves from one AP to another, they change to "Away" and will only be reported "Home" again when they move back to the first AP.

Whenever a device is seen on another accesspoint, this is logged.

Platform mikrotik does not generate unique IDs. ID xx:xx:xx:xx:xx:xx already exists - ignoring device_tracker.xx_xx_xx_xx_xx_xx

What version of Home Assistant Core has the issue?

core-2023.11.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

mikrotik

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 11 months ago

Hey there @engrbm87, mind taking a look at this issue as it has been labeled with an integration (mikrotik) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `mikrotik` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign mikrotik` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

mikrotik documentation mikrotik source _{^{(message by IssueLinks)}}

issue-triage-workflows[bot] commented 8 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

jeroenrnl commented 8 months ago

The issue is still there

marlovh commented 8 months ago

Confirmed, I have the same issue. Using a hAP ax3 as main router and hAP ax2 as secondary AP. Running RouterOS v 7.14.

This issue started when I installed the hAP ax2 yesterday. hass_mikrotik_home_status

jeroenrnl commented 6 months ago

@engrbm87 could you please stop ignoring this?

engrbm87 commented 6 months ago

Devices registered by one AP can't have their state updated by another AP that is configured as a separate config entry. The second AP will try to register the detected device but will fail because the entity unique id (device mac) is already associated with the entity created by the first AP. One solution is to use CAPSMan where you configure the AP that is the CAPS manager which holds all the wireless devices and their connectivity is updated even when they connect to other APs.

issue-triage-workflows[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

jeroenrnl commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

This really is a great way to ensure I will never log a bug again

PWnet commented 1 month ago

@jeroenrnl I (still) have the same issue that has been closed for Stale. https://github.com/home-assistant/core/issues/69954#issue-1202844093

Even if using CAPSMan could be a solution, I think the Mikrotik integration has a problem with the way it handles the device tracking: indeed other integration (like dd-wrt, for example) works without flawns with multiple Accesspoints configuration.

I can't find the email, but some users have suggested some changes to the integration code to handle device tracking properly. As soon as I find the information I will post it here.

In the meantime I hope @engrbm87 can fix the issue.

Regards

psycho160 commented 1 month ago

hi, i think this is because wifiwave2 mikrotik devices use a different capsman. currently the integration querys only the "old" capsman registration table, not the new one.

i have a mixed environment, old and new capsman (running on the same hardware box) and my device tracker shows my phone only available if it's connected to an "old" AP.

Debug log says:

DEBUG (SyncWorker_15) [homeassistant.components.mikrotik.coordinator] Hub is a CAPSman manager

But the integration should also check the "Wifi" part of the code but never reaches self.get_list_from_interface(WIFI)

psycho160 commented 1 month ago

hi, i think this is because wifiwave2 mikrotik devices use a different capsman. currently the integration querys only the "old" capsman registration table, not the new one.

i have a mixed environment, old and new capsman (running on the same hardware box) and my device tracker shows my phone only available if it's connected to an "old" AP.

Debug log says:

DEBUG (SyncWorker_15) [homeassistant.components.mikrotik.coordinator] Hub is a CAPSman manager

But the integration should also check the "Wifi" part of the code but never reaches self.get_list_from_interface(WIFI)

As a workaround i did the following:

created a custom_component of the mikrotik integration

changed the code in the coordinator.py at line 132 (try block) from elif to if:

try:
        self.all_devices = self.get_list_from_interface(DHCP)
        # Check if CAPSman is supported and merge devices
        if self.support_capsman:
            _LOGGER.debug("Hub is a CAPSman manager custom")
            capsman_devices = self.get_list_from_interface(CAPSMAN)
            device_list.update(capsman_devices)
            wireless_devices.update(capsman_devices)

        # Check if WiFi is supported and merge devices (wifiwave2 CapsMan)
        if self.support_wifi:
            _LOGGER.debug("Hub supports WiFi Interface custom")
            wifi_devices = self.get_list_from_interface(WIFI)
            device_list.update(wifi_devices)
            wireless_devices.update(wifi_devices)

        elif self.support_wireless:
            _LOGGER.debug("Hub supports wireless Interface")
            device_list = wireless_devices = self.get_list_from_interface(WIRELESS)
        elif self.support_wifiwave2:
            _LOGGER.debug("Hub supports wifiwave2 Interface")
            device_list = wireless_devices = self.get_list_from_interface(WIFIWAVE2)

        if not device_list or self.force_dhcp:
            device_list = self.all_devices
            _LOGGER.debug("Falling back to DHCP for scanning devices")

        if self.arp_enabled:
            _LOGGER.debug("Using arp-ping to check devices")
            arp_devices = self.get_list_from_interface(ARP)

        # get new hub firmware version if updated
        self.firmware = self.get_info(ATTR_FIRMWARE)

and now all my wifiwafe2 clients and "old" capsman clients are recognized by the device tracker.

UPDATE: Runs good for 3 days now 👍

home-assistant / core