search

CordeliaMist / GagSpeak-Client

Gag Speak Plugin for Dalamud
GNU General Public License v3.0
24 stars 6 forks source link

Toybox error, "Invalid Toybox message parse" #17

Closed hauveli closed 9 months ago

hauveli commented 9 months ago

My toy consistently disconnects in Toybox, where it doesn't with other intiface-compatible applications or plugins.

~~My first guess without looking into it further is that Toybox is sending malformed data to my toy and the toy is restarting after crashing. I will inspect the serial output and update this issue once I have done so.~~

It was as I suspected, but this is an issue with intiface/bluetooth and not with Toybox.

It is possible that this error is related to the error below, which I could not find more log information for.

An error was also encountered: [Result Logic] Invalid Toybox message parse, If you see this report it to cordy ASAP.

hauveli commented 9 months ago

Preface: My setup has each motor configured through intiface to send data as Vibrate#:xxx;, where # is a single digit, and xxx is an integer of any length. (This can be done through intiface configuration.)

Looking at my devices serial output, it seems that Toybox at some point sends a message Vibrate:0, when the only options it should have are Vibrate#:0, where # is an integer between 1 and 4.

Adding code to skip faulty Bluetooth messages fixes the issue, so I will leave this information here for anyone who may have similar issues.

So the remaining problem is the [Result logic] warning, is there a log file I can find to post more information about it?

CordeliaMist commented 9 months ago

not even sure why the result logic is happening, it honestly just seems like it is a problem with you using your own intiface connection instead of the uri provided by the intiface repository.

I dont have one to test that on nor do I want to look into it with these kind of rare one off situations for the few people who are not using it.

If you want to look into it and find a fix yourself feel free to let me know, but it is not something i want to put time into addressing right now

hauveli commented 9 months ago

not even sure why the result logic is happening, it honestly just seems like it is a problem with you using your own intiface connection instead of the uri provided by the intiface repository.

I dont have one to test that on nor do I want to look into it with these kind of rare one off situations for the few people who are not using it.

If you want to look into it and find a fix yourself feel free to let me know, but it is not something i want to put time into addressing right now

The error didn't affect Toybox, but I reported it since it told me to. If it happens again I will look into it and re-open it if it causes any issues. My only guess is it happened because the device crashed in the middle of some function call in toybox. I will close this issue now, thank you for your time responding.