Skip to content
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

Grouping - Slave_id and Master_id are not seen in the summary #36

Open
MarkAlanJones opened this issue Dec 26, 2022 · 2 comments
Open

Comments

@MarkAlanJones
Copy link

"group": { "mode": "master", "uid": "05EA11E8-64E4-4D28-A0A7-0679CA5DA684", "compat_mode": 0

    There is now a Uid --- is this the name of the group ? 
    
    How is a Group Created ? (is there a RestAPI ? )  
@MarkAlanJones
Copy link
Author

I see in the movie sync information that this uid is the master_id

{"frame_delay":66,"leds_number":190,"loop_type":0,"frames_number":60,"sync":{"mode":"master","master_id":"05EA11E8-64E4-4D28-A0A7-0679CA5DA684","compat_mode":0},"code":1000}

the slave has the same slave_id in it's movie sync information

so there is only one "group id" and it is known to the master and the slave.
so i guess when the master sends a udp packet, the slave only reacts if the uuid matches

@JLOrwell
Copy link
Contributor

JLOrwell commented Apr 3, 2023

the key doesn't have to be a uuid. Twinkly is simply saving a uuid in a text field.
That's a change twinkly made in a recent app version. It's actually annoying as heck as there's no longer a way to get the group name unlesss you scrape their web api.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants