-
Notifications
You must be signed in to change notification settings - Fork 6
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
Support New Realtime Protocol #5
Comments
I you provide some examples I can test, I have both the old 105 RGB, new 150 and 250 RGB as well as new 250 AWW. As noted in #1 it would be useful to test with non 3-byte LEDs as well, but I don't have any (yet). |
I have 175 RGB. I tested both formats and I can confirm, that the old format (send_frame) works for me but the new format (send_frame_2) does not. {
"product_name": "Twinkly",
"product_version": "16",
"hardware_version": "9",
"flash_size": 16,
"led_type": 6,
"led_version": "1",
"product_code": "TW175SEUP09",
"max_supported_led": 255,
"base_leds_number": 175,
"number_of_led": 175,
"led_profile": "RGB",
"frame_rate": 25,
"movie_capacity": 719,
"copyright": "LEDWORKS 2017",
"fw_version": "2.3.5"
} |
Is it the only the older generations (2017 IIRC) that doesn't grok the v2 format? My 105 RGB has |
Here are my stats, where the _2 protocol is the only one that works. Firmware is 2.5.9
@jschlyter, it was not clear from your comments. Which versions work across your various devices? |
As mentioned here, it looks like the realtime protocol has either changed in a recent firmware update, or is different for devices that have > 255 lights. As I only have a 750 light Gen 2 device, I cannot confirm which.
However, I have confirmed that the protocol changes that I observed are correct for my device, and I am able to control it with the new format.
I can share the code, but it would be good if someone with an older (or smaller) device would be able to confirm if the original realtime protocol still works. This would inform whether it is best to update the current 'send_frame' or create a second variant.
The text was updated successfully, but these errors were encountered: