Use another RJ-45 cable to connect to the router WAN Port and your modem WAN port. Use RJ-45 cable to connect to the router LAN Port and your computer. Plug the AC adapter of your router to the DC-IN port and connect to power supply. Kindly refer to the following picture to check if all the devices (Modem, router, and the computer) are all connected via RJ-45 cable. Please make sure that your wireless router is connected via RJ-45 cable correctly. To provide you more detailed instruction, you can also click ASUS Youtube video link below to know more about Troubleshooting for failed Internet access through router ![]() So I can't really say if that would be an acceptable "quick fix" or not.Failed Internet access through router I don't have any history on this bug aside from what i've read here (and the info in that thread) so I'm not sure exactly all that the "wired bug" entails. If you would be interested in the backstory on this then here is the thread on my steps to lead me here. Now I know that was because the unifi_data file got updated with data from the new controllers every time the controller IP changed. Then it would work for a day or so then go back to never showing as "home". Ultimately the eventual fix for me was removing my phone's MAC from the unifi_data file (before I knew about this bug I had also tried running the controller software on three different machines). I'm not sure when this bug started but my phone hasn't reliably shown as "home" ever since I switched to the unifi gear in late august (long before v103.x). Obviously I'm limited in being able to write any actual code to help mitigate this problem but please let me know if there is anything you could use to help fix by "behaving like before" means that it will show as "home" for the "considered home" time after every HA restart? IOW, it will act just like it did before the bug fix in v103.6? That's why I offered to post logs or anything else I can do to help with this. I would be willing to put some effort into helping test any solutions to this problem on my system. And expecting people to switch out their existing hardware to "pure unifi" is at least a bit unreasonable due to the expense involved to solve this one bug. The way it is now the unifi integration in HA is absolutely useless for presence detection for people who don't have a "pure unifi" system (and my phone is again no longer being registered as home because the unifi_data file got re-updated to include it in the wireless category). Has there been any real testing done to actually know if the timestamp is messed up? On a cursory inspection of those debug logs I posted about above it didn't seem as if the "last seen" timestamp reported from the USG or unifi switch was incorrect. On the rare occasion that a previously wireless client would go to wired and the user no longer wants to track that client then it's trivial to just disable that one entity in the entity guess I don't know what you mean when you say "if it shows as wired we can't trust UniFi reporting anymore." You mention something about "AFAIK the timestamps gets messed up" but then say that you've never experienced the bug yourself. I think that would be a reasonable compromise to be able to only track wireless clients and also allow the use of non-Unifi hardware. IOW, if the device is listed in the "wireless_devices:" list then that device will forever be treated as wireless no matter what the controller reports (and therefore will always still be tracked as wireless)? So as an alternative would it be possible to write the integration to always track the device as "wireless" after the device is added to the unifi_data the first time no matter how the Unifi controller reports the actual mode that the device is connected? I assume the reason this is needed is to allow the option of tracking only wireless clients? ![]() I've jut today realized that I've been experiencing this bug as well since at least August when I switched to using Unifi gear along with my old ASUS routers as Only thing I could do here would be to introduce an option to skip the wired bug fix. Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant): However, if a device reconnects to an Unifi AP, its mac address will be readded to the list in unifi_data (and will therefore not be recongnized as homeagain) Removing the mac address from unifi_data and restarting HA will fix this issue temporarily. Devices listed in unifi_data will stay at not_home. when it's connected to an AP from a different manufacturer), presence detection stops working. Once a device is listed in unifi_data and goes back to be a wired_client (e.g. Mac-addresses of devices once connected to an Unifi AP will be added to the file unifi_data in /home/homeassistant/.homeassistant/.storage as wireless_devices ![]() Operating environment (Hass.io/Docker/Windows/etc.): Last working Home Assistant release (if known):
0 Comments
Leave a Reply. |