You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
"group": { "mode": "master", "uid": "05EA11E8-64E4-4D28-A0A7-0679CA5DA684", "compat_mode": 0
The text was updated successfully, but these errors were encountered: