I don’t get any errors in the logs. Satisfyer brand using UB400 dongle. Reset pairings multiple times. Everything works fine for the first couple seconds after starting server, but after a varied amount of time, it stops receiving signal(?) It’s still connected but will not do anything even when held up to the dongle.
Odd. I will say I think there might have been a change in Windows that’s made the CSR4 chipset far less reliable than it used to be.
Can you confirm if Intiface running on your phone has the same issue?
1 Like
I’m on Win10. No issue on iOS intiface.
Edit: spoke too soon as soon as I posted it, it stopped too. Instead, it is after 5ish minutes rather than a couple of seconds
So this could be the keepalives not working or working too much… you’re running IC3.0.1? Is there a client connected?
1 Like
3.0.1+37 & 3.0.2+38 respectively. Happens both with and without a client.
If I might chime in here, I’ve been having the same issue regardless of dongle or device with only the official Satisfyer app working.
I took some logs, the official app repeats commands every 0.05s, Intiface only every 3s
1 Like
I have the same problem. Did you figure out how to solve this problem? (I have an ASUS USB-BT540 dongle, Satisfyer)
Chiming in here as I also have the same problem.
Windows 11, TP-Link UB5A dongle (although the same thing was happening with built in bluetooth) I would connect my Satisfyer device to windows, it would connect in Intiface, work for a random amount of time (I counted 30 seconds on one of the attempts) then stop working completely, even with no errors in logs and device still saying it is connected. If I stopped the Intiface engine the Satisfyer device would “disconnect” from windows and Intiface then go into pairing mode. Turning the Intiface engine on again and scanning to reconnect the device would make it work again for a short time before it would just stop working again.
Same issue here on Linux (Intel onboard, 3.0.3) and Android (3.0.4). Happens with and without connected client.
I tried older IC2.6.5 and it worked fine with my satisfyer, although with some major lag. I hope this can be fixed for the newer versions, because i just bought mine.
I can confirm that my Satisfyer is working after downgrading to IC 2.6.8!
Ok, there’s a good chance I broke something in Satisfyer toys on the Central v3 release. Filed Satisfyer toys missing proper repeat keepalive packets after v10 launch · Issue #902 · buttplugio/buttplug · GitHub, will see if we can isolate it.
I’m not sure whether the issue I’m seeing is related to the issue discussed here. Could someone please confirm or rule out whether the behavior below could be explained by the keep-alive issue described in this thread?
Device: Satisfyer Pro 2 Gen 3
The device connects successfully and initially works. However, it disconnects within less than a minute. Intiface does not appear to notice this: it continues to display the device as connected (including showing the graph) and reports vibration as if the device is still active. In reality, the device stops vibrating.
I can tell the device has stopped working by the LED on the Satisfyer: when Intiface has “lost” communication, the LED turns on. As soon as this happens, I know the device will no longer work with Intiface. At that point, the only workaround is to stop the server, start it again, and rescan for the device. After rescanning, the LED turns off for a random, but brief period, indicating that the device is functioning again.
My questions:
- Is the behavior I described consistent with the keep-alive bug?
- Why doesn’t Intiface detect the disconnect? Logging is set to “All,” but I don’t see any message indicating that the device has disconnected. Intiface continues to behave as though the device is still connected, even though the device itself indicates it is “waiting for connection.”
This is a known issue that should be fixed in the next patch.
1 Like