The Handy Device Timeout

danielbaker17 · April 21, 2024, 5:55am

For the last two days my device has been struggling to connect to Wi-Fi
It takes much longer to attempt a connection (up to a minute), and when it does connect to Wi-Fi all subsequent requests result in a device timeout
After a successful connection, the pink light intermittently pulses (approximately every 2 minutes)
Prior to this, I’ve been using my device for a year without any connectivity issues
It is on firmware “Handy FW 3.2.3”
The device still works on Bluetooth

The timeout error is occurring on multiple players:

FapTap.net
ScriptPlayer
HereSphere
Handyverse
HandyControl

Things I’ve attempted to do:

Reset the access key on Handyverse, connecting to Handyverse but the subsequent script test fails
Split my 2.4Ghz and 5Ghz SSID, restart my router, and assign a static IP address to the Handy’s MAC address
Installed HandyControl to run a local script server, which the device connects to but always times out when uploading a script

Any help would be appreciated - I suspect my device is now faulty.

Liquid · April 21, 2024, 6:08am

Some times (rarely) the handy servers have problems that cause this kind of behaviour - it really doesn’t happen often, but when it does it can be easily checked by pinging their server repeatedly, e.g.:

ping handyfeeling.com /t
(can be cancelled with ctrl+c)

If you see lost packages after ~10 attempts (or fewer of course), the problem isn’t on your side and there is nothing you can do about it. Coincidentally I had this exact issue on Friday, after not having any issues for months. Worked fine yesterday.

Regarding the “local script server” - I’m not sure if that works anymore, at least for me that stopped working after FW v3, I’ve been using the handyfeeling.com servers ever since.

danielbaker17 · April 21, 2024, 6:27am

Thanks Liquid.

My ping results are below. Looks stable enough to me - what are your thoughts?

The Handycontrol seems to still be getting use from some users - I downloaded it out of desperation as I was out of ideas.

Pinging handyfeeling.com [161.35.247.27] with 32 bytes of data:
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Reply from 161.35.247.27: bytes=32 time=261ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Reply from 161.35.247.27: bytes=32 time=264ms TTL=50
Reply from 161.35.247.27: bytes=32 time=261ms TTL=50
Reply from 161.35.247.27: bytes=32 time=261ms TTL=50
Reply from 161.35.247.27: bytes=32 time=290ms TTL=50
Reply from 161.35.247.27: bytes=32 time=277ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=261ms TTL=50
Request timed out.
Request timed out.
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=264ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=274ms TTL=50
Reply from 161.35.247.27: bytes=32 time=264ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=271ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=264ms TTL=50
Reply from 161.35.247.27: bytes=32 time=298ms TTL=50
Reply from 161.35.247.27: bytes=32 time=277ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Request timed out.
Request timed out.
Reply from 161.35.247.27: bytes=32 time=275ms TTL=50
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Request timed out.
Request timed out.
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=267ms TTL=50
Reply from 161.35.247.27: bytes=32 time=264ms TTL=50
Reply from 161.35.247.27: bytes=32 time=262ms TTL=50
Reply from 161.35.247.27: bytes=32 time=264ms TTL=50
Request timed out.
Request timed out.
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Request timed out.
Reply from 161.35.247.27: bytes=32 time=264ms TTL=50
Reply from 161.35.247.27: bytes=32 time=263ms TTL=50
Reply from 161.35.247.27: bytes=32 time=264ms TTL=50
Reply from 161.35.247.27: bytes=32 time=264ms TTL=50
Reply from 161.35.247.27: bytes=32 time=293ms TTL=50

loldorf · April 21, 2024, 6:29am

I had the exact same issue over the last couple of days. It seems to work fine now, but I still get an error when uploading larger scripts (around 500kb), even though they worked fine before.

Liquid · April 21, 2024, 6:42am

Request timed out.

That’s exactly what I meant - when that happens you have the issue I described. Also the latency is rather high. My (currently very stable) results look like this:

Reply from 161.35.247.27: bytes=32 time=36ms TTL=52
Reply from 161.35.247.27: bytes=32 time=33ms TTL=52
Reply from 161.35.247.27: bytes=32 time=30ms TTL=52
Reply from 161.35.247.27: bytes=32 time=31ms TTL=52
Reply from 161.35.247.27: bytes=32 time=30ms TTL=52
Reply from 161.35.247.27: bytes=32 time=31ms TTL=52
Reply from 161.35.247.27: bytes=32 time=30ms TTL=52
Reply from 161.35.247.27: bytes=32 time=29ms TTL=52
Reply from 161.35.247.27: bytes=32 time=29ms TTL=52
Reply from 161.35.247.27: bytes=32 time=29ms TTL=52
Reply from 161.35.247.27: bytes=32 time=29ms TTL=52
Reply from 161.35.247.27: bytes=32 time=29ms TTL=52
Reply from 161.35.247.27: bytes=32 time=31ms TTL=52

~30 ms response time and no time outs

There seem to be several other users on the user-support channel on the handy discord that have the same issue at the moment - might be a good spot to stay up-to-date with that.

Piro · April 21, 2024, 7:22am

ahh, this explains the the same issue i am having too
I thought i was going crazy.
Makes sense. Guess will have to wait it out

Pinging handyfeeling.com [161.35.247.27] with 32 bytes of data:
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Request timed out.
Request timed out.
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Reply from 161.35.247.27: bytes=32 time=339ms TTL=46
Request timed out.
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Request timed out.
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Request timed out.
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46
Reply from 161.35.247.27: bytes=32 time=338ms TTL=46

loldorf · April 21, 2024, 5:05pm

Well, it seems like servers are down now. Just great.

handy_lars · April 22, 2024, 8:33am

Hi

We had no downtime yesterday, but there is an ongoing subsea fiber fault between Europe and Asia that is probably the reason why you can’t connect to our servers from this region at the moment. The issue started yesterday and is still ongoing.

If you are experiencing connection issues and can somewhat reliably trigger the issue on demand, we can do a live debug session with you to try to get to the bottom of it.

Contact support on discord and we can setup a date.

system · July 21, 2024, 8:33am

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.