You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Had people hit some issues with the Solace Pro not showing capabilities correctly when connecting in v2.6.4 after using <= v2.6.3. This isn't real surprising since we don't handle capabilities updates correctly for devices that already have user configs since v2.6.1 (a config v3 issue).
Fix from Discord:
For everyone that had a Lovense Solace Pro they had already hooked up to Intiface Central that is now not seeing Linear capabilities in v2.6.4, there is a bug that requires a workaround:
Stop the server.
Go to the devices tab.
Hit "Forget Device" under the solace pro in the device list.
Close and reopen intiface (THIS STEP IS EXTREMELY IMPORTANT)
Make sure the Solace Pro is not in the disconnected devices list on the Devices Tab
Start the server again
Scan for devices on the devices tab.
For this bug specifically, we shouldn't require a process shutdown in the middle of these steps. Something, most likely behind the Rust FFI barrier, is holding the device in memory even after we call Forget up front.
The text was updated successfully, but these errors were encountered:
Had people hit some issues with the Solace Pro not showing capabilities correctly when connecting in v2.6.4 after using <= v2.6.3. This isn't real surprising since we don't handle capabilities updates correctly for devices that already have user configs since v2.6.1 (a config v3 issue).
Fix from Discord:
For everyone that had a Lovense Solace Pro they had already hooked up to Intiface Central that is now not seeing Linear capabilities in v2.6.4, there is a bug that requires a workaround:
For this bug specifically, we shouldn't require a process shutdown in the middle of these steps. Something, most likely behind the Rust FFI barrier, is holding the device in memory even after we call Forget up front.
The text was updated successfully, but these errors were encountered: