This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.

The Homey Community has been moved to https://community.athom.com.

This forum is now read-only for archive purposes.

Homey Wifi Driver / Linux Kernel trouble on Mesh Networks - confirmed

mruitermruiter Member
edited February 2016 in Questions & Help

My Homey gives a connection to server lost message every so many hours.
I did not check its real speed because i have a Mesh network that reports slow connecting device to me and it never reported the homey to have a slow connection. It reports a steady 65mbps connection.

But the Homey does have internal wifi network trouble in its driver or even at a kernel compliation level.
It's shows the basic upping ping response for 5 or 6 pings and then drops to low ping and upping straight away again.

This is something you usualy see when there is a driver problem and is seen sometimes also with realy old network cards on Mesh networks.
At home i have OpenMesh Mesh Network Mimo 3x3 1750Mbps (not that Homey will support that speed but not much does) I have tested this also at my company where we have Aruba Mesh Ap's. Same result.

When i connect it to a simple home tp-link or Asus AP of 30 bucks its ok........

I have attached a screenshot. You can see the packet delay problem of Homey on ip 192.168.0.13.
Ofcourse an ISP connection test on 8.8.8.8 and the homewizard thats next to the homey on 192.168.0.250.

This could maybee also be the trouble of the stutters people are reporting from the speech of the homey and lookups in the cloud or not responding at al to voice commands.

I only have 1 Homey , so maybee more people can check if they maybee also see the same ping / wireless communication trouble on there homey. It could explain why some people report good speech response and other people say its crap or doesn't do anything.

At least i can confirm some kind of Bug in the Wifi on my Homey

See Screenshot

