Hello all.
I started getting a random error message out of nowhere today, “Failed to upload script to handyfeeling.com”
I’m using the Handy 2 Pro. Also, why would the script need to be uploaded somewhere else?
If anyone knows how to fix this or whats going on, please, let me know.
I got it working by using Bluetooth Legacy Mode.
That’s how they made the handy work on wifi. The servers are required for it to work and they have been up and down today.
The only way to use it totally offline is with bluetooth, which sucks.
Yeah, that sucks, but what sucks even more is getting the damn thing to charge.
ScriptPlayer has a setting under the Handy tab to use a local server instead of handyfeeling.
Could be helpful to remember next time their servers are having issues.
Oh, also, you need USB-PD for the Handy 2.
They sell one on the site:
https://www.thehandy.com/store/the-fast-charger-3/
The charger I use worked fine at first but recently The Handy 2 Pro decided not to take the charge.
But thank you, I’ll check it out.
Was about to create a new topic, but will ask here instead. I just received Handy 2 Pro and it doesn’t work with local mode in ScriptPlayer. Handy 1 works no issues, but when I connect Handy 2 Pro and change the Handy key, it says “script loaded” but nothing happens. If I tell it to use servers and reload the script, it functions no issues.
I updated the ScriptPlayer app to 1.2.3 and it completely got rid of the local mode options under the Handy tab.
Has anyone been able to make Handy 2 work in local mode or is that just not possible?
Oh, that might be a limitation of FW4 actually. I don’t have personal experience with the Handy 2, but I know that there is a custom community made firmware created to future proof these devices.
So it is possible, but maybe not on FW 4. Maaaybe on FW 3 and definitely on custom FW (but that voids warranty and might be unsafe).
Thank you for the reply, Rose. I guess I’ll wait and see what happens in the next 6 months.
There’s talk of Ohdoki releasing server code for self-hosting, which would be ideal. I haven’t been able to find anything about custom firmware and don’t want to brick a new device messing with it just yet, so that option is out.