# Controlling looks across a sync group of 25 Pixelblazes

**URL:** <https://forum.electromage.com/t/controlling-looks-across-a-sync-group-of-25-pixelblazes/4782>\
**Category:** Patterns and Code\
**Created:** [October 19, 2026, 9:48pm UTC](https://forum.electromage.com/t/controlling-looks-across-a-sync-group-of-25-pixelblazes/4782 "2026-10-19T21:48:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![istnv](https://forum.electromage.com/letter_avatar_proxy/v4/letter/i/3da27b/32.png) [@istnv](https://forum.electromage.com/u/istnv)\
**Post date:** [October 19, 2026, 9:48pm UTC](https://forum.electromage.com/t/controlling-looks-across-a-sync-group-of-25-pixelblazes/4782/1 "2026-10-19T21:48:48Z")

</div>

Any update on this?  
I have an exhibition coming up where I need to control 25 separate PB units simultaneously.  
There will be over 100 different looks overall, with each units pattern selected by `nodeId()`  
Nothing I have tried via webhooks to change looks work on the followers.  
I would really like to avoid 25 extra connections to change a look across all units.

Thanks.

> [@Significant feature release: Sync multiple Pixelblazes](https://forum.electromage.com/t/significant-feature-release-sync-multiple-pixelblazes/2891/41):
>
> Controls are replicated, but exported vars are not. It’s kind of like poking into the memory of the script and each node has its own memory.
> 
> You could send the vars to each node.
> 
> At some point I will add a way to replicate any data around that you want.

---

<div class="post-metadata">

**Author:** ![wizard](https://forum.electromage.com/user_avatar/forum.electromage.com/wizard/32/4_2.png) [@wizard](https://forum.electromage.com/u/wizard)\
**Post date:** [October 20, 2026, 1:26am UTC](https://forum.electromage.com/t/controlling-looks-across-a-sync-group-of-25-pixelblazes/4782/2 "2026-10-20T01:26:55Z")

</div>

Hi @istnv ,  
There isn’t synchronized vars, but all controls are synchronized, and provide a way to control the look of the entire sync group. You can use sliders to control 0-1 values, toggles for 0 or 1 on/off type settings, and inputNumber controls for arbitrary numbers.

Controls are synced to followers immediately, as fast as possible. All controls are synced to all followers, but you could dedicate specific controls to specific followers using `nodeId()` checks if that is what you want to do.

If you tell me a bit more about what you want to do in your exhibition, I could help with some more specific examples.

---

<div class="post-metadata">

**Author:** ![istnv](https://forum.electromage.com/letter_avatar_proxy/v4/letter/i/3da27b/32.png) [@istnv](https://forum.electromage.com/u/istnv)\
**Post date:** [October 20, 2026, 4:35am UTC](https://forum.electromage.com/t/controlling-looks-across-a-sync-group-of-25-pixelblazes/4782/3 "2026-10-20T04:35:57Z")

</div>

I can’t share too many details, yet, as the event is still in development, but it does need to be completely automated (no operator).

I’ve tried with an `inputNumberGoCue(val)`control, ~~but it does not sync the followers when set via the webhook~~.

💡 OK. Setting it to `1` every time, the followers only ran the pattern once.  
Now I remember mention of values push only if changed.

We will probably end up with a ‘super’ pattern/program that contains the entire event.  
Each unit will show the ‘current’ pattern that corresponds with it’s `nodeId()`.

Hopefully we do not end up exceeding any pattern limits.