Comments



  • Homey - router - external dns
  • mruitermruiter Member
    edited February 2016
    Well, it looks like thats a confimation about a wifi bug.
    Hope more will test because i thing its the base problem of all the people who are complaining about speech trouble. When i put it on a tp link it could do a wiki lookup with no problem. It could never do that before. But who want a crappy tp link if you have a mesh network at 1750mbps in every hole in youre home..


    Just for the record, i noticed it already on the .17 firmware but did not have the time to get into it.

    Whats youre brand of Wifi AP ?
  • It's an ASUS RT-N66U With alot of wireless access settings I tried almost every setting but with no positive result
  • I do see the same varying ping times to Homey compared to my router or external servers.
  • mruitermruiter Member
    edited February 2016
    @Emile we have a problem ?? (almost sounds better the Houston )

    and please everybody, post youre ap brand /type. maybee a patern will emerge
  • PhuturistPhuturist Member
    edited February 2016
    Router: Asus RT-AC68U

    Pinging 192.168.0.120 with 32 bytes of data:
    Reply from 192.168.0.120: bytes=32 time=149ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=77ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=291ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=213ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=35ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=45ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=270ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=187ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=105ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=252ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=16ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=87ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=134ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=5ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=142ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=63ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=284ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=202ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=40ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=267ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=187ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=103ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=2ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=1265ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=7ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=118ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=342ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=290ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=180ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=108ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=629ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=239ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=79ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=312ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=817ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=141ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=61ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=295ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=3ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=119ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=36ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=264ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=178ms TTL=64
    Reply from 192.168.0.120: bytes=32 time=95ms TTL=64
    
    Ping statistics for 192.168.0.120:
        Packets: Sent = 47, Received = 47, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 2ms, Maximum = 1265ms, Average = 186ms
    But I must say, I'm getting similar results when pinging my smartphone for instance.
  • edited February 2016

    Access Point: Apple Airport Time Capsule

    Mac to Homey:

    PING 192.168.178.84 (192.168.178.84): 56 data bytes
    64 bytes from 192.168.178.84: icmp_seq=0 ttl=64 time=304.713 ms
    64 bytes from 192.168.178.84: icmp_seq=1 ttl=64 time=211.052 ms
    64 bytes from 192.168.178.84: icmp_seq=2 ttl=64 time=131.422 ms
    64 bytes from 192.168.178.84: icmp_seq=3 ttl=64 time=47.121 ms
    64 bytes from 192.168.178.84: icmp_seq=4 ttl=64 time=272.908 ms
    Request timeout for icmp_seq 5
    64 bytes from 192.168.178.84: icmp_seq=6 ttl=64 time=111.224 ms
    64 bytes from 192.168.178.84: icmp_seq=7 ttl=64 time=30.557 ms
    64 bytes from 192.168.178.84: icmp_seq=8 ttl=64 time=255.788 ms
    64 bytes from 192.168.178.84: icmp_seq=9 ttl=64 time=169.076 ms
    64 bytes from 192.168.178.84: icmp_seq=10 ttl=64 time=85.185 ms
    64 bytes from 192.168.178.84: icmp_seq=11 ttl=64 time=313.106 ms
    Request timeout for icmp_seq 12
    64 bytes from 192.168.178.84: icmp_seq=13 ttl=64 time=151.846 ms
    64 bytes from 192.168.178.84: icmp_seq=14 ttl=64 time=65.768 ms
    64 bytes from 192.168.178.84: icmp_seq=15 ttl=64 time=308.837 ms
    64 bytes from 192.168.178.84: icmp_seq=16 ttl=64 time=208.329 ms
    64 bytes from 192.168.178.84: icmp_seq=17 ttl=64 time=123.895 ms
    64 bytes from 192.168.178.84: icmp_seq=18 ttl=64 time=47.275 ms
    64 bytes from 192.168.178.84: icmp_seq=19 ttl=64 time=266.349 ms
    64 bytes from 192.168.178.84: icmp_seq=20 ttl=64 time=182.942 ms
    64 bytes from 192.168.178.84: icmp_seq=21 ttl=64 time=100.653 ms
    64 bytes from 192.168.178.84: icmp_seq=22 ttl=64 time=21.427 ms
    64 bytes from 192.168.178.84: icmp_seq=23 ttl=64 time=242.165 ms
    64 bytes from 192.168.178.84: icmp_seq=24 ttl=64 time=164.134 ms
    64 bytes from 192.168.178.84: icmp_seq=25 ttl=64 time=77.775 ms
    64 bytes from 192.168.178.84: icmp_seq=26 ttl=64 time=304.494 ms
    64 bytes from 192.168.178.84: icmp_seq=27 ttl=64 time=236.985 ms
    64 bytes from 192.168.178.84: icmp_seq=28 ttl=64 time=136.128 ms
    64 bytes from 192.168.178.84: icmp_seq=29 ttl=64 time=57.928 ms
    64 bytes from 192.168.178.84: icmp_seq=30 ttl=64 time=277.847 ms
    64 bytes from 192.168.178.84: icmp_seq=31 ttl=64 time=196.694 ms
    64 bytes from 192.168.178.84: icmp_seq=32 ttl=64 time=113.995 ms
    64 bytes from 192.168.178.84: icmp_seq=33 ttl=64 time=31.361 ms
    64 bytes from 192.168.178.84: icmp_seq=34 ttl=64 time=254.193 ms
    64 bytes from 192.168.178.84: icmp_seq=35 ttl=64 time=172.732 ms
    64 bytes from 192.168.178.84: icmp_seq=36 ttl=64 time=89.214 ms
    64 bytes from 192.168.178.84: icmp_seq=37 ttl=64 time=10.524 ms
    64 bytes from 192.168.178.84: icmp_seq=38 ttl=64 time=230.911 ms
    64 bytes from 192.168.178.84: icmp_seq=39 ttl=64 time=149.082 ms
    64 bytes from 192.168.178.84: icmp_seq=40 ttl=64 time=91.599 ms
    64 bytes from 192.168.178.84: icmp_seq=41 ttl=64 time=294.206 ms
    64 bytes from 192.168.178.84: icmp_seq=42 ttl=64 time=211.707 ms
    64 bytes from 192.168.178.84: icmp_seq=43 ttl=64 time=124.845 ms
    64 bytes from 192.168.178.84: icmp_seq=44 ttl=64 time=42.336 ms
    64 bytes from 192.168.178.84: icmp_seq=45 ttl=64 time=280.531 ms
    64 bytes from 192.168.178.84: icmp_seq=46 ttl=64 time=205.299 ms
    64 bytes from 192.168.178.84: icmp_seq=47 ttl=64 time=101.674 ms
    64 bytes from 192.168.178.84: icmp_seq=48 ttl=64 time=21.951 ms
    64 bytes from 192.168.178.84: icmp_seq=49 ttl=64 time=271.351 ms
    64 bytes from 192.168.178.84: icmp_seq=50 ttl=64 time=160.687 ms
    64 bytes from 192.168.178.84: icmp_seq=51 ttl=64 time=81.091 ms
    64 bytes from 192.168.178.84: icmp_seq=52 ttl=64 time=305.971 ms
    64 bytes from 192.168.178.84: icmp_seq=53 ttl=64 time=225.941 ms
    ^C
    --- 192.168.178.84 ping statistics ---
    55 packets transmitted, 52 packets received, 5.5% packet loss
    round-trip min/avg/max/stddev = 10.524/164.900/313.106/91.837 ms


    Mac to iPhone 5S:

    PING 192.168.178.79 (192.168.178.79): 56 data bytes
    64 bytes from 192.168.178.79: icmp_seq=0 ttl=64 time=119.317 ms
    64 bytes from 192.168.178.79: icmp_seq=1 ttl=64 time=35.589 ms
    64 bytes from 192.168.178.79: icmp_seq=2 ttl=64 time=55.363 ms
    64 bytes from 192.168.178.79: icmp_seq=3 ttl=64 time=75.004 ms
    64 bytes from 192.168.178.79: icmp_seq=4 ttl=64 time=100.670 ms
    64 bytes from 192.168.178.79: icmp_seq=5 ttl=64 time=113.758 ms
    64 bytes from 192.168.178.79: icmp_seq=6 ttl=64 time=29.100 ms
    64 bytes from 192.168.178.79: icmp_seq=7 ttl=64 time=54.311 ms
    64 bytes from 192.168.178.79: icmp_seq=8 ttl=64 time=73.509 ms
    64 bytes from 192.168.178.79: icmp_seq=9 ttl=64 time=26.562 ms
    64 bytes from 192.168.178.79: icmp_seq=10 ttl=64 time=70.967 ms
    64 bytes from 192.168.178.79: icmp_seq=11 ttl=64 time=111.639 ms
    64 bytes from 192.168.178.79: icmp_seq=12 ttl=64 time=58.813 ms
    64 bytes from 192.168.178.79: icmp_seq=13 ttl=64 time=70.502 ms
    64 bytes from 192.168.178.79: icmp_seq=14 ttl=64 time=23.987 ms
    64 bytes from 192.168.178.79: icmp_seq=15 ttl=64 time=112.789 ms
    Request timeout for icmp_seq 16
    64 bytes from 192.168.178.79: icmp_seq=17 ttl=64 time=25.599 ms
    64 bytes from 192.168.178.79: icmp_seq=18 ttl=64 time=68.510 ms
    64 bytes from 192.168.178.79: icmp_seq=19 ttl=64 time=3.354 ms
    64 bytes from 192.168.178.79: icmp_seq=20 ttl=64 time=3.064 ms
    64 bytes from 192.168.178.79: icmp_seq=21 ttl=64 time=3.059 ms
    64 bytes from 192.168.178.79: icmp_seq=22 ttl=64 time=2.666 ms
    64 bytes from 192.168.178.79: icmp_seq=23 ttl=64 time=2.722 ms
    64 bytes from 192.168.178.79: icmp_seq=24 ttl=64 time=30.917 ms
    64 bytes from 192.168.178.79: icmp_seq=25 ttl=64 time=63.497 ms
    64 bytes from 192.168.178.79: icmp_seq=26 ttl=64 time=130.586 ms
    64 bytes from 192.168.178.79: icmp_seq=27 ttl=64 time=47.810 ms
    64 bytes from 192.168.178.79: icmp_seq=28 ttl=64 time=43.115 ms
    64 bytes from 192.168.178.79: icmp_seq=29 ttl=64 time=87.096 ms
    64 bytes from 192.168.178.79: icmp_seq=30 ttl=64 time=107.130 ms
    64 bytes from 192.168.178.79: icmp_seq=31 ttl=64 time=131.135 ms
    64 bytes from 192.168.178.79: icmp_seq=32 ttl=64 time=46.968 ms
    64 bytes from 192.168.178.79: icmp_seq=33 ttl=64 time=58.782 ms
    64 bytes from 192.168.178.79: icmp_seq=34 ttl=64 time=3.038 ms
    64 bytes from 192.168.178.79: icmp_seq=35 ttl=64 time=2.475 ms
    64 bytes from 192.168.178.79: icmp_seq=36 ttl=64 time=2.133 ms
    64 bytes from 192.168.178.79: icmp_seq=37 ttl=64 time=18.607 ms
    64 bytes from 192.168.178.79: icmp_seq=38 ttl=64 time=62.991 ms
    64 bytes from 192.168.178.79: icmp_seq=39 ttl=64 time=82.809 ms
    64 bytes from 192.168.178.79: icmp_seq=40 ttl=64 time=105.596 ms
    64 bytes from 192.168.178.79: icmp_seq=41 ttl=64 time=124.982 ms
    64 bytes from 192.168.178.79: icmp_seq=42 ttl=64 time=41.895 ms
    64 bytes from 192.168.178.79: icmp_seq=43 ttl=64 time=62.085 ms
    64 bytes from 192.168.178.79: icmp_seq=44 ttl=64 time=2.607 ms
    64 bytes from 192.168.178.79: icmp_seq=45 ttl=64 time=101.684 ms
    64 bytes from 192.168.178.79: icmp_seq=46 ttl=64 time=99.664 ms
    64 bytes from 192.168.178.79: icmp_seq=47 ttl=64 time=2.915 ms
    64 bytes from 192.168.178.79: icmp_seq=48 ttl=64 time=3.295 ms
    64 bytes from 192.168.178.79: icmp_seq=49 ttl=64 time=77.274 ms
    64 bytes from 192.168.178.79: icmp_seq=50 ttl=64 time=97.923 ms
    64 bytes from 192.168.178.79: icmp_seq=51 ttl=64 time=116.778 ms
    64 bytes from 192.168.178.79: icmp_seq=52 ttl=64 time=34.810 ms
    64 bytes from 192.168.178.79: icmp_seq=53 ttl=64 time=53.947 ms
    64 bytes from 192.168.178.79: icmp_seq=54 ttl=64 time=74.350 ms
    ^C
    --- 192.168.178.79 ping statistics ---
    55 packets transmitted, 54 packets received, 1.8% packet loss
    round-trip min/avg/max/stddev = 2.133/58.514/131.135/40.306 ms

    A bit surprised to see timeouts

  • mruitermruiter Member
    edited February 2016
    could also be a wifi Channel share problem with youre neighbours. Do you also have a loss pinging youre router ?
    On a smartphone i could think it would be a kind of powersave option to shutdown wifi but homey is not battery powered and a dropping wifi connection would cause more trouble then it would safe energy. Better to safe power by turning off the led righ by default .

    To bad we cant open a console on the homey and do a ping from there to the network.
  • Fritzbox 7360
    no led's, no neighbours ;-)


  • Extra info when I download a voice for example I get better/good results will post in minute
  • Turned off Wifi on my Mac, it's now going through ethernet. Still some timeouts on Homey. Speed to my Timeport is excellent. round-trip min/avg/max/stddev = 0.277/0.987/2.461/0.469 ms
    Plenty of neighbours with WiFi though, probably most on 2.4GHz... 
  • ReneBoeijeReneBoeije Member
    edited February 2016

    Looks like a pattern to me... (Ping times in ms on win10 box) Higher peaks seem to happen when ring is flashing, but not 100% sure. (Just watching Homey while pinging.)

    BTW - all of a sudden, 4.5 hours after I updated Homey and installed female voice, while still making comments in a maile voice, it started to comment in the (a?) female voice. Still useless comments - see my gille topic. But happily Home conclude while typing 'something really big inside'. My wife wants to know how she nows.....

  • mruitermruiter Member
    edited February 2016
    Lets not hope its that buggy adhoc power safe mode that was used for some time.
    And should not be used on non battery powered devices at all.
    Could explain the disconnect Homey is saying. My Mesh network will think homey is in trouble some times because of the high pings and ban it from the ap its connected to to force it to connect to the next best ap station in the mesh network available to see if it gets better.

    Only Athom can tell, and will there be some shell access to the homey ? Gues not for copyright reasons ?
    Then there will be no other faith for my second Homey when it comes in to discect it piece by piece  p
  • @mruiter ;
    I have bad news for you on my ASUS router I can see PSM (Power Save Mode) is enabled on homey
    Highlighted one is homey, bottom one is phone

  • @MennoVanDerAat Why is this bad? A problem is pinpointed so it can be fixed. That's a good thing :)
  • Bad bad homey. Green is for you to control, not to beeee. 

  • The big question is, is PSM noticeable on normal usage. PSM also provide less air time, resulting in better performance for other wireless devices. 
  • nklerk said:
    The big question is, is PSM noticeable on normal usage. PSM also provide less air time, resulting in better performance for other wireless devices. 

    In my setting it gets kicked arround on the netwerk because its showing slow response times. Mesh networks use this to try to push a device to a closer / better accesspoint in the vicinity
  • It'd be a good Advanced Setting somewhere - disable PSM on a mesh network, enable it elsewhere. If it doesn't cause any problems I'll happily save a few Wh.
  • Has there been an update on this one? I see the same high pings, but the Homey is connected to a (non-mesh) access-point nearby.
  • Wow, that's a reply to an old thread... There have been numerous firmware-updates since then. What FW-verison are you on? And what do you experience, high ping-times or the systematic going up and down of pings?
  • Homey 1.5.3 & Unifi UAP-AC-PRO:
    Ping wird ausgeführt für homey.iqacorp.ch [10.75.11.203] mit 32 Bytes Daten:
    Antwort von 10.75.11.203: Bytes=32 Zeit=132ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=51ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=49ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=11ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=312ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=18ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=10ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=10ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=1ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=26ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=4ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=5ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=4ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=2ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=2ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=2ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=3ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=12ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=188ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=11ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=67ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=122ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=60ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=555ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=111ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=210ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=518ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=9ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=343ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=207ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=80ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=139ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=129ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=232ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=248ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=733ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=99ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=8ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=87ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=30ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=6ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=10ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=9ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=49ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=7ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=15ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=269ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=6ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=37ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=167ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=41ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=5ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=48ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=8ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=4ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=29ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=42ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=162ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=121ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=20ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=9ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=2ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=9ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=8ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=11ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=77ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=103ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=109ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=26ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=76ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=51ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=8ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=101ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=108ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=16ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=52ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=60ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=54ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=76ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=104ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=120ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=6ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=42ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=110ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=77ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=105ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=110ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=19ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=29ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=46ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=62ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=88ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=111ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=113ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=4ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=43ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=55ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=95ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=101ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=204ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=109ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=42ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=3ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=181ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=76ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=100ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=111ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=10ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=12ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=24ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=51ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=61ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=528ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=94ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=19ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=128ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=48ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=78ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=80ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=119ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=22ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=37ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=59ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=78ms TTL=63
    Zeitüberschreitung der Anforderung.
    Antwort von 10.75.11.203: Bytes=32 Zeit=120ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=5ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=61ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=58ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=72ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=8ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=99ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=117ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=21ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=50ms TTL=63
    Antwort von 10.75.11.203: Bytes=32 Zeit=50ms TTL=63
    
    Sometimes Homey reports back to Unifi as "Power Save Enabled"

  • @bvdbos, I know, but it still seems a problem. Running latest stable version 1.5.3. Would love to see the ethernet option working, but I think that will never happen... Results from ping are really bad:

    Pinging homey.---------.net [1.2.3.4] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 1.2.3.4: bytes=32 time=1046ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=7ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=91ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=511ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=118ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=10ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=6ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=313ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=5ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=217ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=7ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=9ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=7ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=308ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=101ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=4ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=5ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=191ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=31ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=24ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=33ms TTL=64
    Reply from 1.2.3.4: bytes=32 time=4ms TTL=64
  • Your environment has been set up for using Node.js 4.4.5 (x64) and npm.

    C:\Users\****>ping 192.168.8.15

    Pinging 192.168.8.15 with 32 bytes of data:
    Reply from 192.168.8.15: bytes=32 time=2ms TTL=64
    Reply from 192.168.8.15: bytes=32 time=2ms TTL=64
    Reply from 192.168.8.15: bytes=32 time=2ms TTL=64
    Reply from 192.168.8.15: bytes=32 time=4ms TTL=64

    Ping statistics for 192.168.8.15:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 2ms, Maximum = 4ms, Average = 2ms


    Same here
  • casedacaseda Member
    edited December 2017
    Just an short notice for people trying to ping homey.

    Linux, the core used by homey, can respond very slow to ping commands it is has the lowest of lowest priorities internally, and should not be looked for as of "speed of homey", as it is totally unrelated and can happen from time to time, especially if your homey is busy with the other things.
    If it is a constant high ping then it might be something, but not the ping values shown now like the ones from @abeggled or @Caros
Sign In or Register to comment.