8000 known_devices.yaml not updated with Mikrotik Hex V3 and an external access point. · Issue #7604 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

known_devices.yaml not updated with Mikrotik Hex V3 and an external access point. #7604

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Esiravegna opened this issue May 15, 2017 · 5 comments · Fixed by #7690
Closed

known_devices.yaml not updated with Mikrotik Hex V3 and an external access point. #7604

Esiravegna opened this issue May 15, 2017 · 5 comments · Fixed by #7690

Comments

@Esiravegna
Copy link
Esiravegna commented May 15, 2017 •
edited
Loading

If you use a router without wireless, the mikrotik component will return an empty last_results devices list.

Home Assistant release (hass --version):
0.44.2

Python release (python3 --version):
3.4

Component/platform:
Mikrotik

Description of problem:

This line is to blame. Should you to be using a router/access point configuration, this would be empty.

Expected:

Personally, I changed the line to device_names instead wireless_clients:

            self.last_results = {
                device.get('mac-address'):
                    mac_names.get(device.get('mac-address'))
                for device in device_names
            }

Problem-relevant configuration.yaml entries and steps to reproduce:

- platform: mikrotik
   username: you_wish
   password: same
   host: some_ip

Additional info:

I'm quite sure that there's a better way to to this, however I'm not familiar enough with the platform.
@serper
Copy link
serper commented May 16, 2017

I have a mikrotik without wifi and doing this change proposed by Esiravegna works great, I can see all my devices. Without this change I can't see any device. My wifi ap is mikrotik too but dhcp-server is running on my main router without wifi.

Thanks Esiravegna and I hope this is resolve in the next version of hass.

@Esiravegna
Copy link
Author

I found a caveat: It seems that it duplicate devices, and the ID seems to be the Mikrotik client id and not the MAC Address.

@LvivEchoes
Copy link
Contributor

Hi guys. I understood you issues, and try to fix it in next releases of mikrotik device tracker platform. I try provide changes as soon as possible, and let you know immediately.

@LvivEchoes
Copy link
Contributor

But also, i would like to say, that dhcp leases/arp table/etc are not 100% right approach for using them as presence detector.
If you going to use this approach anyway, please decrease dhcp lease time. For home purposes, i would recommend to set it between 5 and 10 minutes.

@LvivEchoes LvivEchoes mentioned this issue May 21, 2017
Merged
1 task
@LvivEchoes
Copy link
Contributor

Fixed in #7690

Couldn't you try and let me know?

@bachulator bachulator mentioned this issue May 21, 2017
Closed
@home-assistant home-assistant locked and limited conversation to collaborators Sep 4, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@Esiravegna @serper @LvivEchoes
0