#Device Init failed - Communication with device timed out

1 messages · Page 1 of 1 (latest)

tight berry
#

Getting Device Init failed - Communication with device timed out when connecting to wootility and unable to save any settings to it - tried multiple resets to no avail.

#

Keeps cycling between - found for 1-2 seconds and then drops again.

#

[2023-05-20 18:30:10.464] [debug] Firmware Update info result: {
latestFirmwareVersion: '2.6.19',
updateRequired: false,
title: 'Fix bug critical scanning bug',
description: '- Fix issue which would cause scanning to take a long time to start when it tries to start quickly. <b>Boards affected: Flaretech, 60HE AVR in Tachyon mode</b>'
}
[2023-05-20 18:30:14.376] [error] Device communication error, closing device Error: Communication with device timed out
at file:///C:/Users/Oskars/AppData/Local/Programs/wootility-lekker/resources/app.asar/public/js/app-bundle.js:2:767814
[2023-05-20 18:30:14.376] [info] Device disconnected 5 id: 524142521023
[2023-05-20 18:30:14.381] [debug] Waiting for task to finish...
[2023-05-20 18:30:14.381] [error] Error with sendCommandWithResponse with command 41 GetGamepadProfile Error: Communication with device timed out
at file:///C:/Users/Oskars/AppData/Local/Programs/wootility-lekker/resources/app.asar/public/js/app-bundle.js:2:767814
[2023-05-20 18:30:14.387] [error] Failed initProfiles on device Error: Communication with device timed out
at file:///C:/Users/Oskars/AppData/Local/Programs/wootility-lekker/resources/app.asar/public/js/app-bundle.js:2:767814
[2023-05-20 18:30:15.362] [debug] Attempting to resume service

frozen night
#

Do you use any software to control the RGB of devices? If so please name them.

tight berry
#

Asus Aura Sync

#

from asus ARMOURY

frozen night
#

Please turn that off and check if then the Wootility works.

#

Please provide all error logs of the desktop Wootility. You can find these at the end of the troubleshooting section in the settings menu of the desktop Wootility.

tight berry
#

tried, no bueno 😦

frozen night
#

If you want you can try a dev firmware which has an improvement for a rare case. For that please use this link: https://beta--wootility.netlify.app/?test-builds=true
Then open the settings menu, go to the updates section, click on "Get test firmware" and select the "2.6.19-test.comm-stability.0 - Improvements to Wootility communication" firmware and then click on "Install firmware".

If you test this please report back how it went for you. I would guess the chance is low that this actually helps you but maybe I'm wrong. So it's worth to try it.

#

In order to install this you may need to use another PC.

#

I'm currently investigating into this issue. It seems to be that different things can cause it. So there are likely multiple issues.
We are testing another cause currently which can lead to this and this seems to be limited to some systems. It will likely take a while until this can be addressed in a future firmware update.

tight berry
#

Thing that I currently noticed which could be false positive is - i turned off lian li - Lconnect and it seems to work for now

#

but might be a temp thing, ill try to validate, meanwhile ill try the test software :p

frozen night
#

Sadly the mentioned dev firmware above seems to be unaffected for this one.

tight berry
#

I dont mind turning it off, as its set to sync with aura sync, if thats a fix temporary ,its ok