-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve amount of decoded frames #51
Comments
Could you enable the |
Sure thing, I hope this is what you where after: debug.txt I put it in a file to not bloat the Issue. |
This doesn't look good. This isn't valid display link traffic. |
Give me a sec, I just noticed that it doesn't report data correctly since uploading the debug firmware.elf |
I really don't know what broke, I'm now only receiving invalid headers for whatever reason. |
Just reboot the ESP a few times. Does it fix it (temporary)? |
Nope, already tried that a few times. |
This log messages does explain the issue probably:
It looks like the firmware of your device has a pretty bad behavior. This is happening:
This issue can be resolved by increasing the
Please start with |
Thanks, I've now set
Appreciate the time and response! |
Could you do me a favor and very your device is already listed as supported device here? https://github.com/syssi/esphome-votronic/blob/main/votronic_display_link.md#supported-devices I would like to extend the list if possible. |
@syssi yes it is, it‘s model number is SR1610 as mentioned in the first post (at the very bottom). |
Hi, just a quick question, I get eight invalid headers every time, is this something that can be maybe fixed or is this something that I can just safely ignore?
I mean it also complains about taking too long but I assume that's how it is.
Here is a snippet from my log:
I'm using the Votronic SR 140 Duo (should be model: SR1610) via the Display Link interface.
Keep up the good work!
Cheers,
Christoph
The text was updated successfully, but these errors were encountered: