So I am using Intiface Central to connect for haptics on a website. When connecting my plug to intiface central it will connect properly and the website reads it. After about a minute or less I get an error on the website and Intiface Central saying the device disconnected. The device has plenty of battery and the bluetooth isn’t messed up cause it connects to my phone just fine. I’ve had this same issue with the same website and software on a laptop as well as my PC. Not sure if it’s the device or a setting I dont have set right. Any help is appreciated.
Which website? Are you using Intiface, or is this connection directly from the website to the device with WebBluetooth?
1 Like
The website is shibbydex.com and the connection is device>intiface>website as well as connecting via Bluetooth USB adapter. The website has audios that sync with haptic scripts. The scripts work and everything goes fine for a few minutes and then it disconnects again.
Ok, so lets take shibby out of the equation: with just your device connected to Intiface, using the sliders in the device tab, does the Satisfyer disconnect?
Also, which platform are you running Intiface on? Windows, Mac, Linux, Android, iOS?
1 Like
After some more testing things are working normally? I think. Will update if problem persists.
To answer your question. Testing things on the device within Intiface Central on Windows and then connecting to the website might have fixed the issue but not confirmed yet. Thank you.
After further testing device is disconnecting when in use despite the device working fine when not in use.
Well I didn’t really expect the client to affect an internal keep alive. I need you to answer the questions in my last post to move forward.
No the satisfyer does not disconnect if not connected to the website. I am running on Windows 10.
I wonder if shibby is sending too many commands… it’s about the only thing I can think that would cause this.
Have you tried the Intiface 3 beta?
have not. i can look into it and try it out and give you an update
i updated and got my hands on the beta. Same problem continues.